Mirko Stocker wrote:
Currently, we are analyzing the RDT-code and are looking for a point where we
can add our extensions. Can anybody give us some advice?
I'm wondering how you're planning to do the analysis; work directly with
the JRuby AST or use some abstraction?
Using something like Parsetree
(http://www.zenspider.com/ZSS/Products/ParseTree/ ) would be easier, I
guess,
but Parsetree is Native Ruby only (at the moment... HintHint).
Have you found some libraries for creating control flow graphs for Ruby
code?
Is there any architectural documentation? Where would be the best place to start? We are
grateful for any information :)
I'm not speaking for the RDT guys, but I guess you could contribute a
Refactor Menu to the context menu or the main menu bar;
and make this menu only active for the RDT editor of if a Ruby file is
selected.
Some of the smaller ones (rename, ...) could be QuickAssist-style
refactorings, instead of only living in the Refactor menues.
BTW: if you want a nice way of getting to know the RDT project model, I
can recommend (shameless plug) EclipseShell
http://eclipse-shell.sourceforge.net
If you look at some of the screencasts for it
http://eclipse-shell.sourceforge.net/screencasts.html
you'll see that it's much easier to get to know the RDT project model
with an interactive shell, than by looking
at it's code or writing static Java code that uses it (at least that's
my experience).
murphee
--
Blog @ http://jroller.com/page/murphee
Maintainer of EclipseShell @ http://eclipse-shell.sourceforge.net/
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
Rubyeclipse-development mailing list
Rubyeclipse-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development