Howard Lewis Ship wrote:
These bugs have to be fixed as well.
The question would be: just how important are them? Don't fall in the trap of 'just keeping yourself busy' - the most important things should go first.
(it's just advice)
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.
Is there a plan to this somewhere we non-committers can contribute / give feedback ?

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.
I'm considering it a limitation because I don't find any real reason as why pages shouldn't have parameters. Anyway, I don't mind if it's classified as a RFE or a critical bug, I'm just saying that it's nice to have easily bookmarkeable pages (as in the ExternalService), with clear parameters (name = value). The "required = true" is a good addition in order to ensure pages have a valid state and avoid boilerplate code (the "if(xxx == null) redirectToIndex()").

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.
Of course, me too. I'm building a production system and it's important to have stable software. Of course, I could use Tapestry 3, but then again, it's been a while, and Tap 4 has a lot of added value I'd like to use.

So, what about developer contributions? The main reason I have no motivation to contribute code to the project is that the few attempts I've tried to make have been ignored. People are busy? Maybe. But it's such a waste of good, motivated, developers, don't you think?

--
Ing. Leonardo Quijano Vincenzi
Director Técnico
DTQ Software




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to