AnsweredAssumed Answered

vrf FW: 7.0 Reminder!

Question asked by mark.goldberg on Apr 12, 2004
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"><TITLE>Re: [vrf] 7.0 Reminder!</TITLE><META content="MSHTML 6.00.2800.1276" name=GENERATOR></HEAD><BODY><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=854031818-13042004>Here is Scotts Post.</SPAN></FONT></DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=854031818-13042004></SPAN></FONT> </DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=854031818-13042004>Mark</SPAN></FONT></DIV><DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> BAYES,SCOTT (A-Loveland,ex1) [mailto:scott_bayes@agilent.com]<BR><B>Sent:</B> Friday, March 19, 2004 3:28 PM<BR><B>To:</B> VRF<BR><B>Cc:</B> Beliveau, Bruno<BR><B>Subject:</B> [vrf] RE: 7.0 Reminder!<BR><BR></FONT></DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2>Hi Bruno and vrf-ers,</FONT></SPAN></DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2>Yes, this is something you'll have to consider.</FONT></SPAN></DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2>Problem is, it's very difficult, maybe impossible, to come up with a design that safely suppresses new features so you can export to older VEE formats without breaking the .vee application. For instance, if you put some of the new .NET stuff in your application, what do we do with it when removing this feature for export? Maybe comment out the Formula object code lines? Ouch, now your code doesn't work right, if at all! Maybe remove the .NET Formula Object altogether. Ouch again! (and more ouch for the unconnected input pins on other objects!). What else? I can't think of much else we could do in this situation.</FONT></SPAN></DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2>And once your .vee is exported back to 6.x, someone has to figure out how to make it work again, assuming that's even possible. You have to hope the damage isn't too extensive. And every time you modify or enhance the app in 7.0 and re-export to 6.x, you would have to fix it again.</FONT></SPAN></DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2>Yes, we might have been able to do something, but I don't know that it would have been very useful, and it would have taken a very large R&D effort for little real value. We preferred to put the effort into Undo and Panel Edit enhancements, the Properties window with associated multi-object property edit, etc.</FONT></SPAN></DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2>By the way, the new data types (UInt8, Int16, etc) introduced in 6.0 had very similar characteristics with respect to preventing loading of 6.x .vee files into 5.x. It's part of the price of progress.</FONT></SPAN></DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2>And Microsoft has the same barrier with their languages. VB6 code can come into VB .NET with reasonable ease, though most applications still require anywhere from a little to a lot of manual intervention to complete the conversion, since the conversion is not perfect. But don't even think about sending your VB .NET code back to VB6! I'm sure earlier revs of VB and of other Microsoft languages posed similar "challenges" for the developer.</FONT></SPAN></DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2>Best Regards,</FONT></SPAN></DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><DIV><SPAN class=746090223-19032004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV><P><FONT size=2>Scott Bayes<BR>Software Technical Support<BR><BR>Agilent Technologies, Inc.<BR>815 14th Street S.W.<BR>Loveland, CO, U.S.A. 80537<BR><BR>970 679 3799 Tel<BR>970 635 6867 Fax</FONT> </P><BLOCKQUOTE dir=ltr style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma   size=2>-----Original Message-----<BR><B>From:</B> Beliveau, Bruno   [mailto:BrunoBeliveau@solectron.com]<BR><B>Sent:</B> Friday, March 19, 2004   3:29 PM<BR><B>To:</B> PDL-LISTS,VRF (A-Lists,unix1)<BR><B>Cc:</B> BAYES,SCOTT   (A-Loveland,ex1)<BR><B>Subject:</B> Re: [vrf] 7.0   Reminder!<BR><BR></FONT></DIV>  <P><FONT size=2>This is a bug for people that send examples to help others on   the VRF.  Those with versions previous to 7 will not be able to receive   vee files from those with version 7.  With version 6, there was always   the possibility to edit the file with a text editor and modify what version 5   doesn't understand (specially with reals ant integers).</FONT></P>  <P><FONT size=2>The same problem when you have many tests stations installed   with versions 5 or 6 and want to develop with the newer version 7 on your   PC.</FONT></P>  <P><FONT size=2>That would be a nice feature to be able to export to previous   version (and loose some functionalities in the process)...</FONT></P>  <P><FONT size=2>-----Message d'origine-----</FONT> <BR><FONT size=2>De:   BAYES,SCOTT (A-Loveland,ex1) [<A   href="mailto:scott_bayes@agilent.com">mailto:scott_bayes@agilent.com</A>]</FONT>   <BR><FONT size=2>Date: 19 mars 2004 16:25</FONT> </P>  <P><FONT size=2>Hello vrf-ers,</FONT> </P>  <P><FONT size=2>*** Make copies of your existing .vee files before you edit   them in 7.0! ***</FONT> </P>  <P><FONT size=2>Just a note to remind you that once you edit a .vee file that   originates from an earlier version in 7.0, then save it, no earlier version   will be able to open the saved file. </FONT></P>  <P><FONT size=2>We had to change the .vee format to support the new .NET and   other features, which prevents older versions of VEE from being able to read   VEE 7.0 files.</FONT></P>  <P><FONT size=2>Also note that Execution Mode has nothing to do with this:   even if you set the Execution Mode to an older one like VEE 5, VEE 7.0's Save   will write the .vee in 7.0 language, not 5.0, and older revisions won't be   able to load it.</FONT></P>  <P><FONT size=2>So always make a copy first, in case you need to use the .vee   in the older revision some day.</FONT> </P>  <P><FONT size=2>VEE 7.0 warns you about this when you try to save a .vee that   originated in an earlier revision, but an extra reminder never hurts, since   you can force VEE to save over the original if you ignore the warnings.   </FONT></P>  <P><FONT size=2>This kind of compatibility break has occurred a number of   times in past, but it's been a while since it last occurred, and people tend   to forget.</FONT></P></BLOCKQUOTE>---<BR>You are currently subscribed to vrf as: Mark.Goldberg@ATK.COM<BR>To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".<BR>To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".<BR>To send messages to this mailing list, email "vrf@agilent.com". <BR>If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". ---<BR>You are currently subscribed to vrf as: rsb@soco.agilent.com<BR>To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".<BR>To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".<BR>To send messages to this mailing list,  email "vrf@agilent.com".  <BR>If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".</BODY></HTML>  

Outcomes