Re: [jdee-devel] Next Gen JDEE
Brought to you by:
paullandes
From: Stephen L. <ste...@st...> - 2015-07-15 18:31:08
|
Paul Landes <la...@ma...> writes: > Keep in mind that this would ideally work from Cask, which I agree > with others is the direction we should move to. What is Cask? A web search turned up barrels and the Cask of Amontillado, but nothing that seems relevant. > JDEE2 (next gen) has been selected as the fork given the popularity of > keeping the name. +1 > I'd like to keep the emacs binding namespace. Currently everything is > `jde-' since the original name was "JDE" until Sun lawyers made us > change the name. > > The more different the namespace the better. Here are a few ideas: > > - `jdt' as short for "JDEE [Version] 2" > - `jdn' or `jden' for JDEE Next Gen For the Ada mode rewrite, I just kept ada- as the prefix; there was no intent to allow both packages to coexist in one Emacs. I also kept the main user customization variables, to help ease the transition. If we can produce a reasonably functional jdee2 in a short time, that's a reasonable approach. I suspect there are many more (and more demanding) jdee users than Ada mode users. And since some of the tools are in Java, you'll want a functioning jde while working on the new one, which argues for a different namespace. Another thought is that three letters is too short for this purpose. How about 'javad' (for Java Development; could be confused with Debugger). Or 'javde' (pronounced "javdee"); that has a nice ring. Or 'jde2'; hints at a possible jde3 sometime :) > I'd also like to separate as much as possible so I think we should > create a separate repo. That will simplify things a bit, particularly if there is a different workflow for the old project (in maintenance-only mode) and the new (in rapid development mode). -- -- Stephe |