A tool for VI version conversion?

[Jick]

Cheers!

Is there any little program, a tool which could make Vi conversion to older versions? For example, if you want to open an example(LV2009).vi with LV 8.0 you have to post it here first, ask someone to convert it to 8.0 and wait.

BR,

Jick

[GerdW]

Hi Jick,

after installing all needed LV versions you have your tool for down-converting... Otherwise ask in the down-convert thread.

That's how it is.

[Jick]

But why there isn't that kind of tool? It does not make sense to me to buy a newer LV only for opening some examples made by "too new LV". Is it too hard to code or what? Wouldn't it be useful and faster way for conversions?

Jick

Message Edited by Jick on 04-28-2010 02:03 PM

[muks]

There was this player but obselete now.Now the only quick way is to ask for the example to be converted here and it will most likely be converted pretty soon.

[muks]

You can also boost the kudo count for this idea.

[tst]

---

Jick wrote:

Is it too hard to code or what?

---

Yes, it is too hard to code. NI would have to take the LV source code, strip away everything but the back-save code, create a GUI, test it, etc. I personally wouldn't want NI to spend any effort on this.

If you want, you can download and run LV 2009 in a fully functional evaluation mode for 30 days.

[tbob]

---

tst wrote:

---

Jick wrote:

Is it too hard to code or what?

---

Yes, it is too hard to code.

---

I doubt that this is the real reason why NI won't produce such a tool.  Realistic reasons:

1.  They would make no profit off of it. (expense incurred, no chance of income)

2.  It would discourage users from upgrading to newer versions of Labview (lost revenue)

3.  This forum already provides for the need, although it is a bit of a bother.

[Brad G]

---

tbob wrote:

I doubt that this is the real reason why NI won't produce such a tool.  Realistic reasons:

1.  They would make no profit off of it. (expense incurred, no chance of income)

2.  It would discourage users from upgrading to newer versions of Labview (lost revenue)

3.  This forum already provides for the need, although it is a bit of a bother.

---

In other words, NI is way more worried about dollar signs than users' convenience? 

[tbob]

---

Brad G wrote:

---

tbob wrote:

I doubt that this is the real reason why NI won't produce such a tool.  Realistic reasons:

1.  They would make no profit off of it. (expense incurred, no chance of income)

2.  It would discourage users from upgrading to newer versions of Labview (lost revenue)

3.  This forum already provides for the need, although it is a bit of a bother.

---

In other words, NI is way more worried about dollar signs than users' convenience? 

---

Exactly.  After all, they are a business and profit is the name of the game.  However, their being profitable makes our lives easier.  So I call it a win-win situation.  Sometimes the inconvenience is worth the price.

[Ben]

Don't to quick to dismiss the amount of work in the back save.

For some LV upgrades (not all) there is the potential for mutating code. If you look at your file operations for an app developed in LV 7 that you open in LV 8 you will see the old File operations were replaced with the new flavors. Dpeneding on what you were doing with the file ops, different mutations were required.

To back-save the mutaion has to be un-done.

So as the versions increase there are more and more types of back-saves that would have to be supported. This potential ever increasing cost to support is limited by the number of version supported.

So the cost of a tool that just did all of the back saves would be constantly growing.

Those people out there that have invested their money in NI would be ill-served if there money was being spent to provide a mechanism that allows users to profit from Ni work without paying for it. So to management, the idea of a backsaving tool would make as much sense as trying to convince the makers of Charmin that they should develop a recyclable version of their product.