Yet another web application framework: Play!

Several years ago (when I started learning Java (not that I ha finished since)), we had only just a handful of web application frameworks to choose from (like Struts, Spring, JSF), and these were used by most of the web developers.
These days, we see a new web application framework appearing each month, claiming that this is that easiest framework you can find, and is way shinier than the others…This is a bit frightening.
Yes I have to agree that diversity is nice but what about the developers? How can you be good in such number of frameworks? How can you pass a job interview with all these technologies available? Hmm…

Today I ran into a new one called Play!, thanks to the following article on Javalobby:

At first look this seems impressive (too), and I have to say that it caught my eye…maybe I will give it a try someday. It would be nice to see how it performs in a production application.

I have some questions to you:
Do we need so many application frameworks, doing almost the same thing?
How easy is for you to decide which one to use from all these shiny ones? (I personally am totally quite confused)

Do you have any taught on this? Please share them with me.

Until next time,

Happy Coding,

MigLayout – adoption in less than 30 minutes

I have no idea how come I have avoided using MiGLayout for my projects until now, but I have to say that I was stupid. 😉
Today I taught I give it a chance. As usual I kind of give every component a limited trial time (1-2 hours), to check how mature is. Usually if don’t succeed to make the component work or it does not give me the feeling that it will work nicely, I just remove it from the project and forget about it. So I did with MiG Layout.

Since I use Ivy in my latest project the first step in adding MiG Layout to the project was to define the dependency. Unfortunately that did not went too well at first try. The it does not have the latest version of the component, and unfortunately the artifacts are not separated from their dependencies (which are broken for 3.7 version) and to avoid downloading the whole internet, i decided to donwload the jars myself and put them in my shared repository and use that instead. With this in 5 minutes I had the dependecy resolved.

It was time to start coding. As a start I have downloaded the two best docs for the component: Quick Start Guide and the Cheat Sheet right from the site. I taught that if these docs don’t make me feel using this component than i’ll just drop it. Well, surprise these turned out to be the best documents a normal developer needs to check (not to read) in order to use the component.

After a short check I rapidly turned to the form I need to implement and started wondering on how to use the layout manager. As usual, it did not work from the first try, mostly because I am too lazy to read documentation, so after a few tries and a  short Google-ing for some examples (“mig layout example”) I managed to make my form look as I wanted to in less than 30 minutes (including Ivy configuration). And this my friend, is something.

I have to say that I am still amazed how simple it is to use it, and how much time can it spare you when developing GUI’s. In Swing making a complex form is a nightmare. Believe me I have tried every approach(every layout manager) but I could not find a solution which was easy and still covering the needs (which I have to say that are only basic needs).

Starting now, the GUI development is fun and fast (which is even better)  again!!!! 😉

One more thing (which is really important): MiG Layout works with Swing, SWT and JavaFX.

Nice work Mikael Grev.

Happy coding