On 4 July 2011 17:13, Sandro Martini <sandro.mart...@gmail.com> wrote:
> I'd prefer something like Command, but usually I've seen that the Command
> pattern returns void in its execute method
Good point. I suppose it could be BXMLCommand?
I also thought about Action as a name, but that clashes with
org.apache.pivot.wtk.Action.

>>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.
> On this I have no idea, could be powerful but I don't know if could generate
> code too much "strange" to read, for example on anyone has to give support
> ... but probably with a real (minimal) example could be easily understood.

Yes, it could certainly lead to some weird BXML files that are written
in multiple 'human languages', but right now it is possible to use
BXMLSerializer to create graphs of objects that have 'non-English'
class names.

The point here was just that internationalization becomes an option.
Someone would be free to could provide translated 'aliases' for
languages spoken in emerging markets or the 5 most common languages
spoken in the world.  Perhaps Pivot would become popular in such a
country simply because of this?

> I like the idea of "BXMLExpander", could be another way to pre-process bxml
> files ... and the right project for it could be the Tools subproject (no
> more existing in 2.0.x) ... let's see what others say.
> Even the version of ApplicationContext for JUnit automated tests could go
> under Tools (or better, "Developer Tools" subproject).
>
> Note, if you want to prototype something, tell me for grants under our
> apache-extras projects ... or otherwise for prototypes with direct impact on
> Pivot core projects a better place could be the /skunk area ... as you
> prefer.

This all depends on whether the idea is accepted and becomes an
official part of Pivot.

If there is no desire to include it, it could easily be forked and
made available as a drop-in replacement for BXMLSerializer.  Then
anyone who wished to use this could just download a tiny jar (with
dependencies on pivot-core) and use 'FooBXMLSerializer' rather than
BXMLSerializer.

Chris

Reply via email to