ni.com checkout is currently experiencing issues.
Support teams are actively working on the resolution.
ni.com checkout is currently experiencing issues.
Support teams are actively working on the resolution.
11-18-2014 06:22 PM
Here is the simple packed project library plugin example we walked through during tonights meeting. I will try to get more details up on the workflow shortly...
11-19-2014 10:29 AM
Hi John:
Here I am wrestling with an app that’s just screaming for a plug-in architecture, and it looks like I was forced to bail on the very LUG meeting that I probably needed to sit in on. Rats! FYI, I appreciate your hard work on behalf of the LUG. Sorry to have missed this one.
John Murin
508-490-9960 ext. 292
john.murin@protonex.com<mailto:john.murin@protonex.com
11-25-2014 07:59 AM
Here is a literature review of sorts on PPL's as plugins:
Plugin Architecture Using PPL's: https://decibel.ni.com/content/docs/DOC-19176
Plugin Architecture Using Classes and PPL's: https://decibel.ni.com/content/docs/DOC-33364
Plugin Architecture Using the Actor Framework and PPL's: https://decibel.ni.com/content/thread/12998?start=15&tstart=0
To PPL or not to PPL: http://labviewjournal.com/2011/07/to-ppl-packed-project-libraries-or-not-to-ppl-part-1/
Packed Project Libraries Part 2: http://labviewjournal.com/2011/10/packed-project-libraries-part-2/
Create Single-File Object-Oriented Plugins for use with a LabVIEW Executable: https://ekerry.wordpress.com/2012/01/24/created-single-file-object-oriented-plugins-for-use-with-a-l...
These are great resources for getting up and running with ppl's as plugins. I have also had a good amount of success with PPL's as plugins in a large Actor Framework application and will do my best to answer any questions. One thing I will mention is that following the SOLID principles of OOD is more or less a requirement to developing large LVOOP componentized (plugin based) applications. The dependency inversion principle is your friend.
-Jon