On 21/01/2008, Eelco Hillenius [EMAIL PROTECTED] wrote:
Fine, this can be a good compromise: documentation written by the
skilled community and reviewed by the developers themselves. I'm not
that hardcore now, but the more I get into Wicket, the more I'll try
to help out as much as I can.
On Jan 14, 2008 1:35 AM, Eelco Hillenius [EMAIL PROTECTED] wrote:
Documenting Wicket's inner implementations and strategies, beyond its
API, is desirable and a huge plus for hardcore developers.
i wouldnt think hardcore developers would be afraid of setting a
breakpoint and walking the
On Jan 14, 2008 1:00 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
easy to say when its not you who has to put in the huge effort :)
I'm just a humble junior developer. :)
Regards,
Fabio Fioretti - WindoM
-
To unsubscribe,
On Jan 12, 2008, at 2:56 PM, Dmitry Kandalov wrote:
On Saturday 12 January 2008 23:25:43 Igor Vaynberg wrote:
sure, and all you need to know is that you subclass
requestcycle.onbeginrequest() and add your own code there and it is
called at the beginning of the request. why do you need to know
On Jan 14, 2008 6:08 AM, Alex Jacoby [EMAIL PROTECTED] wrote:
I've hit exactly this type of issue -- you try to override one of the
public methods, and it turns out that the object isn't fully
initialized yet, so you can't do what you'd hoped to.
do you have the example so we can do something
@wicket.apache.org
Subject: Re: the flow of wicket
I *strongly* disagree with your answer. The fact is that this
information is only beneficial for a really very small portion of our
user base. The documentation effort on the other hand is HUGE! And
subject to change easily. From 1.1 to 1.2 we
On Sunday 13 January 2008 04:19:30 Igor Vaynberg wrote:
Ok, so rarely you need to roll your own
IRequestTargetUrlCodingStrategy, we do provide implementations to
cover most common cases. And even if you do, you only need to know
about IRequestTarget - which has good javadoc, and so does the
On Sunday 13 January 2008 12:47:44 Dmitry Kandalov wrote:
On Sunday 13 January 2008 04:19:30 Igor Vaynberg wrote:
Ok, so rarely you need to roll your own
IRequestTargetUrlCodingStrategy, we do provide implementations to
cover most common cases. And even if you do, you only need to know
On Jan 12, 2008 8:56 PM, Dmitry Kandalov [EMAIL PROTECTED] wrote:
On the whole I think it's the matter of knowing the big picture and not using
framework as a black box.
Exactly. For knowledge's sake.
Documenting Wicket's inner implementations and strategies, beyond its
API, is desirable and a
On Jan 13, 2008 3:28 PM, Fabio Fioretti [EMAIL PROTECTED] wrote:
Documenting Wicket's inner implementations and strategies, beyond its
API, is desirable and a huge plus for hardcore developers.
i wouldnt think hardcore developers would be afraid of setting a
breakpoint and walking the code.
Documenting Wicket's inner implementations and strategies, beyond its
API, is desirable and a huge plus for hardcore developers.
i wouldnt think hardcore developers would be afraid of setting a
breakpoint and walking the code. maybe one of them could even create a
wiki page - open source
It would be faster if you can help us. :)
sure, it would probably be faster if i coded your project
for you too :)
Cool!
Since you're now doing this kind of volunteer work, Igor,
how about coding some stuff for me, too? ;-)
I'll send you the project description
I disagree with this answer.
The fact that request handling stuff is not a public api, is A GOOD REASON
because it should be documented better, not viceversa.
And I really don't understand in which way this could prevent you to change
- eventually - in future wicket versions.
I not a newbie
On Jan 12, 2008 7:16 AM, Paolo Di Tommaso [EMAIL PROTECTED] wrote:
I disagree with this answer.
The fact that request handling stuff is not a public api, is A GOOD REASON
because it should be documented better, not viceversa.
should we document how our xml parser works? how about how wicket
I *strongly* disagree with your answer. The fact is that this
information is only beneficial for a really very small portion of our
user base. The documentation effort on the other hand is HUGE! And
subject to change easily. From 1.1 to 1.2 we changed it quite
considerably. And I have no doubt
+1
On 1/12/08, Paolo Di Tommaso [EMAIL PROTECTED] wrote:
I disagree with this answer.
The fact that request handling stuff is not a public api, is A GOOD REASON
because it should be documented better, not viceversa.
And I really don't understand in which way this could prevent you to change
On Saturday 12 January 2008 19:56:41 Igor Vaynberg wrote:
should we document how our xml parser works? how about how wicket
assembles parts of markup into different markup fragments? all these
things have no effect on you as a wicket user.
a question for you, in what way will knowing the
On Jan 12, 2008 11:11 AM, Dmitry Kandalov [EMAIL PROTECTED] wrote:
On Saturday 12 January 2008 19:56:41 Igor Vaynberg wrote:
I mostly agree but request processing is more exposed to user than xml parser.
I mean it's easier to came across AjaxRequestTarget,
RequestCycle#onBegin/EndRequest() or
On Saturday 12 January 2008 23:25:43 Igor Vaynberg wrote:
sure, and all you need to know is that you subclass
requestcycle.onbeginrequest() and add your own code there and it is
called at the beginning of the request. why do you need to know the
sequence of calls that leads to onbeginrequest()
As far as i know there are some things on the wiki that explains what
hooks (onXxx) is called when.
And for the public methods this is fine and that should be documented,
but still the rest should remain a black box as much as possibe
On 1/12/08, Dmitry Kandalov [EMAIL PROTECTED] wrote:
On
I disagree with this answer.
That's great! You are most welcome to disagree. I happen to disagree with
your disagreement.
That's the great thing about OSS... If you disagree strongly enough, then
maybe you can write more stuff on the wiki.
I think you're missing a good opportunity here: look
It would be faster if you can help us. :)
sure, it would probably be faster if i coded your project for you too :)
Cool!
Since you're now doing this kind of volunteer work, Igor, how about coding
some stuff for me, too? ;-)
I'll send you the project description off-link, but you need to
only 67? :)
-igor
On Jan 11, 2008 9:34 PM, David Leangen [EMAIL PROTECTED] wrote:
It would be faster if you can help us. :)
sure, it would probably be faster if i coded your project for you too :)
Cool!
Since you're now doing this kind of volunteer work, Igor, how about coding
some
seconded
-Original Message-
From: Beyonder Unknown [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 10, 2008 5:05 PM
To: WICKET USER
Subject: the flow of wicket
Hi All,
I am studying wicket from the WicketFilter to the WebApplication, but I
don't understand the concept of
: Re: the flow of wicket
On Jan 10, 2008 5:47 PM, Beyonder Unknown [EMAIL PROTECTED] wrote:
Hi Igor,
Since it got mentioned in the book, I just thought I'd asked for more
information.
IRequestCycleProcessor has javadoc which explains what it is used for.
the actual workflow is unimportant
25 matches
Mail list logo
