As I put the finishing touches on one of my presentations for EclipseWorld 2008 on this, the last day of blaugust, I'm reminded of how far the resource model in EMF, and in the Eclipse platform itself, for that matter, has come over the past few years. Nearly gone are the days where applications assume that everything is on the local file system or that a file extension dictates the content of a resource...
And, after reading Kevin's blog entry about declarative styling, I'm excited about how much farther we may yet be able to go. e4 will indeed change the way we, and the industry as a whole, think about Eclipse; if it doesn't, I believe it will have failed. I'm anxious to start making contributions, particularly in the area of the new platform's resource model. How do you plan on contributing to the future of Eclipse?
PapyrusUML: Papyrus UML support in Hawk
14 hours ago