opengtoolkit-developers

RE: Introducing LabVIEW Version Chooser

[Brian G. <bri...@da...>]

Hello again,

Version 1.1.0 is now available!

You can download the latest version here
=20
http://downloads.dataact.com/LVC-1.1.0.401-setup.exe

If you are using the Automatic launching option (Auto=3DTrue), there is =
now
another option to specify a delay that will allow the automatic =
launching to
be stopped.  To enable this option add "AutoDelay=3DXX" (where XX is a =
delay
in milliseconds) key to the LVC_Action.ini.  With this option enabled, =
there
is an additional button on LVC_Action window which can be pressed or =
<F5> to
stop the automatic action.

The installer will now correctly register LabVIEW extensions on a =
computer
that doesn't have LabVIEW installed and the repair function is now more
robust.  (FYI, I have a recursive delete registry key VI if anyone needs
it).

I am still planning on working on the plug-in architecture, but it won't =
be
available until the next major release.

Thanks to everyone who has tried LVC and for all of the feedback and
support.

Sincerely,

Brian Gangloff

President
Certified LabVIEW Developer

DataAct Incorporated
375 Westminster Rd, Suite 300
Rochester, NY 14607

585.802.6036
bri...@da...
http://www.dataact.com
>=20

dqGOOP beta

[Brian G. <bri...@da...>]

Hello,
Here is a link to a beta version of the dqGOOP Toolkit that I mentioned 
on the Info-LabVIEW list.  The installer ONLY installs into the default 
LabVIEW 7.0 directory.  (C:\Program Files\National Instruments\LabVIEW 
7.0).  Eventually the installer will let you choose which LabVIEW 
version to install for.  I was testing to see if the license page could 
point to an html page, but it doesn't display so I have to fix.

http://downloads.dataact.com/dqGOOP/Setup.exe


The wizard is exactly the same as OpenGOOP, but I added a sequence to 
automatically name the enum for the object reference (thanks to code 
from Philippe Guerit).  I also want add the option to move the probes.

There is a help file that gets installed, the first three topics give a 
summary of the features and how it works.  You can get to it from 
Start/Programs/DataAct/dqGOOP/help or if you create a class and have 
context help on, there should be an active link.

In the Testing folder is a VI already to test performance.  I will send 
test classes for OpenGOOP and NIs GOOP in a little while.

Brian

Re: dqGOOP beta

[Brian G. <bri...@da...>]

Brian Gangloff wrote:

> In the Testing folder is a VI already to test performance.  I will 
> send test classes for OpenGOOP and NIs GOOP in a little while.

Here is the link for the test classes, there are three.  You don't need 
to run the setup.exe for these to work, so you can  just unzip this to 
take a look at a class made with dqGOOP.

http://downloads.dataact.com/dqGOOP/GOOPTest.zip

Brian

Re: dqGOOP beta

[Brian G. <bri...@da...>]

Brian Gangloff wrote:

> The installer ONLY installs into the default LabVIEW 7.0 directory.  
> (C:\Program Files\National Instruments\LabVIEW 7.0).  Eventually the 
> installer will let you choose which LabVIEW version to install for.  I 
> was testing to see if the license page could point to an html page, 
> but it doesn't display so I have to fix.

The installer will now let you choose the LabVIEW directory and the 
license page is corrected.

available at:

http://downloads.dataact.com/dqGOOP/Setup.exe

RE: dqGOOP beta

[Jim K. <jim...@ja...>]

Brian,

First, let me say that this is a very nice and GOOP implementation.  It is
very clever how you get the mutex/semaphore-like behavior "for free" with
the "Dequeue Element" function waiting for an element to be queued.  Also,
how the "Preview Queue Element" function allows reading the data store (when
one is not intending to write data).  However, there is one behavioral
difference b/w the dqGOOP and traditional semaphored data, which you might
have noticed -- a call to "Get Data" will wait until a data modifying member
function has written the data.  Basically the "Get Data" and "Get Data to
Modify" will both wait until "Set Modified Data" is called, since "Preview
Queue Element" cannot return until there is an element on the queue, which
will not occur while data is in the process of being modified.  I don't
think that this is a big deal for most (if any) applications, but it is a
difference worth mentioning.

Cheers,

-Jim Kring


> -----Original Message-----
> From: ope...@li... 
> [mailto:ope...@li...] 
> On Behalf Of Brian Gangloff
> Sent: Saturday, April 23, 2005 9:06 AM
> To: ope...@li...
> Subject: Re: dqGOOP beta
> 
> Brian Gangloff wrote:
> 
> > The installer ONLY installs into the default LabVIEW 7.0 
> directory.  
> > (C:\Program Files\National Instruments\LabVIEW 7.0).  
> Eventually the 
> > installer will let you choose which LabVIEW version to 
> install for.  I 
> > was testing to see if the license page could point to an html page, 
> > but it doesn't display so I have to fix.
> 
> The installer will now let you choose the LabVIEW directory and the 
> license page is corrected.
> 
> available at:
> 
> http://downloads.dataact.com/dqGOOP/Setup.exe
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from 
> real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> OpenGToolkit-Developers mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers
> 

RE: dqGOOP beta

[Jim K. <jim...@ja...>]

Brian,

I presume that you used the Nullsoft Scriptable Installer System (NSIS) for
the dqGOOP installer.  Does NSIS support installing something to more than
one location?  For example, it would be VERY cool if you could have multiple
optional installation locations, such as:

C:\Program Files\National Instruments\LabVIEW 6.1
C:\Program Files\National Instruments\LabVIEW 7.0
C:\Program Files\National Instruments\LabVIEW 7.1

I'm not sure how this would be done, as I have yet to really learn the
capabilities of NSIS.

Anyhow, I would recommend creating an OpenG Package file with dqGOOP since
this would allow a cross platform and LabVIEW version installation approach.
BTW, in a couple months we may have a GUI for building packages.  It on the
to-do list.

Regards,

-Jim Kring

> -----Original Message-----
> From: ope...@li... 
> [mailto:ope...@li...] 
> On Behalf Of Brian Gangloff
> Sent: Saturday, April 23, 2005 9:06 AM
> To: ope...@li...
> Subject: Re: dqGOOP beta
> 
> Brian Gangloff wrote:
> 
> > The installer ONLY installs into the default LabVIEW 7.0 
> directory.  
> > (C:\Program Files\National Instruments\LabVIEW 7.0).  
> Eventually the 
> > installer will let you choose which LabVIEW version to 
> install for.  I 
> > was testing to see if the license page could point to an html page, 
> > but it doesn't display so I have to fix.
> 
> The installer will now let you choose the LabVIEW directory and the 
> license page is corrected.
> 
> available at:
> 
> http://downloads.dataact.com/dqGOOP/Setup.exe
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from 
> real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> OpenGToolkit-Developers mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers
> 

Re: dqGOOP beta

[Brian G. <bri...@da...>]

Jim Kring wrote:

>Brian,
>
>I presume that you used the Nullsoft Scriptable Installer System (NSIS) for
>the dqGOOP installer.  Does NSIS support installing something to more than
>one location?  For example, it would be VERY cool if you could have multiple
>optional installation locations, such as:
>
>C:\Program Files\National Instruments\LabVIEW 6.1
>C:\Program Files\National Instruments\LabVIEW 7.0
>C:\Program Files\National Instruments\LabVIEW 7.1
>
>  
>
Yes, that is the plan.  I will have a components page similar to LabVIEW 
Version Chooser that will list all of the installed LabVIEW versions so 
you can check the the ones you want dqGOOP installed to.  The 
maintenance page will also be working so you can add and remove as well.

>I'm not sure how this would be done, as I have yet to really learn the
>capabilities of NSIS.
>  
>
The registry is the best for Windows (to find out installed versions of 
LV) and maco's could be used for the NSIS code.

>Anyhow, I would recommend creating an OpenG Package file with dqGOOP since
>this would allow a cross platform and LabVIEW version installation approach.
>BTW, in a couple months we may have a GUI for building packages.  It on the
>to-do list.
>  
>
I may need some help in verifing non windows installations.  I've read 
how to distribute help for the mac, but would need someone with a mac to 
test that everything still works.

>Regards,
>
>-Jim Kring
>

Re: dqGOOP beta

[Michael A. <mi...@ai...>]

If you make it a package installable form Commander then handling OS and 
LV versions is already handle for you through the Commander interface. I 
would recommend investigating this approach.

Thank You
Michael Aivaliotis

Brian Gangloff wrote:

> Jim Kring wrote:
>
>> Brian,
>>
>> I presume that you used the Nullsoft Scriptable Installer System 
>> (NSIS) for
>> the dqGOOP installer.  Does NSIS support installing something to more 
>> than
>> one location?  For example, it would be VERY cool if you could have 
>> multiple
>> optional installation locations, such as:
>>
>> C:\Program Files\National Instruments\LabVIEW 6.1
>> C:\Program Files\National Instruments\LabVIEW 7.0
>> C:\Program Files\National Instruments\LabVIEW 7.1
>>
>>  
>>
> Yes, that is the plan.  I will have a components page similar to 
> LabVIEW Version Chooser that will list all of the installed LabVIEW 
> versions so you can check the the ones you want dqGOOP installed to.  
> The maintenance page will also be working so you can add and remove as 
> well.
>
>> I'm not sure how this would be done, as I have yet to really learn the
>> capabilities of NSIS.
>>  
>>
> The registry is the best for Windows (to find out installed versions 
> of LV) and maco's could be used for the NSIS code.
>
>> Anyhow, I would recommend creating an OpenG Package file with dqGOOP 
>> since
>> this would allow a cross platform and LabVIEW version installation 
>> approach.
>> BTW, in a couple months we may have a GUI for building packages.  It 
>> on the
>> to-do list.
>>  
>>
> I may need some help in verifing non windows installations.  I've read 
> how to distribute help for the mac, but would need someone with a mac 
> to test that everything still works.
>
>> Regards,
>>
>> -Jim Kring
>>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> OpenGToolkit-Developers mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers
>
>
>

RE: dqGOOP beta

[Jim K. <jim...@ja...>]

Yes, OpenG Packages are cross-platform in nature and Commander makes
distribution a piece of cake.  Also, I recommend HTML docs for
cross-platform documentation.

-Jim

> -----Original Message-----
> From: ope...@li... 
> [mailto:ope...@li...] 
> On Behalf Of Michael Aivaliotis
> Sent: Sunday, April 24, 2005 1:37 PM
> To: ope...@li...
> Subject: Re: dqGOOP beta
> 
> If you make it a package installable form Commander then 
> handling OS and 
> LV versions is already handle for you through the Commander 
> interface. I 
> would recommend investigating this approach.
> 
> Thank You
> Michael Aivaliotis
> 
> Brian Gangloff wrote:
> 
> > Jim Kring wrote:
> >
> >> Brian,
> >>
> >> I presume that you used the Nullsoft Scriptable Installer System 
> >> (NSIS) for
> >> the dqGOOP installer.  Does NSIS support installing 
> something to more 
> >> than
> >> one location?  For example, it would be VERY cool if you 
> could have 
> >> multiple
> >> optional installation locations, such as:
> >>
> >> C:\Program Files\National Instruments\LabVIEW 6.1
> >> C:\Program Files\National Instruments\LabVIEW 7.0
> >> C:\Program Files\National Instruments\LabVIEW 7.1
> >>
> >>  
> >>
> > Yes, that is the plan.  I will have a components page similar to 
> > LabVIEW Version Chooser that will list all of the installed LabVIEW 
> > versions so you can check the the ones you want dqGOOP 
> installed to.  
> > The maintenance page will also be working so you can add 
> and remove as 
> > well.
> >
> >> I'm not sure how this would be done, as I have yet to 
> really learn the
> >> capabilities of NSIS.
> >>  
> >>
> > The registry is the best for Windows (to find out installed 
> versions 
> > of LV) and maco's could be used for the NSIS code.
> >
> >> Anyhow, I would recommend creating an OpenG Package file 
> with dqGOOP 
> >> since
> >> this would allow a cross platform and LabVIEW version installation 
> >> approach.
> >> BTW, in a couple months we may have a GUI for building 
> packages.  It 
> >> on the
> >> to-do list.
> >>  
> >>
> > I may need some help in verifing non windows installations. 
>  I've read 
> > how to distribute help for the mac, but would need someone 
> with a mac 
> > to test that everything still works.
> >
> >> Regards,
> >>
> >> -Jim Kring
> >>
> >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products 
> from real users.
> > Discover which products truly live up to the hype. Start 
> reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > OpenGToolkit-Developers mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers
> >
> >
> >
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from 
> real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> OpenGToolkit-Developers mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers
> 

dqGOOP new setup available

[Brian G. <bri...@da...>]

There is an updated installer available for dqGOOP on our website.  Here 
is a list of the changes:

    * Added methods for reading locked data
    * Installer will allow installing into all LabVIEW versions greater
      or equal to 7.0
    * Installer allows mass compiling if required (Warning EXIT LabVIEW
      before selecting YES)
    * Wizard will move the custom probes to the
      ..\user.lib\-probes\default directory
    * Help file updated with new VIs and performance charts

Please uninstall the previous version before installing this one.

Follow the link on the downloads page for the new installer
http://www.dataact.com/downloads.htm

The help file is available on line here
http://www.dataact.com/dqGOOP.htm

Let me know if anyone has any questions

Brian