🚀 go-pugleaf

In <1993Jan6.110652.19542@gate.esat.kuleuven.ac.be> tytgat@esat.kuleuven.ac.be (John Tytgat) writes:
>Ok, but what about the practical implementation ? Do we specify a bit which
>determines the kind of text : plain text or messagetrans tag and define a
>path where the template, euh sorry, Glass editor can find the messagetrans
>files ? Or do we define more explicitly in the Glass file which languages
>are supported with explicit filenames (instead of a path) ?

No the ideal solution would be for 'Glass' to generate a file for MessageTrans,
(not the whole one because you will want your own for other things), with the
tags and everything.  Also for good luck it chucks out a file containing
a list of the maximum length of text which can fit in each icon.
Then you can know if the translations you have will fit!

That way you can be sure you never forget to translate a window or
an icon in a window.


Dave

P.S. How about including space for code in the template file - which could
be stripped out before distribution - it would make it more of a whole
development environment than a template editor.  So if you create a menu
you can specify the procedures to be called on each item and hey presto
you have a menu handler.  Also windows could have associated code - then
when you were developing you could grab a 'glass' entry from one application
and it would contain all the code to manipulate it.

Then in the future people could become more ambitious and add automatic
code generation - i.e. I've designed a dialogue box, write me the
code to handle most of it.

--
-------------------------------------------------------------------------------
- David Alan Gilbert - gilbertd@cs.man.ac.uk - G7FHJ@GB7CRG                   -
------(Programmers don't sleep - they just park their heads)-------------------