On 10/29/05, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote: > My question about this and other important bug-cases is: are Tapestry > commiters tired after all these years or something?? I recently invested > in learning Tapestry and ditching JSF (which was a huge setback on a > project I was working on), but I'm starting to think people here are in > "fixing small bugs" mode
These bugs have to be fixed as well. > and no one's paying attention to the > architectural issues and the unnatural bugs (such as... why can't I use > an @If condition to filter a text box?) Tapestry is now nearly six years old. It is no way resemebles the code base when I first started. I made a number of really lucky guesses early on, and a couple of less than ideal choices. Some of the architectural issues are all but impossible to fix without completely disrupting backwards compatibility. At the core, I'm looking for a way to completley eliminate the rewind cycle and come up with a simpler, better way of getting data out of the request, through the components, and into the model properties. or strange limitations (why > can't I use @Parameter(required = true) in a page?). > Because pages don't have parameters, components do. You are looking for an entirely new concept in Tapestry ... one that may be valid, but simply isn't present today, so don't consider it a bug. > Maybe no one's looking well enough at the JIRA database, because there > are lots of abandoned issues over there, and most recent commits have > been of examples re-writing (what for? is it more important than fixing > the problem with Checkboxes - FieldLabels?) or small bugs fixed. I've been making passes through the database and taking on as many bugs as I can. We all have outside responsibilities to our lives and our clients, so things happen when they happen. > > As for Geoff's comment, I still fail to understand why the bug is so > critical. The only concern about it it's the need of restarting the > container in order to fix things. Maybe that's the primary concern about > this. The other stuff can be solved through good conventions in the > project, right ? > > -- > Ing. Leonardo Quijano Vincenzi > Director Técnico > DTQ Software > > > > Geoff Longman (JIRA) wrote: > > [ > > http://issues.apache.org/jira/browse/TAPESTRY-724?page=comments#action_12356303 > > ] > > > > Geoff Longman commented on TAPESTRY-724: > > ---------------------------------------- > > > > Obviously I have not made my case clearly enough to generate even one > > comment. While this issue has been in JIRA for 6 days it has been a bug in > > my ear for 27 days and I emailed Howard privately on the first day. > > > > This all started as I'm trying to get Spindle updated for Tapestry 4 and I > > encountered what I feel is a serious bug in T4. It's behaviour that I'm > > loath to duplicate in Spindle as it is a tool that garners all of it's data > > from the static representation of a Tapestry project. The changes in the > > SpecificationResolver/PageLoader in T4 move this class lookup out of the > > static information and into the runtime behaviour of Tapestry. Spindle has > > never and will never try to duplicate the runtime behaviour of Tapestry. > > > > But that's beside the point, Tapestry is broken and nobody seems to care. > > > > I have ideas and suggestions on how to fix this but they are obviously > > skewed towards making my life as the Spindle developer easier and that may > > clash with the vision for Tapestry as a whole. Without any discussion on > > the issue I'm wasting my time even looking any further. > > > > Maybe I'm a bit short tempered as I have been ill for the last week but I'm > > fed up. I hate it that I feel driven to make the following statement... > > > > Consider Spindle for T4 on hold indefinitey until something moves on this > > issue. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta 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]
