Re: [RDT-Dev] Remote Debug project
Martin Krauskopf wrote: Thomas E Enebo wrote: I would write this specification using unit/test API compatiable tests. This could still serve as a specification and plug straight into our testing framework (we (JRuby) are moving to miniunit/test/unit tests). Having small pass/fail tests will make it easier for us to support this effort. Yes, this is what I'm beginning to work on. It will be bunch of small -Test::Unit::TestCase-s which will be testing every corner of the protocol, runnable against whatever Ruby implementation. So it will as well catch every incompatibility in JRuby vs. CRuby then. Which is also the case now but little cumbersome since one more Java layer. I'll still be filling bugs into your IssueTracker with minimalistic test-cases. That's a great idea, this should help to fix some of the remaining issues with JRuby's tracing implementation (line numbers, bindings) and show the JRuby work left for compatibility with CRuby. Could you make this stuff (tests, etc) available on the net, over at RubyForge or wherever is convenient. I want to chip in some work for that, but I can't justify too much right now - the JRuby RDT plugin offers to many chances for features. One thing I'd like to look at is the Bindings problem - ie. RDT can't show Variables for a JRuby process, because the JRuby tracing system doesn't provide the right type of object. Having a basic Test system available would be nice. murphee -- Blog @ http://jroller.com/page/murphee Maintainer of EclipseShell @ http://eclipse-shell.sourceforge.net/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
Re: [RDT-Dev] State of RDT
Christopher Williams wrote: On 1/22/07, Werner Schuster (murphee) [EMAIL PROTECTED] wrote: VM - I have two (Standard, JRuby) and was surprised that the OK button wouldn't get activated - until I chose something from the combo box; The Add VM Dialog seems a bit too strict about having the user choose a Do you mean until you checked one of the boxes? Never mind, it seems to have been fixed in the current trunk. Another issue: I'm not quite sure how the lookup system for different VMs works - it seems like it tries to lookup some VM configuration based on the project, and if it can't find anything there, it falls back to the DefaultVM (which is the one checked in the Ruby Interpreter Prefs). This means: - I have a C/Ruby Interpreter set as the Default VM - I have JRuby Interpreter set up - when I do a Launch and tell it to use JRuby, this lookup system will fail and just return the Default VM; If you want to see how additional VMs behave in the GUI or interact with the VM system, my JRuby stuff is available at: :pserver:[EMAIL PROTECTED]:/var/cvs/rdt-jruby I saw some locations you marked with some comment about Not knowing how to quickly start Ruby (I think it was somewhere concerned with Ri). I didn't quite get that; In a few locations we start up ri and rdoc. Before we used to get a handle on the default VM and execute it that way. Now with the new API that won't fly so for a while I wasn't sure how to fix it. I did manage to figure out a way to execute those now. Great; Just for the record: a Standard C/Ruby needs to be used for the RI and Rdoc features; I once set a JRuby installation as my default Ruby Interpreter, and the Ri/RDoc features broke (seems like Ri doesn't work in JRuby) and there were frequent 100% CPU usage periods, which came from the TextHover launching JRuby (heavyweight...) and trying to get the Ri for some code. Question: What timeframe for a release do you have in mind? I'm mostly interested if you want to add some more stuff before 0.9 or if the current state == 0.9 (of course, after the changes had some time to settle down); I'd like to add some small extension points (QuickAssists/QuickFixes and an Extension point that might allow to add more Compilers to the Builder process). These could go into 1.0, if the 0.9 release is too close, but they shouldn't interact badly with the RDT features. murphee -- Blog @ http://jroller.com/page/murphee Maintainer of EclipseShell @ http://eclipse-shell.sourceforge.net/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
[RDT-Dev] AST from Editor
Chris and all RDTers, is there any standard way of getting from an Editor - JRuby AST? I am basically just getting the String from the Editor/Document, and then running the Ruby Parser on it... but this happens for various systems (Outline, Syntax Coloring, Realtime Lint, etc), it'd be convenient to cache a copy of the AST somewhere. Whenever a change happens in the editor, this would be updated. The Builder could use this as well. murphee -- Blog @ http://jroller.com/page/murphee Maintainer of EclipseShell @ http://eclipse-shell.sourceforge.net/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
