Few months ago, i was wondering why we do not work with jquery mobile (See also the Demo on your Mobile Device and your Desktop! ) for some classical web applications.
Here a little demo of using a Mobile Device as a Desktop Computer!!!
In several cases, I needed to parse html pages and extract data from specific tags.
For instance, I had to build a wiki migration, or to transform and import massively pages to a CMS.
JSoup, a Java framework, makes easier these operations.
Based on html5 elements, JSoup parses an Url, a String or a file with CSS selectors, or DOM transversal and gives facilities to manipulate the result found: you can easily replace some content, wrap with HTML tags.
If I say 400, you would say ‘Bad Request, client looser’.
If I get 500, you may laugh and go for an ‘Internal Server Error, server looser!’.
Or 200 : ‘OK, Good News for once’.
You probably know 407, 403 or 503. But do you know “414 Request-URI Too Long”?
This page is not only for your bookmark : http://www.w3.org/Protocols
A new Demo of jQuery Mobile Framework has been released. Check it on your Smartphone. The User Interface is really pleasant an sufficient for 99% of need. What if we work with it even for Desktop? I just don’t remember why we work with grids, columns, layers…
If the GWT concept is nice, its use was frusterating : the code generated by the core framework was mostly composed of … Html Tables, which is just a headache to render properly. And most of all, what I did not appreciate with GWT was how people introduced it: “with GWT you don’t have to work with Html”. In my opinion, if your aim is not to deal with Html, then don’t work in web technologies. As a matter of fact, web is Html and Html5 is not Xml yet…
I talked about that with a friend of mine who is my GWT psychologist (thank you Nicolas!) . He told me to have a look to UIBinder, a framework integrated into the official GWT since 2.0.
What I find really exciting in that framework is the possibility to define exactly what you expect as rendering.
But UIBinder brings the real solution: add the component that you expect, add any Css styles you need and bind it to your data. That’s it! The View implementation is very easy and efficient: a template made in xml, a widget class that is bound to your different fields with annotation. You can have the benefit of the whole GWT Engine combined with the best use of the browser with Html and Css.
I hope the GWT Team will integrate that in their best practices, because for me it is the best way to work with the GWT client.
One of the hottest aspects of today’s software market is on mobile devices.
In the other hand, many many software discussions are currently around standards and the User Interface process, the hole question is : what is the most appropriate representation standard for today’s internet need?
JQuery is a serious actor, my favourite User Interface and/or Javascript framework.
This month, it comes with one very exciting news : JQuery has just announced they are about to bring jQuery to mobile devices.
http://jquerymobile.com/2010/08/announcing-the-jquery-mobile-project/ As they say in Mangas : To be continued…
This is the craziest way talking Data, and so modern.
I have seen many confusing maps that try to “cluster” web technologies and have learned not to pay attention on them.
But CMSWatch has just created a drawing that classifies different CMS and Portal technologies in a simple and funny Subway Map. I found it interesting because of the apparent simplicity of the form and the correctness of the classification.
Last month i started a little open source project with google code
infrastructure. It is pretty exciting. The project is hosted in google code. It
includes a wiki, a bug tracker, and you work on its svn repository.
We decided to work with Google App Engine which supports Java now. It
is the biggest benefit of this cloud. You can now deploy Java web
applications on the internet in few minutes!
The presentation layer is being done in Gwt. The gwt/gae Eclipse
plugin makes develpment easier. Since my first experience in Gwt,
there has been improvements in many fields and the community tries to
suggest useful design patterns as
Commands packaging asynchronous calls, Bus Events to resolve communication between widgets.
One best practice that is suggested is MVP, Model-View-Presenter and
not an MVC, Model-View-Contoller for the interaction is easier to
apply test cases.
The Dependency Injection is resolved with Guice framework or maybe
closer to Gwt: Gin which is being finalized.
Links:
As i said beforewhen i tested eXo Porta, i found it was an impressive portal with sophisticated functionalities and User Interface, nicely coded.But, it really seemed not used that much in the communities and thus not very for the future.
That point seems to be corrected today!! eXo and Jboss Portal will be one and only project.
Now IT IS EXCITING to follow!
http://blog.jboss-portal.org/
http://blog.exoplatform.org/2009/06/10/exo-jboss-partnership/