[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ide-dev] A story of Handly and MelnormeEclipse
|
Hi Mickael,
Thanks for your valuable suggestions!
Regarding Handly, I think another part of the problem is that the current design makes it difficult to adopt Handly in projects that must maintain backward compatibility with their existing model API. It is possible with the model adaptation facility introduced in Handly 0.4, but it is rather complicated in practice.
However, big changes are coming to Handly 0.5 (Neon time-frame), which will hopefully make it much less invasive with regard to the model API, so even well-established projects could use Handly if they would so like. Please see this thread for details, if you are interested:
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 ;-)
Best regards,
Vladimir
On 03/11/2016 09:22 AM, Vladimir Piskarev wrote:
Hi,
Hi,
Part of the problem is that it's not easy to find an effective communication channel that parties interested in IDE development and Languages Tools Factorization [4] are listening to.
That's right. And this mailing-list tends to be one of this channel, but I don't think it's the only one to consider. Project-specific mailing-lists (jdt-dev, dltk-dev, cdt-dev...) are to consider as well, and many people interest about Language Tools Factorization aren't following there.
This mailing list appears to be the best available channel for this, but I must admit that I didn't know about it when the Handly project was started, and Bruno also said it had took him quite a while to find out about it. So there might be other people potentially interested in this topic who, however, don't know about this list either.
Perhaps it might be worthwhile to think about if and how the ide-dev list could be made a bit more visible, given that it has no corresponding project and thus no obvious place for newcomers to discover it.
Sure, do you has suggestions to improve that?
For the use-case of Handly, I would suggest you get closely in touch with DLTK if you're not already. Despite the D (for Dynamic), DLTK contains several language-neutral components. It seems to me that the relationship between both project is strong (maybe even worth considering making Handly a module of DLTK to benefit from its community of users and developers).
Cheers,
--
