|Re: [ide-dev] A story of Handly and MelnormeEclipse
My dream is that, eventually, not only DLTK but also the likes of JDT and CDT could benefit from the reusable components and uniformity offered by Handly. Yes, we're aiming that high ;-)
As I read it, I really have the impression that Handly should be inside DLTK, as one of its modules. Handly would really take much advantage of it.
I'd rather keep Handly separate for the time being, with perhaps moving parts of it down to the Eclipse Platform (LTK?) eventually. I believe that it is not necessary to be part of another project to be used by it, right? :-) I mean that DLTK could depend on Handly, not the other way around. (Handly is really much more generic while being much narrower in scope.)
By the way, that would be nice if you can include JSDT in your radar. As you know JSDT was made as a clone of JDT but there are actually many things that do not map correctly and make JSDT maintenance more complicated than it could be. So if you identify parts that could be easily improved thanks to Handly and/or DLTK, without requiring huge refactorings, feel free to speak up on the wtp-dev mailing-list.
Sure, I'll try to find the time to look at that after Handly 0.5 is released. Thanks for the hint and the valuable discussion!
Back to the top