LLB Manager - "Mid-Level VIs" section

[JasonD_at_DL]

In the LLB Manager, it's nice to have a separator between Top-Level VIs and the subVIs.

I'd like to see something for a mid-level VIs. This would allow the "major" (but not top-level) blocks of code to be easier to find when developing, separating them from the low-end subVI pool.

[Intaris]

Don't like LLBs....

[Dennis_Knutson]

LLBs are essentially obsolete except somewhat rarely now as a distribution tool and should never be used to store VIs that are in development. They don't work at all with source code control, the compression is minimal, and a single corrupt VI will make the whole LLB unreadable. They were originally a way to get around the limited allowed length for file names in old windows versions.

Current versions of LabVIEW have projects and the lvlib. With the lvlib, you can make your low level VIs private.

[JasonD_at_DL]

Hmm. I guess I'm too old-school for my own good.

I'll take a more serious look at using Projects.

We tend to pass code around to other developers in our organization (versus a final build), so the LLB had always made the most sense.

Thanks for the feedback.

[AristosQueue (NI)]

Build your VIs as separate files and pass them around as .zip files*. The virtual folder hierarchies of the project tree and the organization layer provided by libraries (all flavors) will serve you much better than any extensions to the LLB. Even better, all those features are available today, not at some future time when (if) this idea got implemented.

* even better, share them around by having different members of your team sync the files from your source code repository.

[Darren]

Any idea that has not received any kudos within a year after posting will be automatically declined.