Using Dreamweaver?
Using Google API?
You will probably love this tools, Dreamweaver Tools for Googleâ„¢ 1.0.1
This is not an open source project, but it’s free at all…
Archive for March, 2007
Ever wants to code an Eclipse plugin to improve your productivity or to check consistency of your code? Well, learning those Eclipse SDK can be a little tedious.
This little project started in the big research institute in France will overcome your problem. Spoon JDT is a plugin of Eclipse to help user process Java file. It integrates tightly with Eclipse (I guess using Eclipse JDT).
What you can do with Spoon? You can create your own FindBugs, checkstyle. Those two projects, while they have a plugin for Eclipse, lacks one feature: Quick Fix. Using Spoon JST, you can even program the quick fix! A wonderful plugin… I must say
TopCoder Open (TCO 2007) has been started. TopCoder Open is a set of competition, both online and on site (for the finals), held by TopCoder, open to anyone, who is at least 18 years old.
Usually, there are only two tracks in the competition, but this year there will be two additional tracks added to the competition, Marathon Match and Studio. In summary, there are 4 tracks in the competition:
- Algorithm Competition, this is the most common and the most popular tracks. Basically, you will be given some problems to be solved. This competition much or less is similar to what are International Olympiad in Informatics or ACM competition.
- Component Development, contains design and development. This is the most unique software engineering approach in the world.
- Marathon Match. Don’t have the speed that algorithm competition needs? Maybe you kind of programming the right things slowly? This is the right track for you. The problem doesn’t have exact solution and its up to you to use any kind of techniques to improve the result.
- Studio. If you’re not a programmer but have some design skill, this is the right track for you.
Welcome to the competition atmosphere! 
Several days ago, Google launch an open source project. This project, namely Guice, is another Dependency Injection framework. This framework rejoices the use of annotation and thus, has lesser complexity compared to the most successful DI framework nowadays, Spring Framework. Spring Framework is using XML as its configuration which makes it a little hard to be maintained when the project goes bigger.
I can see why this framework will probably enjoy its golden time. However, some times ago, Spring has also started a sub project Spring JavaConfig which can be a tough competitors for Guice in the future. Instead of using XML, using this sub project, user can also use annotation to configure their application. I have to mention that this sub project is not mature enough and I think it still lacks of some features which will make people pick Guice if they don’t provide it soon.
Probably, one aspect from Guice that is hard for Spring to catch is its speed. According to some benchmarkings, Guice is about 10 times faster than Spring. The advantages of Spring over Guice are its completeness and its support to many frameworks and libraries in Java. There will be some times before Guice catches this complete features. As a user, I feel glad for the competition and waiting forward for their innovations to help programmers do their tasks.
What I want to express in this blog entry is I think it’s time for Google to create a tighter integration between its frameworks. Currently, there are two frameworks created by Google, they are GWT and Guice. Both of them do different things. GWT works in the front end, bridges the HTML + JavaScript + AJAX with the robustness of Java programming. As we have discuss before, Guice works more in the back end. Before Guice is introduced, there is already an integration project for GWT and Spring. I wonder, if Google doesn’t do anything, there will be no long before another integration project between GWT and Guice comes to the arena.
