Open G version updates, any trouble?

[david_jenkinson]

Hi,

I've been resisting integrating any Open G tools into our project for some time, because I'm afraid of future updates of the libraries breaking things in the code.  But I see there are a couple things in there that I need, and would take me considerable time coding from scratch.  So I have a question for those that have used Open G over the years:  Have you experienced significant problems from opengl library updates breaking things in your code, which you've spend considerable time fixing/working around?  I looks like the VI package manager queries what versions are the latest and installs from there.  I see no way to download a comprehensive "package" that we can use, and not have to worry about  it changing.  Is there one?    I am responsible for 6 test stations, all running identical teststand/labview code, and I'd prefer to source control a snapshot of the entire open G package.  Then I could test new "packages" as they come out on one machine, before installing on all.

Thanks

David Jenkinson

[TCPlomp]

Interesting question you bring up (and valid ones as well).

As OpenG developers we have the policy that an upgrade of a package should never lead to altered results or behaviour. If code should improve and making the improvements changes inputs/outputs a new version of the VI is built with a new name (see  OpenG Wiki)

If such behaviour is found by an OpenG user please report!

I have never had issues with upgrading OpenG packages in the way you mention (breaking code, altering style).

If you are worried you could take advance of VIPC functionality of VIPM, making stale library packages for a given project.

What I advice on several test stations is working with executables. Of every build you distribute you create a source distribution with everything of that application (even vi.lib files) since any VI can change how hard everyone tries to keep them compatible, for instance a VI might have a bug that you unintentionally exploit, the bug gets fixed and your code might be altered.

Ton (OpenG developer)

[Jim_Kring]

Hi David,

As Ton mentioned, OpenG tries very hard to ensure that all updates are very high quality and don't break people's code.

To ensure that you're always using the same version of packages when you start working on a project, using VIPM Professional, you can create a VI Package Configuration file -- here's a great tutorial on how to create a VI Package Configuration file:

• http://jkisoft.com/vipm/guide/using-vi-packages-in-your-projects/

If you have any questions about VIPM Professional or would like a demo, please contact JKI.

Thanks,

-Jim

Message Edited by Jim Kring on 10-06-2008 08:37 AM

[david_jenkinson]

Thanks for all the replies, I have installed and am using some of the nice tools.

Regards

David Jenkinson