On Mon, 29 Jul 2013 15:10:31 -0300, Tony Nelson <tnel...@starpoint.com>
wrote:
I don't think that Tapestry should ship with any css or javascript
personally. At least not the base package.
How would the JavaScript-based base components work? I'm sorry, but
writing JavaScript that deals with the inconsistencies in each browser
would be a waste of time NIH (not-invented-here)-style.
If they want to make a contrib package that adds something that's fine
by me, but why, as a Tapestry user, am I still forced to swallow their
decisions on what libraries I'm supposed to use.
Tapestry 5.4 did just that. And even before that people were able to use
jQuery instead of the bundled Prototype (tapestry5-jquery project).
That's the whole point of the 5.3/5.4 rewrite. Letting users choose
javascript stacks. You can't choose your own js stack if you can't even
choose your own css stack.
Tapestry can deal with that by having a symbol defining whether you use
Bootstrap 2 or 3+, then using it in the components to know how to deal
with Bootstrap.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
