[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[photran-dev] Refactoring the refactoring engine
|
I have some major changes to Photran's refactoring engine that I would
eventually like to commit. This includes
(1) A much, much easier way to add refactorings to the UI. For simple
refactorings, you can write only one class (the Refactoring), add one
line to the plugin.xml file, and it will "auto-magically" appear in all
the correct menus and run a simple wizard. No need to write a separate
user interface (Action) class, unless you need/want to. Or, if you want
to contribute the refactoring the old (hard) way, that's fine too.
(2) There will be six new projects in CVS. The language-independent
parts have been isolated into separate plug-ins that we're reusing in
refactoring tools for other languages.
(3) I also want to reorganize the packages and folders in the
org.eclipse.photran.vpg.tests project, which is a total mess.
For the most part, these changes won't break existing refactorings,
except that
(1) the Refactoring class constructors will change, and
(2) any changes you've made to plugin.xml in the
org.eclipse.photran.ui.vpg will have to be re-done -- they won't merge
with these changes.
Since our release has been postponed until the end of November (cf. PTP
monthly call yesterday), this seems like a good time to put these
changes into CVS.
So, what is everyone's opinion? Is this an OK time to put them in, or
should I wait? I am particularly interested in hearing from Kurt,
Bruno, Stas, Daniel, Mariano, and Greg. If you have any objections, I'm
fine waiting a while longer.
Jeff
