We have created ee-ide because we want to bring the benefits of antegram for java and antegram for web to a vast majority of users that can’t afford using XML annotated code for a variety of reasons. To this effect, we have designed ee-ide following some principles:

• Class outlines - ee-ide lets you view class outlines from within the ide so you don’t need a doclet generator. Class outlines were the original idea that made antegram so convenient to use and productive.
• Non overlapping windows – non overlapping windows make it easy to compare and transfer source code across files and keep handy all the packages and classes you need. Again, this was part of the original antegram concept.
• Pretty much language neutral – a lot of what works in ee-ide, including consistency checks and hyper-navigation, works for many languages, including languages that may not exist yet. We are pursuing this approach. Similarly, ee-ide  provides an easy way to run command line tools, so you’re not bound to built-in facilities
• No project files - so called projects are a bore to set-up. We’re not planning on using project files. Instead we’re designing ee-ide to learn about your code. From time to time, ee-ide may ask you questions when it can’t find your stuff, we’ll keep it in plain english
• Keyboard navigation – we’re designing ee-ide to work well whether you want to use a mouse or not (just try CTRL+UP for a test).
• Simple, data-centric interface. ee-ide is about source code. We’re not overloading our interface with menus and features that you never use.
• Extensibility with a minimal learning curve. We are using a ground-breaking programming technique which probably makes ee-ide the fastest, least committing IDE to integrate with.

Yes… we’ve been told over and over that with E……, JB…… and N..B…., nobody needs another IDE. Surely we need another IDE. We need innovative products that support our workflow.