[Babel] Where to translate?

diegogomezdeck at consultar.com diegogomezdeck at consultar.com
Sat Sep 27 22:19:58 UTC 2003


Hi Scott...

Thanks for your interest to make squeak translatable!

I think that you're proposing can be thought as "translation in the view"
and the path we follow with the current version of babel is "translation
in the model".

If we follow the idea of making the translation a responsibility for the
view we have to expand the protocol for all the widgets (morph, mvc, html
frameworks, etc) including some support to put on them "expandable"
strings to avoid the translation of every combination of concatenated
strings.  (The same idea behind the #format: method in Babel but in the
widgets).

If we follow the idea of making the model translatable, we have to touch
all the models (just like we made).

I think a mix is not an option. I prefer more work but clear concept and
not a mix of concepts just to reduce the amount of involve code.  The
changeset you give as an example (the one with 160 methods) took me just 1
hour of work.

On the other side there are a lot of things that don't match the
model/view separation, example: is the name of a morph view or model? what
about the menus?

I see problems and benefits in both models but I don't think a mix is a
good option. Let's decide on one of them and let's follow it without
counting methods.

Cheers,

Diego Gomez Deck
http://www.small-land.org





More information about the Squeak-dev mailing list