[LVTN] LVOOP Assistant

jgcode · June 28, 2010

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 · June 29, 2010

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.... :blink: :lol:

jgcode · June 29, 2010

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 · June 29, 2010

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 · June 29, 2010

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

That is correct

jgcode · July 20, 2010

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 · July 26, 2010

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 · September 17, 2010

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

Rename LVOOP FP Object Labels

Create Constructor From Template

Create Scoped Virtual Folders

Methods Sandbox (Batch Create Static and Dynamic Methods from Template)

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.screencast.com/users/jgcode/folders/LAVA%20CR/media/270c6792-6600-4f99-b197-00c665092661/jingswfplayer.swf"> <param name="movie" value="http://content.screencast.com/users/jgcode/folders/LAVA%20CR/media/270c6792-6600-4f99-b197-00c665092661/jingswfplayer.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.screencast.com/users/jgcode/folders/LAVA%20CR/media/270c6792-6600-4f99-b197-00c665092661/"> </object>

Unsaved Class Use Case

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 · September 17, 2010

Public Service Announcement

Daklu · September 18, 2010

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?

Francois Normandin · September 18, 2010

Public Service Announcement

Chris has been in the US too long...

jgcode · September 18, 2010

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).

This feature was sponsored by:

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

crelf · September 18, 2010

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 · September 18, 2010

I like it...

I like it...

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

jgcode · September 18, 2010

but I'm not sure it's intuative.

Agreed.

Sorry, I was out most of the morning, so I didn't spend as much time on feature some of it as I wanted to.

But wanted to get it out for feedback

My first goal was proof of concept (that I could script it).

I can always give it a facelift, now that I have the functionality.

So at the mo, you are cloning the active VI, i.e. QD'd VI.

I tossed up separating the functionality into another tool (but didn't for whatever reason) - so I have thought about that it may not be best suited where it is.

So for now (no proj int):

Maybe a dropbox of all VIs in the Class would have made more sense too? You could clone multiple methods at once, but that is not my usually use case.

I could make it a separate Tools Menu action that operates on the Active VI - that might make more sense?

jgcode · September 18, 2010

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.)

Thanks Dave

"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.

My next step is to open this up.

The settings are what I like, but obviously people would have their own templates that they like - so I can point to those.

[Virtual Folders] The LVOOP Assistant gives me the option of adding my favorite folders anytime to the Class without the need to worry about syntax or scoping etc... (and if they already exist it just ignores it). You can start with a few and as your Class changes over time you can bang in more.

"Public Service Announcement"

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

I don't want to get bashed, so I am going with L-VOOP

crelf · September 19, 2010

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

My wisdom is both reentrant and reentrant.

Maybe a dropbox of all VIs in the Class would have made more sense too? You could clone multiple methods at once, but that is not my usually use case.

Yeah, that's a very rare use case for me. It's more of a clone class than a clone method.

I could make it a separate Tools Menu action that operates on the Active VI - that might make more sense?

I guess, but I ultimately want Project Explorer integration - so I can right click on a method and clone it <- make it happen.

Public Service Announcement

You're welcome.

jgcode · September 20, 2010

Project Explorer integration... ... <- make it happen.

I hear ya!

huotom · September 20, 2010

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).

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

Error occurs!

LV could not find addons\_ICON Library\scripting\_icon_lib_scripting.lib.

jgcode · September 20, 2010

Error occurs!

LV could not find addons\_ICON Library\scripting\_icon_lib_scripting.lib.

Thanks huotom.

Sorry, some files were missing from the build.

The new version (0.14.1) is up on LAVACR and has fixed this issue.

Cheers

-JG

jgcode · September 26, 2010

Shortcut to download latest version here

Changelist:

0.15-1 2010 09 26

- Added (): Name of Method VI being cloned is displayed on Clone Dialog

- Fixed (): Order of Virtual Folders in GUI did not match script

- Fixed (): Creating Constructor from Template did not replace Class Input Control (caused by refactoring for Clone method support)

Daklu · September 26, 2010

This is for 2009 only? I'm not given the option to install the package for 2010.

jgcode · September 26, 2010

This is for 2009 only? I'm not given the option to install the package for 2010.

Hi Dave, as per the Readme, only 2009 is currently supported at the moment.

One of the next things I will be doing is testing it in 2010, to make sure its all good.

Are you moving up to 2010?

Daklu · September 27, 2010

Hi Dave, as per the Readme

You mean I'm actually supposed to read that? I suppose you faithfully read all the terms and conditions when you install new software too?

Are you moving up to 2010?

Already have, except for reuse code. Still doing that work in 2009.

jgcode · October 22, 2010

Hi neil

This tool rocks!

Thanks for the kind words.

Ammendment to my previous comment: all newly created classes have correctly sized banner text when set via the LVOOP Assistant

However, a class I created previously (when I still had the font size set to 10 in the Icon Editor) seems to still be using the using the old font size.

I set the Class to defaults (8) if the IE2009 (layer) data was empty, and I always use 8 internally (so this hasn't cropped up for me).

The other reason is I decided to leave all other settings that exist alone is - in case they have been set for a particular reason.

But I could override the 10 to an 8 if this is always preferred (like I do currently for Caps)?

Also, would you mind posting a screenshot of what it looks like?

Cheers

-Jon

[LVTN] LVOOP Assistant

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

jgcode

jgcode

Daklu

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation

Similar Content

Important Information