Re: Next Gen JDEE
[email protected] (Phillip Lord) Fri, 17 Jul 2015 12:09:04 +0100
| Newsgroups | gmane.emacs.jdee.devel |
|---|---|
| Message-ID | <[email protected]> |
(Resent after bounce -- apologies for lateness) Oh, gods, really? Well, I just send a very long email suggesting a future. If no one else is willing, I will have a go at this. Probably, I should "port" the whole lot to use rx.el as this may be a bit more maintainable. Does it handle annotations correctly? I am not going to ask about lambda, since the answer must be no. Also indentation? This one I will not volunteer to do, since I never really learned the indentation engine for CC-mode. Phil Paul Landes <[email protected]> writes: > Is there anyone available that knows font-lock well able to bring JDEE up to > 1.8? I still lacks 1.5 generics fortification, which seems like a big one to > me. > > > On Jul 14, 2015, at 12:27 PM, Przemysław Wojnowski <[email protected]> wrote: > >> On 14.07.2015 15:57, Paul Landes wrote: >> [...] >>> - Inertia: without a lot of activity there's less interest >> Migration to GH is important step in good direction. >> >>> - Popularity of Java: Java is much less popular, and thus, used. >> That said, I think for us who use it less we still need it much like a C >> programmer might still at times need to view or modify bits of assembly. >> Out of curiosity, what is your primary language? >> Anyway, Java is one of the most popular languages and AFAIK very strong >> in corporations. >> >>> Again, my earlier plans were to create a brand new project and port >> over pieces from JDEE. Starting new I think is necessary to start the >> ball rolling where as a major refactoring of the existing code base >> would be an up hill battle against the mentioned inertia of a large project. >> [...] >>> Question in order of importance: >>> - Who has the time and initiative to help out (I can't do it all >> myself with current time constraints) >> To start a new project (even with some existing functionality) is a lot >> of work and without someone spending substantial time on this it won't work. >> IMHO it would be better to set clear goals for the project and refactor >> in small steps towards the goals. This way it is doable, because anyone >> can contribute small parts, knowing what to do. >> >> This way on another, automated testing is crucial for maintainability of >> any bigger-than-hello-world project. >> >> Cheers, >> Przemysław ------------------------------------------------------------------------------ _______________________________________________ jdee-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jdee-devel