I think of compilers and tools like this as a point in time technology. It will be great in the beginning but in the end the developer will rarely “compile” the web application and possibly just edit the output directly – or rewrite it from scratch. The problem I see is the steep learning curve so the latter part of that statement may be a while.
I relate things like this to MFC, MFC was great for C/C++ developers but once you learned what MFC did under the covers for the most part many just went around MFC and removed the bloat.
So if Google and the open source community do this right, GWT may stay around for quite a while. If it ends up creating “bloaded” applications then I think in the end it will not survive.
Lastly, it looks like this approach is gaining popularity. From the comments there were a couple of open source projects and even a commercial project Vaadin that essentially do the same thing.
I check this stuff every so often.
I always find it interesting who are the top referrers for Balfes.net. It looks like most of my hits are from Planet Eclipse, DZone (which is new to me), and Planet Lotus but I also find it interesting how many readers access the feed directly from Google Reader.
Very interesting article for all of you software and services companies out there on CNN Money:
10 things Google has taught us
1.) Passion wins
2.) Focus is required
3.) Vision is required too
4.) A team culture is vital
5.) Treat engineers as kings
6.) Treat customers like a king
7.) Every company is a frenemy
8.) Don’t ignore the human factor
9.) There are no certitudes
10.) “Life is long but time is short.”
I am pretty sure all young companies preach this kind of atmosphere and behavior. The trick is to continue it once you are a big company. It sounds like Google has done just that.
I am sure we will be hearing more of GWT and I would like to hear other opinions on this approach to Web 2.0 development.
Eclipse 4 is right around the corner (release schedule is 2010) and it is currently in an incubator project called E4. You can learn about this stuff with two great recorded weninars from the Eclipse site:
E4 – the Next Generation of the Eclipse Platform (Part I)
E4 – the Next Generation of the Eclipse Platform (Part II)
Over the last few weeks I have received several Eclipse questions for how business partners and customers can extend Notes 8 in new ways. The following two posts should answer some of those questions. The first post shows how you can extend the right click menu for a text selection in a Notes document while the second post explains how you can extend the right click menu in a Notes view entry.
How to extend the right click text selection menu in a Notes Document
Adding right click options to your Notes 8 mail box entries with Eclipse
As described in the wiki article for using the Symphony Spreadsheet container you can reference cells and cell ranges many different ways. I would argue that you should use named ranges all of the time. This will create a virtual reference to the spreadsheet so if the cell or ranges get moved or the editor inserts rows or columns before the range the reference in the CA container will not be broken.
You can create named ranges under the Create menu item:
You then use the dialog to define/edit the named ranges:
Once you create the named range it will then be available in the Composite Application Editor tooling as an entry in the drop down menu from the component toolbar:
As you can see from the wiki article you can use various methods to reference cells but I would stick to named ranges:
Fields are essentially absolute or named cell ranges. The container supports the following formats:
- $<Column>$<Row> – E.g. $A$1
- $<Column>$<Row>:$<Column>$<Row> – E.g. $A$1:$B$10
- !<Sheet name>$<Column>$<Row> – E.g. !MySheet$A$1
- !<Sheet name>$<Column>$<Row>:$<Column>$<Row> – E.g. !MySheet$A$1:$B$10
- #<Named range> – E.g. #MyRange