mercredi 17 octobre 2012

EMF Core does not change, but ..

Using EMF sometime lead to frustration : any relevant change into this core framework means breaking client code and this is a No No !

EMF Core does not change.

In a world of technologies coming and going, new infrastructures poping up here and there, new practices revolutionizing the way we build software ...
EMF Core does not change.

New adopters, from tool vendors, to service provider, industrials, consultants, students...

But EMF core does not change.

Not changing in IT means being dead, right ?  So is EMF dead ? 

EMF Core always has been about giving value and making sure it's long term. One could be worried : but nothing new happens ? I'm gonna miss the NoSQL / documentDB / graphDB revolution  ? I'm stuck with XML and POJO Java APIs from the previous decade ? My software will only be a single-user desktop application ? What about the cloud ?

Stability, Predictability, Compatibility are the key words explaining the success of EMF : others can innovate on top of it, on a solid base, bring it in another space and focus on the value. "Others" here are stands for the "EMF Ecosystem", frameworks, tools which agreed  to access each others data reflectively, to refers to data using URIs by being built on top of EMF and then to provide even more services for the very same ecosystem.

This leads to an innovative and versatile ecosystem, and that's what I'm going to talk about.

15 projects, from tools to work efficiently with Ecore to frameworks to build software applications. Some of them being a few classes, others a whole bunch of Jars, but each one useful in my opinion.  During 25 minutes, at EclipseCon Europe on Wednesday just before lunch.

Technologies for NoSQL, document DB, concurrency, distributed architecture, crowdsourcing and much more, all of them on top of EMF.
More than just a list, for each of them an example of usage in a bigger application and my feedback using it.

 I can only say I already had a lot of fun preparing it and I can only hope you'll enjoy the talk.

mardi 3 juillet 2012

EclipseCon Europe - Time to hurry up !

Picture by Alan Cleaver

It's summer, the Juno release is over and you all deserve to rest and  enjoy your vacations... but hey, you might have missed it but the submission deadline for Eclipse Con europe is very close !

Only 11 days before the early birds deadline.

others already submitted proposals, if you want to share your experience, demo the latests hot features of your project or if you have other cool stuff, go ahead and submit !

jeudi 28 juin 2012

Eclipse DemoCamp Nantes - Live Broadcast


we are seting up a live broadcast of the Eclipse DemoCamp Nantes event (using Google+) , feel free to attend :

It's in french and it should start at 17:30 (UTC+2)

5:30PM - 5:45PM: Registration/Introduction
5:45PM - 6:05PM: Orion: Tools for the Web, on the Web (Stéphane Bégaudeau, Obeo)
6:25PM - 6:45PM: Eclipse Labs for improving DSL development (Hugo Brunelière, AtlanMod Team)
6:45PM - 7:00PM: Break & Discussions
It's started !

lundi 14 mai 2012

Upcoming Events

With Juno's arriving to the end of the release cycle Eclipse Day's are popping up everywhere in the world.
If you are not too far from France, you should consider joining us next week for Eclipse Day Toulouse

Great content, very low price (20€) and Toulouse is so sunny it can only be nice !

I will be there presenting Eclipse Modeling. A 101 session leading you to the jungle of one of the most diverse top level project in Eclipse, describing some of the main components and how you can use them in your day to day work.

Register now, this event takes place next week!

It is said the west of France is less sunny but I'm pretty sure its a myth spread by the Bretons frighten tourists.   The 2012 breizhcamp will be the occasion to confirm my belief.

This is a Java/Webapps event during two days with more than 50 speakers ! I will be representing Eclipse there along with Stéphane. We will give an Acceleo tutorial.

And here is the Breizh Camp trailer :

The EclipseCon Europe call for paper is out ! You should consider to start preparing your submission.  The  conference tracks are :

  • Eclipse Technology
  • Building Industry Solutions.
  • Community and Collaboration.
  • OSGi.
  • Other Cool Stuff.

Lets make this the best EclipseCon ever!

jeudi 22 mars 2012

Preparing EclipseCon US 2012

We are pretty active in Eclipse:

I'd love to show all these things during EclipseCon, especially considering things are happening for  every single project listed here(*). There is just not enough time and many other interesting things to cover in such a short event but feel free to come and talk to us during the conference. On the other hand we are giving several talks worth mentionning :

You did not knew Acceleo was an implementation of an OMG standard ?  Stéphane will present it during the Eclipse/OMG Workshop on Sunday.
Meet Stéphane on Sunday, 15:55 – 16:20

Eclipse is a best platform to build tools. Eclipse Modeling makes things even easier, but why would you need tools ? Aren't they available already  ? Well, generic tools suitable for any use case are hard to make,  you might want to use a given technology and not having any tool.  Good news is Eclipse Modeling enables you to build a dedicated tool in no time. We'll start the EclipseCon conference with a tutorial so that you learn how, leading you through an example tool to build a web app powered by  localstorage, Backbone.js and, JQuery.
We're preparing the tutorial content in a way that you should be able to replay or present it when you'r back home. All the steps are  documented through eclipse cheatsheets and you'll get an all-in-one update-site.

Meet Stéphane and me on Monday, 13:00 – 16:00 in Lake Anne B 

If you're interested in industrial collaboration to provide long term and very long term support for Eclipse technologies, the Polarsys talk on Tuesday is for you.

Meet Gael on Tuesday, 17:00 – 17:50 in Reston Suites B

If you're more interested in technologies, modularity and dynamicity, Mikael is sharing an experiment on bringing EMF in a multi-tenant and dynamic world while trying to reduce API breakages to a minimum.
3MF : EMF To the infinity ... and beyond !

Meet Mikael on Tuesday, 17:00 – 17:50 in Lake Thoreau

If you're into Agile and ALM and don't want to give-up on design documentation, Alex will present the Mylyn Intent project :

Meet Alex on Wednesday, 10:30 – 11:15 in Regency Ballroom A

In a nutshell, it's gonna be legendary :)

(*) I guess I'll should also blog more to share what's happening.

lundi 5 mars 2012

Graphical, textual, table, trees, its your call, to us its just EMF models

Lately I've been making sure the upcoming Designer 6.0 release still plays well with Xtext. 

Results : fairly good. The newly introduced "Modeling Project" let you behave with your Xtext models just like any other kind of models. Everything is synchronized, you can edit using the Xtext Editor, or using the Graphical modeler and the other one gets automatically refreshed. It just feels right.

One identified glitch so far : Xtext DSL's having references to JVM types might need a bit more work.

CDO, Xtext, Acceleo ... the product allows you to leverage the Eclipse Modeling ecosystem while having a huge productivity boost defining modeling environments. Of course we can still argue whether the state machine is more readable using the text or the diagram ;)

Some niceties are visible for those who want to have a deeper look :

  • the State "Soon" has a specific grayish style because it's not linked to transition (incoming or outgoing)
  • the Transition to Event blue dash link uses the "Edge on Edge" new feature for 6.0.
  • and the "Connect" tool in the palette is smart enough to "do the right thing" depending on where you clic : from State to State or Transition to Event. One tool to bind them all !

But where does the "PlanningTheTravel" to "InThePlane" edge comes from ? I created this transition using the graphical modeler. Xtext won't allow to save the model in this state because of the textual syntax, that's why the graphical modeler has been specified in a way which lead to the edge being red.

When building the basis of the modeler takes minutes of work, you have enough time to think about user experience and focus on providing the right feedback, at the right time.

I'm quite proud of what's cooking for this 6.0 release :)