Re: OOC Library and Locales

[Tim Teulings <tim@edge.ping.de>]

Hallo!

>     components.  Each component should have a "locale attribute," which,
>     if not set directly, should match the locale of its parent object.
>     An object with no parent has its locale set to the default, when not
>     set directly.

That does mean  every visible object and perhaps even some more
(DateModel with print method for example). While this is possible
(implement a memeber and access methods in the apropiate base classes),
isn't it a bit oversized? Will you have dialogs where every objects
will not have the same locale?

>     Developers of visual components may also have to create ``Input
>     Methods''.  The reason for this is that some languages (e.g.,

Yes, X has such concept and emacs (based on X?) has one, too. However I
have neither experience nor documentation for this. It is necessary
however.

--
Gruß...
       Tim.