Article - A Challenge to NI: Use your Application Builder

[Jim Kring]

[cross-post]

I'd like to challenge developers at NI to find more ways to incorporate stand-alone (built) LabVIEW applications into their internal systems and processes. Here's a Thinking in G article that explains why:

• A Challenge to NI: Use your Application Builder
  

I hope you enjoy it

Thanks,

-Jim

[MikaelH]

QUOTE (Jim Kring @ May 28 2008, 04:42 AM)

[cross-post]

For example, (native LabVIEW Object Oriented Programming) dynamic method overriding requires VIs of the same name, but it is impossible to store two VIs of the same name inside an EXE? How could this feature conflict possibly happen? I suspect that nobody actually tried to build an application that used LVOOP until well after the feature was implemented. What's even crazier is that NI was working on this feature for many years, before it was released.

Hi

I hope NI will abandon the LLB structure they are using in the exe-file or at least add folder support in the a LLB, this will make it possible to store everything inside the exe-file.

One other painful thing I have is that a quite large application, with lot of classes and lvlibs, it takes me more then 30 minutes to build an executable and during that time I can't use my computer for something else, since LabVIEW uses all my resources.

Cheers,

Mikael

[Louis Manfredi]

QUOTE (Jim Kring @ May 27 2008, 02:42 PM)

I hope you enjoy it

Excellent article Jim, thanks.

Louis

[jgcode]

My first time was with a .lvlib

So much for protecting my VI names with the library namespace!

It just dumped duplicate names outside of the .exe!!

[David Wisti]

Nice article Jim!

I hope I'm not thread jacking but I thought that 8.2 would put same namespace vi's inside the exe with mangled names? But in 8.5 this was changed to placing them outside the exe. I wonder why mangled names is not a build option.

[gmart]

QUOTE (David Wisti @ May 28 2008, 11:01 AM)

Nice article Jim!

I hope I'm not thread jacking but I thought that 8.2 would put same namespace vi's inside the exe with mangled names? But in 8.5 this was changed to placing them outside the exe. I wonder why mangled names is not a build option.

The name mangling (renaming) was one of the main problems with building apps that used LV classes. So for 8.5, the algorithm that handled name collisions was made the same for all project library types.