I think some comments here are *combining* the expected user experience with an expectation of how this is implemented or realized. While I totally understand and accept the reasoning behind this, I don't agree with combining those two.
I think we all agree that the user experience should be something like you save your script and it's (nearly) immediately effective. What happens between that save and the script author verifying the change is imho irrelevant for the script author. The Sling IDE is already supporting such a workflow for developing a bundle: You change your java code, hit save and the bundle is automatically and instantly updated without any additional action of the developer. I think as long as we have a similar workflow for a script author it doesn't matter whether the script gets compiled, put into a bundle, is transferred through hyperspace or whatever. As long as this process is very fast and nearly not noticeable. And ideally such a workflow should not be tied to a special tooling, so supporting a save in any editor would be ideal. The proposed add-on solves some problems and if enhanced could potentially solve some other problems as well. I think it has a lot of potential. And I agree that the script author experience needs to be enhanced. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
