+1. Even with my supposed "good" 4.1 examples of this stuff I wouldn't even dream of going in to T5 with the intention of doing anything that ambitious. If/when I do get to T5 it will be with the same clean slate as any project and I'll quietly ask about which bugs I can fix and generally take very tiny / guided baby steps with very tiny / definable tasks and work my out from there. (if I make it out from there without being pummeled too much =p)
I think more AJAX stuff will be nice but really from the framework POV it is mostly about the rendering model so anything there really would be a huge/ambitious change and not an after thought.. On 6/23/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
I don't know that Ajax support is "low hanging fruit" even with the excellent examples Jesse's put together in 4.1. It's not glamorous, but providing quality patches for the more minor bugs saves resources (i.e., time!) for doing the more complex things like adding Ajax and DatePickers, etc. On 6/22/07, Jeremy F. Kassis <[EMAIL PROTECTED]> wrote: > Hi Howard, > > Thanks for the quick reply on this. I got into T5 last weekend on my > personal time because I saw lots of activity on the tap-users list. I got > through the tutorial gotchas and even got our (ultra-simple) BumpQ homepage > up in T5. But I worked through the night (literally) and was pretty fried > when I posted this. Your T5 documentation was great, I just didn't see this. > Anyway, hope that someone will get some value out of this when searching > tap-users list sometime. > > I'm writing to (tenatively) see if I can help out the T5 project a bit. Erik > and I haven't raised the money yet, but we also haven't been trying. > Everything still looks good, we've just been heads down doing design and > development on our beta app. > > So to make a long story short, we don't have much time or resource to devote > to it, but T5 got my imagination going. > > One of the final barriers keeping us from moving to T5 is the AJAX support. > We make heavy use of the ultra-smooth DojoAjaxResponseBuilder in T4. > > I saw your post about the Ajax Dispatcher and went digging into the T5 > source a bit. If nobody's on it, I'm tempted to give it a try. But I know > that others know this stuff better than I do and could do it faster. > > So, on the other hand, I'm tempted to offer myself to take some low-hanging > fruit to free you or Jesse or whoever up to work on the Ajax Dispatcher. > > Anyway, interested to hear your thoughts on it. > > All the best, > Jeremy > > > > > > -----Original Message----- > > From: Howard M. Lewis Ship (JIRA) [mailto:[EMAIL PROTECTED] > > Sent: Sunday, June 17, 2007 2:19 PM > > To: [EMAIL PROTECTED] > > Subject: [jira] Commented: (TAPESTRY-1583) Cannot Pass Blocks > > to Layout Components > > > > > > [ > > https://issues.apache.org/jira/browse/TAPESTRY-1583?page=com.a > tlassian.jira.plugin.system.issuetabpanels:comment-> > tabpanel#action_12505625 ] > > > > Howard M. Lewis Ship commented on TAPESTRY-1583: > > ------------------------------------------------ > > > > I'd like to see a more realistic test case; what you have > > should be working, even though <t:parameter> was designed > > specifically to address what you are attempting. > > > > > Cannot Pass Blocks to Layout Components > > > --------------------------------------- > > > > > > Key: TAPESTRY-1583 > > > URL: > > https://issues.apache.org/jira/browse/TAPESTRY-1583 > > > Project: Tapestry > > > Issue Type: Bug > > > Affects Versions: 5.0.4 > > > Reporter: Jeremy F. Kassis > > > > > > As per > > http://tapestry.apache.org/tapestry5/tapestry-core/guide/templ > ates.html, the template of a page that calls a layout component > must look > like this: > > > <t:layout > > xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";> > > > My Page Specific Content > > > </t:layout> > > > The layout component looks like this: > > > <html > > xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";> > > > <head> > > > <title>My Tapestry Application</title> > > > </head> > > > <body> > > > <t:body/> > > > </body> > > > </html> > > > If I want a more sophisticated layout that renders blocks > > passed as parameters instead of just a body, i'd be tempted > > to try this: > > > <t:layout > > xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd"; > block1="block:block1" block2="block:block2"> > > > <t:block id="block1">My Page Specific Content for Block > > 1</t:block> > > > <t:block id="block2">My Page Specific Content for Block > > 2</t:block> > > > </t:layout> But tapestry can't bind block1 and block2, because they > > > appear in the template after the binding point. > > > This solution works, but produces an extra <html> tag in > > the output document: > > > <html > > xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";> > > > <t:block id="block1">My Page Specific Content for Block 1</t:block> > > > <t:block id="block2">My Page Specific Content for Block 2</t:block> > > > <t:layout block1="block:block1" block2="block:block2"></t:layout> > > > </html> > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > > > No virus found in this incoming message. > > Checked by AVG Free Edition. > > Version: 7.5.472 / Virus Database: 269.9.1/854 - Release > > Date: 6/19/2007 1:12 PM > > > > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.9.6/862 - Release Date: 6/22/2007 > 3:04 PM > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
