Comments on: TortoiseSVN Right-Click Drag and Drop http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/ an unfiltered stream of data flow consciousness Tue, 7 Oct 2008 04:17:16 +0000 http://wordpress.org/?v=2.6.2 By: Jim Kring http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-224 Jim Kring Thu, 12 Apr 2007 16:03:59 +0000 http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-224 Hi, Everyone. Due to the large number of requests for articles on SVN, I have just posted an article called <a href="http://thinkinging.com/2007/04/12/creating-a-local-subversion-repository-with-tortoisesvn/" rel="nofollow"> Creating a local Subversion repository with TortoiseSVN</a>. Enjoy :) Hi, Everyone. Due to the large number of requests for articles on SVN, I have just posted an article called Creating a local Subversion repository with TortoiseSVN. Enjoy :)

]]> By: Yen http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-221 Yen Wed, 11 Apr 2007 18:41:56 +0000 http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-221 I would also be on the bandwagon of people wanting to see more SVN related posts. I would also be on the bandwagon of people wanting to see more SVN related posts.

]]> By: Jim Kring http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-212 Jim Kring Tue, 03 Apr 2007 21:24:00 +0000 http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-212 Alvin (and others): I would be happy to write articles on these topics -- they are exactly the type of thing that I had in mind. Regarding putting built EXEs (or installers) into SCC, this is not necessarily bad, but is not generally done. I'll write more about my thoughts on this in a full-fledged article in the coming week (or two). Thank you. Alvin (and others): I would be happy to write articles on these topics — they are exactly the type of thing that I had in mind. Regarding putting built EXEs (or installers) into SCC, this is not necessarily bad, but is not generally done. I’ll write more about my thoughts on this in a full-fledged article in the coming week (or two). Thank you.

]]> By: Alvin Moore http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-211 Alvin Moore Tue, 03 Apr 2007 21:10:21 +0000 http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-211 Jim, I had already discovered the way-cool drag and drop stuff in Subversion. It is indeed powerful and useful. I'd appreciate seeing more articles here on subversion and LV, especially given your ad above about having JKI come help you with subversion and LV in the enterprise. I use subversion with LV, don't use LV's built in version control, and haven't used the LV OOP much yet so that stumbling block has not hit much. I read somewhere that you should not check in your builds into the version control system. So built apps (builds) in LV are not checked in. I can see why this is, because they are huge, but plenty of times it feels like that would be the way to go. That way, I have an exact copy of the build I deployed on such and such date. I was wondering what ya'll did at JKI. Are you willing to give any general usage pointers on your blog? Thanks. Jim,
I had already discovered the way-cool drag and drop stuff in Subversion. It is indeed powerful and useful. I’d appreciate seeing more articles here on subversion and LV, especially given your ad above about having JKI come help you with subversion and LV in the enterprise.
I use subversion with LV, don’t use LV’s built in version control, and haven’t used the LV OOP much yet so that stumbling block has not hit much.
I read somewhere that you should not check in your builds into the version control system. So built apps (builds) in LV are not checked in. I can see why this is, because they are huge, but plenty of times it feels like that would be the way to go. That way, I have an exact copy of the build I deployed on such and such date. I was wondering what ya’ll did at JKI. Are you willing to give any general usage pointers on your blog? Thanks.

]]> By: Guillaume Lessard http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-210 Guillaume Lessard Tue, 03 Apr 2007 19:39:39 +0000 http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-210 In response to Tomi's questions: 1. As far as I'm concerned this is an annoyance rather than a show stopper. The real effect is that when you try to go to a revision that is prior to a rename, you may get an error and you need to browse the repository to get the right filename. This is more an issue for directories than files. I rarely rename files anyway. The other two issues are worse. 2. Renaming files is a multi-step process between LV and SVN. For this reason as well as #1, I try to avoid having to rename files. 3. Pre-LabVOOP, I have avoided much of these spurious changes by locking my VIs. I wish it were possible to save the compiled code in a parallel file hierarchy... the project file must make this possible! In response to Tomi’s questions:

1. As far as I’m concerned this is an annoyance rather than a show stopper. The real effect is that when you try to go to a revision that is prior to a rename, you may get an error and you need to browse the repository to get the right filename. This is more an issue for directories than files. I rarely rename files anyway. The other two issues are worse.

2. Renaming files is a multi-step process between LV and SVN. For this reason as well as #1, I try to avoid having to rename files.

3. Pre-LabVOOP, I have avoided much of these spurious changes by locking my VIs. I wish it were possible to save the compiled code in a parallel file hierarchy… the project file must make this possible!

]]> By: Jim Kring http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-207 Jim Kring Tue, 03 Apr 2007 14:59:33 +0000 http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-207 Todd: I use TortoiseSVN as my SCC client. I don't use the LabVIEW Project Environment's SCC capabilities (yet), due to the fact that LabVIEW SCC settings are global and not per project. BTW, PushOK makes a Subversion client, too. Todd: I use TortoiseSVN as my SCC client. I don’t use the LabVIEW Project Environment’s SCC capabilities (yet), due to the fact that LabVIEW SCC settings are global and not per project. BTW, PushOK makes a Subversion client, too.

]]> By: Tomi Maila http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-206 Tomi Maila Tue, 03 Apr 2007 14:55:52 +0000 http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-206 I considered moving to subversion. I asked our IT department if we already have a subversion service running. I was told that yes we do but there is a flaw in subversion and you should consider using another product. This flaw turned out to be a fact that subversion doesn't support renaming files but instead files get copied and the original gets deleted. Does anybody have experience on the practical implications of this flaw in LabVIEW development. Second issue I'd like to raise is the fact that LabVIEW requires all the files to be renamed or moved in LabVIEW so that links between files don't get meshed up. This is especially important when using LabVOOP. On the other hand I think subversion requires files to be renamed or moved in subversion so that the revision history doesn't get meshed up. How these two programs interact in this respect. Third issue I'd like to raise up is the fact that LabVOOP requires often recompiling the whole project. As a result each file in the project, even the files you didn't edit, gets changed. How does this affect the usage of version control software. <a href="http://expressionflow.com" title="EXPRESSIONFLOW - A blog on LabVIEW and visual object-oriented programming by Tomi Maila" rel="nofollow">-= EXPRESSIONFLOW =-</a> I considered moving to subversion. I asked our IT department if we already have a subversion service running. I was told that yes we do but there is a flaw in subversion and you should consider using another product. This flaw turned out to be a fact that subversion doesn’t support renaming files but instead files get copied and the original gets deleted. Does anybody have experience on the practical implications of this flaw in LabVIEW development.

Second issue I’d like to raise is the fact that LabVIEW requires all the files to be renamed or moved in LabVIEW so that links between files don’t get meshed up. This is especially important when using LabVOOP. On the other hand I think subversion requires files to be renamed or moved in subversion so that the revision history doesn’t get meshed up. How these two programs interact in this respect.

Third issue I’d like to raise up is the fact that LabVOOP requires often recompiling the whole project. As a result each file in the project, even the files you didn’t edit, gets changed. How does this affect the usage of version control software.

-= EXPRESSIONFLOW =-

]]> By: Todd http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-204 Todd Tue, 03 Apr 2007 12:32:00 +0000 http://thinkinging.com/2007/04/03/tortoisesvn-right-click-drag-and-drop/#comment-204 I currently use Micrsoft Visual SourceSafe, but I would like to switch to an open source solution. It would appear that NI has not tested Subversion with Labview, but CVS has been tested with the PushOK Windows client. While there currently are many short commings with source code control integration into LabView (can't have a different repository per project) I like a lot of the integration features. Have you tried integrating it with LabView, check in and out form project, for example? I currently use Micrsoft Visual SourceSafe, but I would like to switch to an open source solution. It would appear that NI has not tested Subversion with Labview, but CVS has been tested with the PushOK Windows client. While there currently are many short commings with source code control integration into LabView (can’t have a different repository per project) I like a lot of the integration features. Have you tried integrating it with LabView, check in and out form project, for example?

]]>