Thomas: thank you for the detailed explanation. It is great to learn that qooxdoo already has the neccessary infrastructure for plugins. Good job, as usual ... ! :-) It sound complex, but doable, and certainly, a public API for this would be welcomed by the community.
Since my clients would not kill me if, for now, the plugins remain untranslated, my question is: is it worth waiting for the public API before I start working on this (so many other todos remaining on the agenda), i.e. are you planning on implementing the API any time soon? I'd rather wait and implement it using a stable API than hacking something that might break in the next release. On the other hand, if that is not one of your priorities, it might be worth to go ahead an try going with your info. Thanks, Christian -- View this message in context: http://qooxdoo.678.n2.nabble.com/Translation-not-working-in-plugins-tp5155173p5157081.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
