ok, will do. I'm up battling 12 hour jet lag from Moscow, and my brain is now well past the point of being able to concentrate on anything new, so it'll have to wait until next weekend, I fear. You'll probably start seeing queries from me sometime next weekend. The good news is that I have a crew of fairly talented Russian engineers to help implement this stuff once I've figured out an architecture and know enough to give them some direction, and the company isn't likely to have any issues with releasing our work back to the tapestry community under an open source license of some kind, so we can hopefully generate a very usable component library in fairly short order.
I'll keep the list informed on our progress. --sam On 4/2/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > Heh....I don't know what to say. That's a whole lot of discussion. You might > want to take a look at the turbo grid widget API before making any > assumptions about how it communicates with the server. > > On 4/2/06, Sam Gendler <[EMAIL PROTECTED]> wrote: > > > > Given that I know nothing about dealing with this in Tapestry, could > > you elaborate on the JSON layer. I assume I won't be able to glean > > much by picking apart your tacos code, since tacos is clearly not > > dependant on Tap 4.1. I'm on the tapestry-dev list now, but that is a > > very recent thing. I assume there is an archive, although I haven't > > looked for it, yet. > > > > Why would the server need to know about JSON at all? Wouldn't any > > object be converted to XML and sent to the server as an > > XmlHttpRequest? Unless you are talking about generating JSON in > > javascript, which I understand would be pretty difficult, now, in > > Tapestry. > > > > I'm assuming that for something like the data grid component, with in > > place edits, that each row would be sent to the server as it is > > updated, so there wouldn't be need for rewinding of a form, merely the > > new values of the properties for the object being updated along with a > > primary key or serialiazation of the old one. I would imagine the > > template would send an empty datagrid, and even the initial data > > population would happen via an ajax request, and subsequent updates > > would be a row at a time. I figured I could look at how something > > like the tacos:Autocompleter calls the listener to fetch the list for > > an example of how to populate the datagrid and send updated rows back > > to the server. > > > > --sam > > > > > > > > On 4/2/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > > None yet, but we'd love to add some sort of turbowidgets support. > > > > > > The JSON layer is there already in tapestry 4.1, so it's possble that it > > > might be do-able already. I'm sure Scott would be greatly appreciative > > of > > > people using his great library. > > > > > > On 4/2/06, Sam Gendler <[EMAIL PROTECTED]> wrote: > > > > > > > > I've been browsing around, looking at various DHTML and AJAX solutions > > > > that are available. The Turbo widgets look particularly polished and > > > > easy to use. They are free for non-commerical use and relatively > > > > low-cost for commercial use, so I'm wondering if anyone is using them > > > > successfully with Tapestry. > > > > > > > > I will admit that I'm a bit stumped about how to go about integrating > > > > some ajax functionality with Tapestry, due to constraints raised by > > > > the rewind mechanism, but I'm betting that solutions can be found for > > > > most issues. The TurboGrid component is particularly compelling to > > > > me, allowing client side sorting and in place editing, as are the > > > > slider, which should be relatively easy to support within Tapestry. > > > > > > > > So is anyone out there playing with these, or interested in doing so? > > > > I'll surely be making an attempt in the near future, but I am fairly > > > > new to Tapestry, utterly new to dojo, and far from an expert > > > > DHTML/Javascript programmer. I've always been a backend guy, but the > > > > two seem to be merging. At any rate, I am in the middle of a > > > > commercial project, and some of those widgets are going to be required > > > > eventually, so I know I'll be digging into the problem. > > > > > > > > So keep an eye out for future component announcements from me. > > > > > > > > --sam > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > -- > > > Jesse Kuhnert > > > Tacos/Tapestry, team member/developer > > > > > > Open source based consulting work centered around > > > dojo/tapestry/tacos/hivemind. http://opennotion.com > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Jesse Kuhnert > Tacos/Tapestry, team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://opennotion.com > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
