May be it is too early, but I have a strange problem.
I'm currently playing with backporting some MarkupParser functionality
which makes it is more easy to add IMarkupFilter and insert them at
the right (user determined) place.
This is the original junit output of SimpleTestPanelTest:
...IUnvers
oh that's right. i totally forgot about that semantics change. is that
already in trunk?
i think this since this is really just for initing components that need
context, under the new semantics we would only need isFirstRender and
isFirstRenderAfterAdd. that seems fairly clean and self-explanato
will we also have isFirstBeforeRender and isFirstBeforeRenderAfterAdd? since
in onattach you cannot modify component hierarchy anymore, and you shouldnt
really be attaching models in onbeforerender.
-igor
On 5/4/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
right.
well, if the component wa
right.
well, if the component wants to check for re-init, the method should
definitely not be called isFirstAttach() because a re-init is not a first
attachment.
i think there's a compelling and very common use case for one-shot
isFirstAttach() that works exactly like a constructor with the r
so i propose a vote to add this. i'm +1.
Eelco Hillenius wrote:
>
> Yeah. I actually think I proposed something like this, or at least
> +1-ed one at more than a year ago. You'll have to dig in the archives
> to find out why other people didn't agree back then, but I still think
> it's much e
We (Johan and me) actually discussed this with Jonathan right after we
became active. Jonathan's reason was that he thought it was just
simpler/ more straightforward. On top of that, it saves a little bit
of memory.
Imho, I could live with both, but my preference now would be to keep
what we have
wicket uses callback methods instead of listeners for a simple reason: it is
a smaller memory footprint - there is no list to store, no listener
implementations to serialize. it is further my experience that you very very
rarely need more then one listener, so it cannot justify the overhead imho.
When I've started using Wicket few months ago, I found myself wondering: why
do I have to override methods instead add listeners to my component?
Developing forms is quite strange to me, when I have to override the
onSubmit() method. If we say "Swing-like OO Component Model", why there's no
liste
Yeah. I actually think I proposed something like this, or at least
+1-ed one at more than a year ago. You'll have to dig in the archives
to find out why other people didn't agree back then, but I still think
it's much easier for users to discover something just because it has
an obvious name, and
On 5/4/07, Upayavira <[EMAIL PROTECTED]> wrote:
> So, do we want to propose graduation?
>
> [+1 ] Yes, propose Wicket for Graduation
Definitely - and (briefly) meeting some of the Wicket guys here at
ApacheCon has been a pleasure!
Likewise. Let's do that more often!
Eelco
as of yesterday it is
-igor
On 5/4/07, Ivo van Dongen <[EMAIL PROTECTED]> wrote:
On 5/4/07, James McLaughlin <[EMAIL PROTECTED]> wrote:
>
> fwiw, i've occasionally wanted an onRemove callback in the component
(and
> now behavior :) )
Did I mis something? Is it possible to remove behaviors
On 5/4/07, James McLaughlin <[EMAIL PROTECTED]> wrote:
fwiw, i've occasionally wanted an onRemove callback in the component (and
now behavior :) )
Did I mis something? Is it possible to remove behaviors now? That would be
great, this was something I ran into last week with a timer behavior.
Having worked with many Apache based projects in the past, I'd say (for what
my own voice is worth), that Wicket deserves graduation.
Wicket is a well conceived architecture, and a model that should enjoy a
healthy adoption rate.
[+1] Yes, propose Wicket for Graduation
-jjk
On 5/4/07, Bertrand
well i dont know
if you need second-phase-init then you are likely doing something that is
"context-sensitive" because this context is the only thing you are missing
in the constructor really.
so when you move things around the context changes, so should the component
reinit itself?
-igor
On
good question. re-adding dynamism seems like a fairly unusual use case (can
you think of any good ones?) so i think the answer is probably no. it seems
like if you have a component that dynamically does things on being re-added
you could manage that case on your own.
igor.vaynberg wrote:
>
On 5/4/07, Upayavira <[EMAIL PROTECTED]> wrote:
So, do we want to propose graduation?
[+1 ] Yes, propose Wicket for Graduation
Definitely - and (briefly) meeting some of the Wicket guys here at
ApacheCon has been a pleasure!
-Bertrand
[X] Yes, propose Wicket for Graduation
--
Bruno Borges
Summa Technologies Inc.
www.summa-tech.com
(48) 8404-1300
(11) 3055-2060
On 5/4/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote:
[X] Yes, propose Wicket for Graduation
Jan.
--
View this message in context:
http://www.nabble.com/-VOTE--Propos
fwiw, i've occasionally wanted an onRemove callback in the component (and
now behavior :) ) hierarchy so the object can undo some of its "damage" when
replaced. If we had this, then we could leave that issue to the developer's
discretion. I've had to use the two phase init pattern occassionally, s
[X] Yes, propose Wicket for Graduation
Jan.
--
View this message in context:
http://www.nabble.com/-VOTE--Propose-Wicket-for-Graduation-tf3691551.html#a10324760
Sent from the Wicket - Dev mailing list archive at Nabble.com.
so is it a firstattach if you remove a component and then readd it at a
later time?
-igor
On 5/4/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
Although I do still think we should generally discourage two-phase
construction, it is occasionally truly necessary and it seems like it
might
be nic
In my work project, I've added and frequently use an EmptyPanel which is
simply a panel with empty markup. Although you can do the same thing with
WebMarkupContainer or implement this yourself, it does seem like a nice
conceptual addition, particularly for newbies who might not think "hmm... i
wa
Although I do still think we should generally discourage two-phase
construction, it is occasionally truly necessary and it seems like it might
be nice to have a method up in Component that uses those component bits to
return whether the component has been attached already. This way, when two
phase
In the former Wicket 2.0, the Session attach() was defined in WebSession, and
called in WebSession:initForRequest():
/**
* Initializes this session for a request.
*/
public final void initForRequest()
{
// Set the current session
[X] Yes, propose Wicket for Graduation
On 5/4/07, Upayavira <[EMAIL PROTECTED]> wrote:
After many discussions with folks here at ApacheCon EU, I have confirmed
my previous feeling that Wicket is ready to graduate.
The community is strong, a successful release has been made, and the
community wo
[X] Yes, propose Wicket for Graduation
Juergen
[X] Yes, propose Wicket for Graduation
-igor
[X] Yes, propose Wicket for Graduation
Upayavira-2 wrote:
>
> After many discussions with folks here at ApacheCon EU, I have confirmed
> my previous feeling that Wicket is ready to graduate.
>
> The community is strong, a successful release has been made, and the
> community would really be
[ x ] Yes, propose Wicket for Graduation
[ ] No, Wicket is not ready to graduate
Eelco
I couldn't be more supportive of doing this. IMO Wicket is the best
community we have had in the incubator to date.
On 5/4/07, Upayavira <[EMAIL PROTECTED]> wrote:
[X] Yes, propose Wicket for Graduation
Alex
[X] Yes, propose Wicket for Graduation
Ate
Upayavira wrote:
After many discussions with folks here at ApacheCon EU, I have confirmed
my previous feeling that Wicket is ready to graduate.
The community is strong, a successful release has been made, and the
community would really benefit from
On Friday, May 4, 2007, 12:23:37 PM, Upayavira <[EMAIL PROTECTED]> wrote:
> So, do we want to propose graduation?
[X] Yes, propose Wicket for Graduation
/Gwyn
[X] Yes, propose Wicket for Graduation
[ ] No, Wicket is not ready to graduate
-Matej
On 5/4/07, Upayavira <[EMAIL PROTECTED]> wrote:
After many discussions with folks here at ApacheCon EU, I have confirmed
my previous feeling that Wicket is ready to graduate.
The community is strong, a succes
On 5/4/07, Upayavira <[EMAIL PROTECTED]> wrote:
[X] Yes, propose Wicket for Graduation
Martijn
--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframewor
Upayavira wrote:
After many discussions with folks here at ApacheCon EU, I have confirmed
my previous feeling that Wicket is ready to graduate.
The community is strong, a successful release has been made, and the
community would really benefit from the move to TLP.
For this move, we as a com
[X ] Yes, propose Wicket for Graduation
On 5/4/07, Upayavira <[EMAIL PROTECTED]> wrote:
After many discussions with folks here at ApacheCon EU, I have confirmed
my previous feeling that Wicket is ready to graduate.
The community is strong, a successful release has been made, and the
community
After many discussions with folks here at ApacheCon EU, I have confirmed
my previous feeling that Wicket is ready to graduate.
The community is strong, a successful release has been made, and the
community would really benefit from the move to TLP.
For this move, we as a community need to agr
No no, the wiki is fine, it is just located in another sub-directory!
> fix wiki! :)
>
> On 5/4/07, Erik van Oosten <[EMAIL PROTECTED]> wrote:
>>
>> Oosp, I found it at
>> http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/!
>> Of course, the groupid changed.
>>
>> > Hi,
>> >
>> > Th
fix wiki! :)
On 5/4/07, Erik van Oosten <[EMAIL PROTECTED]> wrote:
Oosp, I found it at
http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/!
Of course, the groupid changed.
Have fun,
Erik.
> Hi,
>
> The wiki page
> http://cwiki.apache.org/confluence/display/WICKET/Wicket+fro
Oosp, I found it at
http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/!
Of course, the groupid changed.
Have fun,
Erik.
> Hi,
>
> The wiki page
> http://cwiki.apache.org/confluence/display/WICKET/Wicket+from+source says
> that you can find the latest snapshots on
> http://wick
Hi,
The wiki page
http://cwiki.apache.org/confluence/display/WICKET/Wicket+from+source says
that you can find the latest snapshots on
http://wicketstuff.org/maven/repository/wicket/wicket/. There is no such
build for the trunk.
Will this be added?
Regards,
Erik.
--
Erik van Oosten
http://ww
40 matches
Mail list logo
