Accéder au contenu principal

Bringing Desktop UI to Web

Web is originally and mostly an HTML world with page by page navigation. Oh yes there is flash but it is designed for graphist with massive website and it was always used for merchandising and promotion site.

In business, in the better case, we had some techno like Struts for it's Model View Controller architecture. Sadly this was not a good looking user interface with old fashioned page by page navigation with maybe some css styling.

Almost two years ago, a "new" techno appears called Ajax. This was the begining of revolution and what we call "Web 2.0". Why it was revolution ? because it enables changement in a page without changing this page thanks a little command and a good use of DOM model (the HTML model of a page). With the use of massive javascript, good looking UI for web appears like Dojo.
But a problem remains, a techno problem because it's need to the developper to know very well javascript and html DOM. These techno are not known very well, not very interesting to code and difficult to maintain.

It was at this time that GWT from Google appears. For me, it was amazing. Why ? firstly because it is like coding Swing (the desktop UI techno from Java) and it pushs the developper to see it's website like a desktop UI with frames, menus, buttons ... Secondly it was easy to code, easy to debug and easy to maintain.

Now GWT and similar techno have made their ways and it becomes better and better with more and more UI component like SmartGWT or Tatami Toolkit or AjaxSwing which converts your old Swing application to web with little (no ?) refactoring.


Posts les plus consultés de ce blog

Summary of 'Clean Architecture' by Robert C. Martin

Summary of 'Clean Architecture' by Robert C. Martin
Uncle Bob, the well known author of Clean Code, is coming back to us with a new book called Clean Architecture which wants to take a larger view on how to create software.

Even if Clean Code is one of the major book around OOP and code design (mainly by presenting the SOLID principles), I was not totally impressed by the book.

Clean Architecture leaves me with the same feeling, even if it’s pushing the development world to do better, has some good stories and present robust principles to build software.

The book is build around 34 chapters organised in chapters.
Programming paradigm After some introduction, there is an overview of three paradigm of programming:

structured programming which imposes discipline on direct transfer of controlobject oriented programming which imposes discipline on indirect transfer of controlfunctional programming which imposes discipline upon assignment

Uncle Bob tells us that each of these paradi…

Le développeur incompétent est un mythe

Sous ce titre complètement arbitraire et très clairement provocateur, je vais passer un contre pied aux derniers articles que j'ai lus sur le métier de développeur.
Par exemple : 
Ça tombe bien c'est juste avant la soirée du Paris JUG sur le métier de développeur ! Et comme on se plaint que les présentateurs ne sont pas de vrais (?) développeurs, je vais en profiter pour donner mon avis.

Alors voila, d'après ces articles, un bon développeur connait ses fondamentaux.
Ok soit mais quelle est cette liste de fondamentaux ? 
Chez certains, c'est les maths et l'algorithmie pure, d'autres c'est C++ par coeur et savoir retourner une chaine de caractère en moins de 3 instructions et une seule allocation mémoire, d'autres c'est Java JEE, ses 100 jsr et frameworks in…

Behaviour Driven Development at Zenika

I have assisted to the Zenika's conference about Behaviour Driven Development given by Mauro Talevi from Agilesque.

The presentation was mainly decomposed in 3 parts : Introduction to BDD, Presentation of JBehave (the API used to do BDD in java) and return on experience about a real project.

Introduction to BDD.

BDD brings together Test Driven Development and Domain Driven Design by
- describing behaviour is a better form of testing
- describing needs from from point of view of it's stakeholder

BDD relies on the use of a specific language to help communication between the business, developers, testers, analysts and managers. It improves presentation.
Behaviours are described by scenarios with a why ? the value, a who ? the actor and the what ? the feature.
BDD introduce a grammar of steps GIVEN a context, WHEN there is an event, THEN produce an outcome AND do other steps.
BDD offers step parametrisation, aliases for changing language or tabularisation for changing parameters for a give…