Jesse Kuhnert wrote:
I'm going to be spending a little time this weekend trying to enhance
the debugability / error friendliness of some of the new ajax features
now that I've become more aware of certain bad defaults I've
introduced....Any help / suggestions are welcome.
Here are my own thoughts + stuff i'm working on:
- I miss the
void addStatusResponse(String status)
functionality we had in tacos. An implementation
that simply publishes those status messages to a topic
(dojo.event.topic.publish) is what i have in mind for this. If you
have other plans or simply want to stop me, please step in!
- I'll be working on a 'Ajax request in process so show/hide dom
element' component.
I don't think it requires major changes and i'm just mentioning this so
we don't
duplicate efforts.
Andreas, I don't want to appear to be "tasking" you - but as you did
some work on introducing the new @Style component semi-recently I was
wondering what you thought about tackling
https://issues.apache.org/jira/browse/TAPESTRY-1261 ?
Well, let me take a look at it and report back.
BTW, feel free to assign issues directly - at the very worst, i'll just
reassign back :)
I'm still not
quite sure how we go about doing that one.
--
Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
