Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [e4-dev] Do We Need a Book?


Am 09.01.12 17:34, schrieb Stefan Mücke:
> Hi Eric and Mike,
> I think that before you invest resources into writing a book, you should provide good documentation (by updating and supplementing the existing documentation). Without good documentation, I would think twice before adopting Eclipse 4.
> Also, there are many things that are *far* more important for Eclipse 4 than having a book. One thing is polishing, of which there is clearly still a lack in Eclipse 4.2. Another point is performance, especially start-up performance. This might not be important for the Eclipse SDK and for some huge business applications, but for ordinary RCP applications (like RSSOwl), this is very important. On my second computer, a Mac mini (Core 2 Duo T5600), Eclipse 3.6.2 takes 6.5 seconds to start, and Eclipse 4.2 M4 about 9.5+ seconds (both are warmed-up times).

Agreed - getting Eclipse 4 out with max performance and stability is the
most important thing. There are many areas to improve starting from
memory leaks to stuff like closeing of editors.

> The workbench still lacks features regarding DND. For example, when you drag the Package Explorer somewhere else, you cannot restore the original position, because the window's border is no longer a drag target as in 3.x.

Hm - just tried and it worked

> Another thing that really bugs me about Eclipse 4 is that it constantly allocates memory in the background. When you enable the heap status, you can observe this. This is because Eclipse does some polling of certain context values in order to implement lazy plug-in activation. However, there is something inherently wrong with this approach. There should be some other mechanism that is triggered when context values have changed or might have changed.
> A few days ago there was a blog post on Planet Eclipse about "Butterflyzer" where the developers ported their code from 4.x to 3.x because Eclipse 4 is just not ready, which is very sad. Quote: "... E4... and isn't quite mature enough yet".
> Source:

If I read this correct they did not port their code from 4.x back to 3.x
but created their own RCP like framework which though I can understand I
think if they would have invested their time into EAP they would have
provided value to everyone.

> Instead of using the E4 workbench, they adapted the old E3 one. I am planning to do the same for my RCP app.
> In September 2010, I created an updated outline of what I would like to find in the documentation as an RCP developer. I hoped this could help start the documentation process, but there's still no E4-related documentation in the Eclipse SDK's online help. Here's the bug with the outline:
> IMHO, writing a book about Eclipse requires something like the original "Eclipse Jumpstart" team at IBM. Ideally, the existing and excellent book "Java Developer's Guide to Eclipse" should be updated (see However, it is obvious that this would require a *huge* effort and quite a few people.
> Bottom line: Please don't waste resources on writing a book before the Eclipse 4 platform is really ready for prime time.
> My two cents. Best wishes and Thank you for all your efforts!

I hope I can find some more time in next weeks to restart contributing
to Eclipse 4.x but doing my JavaFX stuff is high on my list as well.

B e s t S o l u t i o n . a t                        EDV Systemhaus GmbH
tom schindl                 geschäftsführer/CEO
eduard-bodem-gasse 5-7/1   A-6020 innsbruck     fax      ++43 512 935833                      phone    ++43 512 935834

Back to the top