Community
Participate
Working Groups
This is something to think about for the future.. I would like to be able to format my plugin.xml file, in the same way as with the JDT and java source files. This would involve having a preference page for the style/formatting, then hitting CTRL-SHIFT-F would reformat my plugin.xml file in a nice consistent format.
Janek has implemented the format MANIFEST.MF functionality and will concentrate on the format plugin.xml functionality at a later date. Work done with respect to the format MANIFEST.MF functionality * Moved the "Format" context menu entry to the top-level under "Open" action - added mnemonics * Refactored "Format" context menu contribution to the PDESourcePage - disabled contribution for all pages except the BundleSourcePage * Added Format manifest action to the PDEFormEditorContributor class * Created extensions to implement the Ctrl+Shift+F key binding - disabled key binding for all pages except the BundleSourcePage - externalized all strings for extension point names and descriptions * Refactored FormatManifestAction to the actions package - created new interface for PDE editor action definition IDs See attached Patch #1
Created attachment 44924 [details] Patch #1
Thanks for the patch - released.
Reopening for XML related enchancements...
*** Bug 152991 has been marked as a duplicate of this bug. ***
*** Bug 207995 has been marked as a duplicate of this bug. ***
Hi Mike, just checking in :) I was wondering if you have found time to work on this bug. If your other work is taking all your time please let me know and we can go ahead and take care of it.
Any progress on formatting plugin.xml files? I'd really love to see this. Looking into plugin.xml files really can hurt your eyes at times, mostly due to formatting issues (using tabs and spaces on the same line and stuff like that).
Unfortunately no. Haven't been able to find spare time in a long time to do PDE work. As a result, I will return this back to the inbox.
Not planned for 3.5
*** Bug 293761 has been marked as a duplicate of this bug. ***