Sandro made the same completely valid point. This was just another example of one of the many possibilities that this simple change would allow. It is certainly not a suggestion that the Pivot project should perform such a task.
I was trying to demonstrate how a small change would permit 'custom' aliases of stock Pivot components. These aliases then essentially become a 'DSL' for a specific problem domain. However, the option would remain open to someone who *did* wish to create and maintain their own translations for use by teams in various countries. Combined with the 'expander' tool idea, this would allow GUI development in one language to be seamlessly introduced into a more traditional international project workflow. This is very similar to how the previously mentioned Project Lombok can be used by one developer on a team without the knowledge of anyone else they interact with. And of course, there may well be alternative ways to achieve many of the examples I listed, but that was not the point of the email. On 5 July 2011 19:57, Greg Brown <[email protected]> wrote: >> This proposal also opens the possibility of >> internationalizing/translating bean class and property/styles names >> via simple alias classes. Styles can be exposed as bean properties to >> simplify things even further as demonstrated below. > > An interesting idea, but it could cause quite a bit of confusion and would > make documentation a nightmare. Might be easier to simply localize the bean > properties, via annotation or some other means. > >
