if you look at the docs for tap 4.1, you'll see the contrib components
there. I haven't used them all, but table definitely works. I
haven't looked to see if it supports async operations now. My guess
is that that work has yet to be completed, but it will still work the
way it used to. I defin
What about the Contrib components available for 4.0? Will these work with 4.1?
On 12/5/06, Daniel Tabuenca <[EMAIL PROTECTED]> wrote:
So tacos 4.0 is definetly not compatible with Tapestry 4.1? If so, it
would be nice to include old components and forward them to tapestry
with a not that they
So tacos 4.0 is definetly not compatible with Tapestry 4.1? If so, it
would be nice to include old components and forward them to tapestry
with a not that they are deprecated.
On 12/5/06, andyhot <[EMAIL PROTECTED]> wrote:
No, not really...
I've recently started tacos-4.1.0 snapshot releases..
No, not really...
I've recently started tacos-4.1.0 snapshot releases... but they only
contain
the sitemap components = really cool way to get an instant menu system in
your app.
Anyway, some tacos components can now be replaced with the ones tapestry
provides,
which ones are you currently using ?
If I'm currently using 4.0.2+Tacos, can someone tell me if I can
upgrade to 4.1+Tacos and incrmenetally port my pages that use tacos
components to the new 4.1 ajax framework?
On 12/5/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
Given the parameters that you describe for your app, I'd definitely go
Given the parameters that you describe for your app, I'd definitely go
with 4.1. The only reason I wouldn't is if you knew you were going to
be building a very large app that was going to use a significant
percentage of the API, since in that case, you might struggle keeping
up with changes. But
