eclipse doesnt catch this, neither does javac i dont think :| they catch
generics and other language constructs, but you can still import classes
like stringbuilder
-igor
On 2/27/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Eelco Hillenius:
> > I already have 1.4 compliance level in
but there is also an enabled action that can work very well for this. if the
page is not enabled it wont be rendered
-igor
On 2/27/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
you are correct that there is an underlying assumption that a user's roles
cannot change within a session. to sol
could you please add it to jira, thanks
-igor
On 2/27/07, Stefan Lindner <[EMAIL PROTECTED]> wrote:
The current slf4j version included in wicket2 examples is 1.1.0. It should
be 1.3.0 because the Logger class name changed and the core wicket library
already uses the new name.
Stefan Lindner
but i use it all the time just as a textfield, so you are saying i am
screwed because all of a sudden my model would be null just because there
are no autocomplete options?
i think what is really needed here is another component.
-igor
On 2/27/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
but that is so disjointed.
for example how will that interact with setrequired(true)? you entered
something into text but the model is null?!?
also
lets say i want to create a new person if one doesnt exist. if i know this
field works with strings only there is one thing for me to do, write a m
but what good is it if the model is set to null when that entered text is
still a valid entry? how does the user then get that entered text? why isnt
the text the model?
thats why it is the way it is - working with strings only.
-igor
On 2/27/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
i
[ ] No, I object! Java 1.4 examples are the thing I live and die for
[X] Yes, make one examples project to rule them all, and by all means,
make it Java 1.5 dependent
its a combobox, what if they submit text that is not part of any existing
selection?
-igor
On 2/26/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
Don't you think it should work the same as other list selection
components?
You give the component a list of objects to choose between using the t
looks very neat!
there is a com.apple import in the quickstartapplication that you might want
to remove :)
i think we should also redo the component reference. im very fond of the
backbase ajax explorer examples - which is their component reference. i like
the nav tree on the left, and really li
thanks! :)
-igor
On 2/26/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Igor Vaynberg:
> jbq, if you wouldnt mind could you please create patch filenames
> with an extension. .patch or .txt will do. its a pita to open
> these files in winblows if they have no exte
jbq, if you wouldnt mind could you please create patch filenames with an
extension. .patch or .txt will do. its a pita to open these files in
winblows if they have no extension since you have to go through the "open
with" dialog everytime.
thanks,
-igor
On 2/26/07, Jean-Baptiste Quenot (JIRA) <
you are assuming that identity is only defined by the class. but what if
pageparameters/models are also involved?
then that code has to go somewhere anyways
-igor
On 2/25/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
let's just take a step back and ask: how can we make this less work?
cou
add( new link("foo") {
onclick() { setresponsepage(new MyAccountPage()); }
boolean linksto(Page page) { return page.class.equals(MyAccountPage.class);
}
}
simple as that and the bookmarkablepagelink already also does this
-igor
On 2/25/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
i don
why not let us remove it, and you copy it into your project
-igor
On 2/25/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
i don't want to gang up on martijn here, but that's what i meant.
i also think we should refactor pagelink with the remaining two
constructors to:
pageclasslink (the on
>
> Frank Bille wrote:
>> On 2/22/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>>>
>>> why dont we just remove PageLink altogether?
>>>
>>
>> +1, remove the bastard :)
>>
>> Frank
>>
> a big +1 from me too.
>
> -Mat
gt;>
>> igor.vaynberg wrote:
>> >
>> > whats the usecase btw? what are you going to do with that exception?
>> those
>> > are only render-time exceptions, dont see what use they are to you
>> >
>> > -igor
>> >
>> &
wrote:
>
> whats the usecase btw? what are you going to do with that exception?
those
> are only render-time exceptions, dont see what use they are to you
>
> -igor
>
>
> On 2/22/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>>
>> irequesttarget.respond doesn
why dont we just remove PageLink altogether?
-igor
On 2/22/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/22/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
> * Igor Vaynberg:
>
> > yet another example of noobs precrecreating page instances
> > be
whats the usecase btw? what are you going to do with that exception? those
are only render-time exceptions, dont see what use they are to you
-igor
On 2/22/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
irequesttarget.respond doesnt declare it throws any exceptions, so we
would n
irequesttarget.respond doesnt declare it throws any exceptions, so we would
need to refactor ajaxrequesttarget.respond into some protected method.
add a jira issue
-igor
On 2/21/07, Oscar Bueno <[EMAIL PROTECTED]> wrote:
Hi,
Now the respond method of the AjaxRequestTarget is caching all th
+1
-igor
On 2/22/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
yet another example of noobs precrecreating page instances before the link
is clicked. the api of that constructor simply sucks. and yes martijn, it is
very convinient to do new pagelink
yet another example of noobs precrecreating page instances before the link
is clicked. the api of that constructor simply sucks. and yes martijn, it is
very convinient to do new pagelink("back",
backpageinstancesyougotpassedintothispage), but you can live with a few more
lines of code :)
so the
the biggest thing holding up the release are a few missing iclas, working
on that now.
-igor
On 2/22/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* [EMAIL PROTECTED]:
> Author: ehillenius
> Date: Thu Feb 15 10:19:54 2007
> New Revision: 508062
>
> URL: http://svn.apache.org/viewvc?vie
applied
-igor
On 2/22/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Igor Vaynberg:
> This is a vote to apply a patch in
>
> https://issues.apache.org/jira/browse/WICKET-290
+1 this was a big showstopper before the relative URL refactoring
--
Jean-Baptiste Q
rt for soft/weak References ..
because you can't serialize a weak or soft reference.
If you make a test, use the WebCompressing strategy and look what happens
with the URLCompressor class.
johan
On 2/21/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>
> right, thats what i meant
right, thats what i meant
-igor
On 2/21/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
And they don't have to. At least not according to what they are doing with
it.
Eelco
On 2/21/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> they dont
>
> -igor
>
>
>
they dont
-igor
On 2/21/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
i am very interested how the handle the special serialization cases.
like readObject and writeObject methods or writeReplace..
johan
On 2/21/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> > Looking forward to it! I
On 2/20/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
do remember we are trying to avoid serialization and writing of the file
in
the request thread itself
So the request can be fast. Only the background thread(s) should do the
serialization and writing
The only time the request thread is doing
On 2/19/07, Ryan Holmes <[EMAIL PROTECTED]> wrote:
I know you guys have already thought about/discussed this, but can't
you reduce the size of the page map by storing deltas? I thought I
saw a thread about it in the dev list archives... What I'm getting at
is that if you could significantly redu
Event(AjaxTarget)
{
ajaxtarget.add(component);
ajaxtarget.setFocus(component,ignoreEvents)
}
then i can controll it on the serverside completely
johan
On 2/19/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
>
> really?
> matej, do tell!
>
> i can work on it also because i really need
eed it :)
johan
On 2/19/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>
> yes, tracking is easy with our new event thing :)
>
> get on it matej!
>
> -igor
>
>
> On 2/19/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> >
> > attach an onfocus event
yes, on large scale maybe. i am talking about small self-contained modules.
and this isnt really InstallHook :)
not all approaches like this are bad. eclipse/osgi is one example where
there are a ton of tiny modules that work together really well.
-igor
On 2/19/07, Jonathan Locke <[EMAIL PROTE
see this is where we would disagree. if a strategy adds some annots for you
to use the compoudness is seamless. as long as the strategy in the module is
designed as an "mixin" it should work just fine no matter what user has got
going. thats why its an interface :)
-igor
On 2/19/07, Jonathan Lo
you can have multiple strategies easily working together. just keep looping
through them until you get a false out of one (a veto) and then stop. if no
false then it passes - true. just what a compound strat would do.
but setonce and exception wont work. then module can never set one, so we
lose
the thing i dont like about is that if a module installs a strategy the user
can then later overwrite that strategy in security settings by simply
calling set with his own. its the semantics of set/get vs add that suck in
this case, add is more preferrable with veto return values from the
strategi
+1
-igor
On 2/19/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
Any objections now? (for 1.3 and 2.0)
Because you can't remove a behavior from a component and now you
also can't dynamically disabled one either. So thats a bit annoying.
johan
yes, tracking is easy with our new event thing :)
get on it matej!
-igor
On 2/19/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
attach an onfocus event on all focusable components
then have a javascript variable in the page that gets that assigned
then i prepend a script that uses that la
+1 but i still think an exception is better
-igor
On 2/19/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
+1
On 2/19/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> > I'd like to apply the fix for issue WICKET-298
> > (http://issues.apache.org/jira/browse/WICKET-298) to Wicket 1.2.x. The
>
a
log takes the hours I was talking about. :( Debugging is more effective
most of the time.
Regards,
Erik.
Igor Vaynberg wrote:
> all these cons are invalid
> you would also get class not found on the annotations like @SpringBean
> and a log message tells you what modules have b
this before. The only
catch with auto-discovery/config/whateveryoucallit is - like we can
see now with JMX - what do you do when people want it to be not
activated. If we can have that as part of the pattern, I'm all for it.
Eelco
On 2/18/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>
all these cons are invalid
you would also get class not found on the annotations like @SpringBean
and a log message tells you what modules have been initialized
:)
-igor
On 2/18/07, Erik van Oosten <[EMAIL PROTECTED]> wrote:
Hi Igor, Jonathan,
Good idea, I have never liked the way I had t
i guess another thing to consider is that in both of these cases there are
no sideeffects of installing these things. if you dont use the annots
everything is as it was before. so its not like you drop this file in and
all of a sudden things get weird.
-igor
On 2/18/07, Igor Vaynberg <[EM
i disagree. having things explicit is very nice when there is a need for you
to know, but what if there isnt?
take wicket-spring module. its only service is to make fields annotated with
@SpringBean injectable. why should the user care that this is done with the
componentinstantiationlistener, or
just thinking out loud...
for a long time we have had problems with addons that have their own
application subclass because if you wanted to use more then one addon you
had to bastardize the code of one and add it to the application subclass of
the other. recently i refactored wicket-spring to no
energy on discussions like this. my last 2c.
-igor
On 2/18/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/18/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> why are we still arguing about this?
>
> just deprecate the damn method already and add the variant
Because th
why are we still arguing about this?
just deprecate the damn method already and add the variant
-igor
On 2/18/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
If the break is hypothetical, then why not leave it in there, perhaps
using @deprecated?
If there is just one user depending on it, th
i look at it differently. i see wicket-datetime as a collection of
date/time-related components built around joda. only one of them is a
datepicker and that just happens to be backed by yui. if i want to use a
datepicker why would i need a dependency on the entire wicket-yui? i dont
care what the
oh, btw this is a fix for [Wicket-user] Relative URL-s on the page stop
working after HTTP POST
-igor
On 2/16/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
This is a vote to apply a patch in
https://issues.apache.org/jira/browse/WICKET-290
i have briefly tested it and it seems to wo
+1
-igor
This is a vote to apply a patch in
https://issues.apache.org/jira/browse/WICKET-290
i have briefly tested it and it seems to work, if anyone thinks this will
break something please speak up.
-igor
> well i think at this point we need to create a process for introducing
new
> core modules that will determine how the responsibility for maintaining
them
> is assigned
That could be:
1) someone proposes a new module (like I just did)
2) if no-one *opposes* this means 'go ahead'
3) that person
On 2/16/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/16/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> honestly i dont think any yui stuff should be in extensions.
> what is to stop wicket-stuff-dojo to want to move to extensions as well?
jbq
> is a committer a
onents in Wicket extensions as it's just a
javascript dependency which won't be in your way if you're not using
the components that are based on it.
Eelco
On 2/16/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> i would like to have a separate wicket-datetime for the datepicker
and while you are at it you should fix the datepicker's namespace to
wicket.datetime
-igor
On 2/16/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
i would like to have a separate wicket-datetime for the datepicker and
date related stuff, if you want to create a separate yui proje
i would like to have a separate wicket-datetime for the datepicker and date
related stuff, if you want to create a separate yui project and then copy
the datepicker from datetime into there as well that is fine by me
-igor
On 2/16/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Committers, can
[x ] apply to 1.2.x
-igor
i hope you see this is a bit of a catch 22
without user testing we wouldnt even know that proxies do not work properly
:)
my vote is this
+1 to have it on by default, but the stack trace should include instructions
on turning it off and a message for users to email the stack trace.
best of bot
-- Forwarded message --
From: Igor Vaynberg <[EMAIL PROTECTED]>
Date: Jul 20, 2006 3:55 PM
Subject: form.onsubmit vs button.onsubmit
To: wicket-develop@lists.sourceforge.net
i just noticed that we call button.onsubmit() /before/ form.onsubmit(), i
always believed this to be the oth
johan
On 2/14/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
>
> Why wouldn't you be allowed to do that? Does anyone object?
>
> -Matej
>
> Igor Vaynberg wrote:
> > thats because we have ten thousand methods for attaching and
detaching,
> and
> > behavior
On 2/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
I'm not sure. The idea behind that is that whether your requests ends
normally or with an exception, you'll always have that cleanup method
called (I know there was a bug, but that's not the point). If we don't
have that and you need to free
what needs to be changed is this:
ibehavior needs to extend idetachable
detachmodels() -> detach()
remove abstractbehavior.cleanup()
-igor
On 2/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
So this is what we have now:
public interface IBehavior extends Serializable
{
/**
cleaning it up further
-igor
On 2/14/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
+1
I hope it will work this time. We are fighting this since 1.2.1 or so.
-Matej
Igor Vaynberg wrote:
> currently things are not properly detached in 1.2.x after an ajax
request.
> this patch [1] fixes
+1
-igor
currently things are not properly detached in 1.2.x after an ajax request.
this patch [1] fixes it.
the root of the problem is that only components that are rerendered get
behavior.cleanup() called. but if you have something like this:
page
+- ajax link
+- panel
and that ajax link repaints the
i agree 100% this should be a server-side setting
btw if we had access to svn we could configure eclipse to format the code
upon checkin, it has a headless switch for that :|
-igor
On 2/13/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
so that is sooo stupid.
configuring something so it affe
ok anon users can no longer edit pages or leave comments
-igor
On 2/13/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
I was able to edit pages using just a captcha as an anonymous user.
Martijn
On 2/13/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> i thought it was
>
&
i thought it was
you need to login to comment/edit pages
you need to fill in a captcha to signup
-igor
On 2/13/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Not sure if captcha is on for comments, it is for editing pages.
Anyhow, I removed the spam.
Martijn
On 2/13/07, Johan Compagner <
On 2/13/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
So i will make it identity equal for all objects except String
but isnt string identity guaranteed for equal strings because the jvm pools
them?
so String a=new String("a");
String b=new String("ab").substring(0,1);
b==a
-igor
hrm, so the default jdk serialization is also building a toc? interesting,
thats what i wanted to know.
-igor
On 2/12/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> no, this is different
>
> B b=new B(); b.a=new A(); b.aprime=new A();
>
> they are different instances, i am talking about cla
On 2/12/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/12/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> hmmm
> so if you have something like this
>
> class A {}
> class B { private A a; private A aprime; }
>
> when you serialize B does it write the
ts should be enough i think?)
So i guess having a build in map of the first 254 mostly used classes and
only write a byte
and let the rest be just as the classname (only once, the second time it
is
a handle)
johan
On 2/13/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>
> well you kn
hey directly use the back button at that time same time
So if i set it up. Then i don't think i would use a NAS server anyway.
Because that overhead you have with that for only catching a failover and
then
directly a backbutton. I don't think i would use that.
johan
On 2/12/07, Igor
we discussed it before
the consensus at that time was to keep them because they make
blaming^H^H^H^H^H^H^Hdelegating easier
-igor
On 2/12/07, Frank Bille <[EMAIL PROTECTED]> wrote:
On 2/12/07, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:
>
> In general, @author tags and attributions are p
does that go toward final releases or betas too?
-igor
On 2/12/07, Upayavira <[EMAIL PROTECTED]> wrote:
Igor Vaynberg wrote:
> we have a user list on sf.net
>
> usually when incubating in apache the user list moves over after
graduation
> from the incubator
Or more likel
we have a user list on sf.net
usually when incubating in apache the user list moves over after graduation
from the incubator
-igor
On 2/12/07, Luca Botti <[EMAIL PROTECTED]> wrote:
And sorry to anyone if it has been discussed before
> On 2/12/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> > before we start doing all this have you guys tried the jboss
serialization
> > thing yet?
>
> Yes, and it didn't even remotely work for the project I'm working on.
> Furthermore, maybe I'm wrong,
before we start doing all this have you guys tried the jboss serialization
thing yet?
the problem, like johan mentioned, is that this wont work across jvms
because he keeps some kind of cache? but then this makes it useless for
clustering. i think whatever solution we come up with needs to work a
i think we should externalize it away from the page. the page doesnt need to
know HOW it is versioned, all it needs to have is a listener for when its
state is changed and we have that through addStateChange
-igor
On 2/12/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
or i can make it so that
its in trunk, who cares how much trivial api you break...if this saves a
creation of a string (charseq->string->charseq) then keep the change
-igor
On 2/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: ehillenius
Date: Sat Feb 10 21:53:52 2007
New Revision: 505851
URL: http://svn.
wrote:
On 2/10/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> also why do we all need to look into it? most of us are not release
people,
> we dont know much about building one or what is correct and incorrect.
You're part of the PPMC. That means that the release is *our*
re
what do you mean flag 1.2.5 as non-ok? as far as i am concerned those
changes can go into 1.2.6, but i thought since you havent uploaded the
release you can rebuild it. but since you have already those changes can
wait until 1.2.6. no biggie. there is no reason why we shouldnt have a
1.2.6especial
at this point lets just rebuild 1.2.5 (since there were problems with it
anyways?) and call it a day. whats done is done.
-igor
On 2/9/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/9/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> Why are there commits on 1.2.x *after* the 1.2.5 relea
[x] no, I rather use this library
http://www.dreamprojections.com/SyntaxHighlighter/
it is what pastebin uses, seems to work very nicely - although rendering
Component.java does take a while :)
-igor
why dont you just tell us what you messed up instead of having a scavanger
hunt? :)
also why do we all need to look into it? most of us are not release people,
we dont know much about building one or what is correct and incorrect.
-igor
On 2/9/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
it doesnt if validation fails...
-igor
On 2/8/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
it should be doesn't it? what is your setup
On 2/8/07, Flavius Burca <[EMAIL PROTECTED]> wrote:
>
>
> When you submit a form via ajax it should automatically update all form
> component's modelso
Rantalaiho <[EMAIL PROTECTED]> wrote:
On Wed, 07 Feb 2007, Igor Vaynberg wrote:
> what you want can easily be accomplished via
>
>
>
> add(new WebMarkupContainer("fragmentid").add(new
> SimpleAttributeModifier("class","error"));
Hmm... Do you
but at
least its a start
-igor
On 2/8/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
Igor Vaynberg wrote:
> On 2/8/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote:
>>
>>
>> >but what is a previous page? you said you only have a single page?
>>
>> Yes,
On 2/8/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote:
>but what is a previous page? you said you only have a single page?
Yes, we have one 'physical' Wicket page. But of course, our application
contains various 'conceptual' pages (physically panels), i.e. components
that make up the body of that
leak what? the vote is on the same mailing list as this :)
-igor
On 2/8/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Igor Vaynberg:
> weve been saving it for your first commit!
Shhh! The vote is not finished, you're not supposed to leak ;-)
--
Jean-Baptiste Qu
weve been saving it for your first commit!
-igor
On 2/8/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Nick Heudecker:
> I'm trying to set a String[] as a value in PageParameters. Here's what
I've
> tried so far:
This is a Wicket bug. See:
Handle String array in PageParameters
htt
On 2/8/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote:
So is it a bad practice to simulate this back-button behaviour in buttons
within the page ?
i think so, wicket handles all this for you by detecting changes to the page
(when page.dirty() is called)
We have a lot of pages where 'exit' or 'c
+1 (binding)
-igor
On 2/8/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Hi all,
Jean-Baptiste Quenot has been very helpful over an extended period by
providing patches, taking part in discussions on the lists and on
##wicket, and he and some of his colleagues are working on the Dojo
integra
yes i use svnkit
i threw the config into C:\Documents and Settings\ivaynberg\Subversion, not
sure how to test if it actually gets picked up
-igor
On 2/7/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Igor Vaynberg:
> we use subclipse, not sure how to hoook that config
we use subclipse, not sure how to hoook that config file into it...
-igor
On 2/7/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Eelco Hillenius:
> I hoped this was automated by now. Hrm. What's the best way to fix
> this and be sure we'll be consistent in the future as well?
To fix i
you are seriously abusing fragment judging by the usecase you provide - just
adding something to the markup tag like an attribute modifier...
what you want can easily be accomplished via
add(new WebMarkupContainer("fragmentid").add(new
SimpleAttributeModifier("class","error"));
fragments are
On 2/7/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Well, it's more indirection and you don't want to have people bitching
about too much indirection on ##wicket do you? ;)
pfft, i vote for IMarkupSaferMaker5000
-igor
On 2/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > The process events step was specifically designed to facilitate a
> > processing model where the event handling and render step were
> > separate, i.e. portlets. Besides, I think it is pretty clean to have
> > that distinction.
>
>
> whil
On 2/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
The process events step was specifically designed to facilitate a
processing model where the event handling and render step were
separate, i.e. portlets. Besides, I think it is pretty clean to have
that distinction.
while it might be clea
one of the shorcomings i would like to address is that there is no way to
introduce try/catch easily around the entire request processing
the other one is the rediculous amount of indirection and also the number of
steps involved
what i would like is something like this (keeping in mind its just
this is where matej's idea of hybrid urls comes in. perhaps he can elaborate
a bit more...
-igor
On 2/6/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
On 2/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> > Problems with Wicket:
> > * the SecondLevelCachePageStore is 'page-oriented': whil
301 - 400 of 799 matches
Mail list logo
