This topic is continuation of this one..

So after some cleaning up (which in this case means few hours of work beside repairing broken code ) I can put on the table what I have.
The main file is VIpreVIEW.vi. You have to open it, fill all paths, sizes, etc. and run (not very professional, isn't it?). After some work (depending on VI complexity) it will create a lot of files at target path. Most of them are temporary files, but I do not delete them yet for debug purposes. Open {name}.html file in a browser and watch the result. I included SWFtools binary in this package (it's GPL) but I don't know how it is with all that legal stuff.

Know issues:

• it is sloooow
• sometimes it is even slooooower
• additional 1px black line appears at each case (it is not an issue in alternative flash players as Gnash)
• tips appear even for objects in hidden cases (still don't know how to solve this)
• tips appear for each object (even not necessary, like comments) and often display sth stupid - this is for debug
• FlatSequences cause errors - I always didn't like them
• did I mention it is slow?
• many others

Any comments are welcome, particularly if someone has an idea how to speed it up a little. I already tried to convert it to non-recursive version. Although I had some problems, it seems that recursion is not the reason. I think now that a bottleneck is speed of switching cases externally. If it is true, the stack version of algorithm should work even slower.
And of course GUI in final version will not look like this.

This post has been edited by vugie: Feb 26 2008, 12:58 PM

Hi Vugie,

I miss some VIs.
log.vi
lv2gbl-log.vi

Ton

I can't upload them now, but they are not necessary - simply delete all instances

______________
Edit: I updated the file with lost VIs

This post has been edited by vugie: Feb 26 2008, 08:43 AM

OK, I had a chance to play with a bit and it looks really nice. It works fast enough for small VIs, which I suspect is most of what will be thrown at it if it's used for sharing code online.

Would you be interested in adding it as another option inside the CCT? That would provide the tool with the options of either capturing an image or a flash demo.

The only thing that needs to be checked out is how to embed it. I've seen that the only thing you need is the swf file, but we need an easy way of copying and pasting both the file path and the embed tag code.

It is interesting proposition but there are two issues. At first, my employer is a sponsor of time spent for this project and therefore credit and link should be included in both GUI and SWF (however it has not to be anything covering half of the window). Second one in the license - definitely binary of script compiler should be included in distribution (it's GPL), so whole the project should be GPL and contain also source code of compiler (but I'm not sure about it). So keeping CCT BSD licence will be rather impossible. But I may be wrong, I'm not too familiar with license issues.

What concerns embedding, beside swf also its dimesions should be known, because browser pointed directly to sfw file stretches it to window size. BBCode contains tag to embed flash ... checking whether it works here...

... works, but forces to reduce flash size to pretty small values...
Here is an example how it should look like

This post has been edited by Michael_Aivaliotis: Mar 11 2008, 09:55 AM

In the GUI, we have acknowledgements in the about screen and it can go in there. I don't want to start filling the main screen with logos and links.

In the flash movie, I don't think a link or an additional icon would be a problem.

As for the license, I don't have a problem with distributing the original with the CCT, but I want to avoid making it GPL. If we have a basic agreement, I think we can look more deeply into this to understand how it works. Maybe someone familiar with licenses can shed some light. Jim, maybe?



I tested it in the NI forums, but the forums there do not allow attaching swf files. We can ask the moderator to change that. Pointing it to an external file works fine and you only need the embed tag there. If our tool is doing the capturing, it can also prepare the tag text and set the sizes to be right.

I've extended the flash size limit on the forums to 550x550. Now the above flash looks nicer. So to embedd flash just use the bbcode tag.

If you integrate something covered by the GPL into a project it usually makes the whole project being covered by the GPL. Specific provisions such as an amendment to the GPL for the Linux kernel being excluded.

To be able to integrate libraries or subcomponents that are desired to be GPL like licensed without making the rest of a program being GPL too there has been specifically the LGPL license created for. This allows including LGPL licensed components in a dynamic way into another application which can be of any other license including fully closed source.

Purists claim that even calling a GPL based application over the command line explicitedly from inside another application is forcing this application to be GPL too, but I think that is a completely useless restriction and most likely not enforceable at all.

Rolf Kalbermatter