Timeline for Class design for internationalized object
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2012 at 6:14 | vote | accept | Nick B. | ||
| Aug 3, 2012 at 6:14 | |||||
| Aug 2, 2012 at 13:24 | comment | added | superM | @Nick B., this approach can be changed by grouping properties into location-specific classes, if their quantity isn't large of course. For example, US, UK and Canada have the same group of additional attributes. | |
| Aug 2, 2012 at 13:08 | comment | added | Nick B. | You are suggesting something like a hashmap for everything that is not clearly an international value, I understand the flexibility this gives and certainly solves the problem of having different instances of the same product for each country. I think that perhaps generics could get around the parsing issue but do you not think this might take a performance hit? I'm also slightly concerned that enumed properties might be less convenient for a developer than having clearly defined values. I'm not sure that the fields themselves will change with any great frequency. | |
| Aug 2, 2012 at 12:14 | history | edited | superM | CC BY-SA 3.0 | added 224 characters in body |
| Aug 2, 2012 at 10:07 | history | edited | superM | CC BY-SA 3.0 | added 126 characters in body |
| Aug 2, 2012 at 10:01 | history | answered | superM | CC BY-SA 3.0 |