I am definitely a fan of the synchronization idea using something like the Source Control Synchronization dialog in Eclipse. This would be a must have feature in my mind. It would be useful in the case where a developer may have deployed say another package and isn't 100% sure they're not about to overwrite something someone else did or needs to confirm they changed what they thought they'd changed, etc.
As for auto-sync, I am not 100% sure it's that great of an idea. There is definitely a potential for disruptive changes, I am not 100% sure there's a great way to configure it and at least in Eclipse it may end up with either the potential for concurrent changes and unpredictable results or locking the IDE until the changes have been completely loaded into Sling. This is what happens in CRXDE, it's almost useable when using localhost, but any sort of network traffic and the IDE is frustrating beyond belief. I just feel like a common use case is to make a few changes in 2+ files, save both, then load the changes into the repository and test. I don't think developers are always or necessarily most of the time making changes in just a single file at a time. -Dan -----Original Message----- From: Robert Munteanu [mailto:romb...@apache.org] Sent: Monday, June 03, 2013 8:18 AM To: dev@sling.apache.org Subject: Re: [tooling] Moving forward with IDE tooling > I have found Sling -> FS auto syncing useful for several reasons. > 1. The IDE lets me know if files in the repo are being changed, with > the message, '....do you want to reload this file.' > 2. When I do a svn status, or git status I know I am looking at an > exact copy of what I just tested. > 3. Because of 1 and 2 I can be certain that what I am editing is what > I am testing and the repo: > a) Hasn't mysteriously branched. > b) Hasn't overwritten the change I just made with one of its own. (try > one way sync to experience this, its very frustrating until you work > out whats > happening) > 4. I can load things into the repo and have them appear in the IDE. > > But I dont want to steer this thread if the intention was for tooling > that would only work if everything is done in the IDE. I agree that we must allow developers to sync repository -> IDE workspace. I believe that this must be under the developer's control all the time nevertheless. A visual paradigm that Eclipse uses is the Synchronize view [1] , which is something we can build upon. For IntelliJ we should use what makes most sense in its visual paradigm. IMO this action should be manually triggered. Robert [1]: http://imgur.com/Zht175G ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3343 / Virus Database: 3184/6378 - Release Date: 06/02/13
