From: Brandon M. <bnd...@ho...> - 2000-12-11 15:48:23
|
I'm afraid you missed the point of this thread, but at the same time, you've stumbled upon another feature that would be nice to have. Especially since the purpose of this API is to provide functions for a user interface. So, why not build in Internationalization functions? A single file can contain the text for a language... multiple files, multiple languages. The functions simply get the text for any particular language. Oops... this would also require some sort of widget standard so that the same internationalization method would work across all widgets. The widgets should pull it's text from the same object. A simple standard of: WText.OK="Ok"; WText.CANCEL="Cancel"; WText.NO="No"; Why have a different object, or different properties of the same opbject point to the same text? It's just a waste of memory. I would release this code, but as Dan should know... I'm in a tough spot with releasing what I have at the moment. ----- Original Message ----- From: "Stephan Reindl" <SR...@la...> To: <dyn...@li...> Sent: Monday, December 11, 2000 9:20 AM Subject: AW: [Dynapi-Dev] DynAPI build, Splitting files > Oh come on. If you're supposed to write an international site for visitors > in 5 languages, would you really consider writing (and editing) all the > different texts, labels, figure captions, etc in ONE file only and > separating the languages by deeply nested if`s ? > Would you say, ok, I don't know german so well, but it's important to see > all the versions together in order to be sure that any change is done > simultaneoulsy. I try to learn german (and french and kisuaheli, etc.) > Or would you prefer to define the "look & feel" of the site, split the files > and let the german version be done by a native german speaking (if > available)? > > Stephan > > > > > > What advantage would you gain by splitting up your example? Speed > > wise, that is not the reason for loading taking a long time. The > > speed problems are due to DynLayer creation. If you haven't seen yet, > > Dan is creating a new inline dynlayer creation system that will speed > > up this process. While splitting up the core files may seem nice, it > > offers no real advantage. Especially with the new jspack files, the > > file sizes are going to be small anyways. > > > > -- > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > |