LVOOP and lvlibp

[10Things_Rob]

I'm a relative latecomer to LVOOP.

And now I think I'm going to have to use Packed LabVIEW Libraries with them for distribution (particularly on RT). So I have a basic question...

If I have an application that I am developing, it seems that using packed libraries is going to completely screw up debugging. Either I create and debug the application and THEN create the packed libraries, in which case all of my code is linked to the source and not the library, which will suck because I have to re-link everything, OR I have to create and distribute the classes in the libraries first and then use them in the application. Then if I find a bug, I can't SAVE them, so I have to figure out what changes need to be made and THEN make them and THEN distribute them and then reload them.

Am I missing something? This seems like a big chunk of time I am going to have to spend doing non-value-added easy-to-screw-up activity.

Thanks for any insight.

[Norbert_B]

LVOOP starts with OOD (object oriented design). The question about debugging should be answered there:

If you require the full architecture for debugging basic classes (aka their implementation), you have to use the full architecture. If you can "unplug" the basic classes from the architecture and test them seperatly, you will have to use test beds.

The second case is preferrable since it adapts better modularization.

Nevertheless, getting from lvlib to lvlibp is only a mouse click in your LV project (rightclick -> replace with Packed Library). So maybe this will help you out a bit.

I hope you are familiar with possible pitfalls of the lvlibp. (just preventing future support load 🙂 )

hope this helps,

Norbert