Well, this community can help to make the publisher's decision easier. If
somebody of you is interested in a book translation, just comment here. I
will forward this thread to the publisher. The more interests available the
more likely they will do it. So give the publisher the impression how big i
Em Sun, 14 Jun 2009 08:57:03 -0300, Onno Scheffers
escreveu:
Are you saying that the component libraries themselves should be able to
switch between the supported JavaScript frameworks as well?If that's the
case, there is quite a bit of wrapping-code Tapestry needs to
introduce/support.
>
> At the very least then we need a way to describe the "stack" used by a
> component and guard against incompatibilities, i.e. Protoype needed by
> component A and jquery by component B resulting in a conflict on the $()
> function.
For jQuery it shouldn't really be a problem. The $()-function
On Thu, Jun 11, 2009 at 7:05 AM, Onno Scheffers wrote:
> ${} is a shortcut to make it very easy to insert some property-value into
> your template without having to use a component for it. There are typically
> 3 ways to insert some content into your page:
>
> 1. The way you're using components,
Em Sun, 14 Jun 2009 02:12:34 -0300, Angelo Chen
escreveu:
maybe dispatcher? you can find a related articles in the wiki page for
t5.
Or a request filter. A dispatcher is more suited for logic that needs page
redirection. For example, I implemented an access logging package
implemented
At the very least then we need a way to describe the "stack" used by a
component and guard against incompatibilities, i.e. Protoype needed by
component A and jquery by component B resulting in a conflict on the $()
function.
On Sun, Jun 14, 2009 at 6:10 AM, Markus Joschko wrote:
> I agree with On
I agree with Onno. There is a difference between component libraries
and the framework itself.
I want to use the framework without being forced to include some
specific javascript library. That includes
basic components like form fields etc.
I wouldn't mind if more complex components still dictate
>
> In release X (say 5.2) we introduce a more complete Tapestry isolation
> layer
> and recode Tapestry's internal logic and components to use it. The
> isolation layer maps to Prototype and includes parallels to the common
> constructs of Prototype used by Tapestry (i.e., $(), observe(), and som
