69 replies to this topic

[jgcode]

Changelist:
2.6-1 2010 06 28
- Fixed (): Classes as Sub-Libraries caused error as Namespace was incorrect

Damn! forgot about Neil's post, have done that now - for next release

[Daklu]

Hmm... the theme creator needs the icon editor api package v2.0, but apparently I'm too stupid to find it. Can I have a hint?

[jgcode]

Hmm... the theme creator needs the icon editor api package v2.0, but apparently I'm too stupid to find it. Can I have a hint?

Yes

Installation and instructions:
Install package using VIPM.
*Ensure that the x.vi does not already exist as a quick drop plugin, if so you will have to manual manipulate the install.

VIPC file included for dependencies (list only), repackaged Icon Editor API included as package

.

How's that?

So its in the .zip version not the package version downloadable.

But you can get it here from my post too

Cheers!

-JG.

If you have any feedback to make this better please let me know too. I would be very interested in what you think.

[Daklu]

VIPC file included for dependencies (list only), repackaged Icon Editor API included as package.

How's that?

I tried... I really did... For the life of me I can't figure out how to parse that to mean, "download the zip file if you don't have the dependency." But like I said, I'm a little slow.

So its in the .zip version not the package version downloadable.

Are you sure about that?

But you can get it here from my post too

Ahhhhh... better.

If you have any feedback to make this better please let me know too. I would be very interested in what you think.

Me? I don't ever have opinions...

[jgcode]

I tried... I really did... For the life of me I can't figure out how to parse that to mean, "download the zip file if you don't have the dependency." But like I said, I'm a little slow.

LAVA keeps getter cooler, and with the recent upgrade, you can now upload multiple files to the LAVA CR.
Before the rules were to upload a .zip contain XYZ.
The upgrade allows you to post a package (.opg/.vip) version too!
The first time I have done this is with this project the other day so the readme is actually referring to the .zip (and I may need to brush up on my grammer if it now contains artifacts that are now confusing).

VIPC file included for dependencies (list only), repackaged Icon Editor API included as package

Are you sure about that?

Yes, very

I think I am assuming you (and others) are familiar with VIPM nomenclature (and my interpretation of it)?
So I will parse this string:

• Dependencies are what you need to install with the package to make sure its not broken (simple really)
• The .vipc file contains a list of dependencies
• By this I mean the dependent packages are listed by name but are not physically inside the .vipc file.
• However, in this case, the exception is the Icon Editor API package
• My logic is that some files are easy to get to (through the VI Package Network) and some are harder to get access to (e.g. Icon Editor API you would have to go to the post)
• So I include the harder ones in the .vipc file as a physical package - as I think this is generally easier for the user.

Now not to confuse issues, in this project I have now included all other reuse VIs internally in the code (by namespacing them etc...) so the .vipc file will only include the single Icon Editor API dependency:

Dependencies:
jgcode_rpk_ni_icon_editor_api>=2.0

Actually I would rather have no dependencies at all, the reason for this, in this case, is that NI's Icon Editor API calls VIs outside of symbolic paths (e.g. vi.lib).
This means that if you move code (i.e namespace and include with your own release/project code) all linkages will break!
The workaround is to get the user to install the package separately.


***

Also here is an example what I am talking about, and what the .vipc file would look like:



When the file is opened in VIPM you can see that there is an package-glyph associated with one item and no-glyph associated with the other item.
So the package-glyph means that physically that package is in the .vipc file, the no-glyph meast you need to BYO
All you need to do is Tools>>Apply Package Configuration to install the files.




Hope that makes sense?

[Daklu]

• By this I mean the dependent packages are listed by name but are not physically inside the .vipc file.
• However, in this case, the exception is the Icon Editor API package

I see it now. I've evaluated VIPM configuration files and like the feature, but since I don't work with them regularly it didn't even occur to me to try applying the configuration. (Had I noticed the vipc file's size I might have figured it out.)

• My logic is that some files are easy to get to (through the VI Package Network) and some are harder to get access to (e.g. Icon Editor API you would have to go to the post)
• So I include the harder ones in the .vipc file as a physical package - as I think this is generally easier for the user.

Can't dispute your reasoning. Curious, why didn't you put the Theme Creator package in the vipc file?

I have now included all other reuse VIs internally in the code

I noticed that in the changelist. Thanks!

[jgcode]

Curious, why didn't you put the Theme Creator package in the vipc file?

Good question. A few reasons:

• Traditionally dependencies go in the .vipc file only
• I can't script a .vipc file, so dependencies are a "pre-made" file and during the build process the file is added to the zip just like any other support file, whilst the package gets created from a source distribution each time.
• Majority of times people have the dependencies and just want the new package anyway
• If I want the package in the zip, then having it in the .vipc file will add extra size.

But you are correct it is a valid way to distribute code, but I can't script it at this stage.

I am guessing you would prefer it in one file?

[Daklu]

I am guessing you would prefer it in one file?

Not at all, I was just curious. Had I been more familiar with vipc files I likey would have clued in to the dependency right away. If the zip file had contained only the vipc file (with the package inside) I *might* have figured it out. Once I saw the package in the zip file I completely disregarded the vipc file.

No need to change your distro. A better solution is to get smarter users....

[jgcode]

Not at all, I was just curious. Had I been more familiar with vipc files I likey would have clued in to the dependency right away. If the zip file had contained only the vipc file (with the package inside) I *might* have figured it out. Once I saw the package in the zip file I completely disregarded the vipc file.

No need to change your distro. A better solution is to get smarter users....

That's ok as VIPM 2010 will have a cool new feature that will have you covered

[Daklu]

That's ok as VIPM 2010 will have a cool new feature that will have you covered

VIPM will make me smarter? Sign me up for 11 copies!

[jgcode]

VIPM will make me smarter? Sign me up for 11 copies!

That is correct

[jgcode]

New Version

Version History (Changelist):
3.2-1 2010 07 20
- Fixed (): Caching the plugin caused an error whereby the QD'd VI's Reference become corrupted between application instances. This was fixed using VI Analyser functions (mad props to Darren who sorted this issue out for me).

Known Issues:
When the plugin is cached, the Getting Started Window (GSW) will not appear as a VI is still 'open'. I currently to do not have a work around for this, only to use (Ctrl + Shift + X) on a call to the plugin to uncache it and then the GSW will appear.

See this topic for more info on caching.

[jgcode]

Version History (Changelist):
3.3-1 2010 07 26
- Fixed (): Getting Started Window now shows when plugin cached in the background and no other VIs are opened
- Added (): Reset to Original Theme Color button
- Added (): Reset All Settings button

[jgcode]

Hey guys.
I have updated the LVOOP Theme Creator to LVOOP Assistant as I have added some cool new features.
Check out the vids below. Feedback much appreciated.
Enjoy!


Cheers
-JG

Intro
<object id="scPlayer" class="embeddedObject" width="1009" height="728" type="application/x-shockwave-flash" data="http://content.scree...swfplayer.swf"> <param name="movie" value="http://content.scree...swfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/8105de4a-4418-472a-9e60-c8b013c6465c/FirstFrame.jpg&containerwidth=1009&containerheight=728&content=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/8105de4a-4418-472a-9e60-c8b013c6465c/LVOOP%20Assistant%20-%20Intro.swf&blurover=false"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.scree...c8b013c6465c/"> </object>

Rename LVOOP FP Object Labels
<object id="scPlayer" class="embeddedObject" width="1009" height="728" type="application/x-shockwave-flash" data="http://content.scree...swfplayer.swf"> <param name="movie" value="http://content.scree...swfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/61961fba-3f9d-4c67-8f39-b1f586d1b70e/FirstFrame.jpg&containerwidth=1009&containerheight=728&content=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/61961fba-3f9d-4c67-8f39-b1f586d1b70e/LVOOP%20Assistant%20-%20Rename%20LVOOP%20FP%20Object%20Labels.swf&blurover=false"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.scree...b1f586d1b70e/"> </object>

Create Constructor From Template
<object id="scPlayer" class="embeddedObject" width="1009" height="728" type="application/x-shockwave-flash" data="http://content.scree...swfplayer.swf"> <param name="movie" value="http://content.scree...swfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/a58b5ff7-11f6-4d50-a9c3-b008e0af3e99/FirstFrame.jpg&containerwidth=1009&containerheight=728&content=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/a58b5ff7-11f6-4d50-a9c3-b008e0af3e99/LVOOP%20Assistant%20-%20Create%20Constructor%20From%20Template.swf&blurover=false"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.scree...b008e0af3e99/"> </object>

Create Scoped Virtual Folders
<object id="scPlayer" class="embeddedObject" width="1009" height="728" type="application/x-shockwave-flash" data="http://content.scree...swfplayer.swf"> <param name="movie" value="http://content.scree...swfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/14f3684e-d9fd-4152-b393-ef6843deb121/FirstFrame.jpg&containerwidth=1009&containerheight=728&content=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/14f3684e-d9fd-4152-b393-ef6843deb121/LVOOP%20Assistant%20-%20Create%20Scoped%20Virtual%20Folders.swf&blurover=false"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.scree...ef6843deb121/"> </object>


Methods Sandbox (Batch Create Static and Dynamic Methods from Template)
<object id="scPlayer" class="embeddedObject" width="1009" height="728" type="application/x-shockwave-flash" data="http://content.scree...swfplayer.swf"> <param name="movie" value="http://content.scree...swfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/c0a6f59c-b35d-422e-8e1c-4c1e1705dcaa/FirstFrame.jpg&containerwidth=1009&containerheight=728&content=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/c0a6f59c-b35d-422e-8e1c-4c1e1705dcaa/LVOOP%20Assistant%20-%20Methods%20Sandbox.swf&blurover=false"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.scree...4c1e1705dcaa/"> </object>

Tools Menu Plugin (in addition to Quick Drop Interface)
<object id="scPlayer" class="embeddedObject" width="1009" height="728" type="application/x-shockwave-flash" data="http://content.scree...swfplayer.swf"> <param name="movie" value="http://content.scree...swfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/270c6792-6600-4f99-b197-00c665092661/FirstFrame.jpg&containerwidth=1009&containerheight=728&content=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/270c6792-6600-4f99-b197-00c665092661/LVOOP%20Assistant%20-%20Tools%20Menu.swf&blurover=false"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.scree...00c665092661/"> </object>

Unsaved Class Use Case
<object id="scPlayer" class="embeddedObject" width="1009" height="728" type="application/x-shockwave-flash" data="http://content.scree...swfplayer.swf"> <param name="movie" value="http://content.scree...swfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/8aeafd6a-7cb4-459d-834c-4d62b8e6e25d/FirstFrame.jpg&containerwidth=1009&containerheight=728&content=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/8aeafd6a-7cb4-459d-834c-4d62b8e6e25d/LVOOP%20Assistant%20-%20Unsaved%20Class.swf&blurover=false"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.scree...4d62b8e6e25d/"> </object>


Currently, some options are hard-coded to my style but there is no reason I can't open all this up if anyone wants me to e.g.:
Link to your own Static/Dynamic method (.vit) templates
Create your own Virtual Folder names etc...

[jgcode]

Public Service Announcement

<object id="scPlayer" class="embeddedObject" width="378" height="333" type="application/x-shockwave-flash" data="http://content.scree...swfplayer.swf"> <param name="movie" value="http://content.scree...swfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/3cd7631c-c3b5-4dda-8550-d8774d332741/FirstFrame.jpg&containerwidth=378&containerheight=333&content=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/3cd7631c-c3b5-4dda-8550-d8774d332741/L-VOOP.swf&blurover=false"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.scree...d8774d332741/"> </object>

[Daklu]

Nice job Jon! LVOOP Assistant is now my second favorite user contributed tool. (Hard to dethrone CCT, though I will definitely use this more than CCT.)


"Link to your own Static/Dynamic method (.vit) templates
Create your own Virtual Folder names etc..."

Both of these occurred to me while watching the videos. Being able to set my own templates would be more useful for me than defining custom virtual folder names. I tend to create virtual folders on an as needed basis depending on the class requirements rather than use a pre-defined set of folders.


"Public Service Announcement"

Since LabVIEW is a contracronym is the first place, shouldn't it be LVIEWOOP? Or just LOOP?

[François Normandin]

Public Service Announcement

Chris has been in the US too long...

[jgcode]

Feature Request: Clone a Method VI

I have updated the repository with a new version - you can now easily clone a method using this tool.
Supported Templates include:
4815 - 4x2x2x4
4833 - 5x3x3x5
4834 - 6x4x4x6
4835 - 8x4x4x8
(Assumes any other LVOOP Class Control is a data member or parameter).

<object id="scPlayer" class="embeddedObject" width="1113" height="737" type="application/x-shockwave-flash" data="http://content.scree...swfplayer.swf"> <param name="movie" value="http://content.scree...swfplayer.swf"> <param name="quality" value="high"> <param name="bgcolor" value="#FFFFFF"> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/a4f9ea3b-9061-4523-88b1-452d556909df/FirstFrame.jpg&containerwidth=1113&containerheight=737&content=http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/a4f9ea3b-9061-4523-88b1-452d556909df/LVOOP%20Assistant%20-%20Clone%20Method.swf&blurover=false"> <param name="allowFullScreen" value="true"> <param name="scale" value="showall"> <param name="allowScriptAccess" value="always"> <param name="base" value="http://content.scree...452d556909df/"> </object>

This feature was sponsored by:


Where drinking from a camouflaged can... ...makes you look tough.

[crelf]

This feature was sponsored by:

Where drinking from a camouflaged can... ...makes you look tough.

Firstly, it was "Miller High Life", and secondly, it was in a camo can so people wouldn't know that I was drinking it

Feature Request: Clone a Method VI
I have updated the repository with a new version - you can now easily clone a method using this tool.

I like it (not sure why that functionality isn't there in base LabVIEW, although I usually use the Endevo GDS for cloning), but I'm not sure it's intuative. For example, you're opening your tool and cloning a method from one class to another, but I find it difficult to know which method I'm cloning once I'm in the assistant. I guess project explorer integration would help this (eg: right click on a method and choose "Clone", then have a dialog that lets me select the target class <- that's how the Endevo GDS works). This would men breaking up your assitant's functionalites to groups (no longer a monolithic UI), but I think that would be more intuative in the long run.

I like it (not sure why that functionality isn't there in base LabVIEW, although I usually use the Endevo GDS for cloning), but I'm not sure it's intuative. For example, you're opening your tool and cloning a method from one class to another, but I find it difficult to know which method I'm cloning once I'm in the assistant. I guess project explorer integration would help this (eg: right click on a method and choose "Clone", then have a dialog that lets me select the target class <- that's how the Endevo GDS works). This would men breaking up your assitant's functionalites to groups (no longer a monolithic UI), but I think that would be more intuative in the long run.

btw: The reason that I'm suggesting changes is that I think that this tool has a real future - as I said, there's some stuff in it that I think should be included in LabVIEW by default, so I think it's probably a good time to start discussing use cases outside of your own, writing down features and planning out medium-term goals for it.

[Daklu]

I like it...

I like it...

Chris Relf... a man whose wisdom runs so deep he quotes himself!