Module based design

[havard@wide.no]

Hi

We have made a report generator using the LabView object structure. The ancestor object talks to the printer and childs produce report content. This makes us able to add/change reports without breaking other functionallity in the code.

Now I would like to separate reporting from the rest of the code. The aims are to work on multiple parts of the code simultainiusly and to reuse code.

Where should I start looking?

Could libraries be usefull in this case?

[crossrulz]

I'm not sure what you mean by "seperate reporting from the rest of the code".  Trying to make these a reuse library?  Trying to make a reporting module that other parts of code use some communications scheme to send data to?

[havard@wide.no]

Your option "reuse library" sounds good. We have 1 ancestor and about 10 child objects that generates different report types.

[mikeporter · Accepted solution]

I always put my class structures in libraries because I get better access control.

I also hide the subclasses from the calling application and create a layer of interface VIs in the top-level parent class.

Mike...

[havard@wide.no]

Thanks!

Youy write "hide the subclasses from the calling application" . What do you mean?

[mikeporter]

I set the Access Scope of all the subclasses to private so the only access calling applications have is through the dynamic dispatch interface VIs in the top-level parent class.

Mike...

[crossrulz]

I also recommend you learn to use VI Package Manager.  It makes sharing your reuse a lot easier.