Re: Implementation question (LabVIEW)

Hi,

On Monday 18 October 2004 19:55, Michael Porter wrote:
> I am beginning the process of evaluating using Subversion for storing code
> from a development environment from National Instruments called LabVIEW.
>
> I am looking for personal experience, advice on how best to work them
> together--anything you might have to offer...
>
> TIA
> Mike...
>
> Michael Porter
> Porter Consulting LLC
> "...after all, He's not a tame lion..."

That's what we do, with great success (see my last post about BDB/FSFS). The
problem with LabVIEW is that LV modifies the VIs 'at will', causing massive
changes on every commit. What we do is checking the
'Options/Miscellaneous/Treat read-only VIs as locked' (since LV6.1) and
'Options/Miscellaneous/Don't save automatic changes for these VIs' (since
7.0) options, that helps a lot. Now you only need a tool to set the read-only
state for locally unmodified VIs, and reset to read/write befor any update or
merge (as SVN fails to do that properly on win32, for whatever reason).

I would really love to see LV only changing files on 'real' edits, but that's
another issue. Also, having 'plug-ins' into the normal SVN libs (called on
each local file before/after any SVN action) would be of great help, but...

Apart from these annoyances, SVN and LabVIEW work together like a charm.
Please be aware, that you would run into the same problems with ANY external
revision control system.

Hope this helps,
 Jörg

-- 
Leading SW developer  - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org