I think enums serve just that purpose. For now, put it in code. If it becomes a problem later, you can copy and paste that date elsewhere. I know the feeling of wanting to do things right the first time, but premature optimization turns out to be pretty harmful.
Best of all, you can probably just find someone's existing enum on google code search. Plug and play! On Wed, Sep 2, 2009 at 7:45 PM, Jarda<[email protected]> wrote: > > I mean I need to provide like 100+ strings that I know at compile- > time. But I had this feeling that writing all of them directly into > code is not the proper way. (But I am far from thinking of myself like > of expert. :) > > On Sep 3, 1:34 am, Daniel Jue <[email protected]> wrote: >> Is the static list editable? >> >> If not: >> static final String >> or >> enum >> >> Note that enums can be more complex than just named elements. >> >> 2009/9/2 Jaroslav Záruba <[email protected]>: >> >> >> >> > Hello >> >> > What is the best way in GWT to store static list of strings? >> > I need to provide list of countries, so creating a Constants interface >> > does not seem to be the best solution. >> >> > I supposed I could store the list in properties-file (countryCode: >> > countryName) and then iterate over its keys. But I failed to >> > accomplish that as I am yet to find out how to access such files in >> > GWT-environment. >> >> > I have only seen one video about Linkers and Generators in GWT (http:// >> >www.youtube.com/watch?v=cyfVHNAM80E), could they be the answer... >> > somehow... ? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
