I am curious about this conversation. I write apps that run in several languages...10,12,15 languages. To date I have used indexed arrays. At times memory boundaries have been an issue, but I have always been able to solve these issues with segmenting. For each form I create in constructor, I dynamically fill it at run time with the appropriate language array. This way one prc supports several languages dynamically. I am not sure the way I am doing it is the most efficient. But, I wouldn't want to use constructor for 10 languages X 100 screens. Do you need to use constructor for overlays?
Rick Gadbois PHT Corporation [EMAIL PROTECTED] -----Original Message----- From: Dave Johnson [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 19, 2000 1:54 PM To: Palm Developer Forum Subject: Re: strings and string lists Charles Rezsonya wrote: >Are there any pro's or con's against using strings&string lists versus hard >coding strings into the app? One BIG one is internationalization. If you're planning to sell your product anywhere that has a different language than the one you write it, you'd better use resources. Otherwise it means code changes and a recompile to change a string. Dave Johnson -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
