Jesse, those where 3 ideas, not 2 :P.
But anyway...
1) As far as I understood, this translator stuff is to make Tapestry
more autobinding capable. Since most of my forms deal with "foo.bar"
expressions (some object and a property inside of that object), as long
as autowiring supports that, I'm happy.
2) This is for the performance concerned guys ;). Needed, though.
3)
Yet-another-Hibernate-Tapestry-Integration-Project? Really, why don't
people just use Spring? Unless someone comes up with a Seam equivalent
for Tapestry, I don't understand exactly what's the purpose of this.
That said, I do have some Hibernate-Spring-Tapestry stuff I could
eventually contribute, dealing with long sessions (which are needed for
*everything* in Hibernate.... what a waste of resources..).
My 2 desired things:
4) A janitorial project / section / component / whatever. Yeah, I know
it's not as sexy. But really... it's needed.
5) DHTML subproject... not only Ajax but also simpler effects, including
validation, enabling / disabling components, etc.. I wrote about this
some time ago.
In any case, I'm getting worried that the focus is losing in this
development. I wonder, why don't we focus all resources into removing
the rewind cycle, or eliminating abstract classes, or some of the other
stuff Howard said he would like for Tap 4.1 / 5 ?
Or else we'll end up with a 3 year development cycle...
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Jesse Kuhnert wrote:
If there was a theoretical person who wanted to cut their teeth on tapestry
a little more closely than just using it, what would everyone like them to
work on ?
I know we'd all like documentation / various infrastructure stuff done but
this is more an exercise in learning tapestry internals as well as proving
coding abilities and such...So, the value has to be on both sides.
I don't think there's anything we could throw at this theoretical person
that they couldn't handle, so feel free to think of whatever you like. Keep
in mind that I think we should probably just pick one for now, so think
about it before voting :)
My two ideas so far are:
1) Find a way to do what I described earlier with elimintating the need to
specify a translator binding...If this means working with Patrick Lightbody
over at opensymphony (where the ognl code now lies dormant) , then so be it.
2) Work with mind bridge to see what these patches he had for OGNL were a
long time ago that theoretically sped up runtime performance of these
operations. I see that these things are already being compiled and cached
though, so I'm wondering if this effort is even needed.
3) Work with whoever exists in the community doing hibernate things with
tapestry and make Howard's EditObject blog entry a reality. This would
hopefully be done in some project either hosted as a sub project on
http://howardlewisship.com or as part of an existing project, like honeycomb
/ James Carmen's work with trails / hiveutils / etc...
I'm personally hoping for #3 because I think it will provide the most value
for the community. Everyone's input is welcome.
--
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]
