here are the assumptions that I have based the string editor upon
1 all language files for a mod are in the SAME sequence (might not be true)
2 the entries do not have to be in any particular sequence ( confirmed by blair fraser)
3 new strings can be added to the end of the list without effecting performance ( confirmed by blair fraser)
4 altering the text in the display boxes before using the save or add functions is acceptable for entry of information to the program
5 NOT changing the string data (stored in a string array) until told to either add or save the data is acceptable
6 all button labels should be OBVIOUS(ie suggest what the button does) and with tool tips telling how to use the function
7 having the text for all(up to 6 at current size) of the language files for a mod on screen at the same time will help translators
8 no more than six languages(at curren t screen size in the program) will be worked upon at the same time(if more are wanted the program will want to have a higher resolution than 800 X 600. if you want a larger screen in this program please post stating the prefered screen resoution & I can re-design the program to fit with extra languages
9 stars & planets names have a limit of 511 ( 3 digit name counter in string file might actually be larger)confirmed by blair
10 caps & starbases names have a limit of 511 (2 digit counter in string file might actually be larger) confirmed by blair
11 users do not want to have to create all spacing and labels for each entry eg the stringinfo,id " & value " line headers.
if there are any comments please post.
personally number 11,2,3 are in my opinion are good ideas, 4& 5 are simple to program, 1 might be a significant problem, but do not know yet & could be altered in the program with indexes for each language(more fiddle in the program), 9 & 10 might not be real limits but could be,7 & 8 are more for translating mods between languages, but as I only speak english I do not know if this idea helps
harpo