I'm rewritting a LV 6.0.2 app in LV 7.1.1 taking the advantage of events and making it more modular and expandable.
One part is a driver layer for the security testers of my customer. This driver consists of by now of 60 VIs and CTLs. This driver is deployed as Active-X Server, DLL and LLB and also used in the main application. This driver is acompanied by help in CHM and PDF format for the programmers. I also created some VIs and CMD files for automatical build. The driver is not complete by now. It misses the private functions for firmware update and setting internal parameters. It will expand by another 25-30 VIs for the driver and 2 apps.
Another part is the main application which now consists of 8 kernel modules builded by 375 VIs and CTLs. These modules are not all ready. I'm expecting to get another 100-180 VIs and CTLs. Missing by now are another 12 modules each expected to be 20+ VIs and CTLs. Together with them a programmer reference is builded. Each module is located in one LLB. There are more than one implementation for one module. As long as the interface of the module builded by CTLs and fixed named VIs aren't changed the modules can be exchanged. All the modules will be automatically build by some VIs and CMD files.
These two parts are now aimed for Windows but there are plans to get them running on Linux too. We have made some investigation and found that we need only a limited number of functions differently implemented for each platform. We will expand our build process to have the work and testing done on Windows and include an automatic build on Linux. The Linux version is aimed to run in an embedded PC of an automated test system in a light or full version. We need to rescale and rearrange the UI of the Linux version during the build process.
Another part is a custom installation routine to enter some registry information and doing a first configuration of the application when the end user installs it on his machine.
Also there is a plan to build a deployment application. This will automate the process from getting the right modules from a master layout to the the CD the end user is buying.
The problem of measuring how large an app is appears not only in the number of VIs and nodes. This is only the sight from the programmers state. Its also related to the number of steps you need to build it from the sources. And its not only the EXE and LLBs its also the programmer and end user information.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions