I agree with Carsten, this seems to be an implementation detail. That said, this doesn't mean it is not important provided we would think it can't be resolved in a reasonable way.
However, towards that end, I think that in the first place, it should be easy enough to takle via tooling and in the second place, we could even make it reasonable the same experience. It should be easy enough to create a "bridge" bundle that monitors folders in the repository and processes their content on change the same way the provided maven plugin does. Subsequently, it would turn around and install/update a surrogate bundle with the script and the metadata. That way, you'd be back to where you've been before namely, save a script, refresh, done. The benefit too of such a bridge would be that it'd be yet another add-on (to the add-on) - hence, if you don't install it in production you don't have to worry about it (and provide the scripts via bundles) while during development (or a funky - "we rewrite ourselfs dynamically" - production) you can just install that bridge and work on the scripts from the repository like today (just have to follow the new layout). regards, Karl On Fri, Apr 27, 2018 at 9:40 AM, Carsten Ziegeler <[email protected]> wrote: > 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] -- Karl Pauls [email protected]
