The one large difference though is that the engine service (Direct or AjaxDirect in most cases) doesn't control the output type anymore like tacos does (since we have control of tap source)...Now the tapestry ResponseRenderer cooperates with the different builder types to determine and let them deliver the appropriate response.
On 6/1/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
On 6/1/06, Pedro Viegas <[EMAIL PROTECTED]> wrote:
> Very nice!
> Tell us Sam, are those table improvements AJAX related?
Not really. Since tapestry 4.1 is going to have some kind of json
service thanks to Jesse, I have been waiting to make data fetch
asynchronous until I have a chance to look at Jesse's changes in tap
4.1. However, it would not at all be difficult to just build a custom
tapestry service to handle data fetches and plug that into the
tapestry component that is in tacos. If you have the Enjjoying web
development with tap 4 e-book, it has a chapter which covers builing a
custom service, and I bet that you could implement such a thing very
simply. THe dojo widget itself is already built so that it can accept
data asynchronously. In fact, if you look at the _javascript_ that is
generated by the tacos component, you will see that it populates a
data structure in a function and then calls a callback into the table,
just as if it had received the data asynchronously. So what I am
trying to say is that, even though it isn't a priority for my team, I
think you could populate the data asynchronously in a day or two,
depending upon your tapestry experience. If you want to try it, I
will offer you whatever help I can and I will certainly merge your
changes back into tapestry in a very timely manner.
Incidentally, I got an email from the turbo ajax folks about your
interest in turbo components in tacos. I started my dojo and tapestry
adventures by wrapping some of the turbo widgets as tapestry
components, including the turbo grid. I am sure I could pull some of
those early revisions out of our SVN repository if you want them, but
we found the turbogrid to be very slow when dealing with large data
sets, which is exactly why we built our own (starting from someone
else's work in the dojo trac, admittedly). I also have tapestry
components for TurboSlider, TurboButton, TurboRangeBar, and
TurboPageBar if you want them. I don't really remember how complete
they all were, although they were all usable in tapestry pages, but
they would certainly get you started. But there is still the turbo
license to be dealt with for commercial projects, which is why I never
added them to tacos. Besides, as I learned my way around dojo, I
prefer the flexibility of being able to modify the widgets for my own
use instead of being bound to the turbo closed-source widgets. This
has been invaluable when building our applications.
--sam
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
