Hi, First of all i18n of GWT is using property file like classical java, but during compile time. Not using the file directly during runtime is quite obvious: the app live in the browser and has no direct access to the file systems.
You could write a generic approach to download properties files from server. This has at least 3 drawbacks a) It is slow b) It does not check whether a constant is used at all c) It may be a security whole. There are enough good reasons to do i18n not exactly like java does. I feel quite confortable with GWT i18n. Stefan Bachert http://gwtworld.de On 10 Jul., 04:52, Aladdin <[email protected]> wrote: > All I want is to create I18N support in my application , it has been > three days and it's now 5:37 am because the GWT team want invent new > language other than Java. > > So my question , why instead of using the Java's regular resource > bundle the GWT team go with their imagination and invent new way , so > experts Java developers have to learn new APIs and methods ... give > us a break !!! > > All I want is old fashion properties file that users can add new > locals to my application without having to recompile the code . > > ClientBundle , Dictionary , Constants ... blah ... blah ... blah .. > > GWT is a great product , but please just give us Java ,because when > you say it's Java it's not only the syntax , it's the library ... this > what took me 10 years to master not how to write if ..else > statement ... > > Or just call it GWT++ > > Aladdin -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
