Actually, I think they'll probably add support, but the problem is 'when'... Also, in the eclipse development, they start with java, and extend as requests come... in my case, the request was deffered for the next release (
3.2), but they gave no mention on when would it be implemented...
Also, there's a generic core, but it is not so generic as one would expect... I mean for basic stuff, it really gives a good support, but after you want things that where not initially thought of, it might be kind of tricky to get it... So, you'll usually end up with a lot of code, just trying to get rid of some indirection layers they put in the way ;-)
In the end, I think they do have interest in making those APIs, the problem seems to be that the 'process' they have to keep things in order slows it down much more than it should...
I mean, I had a request, implemented the code to do what I asked, submitted it, and they didn't add it to the core API because it was the last day for API changes in the 3.2 release... so, that makes that request frozen for a some months until they do consider it again ;-(
Unfortunatelly, what keeps happening over and over again is that I really have to 'hack' Eclipse to get what I want from it... on the other way, fortunatelly, the code is all there so that I *can* hack it ;-)
On 2/20/06, Fabio Zadrozny <firstname.lastname@example.org> wrote:
Yeap... probably making my own shell instead of the one Eclipse uses would make it easier... it's api still does not make it possible (and I wonder if it ever will).
I don't know much about Eclipse (I just downloaded it to try out pydev), but I thought it was supposed to be a pretty generic IDE backbone. If that's the case then you'd think they'd be interested in providing good core support for the many dynamic interpreted languages that are out there. The features you want (and we users are asking for) are the same ones one would want in a debugger for any interpreted language, perl, ruby, python, etc. I can't imagine that the Eclipse developers would refuse to add a few API hooks here and there if it makes support for those languages better.
Or is it more like a generic backbone in theory, but in practice all the developers are mostly Java users, so that's all any of them care about supporting?