LAVA Forums Buy cool LAVA gear Forums RSS Feed

Welcome Guest ( Log In | Register )

Tags
(This content has not been tagged yet)
 
Reply to this topic Start new topic
> Different LV versions of CR code
JDave
post Sep 5 2007, 09:11 PM
Post #1


Extremely Active
****

Premium Member
Posts: 430
Joined: 2-February 05
From: Southern California
Member No.: 1519
Using LabVIEW Since:2004
LV:8.20 ,7.1.1 ,8.0.1
United States Peru us_california


If I have code that I want to make available in multiple LabVIEW versions (e.g. 7.0, 7.1, 8.2) how do I go about doing that?

If I put the different versions in the zip file, how do I indicate that when loading the new file? The CR page states what the LabVIEW version is, so would I just put some notes on the description stating that there are actually several LabVIEW versions contained contained in the zip file?

Thanks,

David


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Ad
post Sep 5 2007, 09:11 PM
Post #















Tags
(This content has not been tagged yet)
Go to the top of the page
Quote Post
PJM_labview
post Sep 6 2007, 01:04 AM
Post #2


Extremely Active
****

JKI
Posts: 612
Joined: 19-June 03
From: Bay Area, CA (USA)
Member No.: 121
Using LabVIEW Since:1998
LV:8.5.1 ,8.6 ,8.2.1
United States France Nothing Selected My Blog


David

If you were to use OpenG Pakcage file (ogp) then you could defined different versions of your librarie(s) to be installed under different LabVIEW versions. If you were to do this, then the ogp version becomes THE unique version. You do not have to worry about where or how to document the different versions included in your zip file. Unfortunately, if you have never made an ogp, this will requires a little bit of work to get started.

Just a though.

PJM

--------------------

Got VIPM?

JKI . VIPM . EasyXML . OpenG . LAVA . Builder . Blog



Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Jim Kring
post Sep 6 2007, 01:25 AM
Post #3


Changing the world, one VI at a time.
*****

JKI
Posts: 1692
Joined: 22-October 02
From: San Francisco, CA
Member No.: 17
Using LabVIEW Since:1995
LV:8.2.1 ,8.5 ,7.1.1
United States us_california Nothing Selected My Blog My Gallery


QUOTE (PJM_labview @ Sep 5 2007, 06:04 PM) *
David

If you were to use OpenG Pakcage file (ogp) then you could defined different versions of your librarie(s) to be installed under different LabVIEW versions. If you were to do this, then the ogp version becomes THE unique version. You do not have to worry about where or how to document the different versions included in your zip file. Unfortunately, if you have never made an ogp, this will requires a little bit of work to get started.

Just a though.

PJM


Yes, yes, yes!!! This is the beauty of the OGP file format.

David, if you have questions about how to do this, please ask smile.gif

-Jim

--------------------
-----------------------------------------------------------------------------------------------------
| Book | OpenG | LAVA | Champion | VIPM | Builder | Blog | JKI |
-----------------------------------------------------------------------------------------------------


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Michael_Aivaliot...
post Sep 6 2007, 02:51 AM
Post #4


Confucius say: Crowded elevator always smell different to midget
Group Icon
*****

Admin
Posts: 2363
Joined: 13-October 02
From: Planet Earth
Member No.: 2
Using LabVIEW Since:1994
LV:8.5 ,8.2.1 ,7.1.1
Greece Canada United States My Blog My Gallery


Is there a reason for the different versions? Can you just publish the lowest version? Others can just recompile up. Otherwise, just indicate the latest version and please put all the other versions in the description.

--------------------


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
JDave
post Sep 6 2007, 02:21 PM
Post #5


Extremely Active
****

Premium Member
Posts: 430
Joined: 2-February 05
From: Southern California
Member No.: 1519
Using LabVIEW Since:2004
LV:8.20 ,7.1.1 ,8.0.1
United States Peru us_california


QUOTE (Michael_Aivaliotis @ Sep 5 2007, 07:51 PM) *
Is there a reason for the different versions? Can you just publish the lowest version? Others can just recompile up.

My latest CR submission was written in version 8.2. I originally started writing it in 7.1, but there are new control properties in 8.2 that give more information. Plus some subtle changes in how events were handled required a change. So the code for 7.1 is distinct from 8.2.

QUOTE (Michael_Aivaliotis @ Sep 5 2007, 07:51 PM) *
Otherwise, just indicate the latest version and please put all the other versions in the description.

Sounds good. thumbup1.gif


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
JDave
post Sep 6 2007, 11:01 PM
Post #6


Extremely Active
****

Premium Member
Posts: 430
Joined: 2-February 05
From: Southern California
Member No.: 1519
Using LabVIEW Since:2004
LV:8.20 ,7.1.1 ,8.0.1
United States Peru us_california


QUOTE (Jim Kring @ Sep 5 2007, 06:25 PM) *
Yes, yes, yes!!! This is the beauty of the OGP file format.

David, if you have questions about how to do this, please ask smile.gif

I have yet to look fully into this, so I just have a few general questions.
  1. Does the OGP format handle unique code for different versions, or do you have to develop the code in the lowest version possible and have only one chunk of code? This is not a common problem, but you can't always go back to even version 7.x with some code.
  2. Does the OGP file use the existing menu file on the development machine to allow the OGP installation to also have menus on the palette?
  3. I didn't see anything in the new VIPM beta version about building packages. Is this something upcoming soon?
Thanks.


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post
Ton
post Sep 7 2007, 04:55 AM
Post #7


CCT It
*****

Premium Member
Posts: 1331
Joined: 13-June 05
From: Woerden, Netherlands
Member No.: 2399
Using LabVIEW Since:2001
LV:8.5.1 ,6.1 ,8.2.1
Netherlands hol_utrecht Nothing Selected My Blog My Gallery


QUOTE (dsaunders @ Sep 7 2007, 01:01 AM) *
I have yet to look fully into this, so I just have a few general questions.
  1. Does the OGP format handle unique code for different versions, or do you have to develop the code in the lowest version possible and have only one chunk of code? This is not a common problem, but you can't always go back to even version 7.x with some code.
  2. Does the OGP file use the existing menu file on the development machine to allow the OGP installation to also have menus on the palette?
  3. I didn't see anything in the new VIPM beta version about building packages. Is this something upcoming soon?
Thanks.

Here I show how to have multiple Typefs for multiple versions.
The OpenG packager, is just an advanced copy function. It tells VIPM (via the OGP file) which files should be copied where. And the possibilities are endless, you can include OS specific VIs/dll/libs. You can include labview version specific help documentation.
Using OpenG packager can be hard, and documentation is on the to-do-list but might take a while.

Ton

--------------------
Certified LabVIEW Developer
Shouldn't you be programming a Code Repository solution?


Tags
(This content has not been tagged yet)
Go to the top of the page
+Quote Post

Reply to this topicStart new topic

 




Time is now: 22nd November 2008 - 04:50 AM