On Thu, 22 Apr 2010 09:20:31 -0300, Robin Komiwes
<[email protected]> wrote:
Hi,
Hi!
As it is made for Autocomplete mixins, why not using this kind of coding
style for JS and CSS inclusion:
/**
* @param config
* parameters object
*/
protected void configure(JSONObject config)
{
}
Then Tapestry components wouldn't be JavaScript stack-agnostic, as you
would need a PrototypeAutocomplete and a JQueryAutocomplete. Why not use
normal parameters for stuff that can be configured?
Howard already stated that he doesn't think subclassing Tapestry
components is a good idea, as it would be harder to improve them without
breaking backward compatibility.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
