My first LVOOP project: advice appreciated

Question

Hi all,
I just
started using LVOOP and I would like somebody to check my first achievement and
give me some advice what I should improve regarding:
Project organization
– Auto populating vs virtual folder. I prefer the auto populating folders but
with classes it seems to be better to use the virtual folders
Disk organization
– Do you use plain structure of the classes or nested (children folders).
Special folders for private/public methods?
PrivatexPublic… –
Are there some methods that I use and should make them private? I left
everything public for now.
But mainly
if the design, the methods and the way I handle the problem is “as it should be”,
or if there is space for some significant improvement.
The program
should list all in system connected and supported Daqmx devices and then select
only those for DAQ and those for Output. The class hierarchy is attached.
LV 2011, Win7
Attachments:
ListDevices.zip ‏725 KB
DeviceClassHierarchy.png ‏38 KB

Answer 1

Hi Ceties,
it's difficult to answer general questions about architecture because every person can do it differently, and still all of those ways can be right.
Your device class hierarchy seems well designed and I wouldn't change anything there.
The most comfortable way for me to organize my project is to use auto-populating folders. 
I also wouldn't use nested file organization, rather separate folder for every class. This way you don't need to remember the inheritance pattern while going through the files outside of the project.
For more information please visit:
http://zone.ni.com/devzone/cda/tut/p/id/3573#toc4
especially the last paragraph "Additional Resources"
I hope that helps, TRSns
Best regards, Piotr
Certified TestStand Architect
Certified LabVIEW Architect