Re: [RDT-Dev] Eclipse 3.2 Features and backwards Compatibility

2006-08-01 Thread zdennis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Markus Barchfeld wrote: I would neglect backward compatibility to 3.1 for the sake of simplicity. I agree with Markus. And on the terms of upgrading, is there an easy way to port plugins of an existing eclipse 3.1.x installation to 3.2 wi/o having

[RDT-Dev] Cheatsheets

2006-08-01 Thread designker
Hi,The JDT keeps its cheetsheets in org.eclipse.jdt. They are also reused via the tutorial so this seems to my (naive?) eyes sensible.RDT has its current cheetsheet in org.rubypeople.rdt.debug.ui. I guess the logic here is that it uses some part of the debug UI? What would be the issues of having

[RDT-Dev] Broken Overview and Tutorial

2006-08-01 Thread designker
Hi,After messing around with org.rubypeople.rdt I have fixed the RDT Overview and Tutorial that no longer appeared as of RDT 0.8. I am not 100% sure I have fixed it all as the org.rubypeople.rdt.doc.user that is in the trunk has an empty HTML folder and I think that is where the RDT help should

Re: [RDT-Dev] Eclipse 3.2 Features and backwards Compatibility

2006-08-01 Thread David Corbin
On Tuesday 01 August 2006 11:25, zdennis wrote: Markus Barchfeld wrote: I would neglect backward compatibility to 3.1 for the sake of simplicity. I agree with Markus. And on the terms of upgrading, is there an easy way to port plugins of an existing eclipse 3.1.x installation to 3.2 wi/o