Since I missed much of the early conversation about these features, is there some documentation about how to use them? I am particularly interested in the JSON response builder and how I would plug into that in order to fetch data to populate widgets. At the very least, could you point me at the relevant files in the source code that would allow me to figure it out?
For instance, what I am really after is to build a form in tapestry which will submit back to tapestry via an xmlhttprequest and then receive json data which it can use to populate a grid. If I could do that, I could do some amazing things in my application and would be more than happy to be a tap4.1 beta tester of this functionality, but I don't have a ton of time to devote to reading source code to figure it out. --sam On 6/1/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Looks great guys! Esp all of the internal java code refactoring that's been happening. Makes me very happy to know it's improving :) I'm going to be trying to finish up the majority of features by the end of the weekend for tap 4.1 and wanted to know what everyone feels is really crucial to get in there. (keeping in mind time constraints). Either way a definitive list would be very helpful. Andreas should be able to assign JIRA issues to me/4.1 specifically once a good list is made. These are the broad brushstroke items I expect to have done: -) Ability to package dojo js within jar - done -) Rewriting of tapestry js to use dojo package system + test - done (partially) -) Native (ie non-enhanced class) support of ResponseBuilder-ish interfaces. done -) DojoResponseBuilder (not completely the same, but similar ) - done -) JSONResponseBuilder - For json style request/responses -) Leonardos very cool AjaxEventSubmit component in the form of a new annotation called EventListener (the xml .page .jwc has yet to be defined). This one is obviously a lot easier to use now that we have control of tapestry ;) -) ScriptTemplate/ PageRenderSupport control - done (ie we can control via ResponseBuilder exactly what script output is written, filtering by the component contributing it...The ResponseBuilder is also now more or less the new PageRenderSupport object instead of the Body component.....Allowing cool things like Dojo event.connect calls for initialization script stuff /etc...) -) Form handling - AjaxEventSubmit - ish submission of forms via EventListener annotation. Will also be supporting optionally validating the form (on client and server ) when submitted, as well as controlling which form components have their values submitted. (for partial submissions) -) Will be making small fix to Any component to eliminate unique id headaches Anything else major that I'm missing? (A jira issue for handling Direct component renders would be welcome, but isn't something I think will make it into the first alpha release, probably the second) If possible I'd appreciate it very much if Andy took over managing this list and getting the right things into jira and assigned to proper milestones/people etc...but that isn't absolutely needed. (don't want to sound too bossy ...umm. Please? heh ) -- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
------------------------------------------------------- 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
