Showing posts with label technologies. Show all posts
Showing posts with label technologies. Show all posts

2008-12-28

Screen Flows support released

It took a while longer than promised, but now I am happy to release the screen flow implementation I talked about at Eclipse Summit Europe '08 to the public.

Just go to http://code.google.com/p/screen-flows-in-eclipse/ and you should find both the presentation as well as all the needed sources. If you find any problems with the implementation or just find a way to enhance them, then please free to submit your changes.

2008-07-16

Missing Books considered harmful

A very large percentage of of my customers are just starting to use Eclipse and Eclipse based technologies for their applications. So apart from having the basic 4-6 days training in RCP, EMF, GMF, etc they all have have one common and very important question: "Which books should we buy?"

And that question has become increasingly difficult to answer lately.

There are a number of absolutely good and noteworthy Eclipse books, but almost all of these are not up-to-date and that can be a major problem for people that need a good reference guide and best practices guide to Eclipse.

Almost all of the books on Eclipse are one or two versions behind the current baseline and that means the readers will not be able to take advantage of the new and improved stuff. And consequently they are rather frustrated when the only source to the new functionality is... the source.

Yes, I do know that many of the books in question are under revision and expected to be here any time soon, but even these revisions are delayed - in some cases as long as a year. And yes, I do know that the authors of technical books do not get rich from their work, so they have little incentive to update their books.


But there must be something that can be done about this. Just consider the number of books that are marketed by Microsoft on their many technologies and consider which role these books play in many developers life.
Before you start: yes, most of Microsofts software is closed source and consequently you need the books... but why should you have to read though 8-12 millions lines of code to understand just what the new and much improved APIs do?

I would suggest that we add a new criteria before an incubator project can graduate: there must be a book or at least a number of authoritative articles on the project. And for each new major release, there must be an official update of these...

Whether the foundation should be part of this work or not, I don't know. I can easily see arguments for both...

2007-05-15

The next major Eclipse technology

The Eclipse Universe includes a very large number of tools and technologies. This is - in one sense - one of the best testaments to the success of the platform. But it is also one of the most infuriating aspects of the platform, when you make a living as a Eclipse service provider.

As an Eclipse service provider, you are always expected to know more about the different Eclipse technologies than what you customers know. And you are expected to be able to give advise about which technologies your customers can/should/could use to solve specific problems.

If you provide training based on the Eclipse platform, some things are obvious. You must have training in RCP as this is the basis of everything else. And we have seen GEF and EMF both being used in many very diverse projects - both are now part of the must-know technologies of the Eclipse Universe and consequently you must have training for these technologies.

But then it becomes much more difficult. Which technology or technologies are next in line?

BIRT? Business Intelligence is a very hot term, and BIRT does support some very basic abilities in this regard, so...?

GMF? Being a combination of EMF and GEF, GMF seems a logical candidate.

Or is it EMFT, M2T, TPTP, ECF, RAP, Higgins or something else?

One can argue for any of these as the next hot technology. It is so difficult to figure out, which Eclipse technology that will be the next important thing, that we must have training for.