Community
Participate
Working Groups
The save actions options (in the java plug-in) is great! However, it would be fantastic if a generic set of save options could be applied to all files. Tasks such as removing trailing whitespace etc. are more or less common for all types. Thanks!
It would need to be pluggable--WTP has "Clean Up" functionality as well.
Yes, of course. However, we probably won't have time to work on this for now.
This enhancement - making the clean-up profiles API/UI and save participant mechanism extensible and part of the platform - has a strong vote and support from the WTP XML Web Services team too. We can work closely with our WTP SSE friends and be early adopters. Shouldn't anyone from the JDT team be ccd as well?
>Shouldn't anyone from the JDT team be ccd as well? The Text team covers/watches Platform Text and JDT Text.
Sorry, we have to shift this to M5.
Depending on what clients expect from the generalized solution, different approaches will be needed. When to trigger: * on save in editor + can choose simple save using Text editor - save actions are not executed, e.g. doing a refactoring * on save of a file of a certain content type + works whenever that file is saved - user no longer has simple text editor - can have unexpected results/breakage for existing clients that don't expect additional operations done on save - expect more troubles/conflicts with this approach Currently, we trigger it when saving in the Java editor but some people also want it when touching the file with a refactoring (see e.g. bug 244458). ==> Both approaches are appealing. We probably need a registry with save actions and clients can then either honor them or not, i.e. opt-in instead of always doing it when a file is saved. Where to add the hook: * file buffers * saveable * document provider * editor * combination of the above Currently it is in the document provider with the exception of error reporting to the user, which is in the CU editor. Other issues: * I think project specific settings are needed for save actions to be usable but currently this is not supported by Platform UI. We would have to provide this as well. * do we only want a save action hook or is the whole clean up stuff required? * relation between clean up (profiles) and save actions: in JDT we have clean ups and save actions (which are able to run most but not all of the clean ups). Clean ups are stored in profiles but the save action is currently not able to use/specify a clean up profile (see bug 178429). Unfortunately, given the open questions/issues and other priorities we won't be able to do this for 3.5. Sorry. Nevertheless, I encourage interested parties to comment in this bug what their concrete expectations are (e.g. execute per content type or only when in a certain editor).
I would like to see something like this investigate in 3.6... PDE would love to take advantage of this.
Need removal of trailing whitespaces.
Ok, as an interested party I want trailing whitespaces to be stripped off in edited lines for all text files by default. I do not care about any other Save Actions for now, but I really don't want any other edits to happen without my review. This makes me think that perhaps it is not a save action that should strip whitespaces, but the text editor component that should do it once I leave the edited line.
Still missing "Save actions" for e.g. HTML, XML and others. Is this still in progress?
(In reply to Markus Rathgeb from comment #10) > Still missing "Save actions" for e.g. HTML, XML and others. > Is this still in progress? No one is working on this.
