Why oh why? (updated)
17/07/07 09:35 Filed in: GWT
Google web toolkit is quite nifty. Though they have
done some things that I really really don't like.
java.util.Date. Need I say more? They should have provided their own Date class. Or at least made a class which you could convert into a java.util.Date when needed. java.util.Date is deprecated which means that Eclipse shouts at me all the time when I use it - though I have no other choice
And it is quite evil as well -
year is subtracted by 1900, first month of the
year is 0. Oh how I hate java.util.Date.
I18N. The support for Internationalization is quite good, but why can't your setText methods understand ØÆÅ? When you do other languages than English you end up with setting everything as HTML to get passed this
Update: As of new version of GWT this is fixed - go use 1.4. To avoid charset issues, I'd recommend writing such letters using unicode notation. (Like F\u00F8dselsdato)
java.util.* support. Well, this is quite okay, but here is what I miss:
- Better support for MessageFormat. It says "subset of the formatting features". What it should say is "We support string/numbers parameters and that's it - none of the nice formatting rules are present".
- java.util.ArrayList - I miss the constructor with int parameter. It would make writing code for GWT combine better with my programming habits from regular Java. If you know the size of your collection, you should always provide it for better efficiency.
Validation. There's no support for validation of fields. I had to write my own simple solution. Maybe it's for the best, as most people writing validation framework seems to overkill them.
Compilation. Play it by GWT rules. Put your code outside of the packages you specify from the start and GWT won't find them. Might be finger trouble from my side, but it sure didn't look that way. Though having sub folders where I put my code works nicely.
PS: I really like GWT even though I find some stuff I don't like
java.util.Date. Need I say more? They should have provided their own Date class. Or at least made a class which you could convert into a java.util.Date when needed. java.util.Date is deprecated which means that Eclipse shouts at me all the time when I use it - though I have no other choice
And it is quite evil as well -
year is subtracted by 1900, first month of the
year is 0. Oh how I hate java.util.Date.
I18N. The support for Internationalization is quite good, but why can't your setText methods understand ØÆÅ? When you do other languages than English you end up with setting everything as HTML to get passed this
Update: As of new version of GWT this is fixed - go use 1.4. To avoid charset issues, I'd recommend writing such letters using unicode notation. (Like F\u00F8dselsdato)
java.util.* support. Well, this is quite okay, but here is what I miss:
- Better support for MessageFormat. It says "subset of the formatting features". What it should say is "We support string/numbers parameters and that's it - none of the nice formatting rules are present".
- java.util.ArrayList - I miss the constructor with int parameter. It would make writing code for GWT combine better with my programming habits from regular Java. If you know the size of your collection, you should always provide it for better efficiency.
Validation. There's no support for validation of fields. I had to write my own simple solution. Maybe it's for the best, as most people writing validation framework seems to overkill them.
Compilation. Play it by GWT rules. Put your code outside of the packages you specify from the start and GWT won't find them. Might be finger trouble from my side, but it sure didn't look that way. Though having sub folders where I put my code works nicely.
PS: I really like GWT even though I find some stuff I don't like
|