How to Enable Code Snippets

Add .appclw and .APPCLW (no “*” in front of it) to the list in the Code Snippets setup. This tells the IDE to show snippets in the code completion list for the embed editor and the embeditor.

In my IDE I have this set of extensions for Clarion snippets:

How to Enable Code Snippets

Using Code Snippets

The following is a short video showing one of the new wizards I have been working on this last week.

The program is written in Clarion, the skinning is using the Noyantis Clarion wrapper around the Codejock skin framework, the wizard design is “inspired” by this article – Silverlight Metro Style Wizard (ok, it is practially a duplicate but I was curious to see how close I could get with Clarion!) and the icons are created with the Metro Studio by Syncfusion.

If you have been following on the skype cw-talk chat or on twitter you may have seen a few in progress screenshots 🙂

 

-brahn

That poor tired old “TealGray Retro Theme” I hacked around to work the way I wanted was well over due for replacement. In line with my current focus on UI clean-ups for work related projects I found this great Metro.Press theme – “Metro.press is a responsive premium WordPress Theme inspired by metro design” which seems to fit very nicely. It’s amazing how hard it is to find a nice simple theme that isn’t designed around massive amounts of graphics. Anyway, this should also work very nicely from a mobile or tablet.

Enjoy!

-brahn

If you are getting a lot of \bin\*.xlog files you might want to try the following.

Note: If you are curious you can use my free IdeDebug addin to view the contents of the xlog files before you delete them. For my own personal curiosity, let me know if you are seeing anything other than what is mentioned here.

 

The most common one is this:

SoftVelocity.TextTransform has not been loaded because it requires
SoftVelocity.GeneratorX.

To stop it, delete or rename this file:

This is taken directly from a newsgroup posting on softvelocity.public.clarion6. I hope Robert doesn’t mind me reproducing this here, I think it is a very helpful explanation that should be useful to folks running into SEGDEF problems with Clarion…

Re: Any increase on DCT & Window limits?
On 22/01/2004 12:20:26 AM, robert.zaunere wrote:

There are many theories floating about with regard to this "limit",
unfortunately none of them are accurate.  There is a Zero correlation to any
16bit issue in C6 with this topic of SEGDEFs, as 16bit is not even supported
for compilations, and the segment limit has not changed from C5x.

As explanation as to what does happen, the linker must collect information
about object and resource files to be linked into the target. The limit for
number of segments per object file is ~16k. 

The compiler produces segments for things like:

– Every Procedure or ROUTINE is a separate segment;
– Every static variable or constant string is a separate segment;
– Every FILE structure produces 5 segments, plus if the FILE declaration has
NAME, OWNER or driver string, one segment
  per every for one of these strings, plus one possible segment if FILE is
threaded, every KEY, every Memo, every VIEW, every QUEUE, etc. etc.

So in general, the current linker limit means that a single source file can
have _thousands of declared (and used in the program) variables. The most
probable ways to get the "too many SEGDEF…" error are:

1- to include too many INCLUDEs that declare variables; solution is
  to include files on the module level rather than globally everywhere
  where it is possible
2- to declare too many FILEs with large number of KEYs and/or MEMOs in
  one source file (the main source file, as a rule);

#1 is your control. As for #2 its also in your control, but we’ll be providing
template support in C6.1 that will allow you to easily split the file structs
generated from extremely large DCTs (those with with many hundreds of files
defined in them) into > 1 source modules.  That means that when such DCTs
produce an excess of  the ~16000 segment limit you can get past it.  However,
there are other alternatives you can take right now, like reducing the # of
files declared in a single DCT to something more in line with what Files are
really being used in the APP, or to declare files on the member module level if
this is possible (i.e. the FILE is only used in particular procedure ).  But
the template solution will be forthcoming.

Regards,

Robert Zaunere
SoftVelocity Inc.

-brahn