Hi Chris,
>Better naming options might be
>
>public interface Command<T> {
> public Collection<T> execute();
>}
>
>or
>
>public interface Function<T> {
> public Collection<T> execute();
>}
>
>
>On 3 July 2011 04:36, Chris Bartlett <[hidden email]> wrote:
>> public interface Transformable<T> {
>> public Collection<T> transform();
>> }
>
I'd prefer something like Command, but usually I've seen that the Command
pattern returns void in its execute method (for example take a look here:
http://en.wikipedia.org/wiki/Command_pattern ), so why not
TransformableCommand (or Transformable) ?
It's just a suggestion, to avoid confusion with generic patterns ...
>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.
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.
Bye,
Sandro
--
View this message in context:
http://apache-pivot-developers.417237.n3.nabble.com/Idea-for-a-useful-change-to-BXMLSerializer-tp3133361p3137116.html
Sent from the Apache Pivot - Developers mailing list archive at Nabble.com.
