Paul Landes <lan...@mailc.net> writes: > I'd like to bring up the topic of a major refactoring. I don't think I'm in > the minority in the mode of thinking that JDEE needs a major refactoring > given: > > - Girth of the project: it's a lot to maintain and various plugins might not > be used any more > - Inertia: without a lot of activity there's less interest > - 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.
Java is pretty strong in the enterprise segment. > 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. > > To reiterate from a previous thread, some top level ideas: > > - Replace beanshell with clojure This would be nice. Heres another alternative: http://openjdk.java.net/jeps/222 > - Replace semantic with some Java based parser (maybe compiler like > ASM)--however all fly compilation and syntax correction etc happens in > Java. This includes more advanced high lighting. I would advocate using the CEDET infrastructure, of which Semantic is a component. > - Entire project becomes an Emacs plugin What does this mean? > - Move to a plugin approach so each add on is a separately maintained Emacs > plugin. If someone wants to resurrect jde-debug from JDEE into the new > version, then that person creates a new Emacs plugin that fits in some next > gen JDEE plugin architecture. This gets rid of some bloat ini the core next > gen JDEE. > > 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) > - Should the project have a new name or carry the same name? My feeling was > start a brand new project for the purpose of name space and maybe create more > "buzz" as a "new" Emacs java development library. There are other new emacs java environments, so it can be argued using the jdee name is actually a strength. > > Given all of this, I'd like to hear others opinions how to proceed with > JDEE--especially from the previous contributors of JDEE, which I've seen more > of lately. > > Regards, > Paul > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/_______________________________________________ > jdee-devel mailing list > jdee-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jdee-devel -- Joakim Verona ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ jdee-devel mailing list jdee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jdee-devel
