Hi guys, I know it’s been a while since I’ve talked about Intent, but don’t worry, William and I are working hard! This post will give you an overview of some of the features that will be provided for the Kepler release. Reminder: What the heck is Intent and why should I care? Intent is a documentation environment providing tooling for keeping your doc synchronized with your technical artifacts (models, code, plug-in dependencies…). Any time you make a change on the code, Intent will display synchronization issues showing the sub-parts of your doc that needs to be updated, leaving you the choice to update the doc right away, or later (e.g. just before a release). By giving your doc the ability to react to changes, Intent turns your doc into a true Agile Documentation. Please find all usefull informations (tutorials to get started, talks transcripts, example videos…) on the Intent wiki. Do not hesitate to spam us with questions or remarks on Intent forum....

Coming back to work after a great conference week in Ludwigsburg and after doing two different talks there, it’s time now to share my slides. I just uploaded them on the EclipseCon web site : Buildroot Eclipse Bundle : A powerful IDE for Embedded Linux developers Build your own System Engineering workbench...

After agile methods, devops, continuous integration, model driven development, ... here is coming the new awesome approach to improve quality and productivity: CHOCOLATE!Here are the slides of my talk at EclipseCon Europe 2012.I spoke about gamification, pleasure-based management, packaging tooling, continuous quality improvement, ... with  a common thread based on "choco-commit".It was a challenge to use a fun way to explain so many different aspect of industrialization in software development.Thanks for all the feedback I received about it.Chocolate Driven Development on PreziI hope several of these ideas can help you improve the pleasure of making good softwares or can be useful to discover some Eclipse plug-in to simplify packaging and agile development.Lien d'origineAuteur d'origine: Etienne Juliot...

This week is EclipseCon Europe 2012, and as always we’re going to have a great time. Thursday, I’m going to show you why your doc sucks, and what should you do to be able to proudly say “RTFM” to your users and team members. Here is a quick teasing, but you’ll have to attend my talk to see a full use-case showing how can Intent be used to document Enterprise Architecture Models (computed through the SmartEA tool). 1. It’s 2012, we need to be able to detect when doc gets outdated! To do so, Intent maintains formal links between doc parts and technical artifacts (whether it’s Models, Java Code, Manifest file, C++ Code…). This allows to automatically determine which parts of the Doc have to be updated when a change occur, preventing you from a painfull manual search through the hundred of pages of your doc. And of course, Intent leverage these formal links, providing tooling for querying your doc (“Which doc parts define/reference/co...

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 ...