Oh god! I've been very busy lately, and now I think I'll have to catch
up on everything!
Great work!
Jesse, hmm I see you mention the unique id issues, but only for @Any? I
remember setting a JIRA issue sometime ago about client ids, and I think
Tapestry 4.1 would be a great place to solve this for every component
(basically having "clientId" to be guaranteed to work for every component).
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Web Application Design and Programming
http://www.dtqsoftware.com
Jesse Kuhnert 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
