I have done two major projects with GOOP so far. For more details, please
see the wesbite www.quantumsignal.com or email info@quantumsignal.com
As some background, design-time should dramatically decrease when using GOOP
with any serious labview application. Classic labview involves passing
hundreds of parameters and variables around the top-level diagram. GOOP
stores all variables/parameters in a single, central memory location and
allows access like any normal cluster. This divorces the GUI from the
implementation, allowing algorithm programmers to manipulate raw data and
interface programmers to change the look-and-feel effortlessly.
Now your question; how does this impact performance? Any major labview
program gives you headaches, but I think GOOP gives yo
u the fewest. You will
have lots of bundling and unbundling of clusters. This could be a nightmare
if you store waveform datatypes; several megabytes of double-precision
cd-quality audio within the object would make even a simple VI take several
seconds. However a well-written GOOP program with reasonably sized objects
(parameters, variables, and data only) feels no different in speed.
Any more questions just post or email. I've had very favorable results so
far. It certainly is no C++ but provides a much more friendly LV experience
for large programming projects.
-joey
"Teimur" wrote in message
news:506500000008000000BC4C0000-1023576873000@exchange.ni.com...
> Hello All.
> I have written the programm using kind of OOP based on example I get
> from NI.(Example attached) In principle it works good. I have only
> some problems with performance of my program, it is a litle bit slow.
> And I am thinking to rewrite it Using GOOP.
> The question is: Will it improve preformanc
e of or not?
> I doubt about it.
> Thanks. Timur.
