Eclipse DemoCamp Hamburg 11/2009
Join the DZone community and get the full member experience.Join For Free
the eclipse democamp in hamburg was a huge success - more than 110 people signed up and most of them actually showed up at the event:
the program was packed with interesting talks and we were lucky to be able to present some very well known speakers:
- tom schindl: e4 - a short overview
- jan köhnlein: combining graphics and text in model editors
- jochen krause: rap
- nils hartmann, gerd wütherich: fifty ways to build your bundle...
- ekke (ekkehard gentz):redview - dynamic views for business applications
if you were not lucky enough to attend the democamp, here is a short summary of the sessions:
e4 - modeling meets runtime (jochen krause on behalf of tom schindl)
tom schindl couldn't attend the democamp due to heavy snow in innsbruck (the airport was short of planes to fly out, actually). after a short vcon with tom, jochen krause held the e4 demo on tom's behalf.
e4 has three principal aims:
- simplifying the eclipse programming model
- enabling the platform for use on emerging web-based runtime technologies
- and broadening participation in development of the platform
one of the measures to make programming eclipse easier is to define a list of core services and make sure they have a really decent api. this list of services is called "the 20 things" (see the eclipse wiki for more information ).
you might have heard that emf is playing an important role in e4 and i think it is one of the most amazing things about e4 that the entire workbench is modeled, of course using emf. actually, you can change the workbench at runtime by just modifying the underlying model at runtime. i think it is very exciting to see modeling and runtime technologies converge in this project.
e4 also makes massive use of dependency injection, which allows for a flat object model (instead of providing a subclass for every special feature, you can just inject other classes providing that particular feature). we had a discussion about dependency injection. jochen showed that several methods in e4 use string-based dependency injection, which of course leads to several problems. sven pointed out that this is not a di problem per se and suggested to use interfaces to alleviate the situation.
heiko raised the question of whether we should have a dedicated session on dependency injection at one of the next democamps:
jochen continued his session, explaining how the e4 ui is being rendered by a presentation engine which can be configured using various renderers, each one providing an individual look and feel.
e4 is the future of eclipse, and jochen concluded his talk by pointing out that in order to ensure e4 has a sustainable future, companies and individuals should participate in the development of e4. this can be done by:
- playing around with e4 and providing feedback
- participating in the development process (see the e4 project homepage for more info)
- paying existing committers (see tom's blog posting to learn how to buy one and get one free)
more info on e4 can be found on the eclipse wiki .
after the talk, we had a short break to set up the next presenter, enjoy some refreshments and, of course, socialize:
combining graphics and text in model editors (jan köhnlein)
after the break, jan köhnlein took stage and told the audience that graphics and text and no different, but really are just two views on the same thing:
jan pointed out that both text and graphics have their relative virtues:
- provides a detailed view on things
- can have a very formal syntax
- can be typed using standard text editors
- can be managed using standard versioning mechanisms (merge / diff)
- can be typed fast
graphical representations on the other hand...
- provides high-level views and a good overview
- suggests non-formalism
- requires custom editors for your graphical notation (i.e., you need to write them)
- has no good support for merging / diffing
- requires the user to use a mouse a lot, and thus is slower than a text editor
apparently, both have advantages, so why not use both?
in the following 5 minutes, jan gave an ultra-quick introduction in how xtext (as a representative of a textual modeling toolkit) and gmf (as a representative for a graphical modeling toolkit) work. the bottom line is both use ecore metamodels, so we should be able to combine both.
it turns out, however, that xtext and gmf metamodels are slightly different and you need to take some precautious steps in order to make them interoperable.
after this excursion into the theory behind the convergence of graphical and textual editors, jan showed two editors, one graphical and one textual that synced live. changing the model in one editor and saving it effected an immediate update in the other editor - really neat.
jan pointed out that this is all very fine, but sometimes you really want to have a tight integration. as a proof of concept, he showed a gmf-based editor with an embedded xtext editor: as soon as he pressed f2 to edit a field in the graphical editor, an inline xtext editor would pop up, featuring syntax highlighting, code completion and error markers - really awesome!
all these exciting things must have made people gasp for air, because the oxygen level in the room was very low at the end of the session, so we had another break. as always with gathering like this, hallway talks very equally important as the sessions, and people made good use of the break:
rap (jochen krause)
jochen's presented his talk on rap without a single slide - "in the tradition of the karlsruhe democamps", as he pointed out.
no technical session without some history and some theory, so jochen first explained that rap implements the half object pattern and demoed the very first version of rap. while running an eclipse ui in the browser is all very exciting, feedback from initial users wasn't too positive: "please spare us this look'n'feel in the browser!"
so the good people at innoopract (now eclipsesource) spent some time to implement custom styling for rap uis, which jochen showed in his second demo, which he called "the enterprise look'n'feel" due to it's feasibility for enterprise applications.
the third demo featured "rounded corners" (see rap new & noteworthy ). while this might seem like little gained, jochen explained that implementing rounded corners was both important on an acceptance level and challenging on the implementation level. would you have thought that rounded corners are implemented using css on firefox and vml on internet explorer?
of course, rap is implemented as an open source project at eclipse, welcoming any contribution from users worldwide. jochen demonstrated how great the open source model works by showing off a ribbon-style command bar for rap which is available on google code (see the rapit project home page )
in the next demo, jochen showed how he integrated emf and rap. his goal was to rapify the emf tree editor for emf models. it turned out that basically it is very simple to convert the emf editor (or any other eclipse plug-in for that matter) into a rap application - only very little adjustments were needed. however, as web applications are multi-user applications by definition, additional care has to be taken when converting editors. as eclipse is a single-user application, editors are not prepared to be executed in a multi-user environment. jochen explained how he tried to use cdo to store the edited models on a remote server, but failed due to the complexities of cdo. he succeeded by using couchdb , a database written in erlang and with an http interface (look ma - no jdbc driver needed!).
jochen concluded his session with a few notes on features they've just completed (drag'n'drop) or which are not available (yet) like gc.paint.
after that, he took some of the audience's questions, e.g. "how many users can a rap server take?". of course, it depends, but you can roughly count 1mb per user and workbench.
jochen thought it would be ok to continue without a break, but martin decided we should rather have a short break to let in some air.
more information on rap can be found on the eclipse wiki and on the project homepage . jochen's company eclipsesource provides professional services, training and resources around rap, so have a look at their website.
50 ways to build your bundle (gerd wütherich & nils hartmann)
after the "short" break, gerd wütherich and nils hartmann presented their view on build management: "fifty ways to buid your bundle":
facing the fact that nobody seems to be too excited about build management these days, they decided to arrest people's attention by adapting the well-known story " a christmas carol " by charles dickens . a brilliant idea, which really made people laugh at various points throughout the presentation.
the presentation was subdivided in three parts:
the ghost of build past
gerd and nils explained how in the past, people have been building bundes using pde build, using a manifest-first -approach. building bundles with pde build is rather cumbersome: you have to setup map files in order to help pde build to derive ant build files which will then be executed by the antrunner inside eclipse. while this ensures the build process sees exactly what eclipse sees when you develop your bundles in the workspace, this basically makes debugging your build process very complicated.
the ghost of build today
today, we've got bundles everywhere and osgi is being used not only for eclipse plug-ins, but also for conventional applications. as good programers obeying the dry principle , we want to have a redundancy-free description of our build artifacts, i.e. derive build dependencies by looking at manifest.mf . in the enterprise, things can get really nasty, as we often need to integrate various very different build systems: you might have to build an ejb client jar (maybe using maven) which then need to be integrated in an eclipse rcp client application, which again needs to be built using pde build.
nils and gerd showed a slide which listed all major build tools for bundles, among them:
- springsource tool suite
- pde build
- maven tycho
after which they showed three exemplary setups how to actually build bundles:
please refer to their slide deck, slides 14 - 16 for detailed diagrams on these three setups:
ghost of build future
as things get more complicated, build management will also most likely become more complicated. gerd and nils pointed out that build management might be an unthankful job, but it must not be assigned to "people that aren't good at programming". instead, they advocated making build management a first class citizen in computer sciences education.
more information on the tools and techniques presented are available at their respective home pages. in addition, you can contact nils and gerd and bug them with your questions. they're consultants, so they can be hired.
redview - dynamic views for business applications
the final session was held by ekkehard gentz, better known as ekke . he showed a smart combination of eclipse technologies: riena, emf, openarchitectureware (xpand, xtend, mwe) and xtext. of course, being an open source advocate, ekke and his team mate florian provide this stack as an open source project on google code .
redview is a declarative framework based on the eclipse modeling framework (emf), for creating rcp views enriched with riena ridgets . it uses emf to describe the application with a model. an xpand-based code generator will then transform the model into code for the application. ekke states that their goal is not to limit developers' creativity, but instead relieve them from the burden of having to write all the boilerplate code.
redview supports the most important ui elements, including some nebula widgets. one thing i fond very impressive was their ui editor. ekke gave a demo in which he hosted the ui model on a cdo (which seems to be eclipse's wunderkind) server on a virtual machine. he started a second virtual machine, running an instance of the application. upon changing the ui model in the ui designer on one machine, the ui was updated immediately on the second machine. ekke pointed out that this usage pattern is especially useful in prototyping scenarios: the developer changes the model on his pc in his office and the customer can immediately see the changes on his machine, hundreds of kilometers away.
after the demos, we raffled off 20 eclipse keybinding mugs (see kim moir's blog post for a 360° shot of the mug) - congratulations to all winners! it-agile also provided a fine selection of agile swag: retrospective mugs, team calendars, post-its and what have you:
despite the fact ralph müller couldn't attend the event, we eventually headed to the east bar for some frosty beverages.
all in all, it has been a very enjoyable event and from what i gathered, most attendees seem to have enjoyed the democamp as well.
thanks everyone for attending! also, thank you to all speakers. last but not least a big thank you to natalia for taking pictures of the event!
hope to see you again at the next democamp in summer 2010!
Opinions expressed by DZone contributors are their own.