Another baby, congrats!
Eelco
On Fri, Mar 25, 2011 at 10:44 AM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
For the past nine months I have been quietly working on a book about
Wicket. Unlike other books on the market this one does not attempt to
teach you Wicket from the ground up. Instead,
I don't know whether it is used structurally atm, but I have used
Findbugs at least once or twice a few years ago with Wicket.
Eelco
2011/1/24 César Couto cesar...@dcc.ufmg.br:
Dear developers,
I am a PhD student at UFMG, Brazil and as part of my research I am
making a study about the
Doesn't solve anything in particular, right? Personally, I think the
current names are fine.
Eelco
On Mon, Jan 24, 2011 at 1:19 AM, Martin Grigorov mgrigo...@apache.org wrote:
On Tue, Jan 18, 2011 at 3:02 PM, James Carman
ja...@carmanconsulting.comwrote:
ApplicationLifecycleListener?
On
We've always opted for specific, descriptive names, even when grossly
verbose :) I, too, think we should rename it. I like the approach of
moving it to an interface that extends IInitializer, deprecate and remove in
1.6. Although, I feel like a 1.5 name change would be absolutely fine -
As far as I am concerned, that depends on this issue I just found:
https://issues.apache.org/jira/browse/WICKET-3363. If that's just a
problem with the example (probably the case, as the other localization
examples work fine), I am +1 for releasing. If internationalization is
broken, then I am -1.
duh :-)
On Fri, Jan 21, 2011 at 2:58 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
ault is the cut off DefaultMarkupSourcingStrategy
-igor
On Fri, Jan 21, 2011 at 2:52 PM, Eelco Hillenius
eelco.hillen...@gmail.com wrote:
As far as I am concerned, that depends on this issue I just found
We shouldn't just remove things that were part of the public API
without either providing an alternative or at least a good reason why
it should be removed (and have that documented clearly as part of the
migration documentation).
Eelco
On Thu, Jan 6, 2011 at 7:57 AM, Martin Grigorov
Used to be used to determine whether the underlying session should be
updated, which is/ was relevant for session replication.
Eelco
On Wed, Dec 29, 2010 at 2:03 AM, Juergen Donnerstag
juergen.donners...@gmail.com wrote:
In 1.5 trunk WebSession has a transient variable dirty which is set to
. or,
override
onconfigure() and set visibility there in a more
deterministic
fashion.
-igor
On Mon, Nov 29, 2010 at 10:21 AM, Eelco Hillenius
eelco.hillen...@gmail.com wrote:
To expand, unless I'm missing something (new?), things
huh? that doesnt make any sense. the callbacks like onconfigure simply
give you checkpoints for calculating and caching visibility rather
then calculating every time.
I wasn't arguing against onConfigure (which is a fine trade-off) but
saw an example of where relying on just setVisible would
On Tue, Nov 30, 2010 at 12:55 AM, Eelco Hillenius
eelco.hillen...@gmail.com wrote:
On Mon, Nov 29, 2010 at 11:51 PM, Juergen Donnerstag
juergen.donners...@gmail.com wrote:
I'm curious. Which ideas would you steal from SiteBricks and JaxRS?
There are also many interesting ideas in Apache Sling
Niether is evil. It has potential pitfalls, which you should just be
aware of. We use such overrides all over the place and never have
problems with them either. :-) Avoiding it is safer, but also more
verbose (in 1.3.x at least).
Eelco
On Mon, Nov 29, 2010 at 9:49 AM, Igor Vaynberg
with when trying to figure out how it got to be
in that state. So, sorry Igor, but we disagree on this one.
Eelco
On Mon, Nov 29, 2010 at 10:13 AM, Eelco Hillenius
eelco.hillen...@gmail.com wrote:
Niether is evil. It has potential pitfalls, which you should just be
aware of. We use
Well, in the past, the canned answer was override
isEnabled/isVisible. Changing that paradigm and doing a complete 180
is troubling.
I don't think that's the case though. We've had many discussions on
this list (and in private even), and we've always felt uneasy about
supporting two rather
it has nothing to do with requiring a function to be set. the problem
is that the function is free to change its mind at any moment, but we
rely on it returning the same value during some fixed periods of time.
if we truly want to support isvisible() we would need to cache/memoize
the value
On Mon, Nov 29, 2010 at 7:45 PM, richard emberson
richard.ember...@gmail.com wrote:
If wicket was going to be coded over again, would you make
isEnabled and/or isVisible final methods?
If *I* would do it, I'd probably write it for Scala and lean more
heavily on functions rather than mutable
On Thu, Mar 4, 2010 at 1:38 PM, Johan Compagner jcompag...@gmail.com wrote:
no integration needed?
How do you compare (with the repository version or another version, branch)?
how do you check what is all incoming? (synchronize with working sets)
History view: getting a revision, comparing 2
hmm.. no image attached..
You can't send attachments to the mailing list (true for most public
mailing lists); Apache drops 'em.
Eelco
Don't know anything about it.
Anyone else?
Not me. I don't think anyone of the core team was hired for an
optimization job or we'd surely have had a discussion about it.
Eelco
Hey Matt, if you're reading with us, maybe you can explain the
scalability issues you ran into? How many concurrent sessions did you
need to be able to handle? What did you try when optimizing?
Cheers,
Eelco
On Wed, Oct 14, 2009 at 2:26 PM, Eelco Hillenius
eelco.hillen...@gmail.com wrote
Looks like an overall improvement. Definitively reduces the spaghetti
a bit. Not crazy about getCompatibilityScore though. I understand it's
purpose and maybe it's the best solution, but it looks like a crutch.
Eelco
On Tue, Oct 6, 2009 at 8:13 AM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
Why not use toRequestHandler/ toHandler and toUrl in RequestMapper?
Eelco
On Tue, Oct 6, 2009 at 9:53 AM, Eelco Hillenius
eelco.hillen...@gmail.com wrote:
Looks like an overall improvement. Definitively reduces the spaghetti
a bit. Not crazy about getCompatibilityScore though. I understand
I must admit that I don't get the whole detachable stuff in Wicket. I'm used
to think in horizontal tiers
where one tier does all the caching automagically (e.g. 2nd level cache in
JPA/Hibernate) and the
other tiers don't know about that fact.
What models in Wicket can achieve is that data
On Mon, Oct 5, 2009 at 12:14 AM, Eelco Hillenius
eelco.hillen...@gmail.com wrote:
I never liked the code format we're using (curly braces on the
next line), but heck even though Wicket is the only project I've ever
worked on (as far as I can remember) where I used that
It's in the Topicus
And good, consistent naming of classes and
other identifiers is a non-trivial aspect of good design and coding,
especially in publicly used parts of frameworks
True, but imho that has more to do with choosing names that
communicate what things do well, not so much whether there are certain
-1
Breaks compatibility for nothing other than a superficial
'improvement'. Also, I do see the I used in other projects, and
actually like the convention (a whole lot better than using
AbstractFoo and Fooimpl fwiw).
Eelco
On Fri, Oct 2, 2009 at 3:28 PM, Igor Vaynberg igor.vaynb...@gmail.com
You'd have to rewrite the guts of SerializableChecker a bit, e.g. to
send a message to observers rather than just throwing a
WicketNotSerializableException. A default observer can throw that for
instance, but you could couple other observers, for instance one that
calls addError. One problem I
+1
Eelco
If someone would pick up the initiative, it might be an option to move
to google code or some other hosting party.
Eelco
On Thu, Sep 18, 2008 at 2:28 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
I did it here:
its *not* my opinion - I just read the article and thought you might want to
know about it. I mean, beside that, it seems as wicket is very secure in
comparision to the other frameworks mentioned there - Honestly, I dont know
why this harsh reactions (other mails) came.
Thanks for sharing. I
Yeah, that's a quite annoying way from them to sell their product.
More than half of it isn't even really related to web frameworks, but
to how people use them. Injection flaws for instance... duh.
Eelco
On Wed, Jul 30, 2008 at 2:53 PM, Matej Knopp [EMAIL PROTECTED] wrote:
That article is
On Wed, Jul 30, 2008 at 3:48 PM, Eelco Hillenius
[EMAIL PROTECTED] wrote:
Yeah, that's a quite annoying way from them to sell their product.
More than half of it isn't even really related to web frameworks, but
to how people use them. Injection flaws for instance... duh.
I actually think
On Wed, Jul 9, 2008 at 7:13 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
i dont see a reason for this to go into wicket. it is a terracotta
specific optimization and there is already a terracotta-wicket module
right?
And that would be easier for users too I would think: one less
dependency to
One extra note, I had to manually instrument
org.apache.wicket.protocol.http.pagestore.AbstractPageStore
Why do page stores need to be serializable though?
And did you attach your code to a JIRA issue (and which)?
Eelco
On Thu, Jul 3, 2008 at 11:37 AM, Ari Zilka [EMAIL PROTECTED] wrote:
This is the agreed upon approach mimicking the DiskPageStore. No?
Well, the DiskPageStore takes care of storing pages, but by itself
would never be transferred across a cluster. So making it IClusterable
wouldn't make sense.
TC because you can then share more than just Wicket state. You can do
Hibernate 2nd level cache, EHCache, and your own POJOs, all in the same
impl.
That is definitively a big pro for me. A one stop shop solution for
your clustering needs :-). And it comes with tools, source and
professional
[ x ] release wicket 1.3.4
[ ] don't release wicket 1.3.4, because...
Eelco
On Tue, Jun 17, 2008 at 6:01 PM, Bruno Borges [EMAIL PROTECTED] wrote:
Isn't a good idea to just remove Component.getModelObject() and others
HelpfulMethodsSarcasm ?
Wouldn't this reduce this generic problem thing?
Well, we'd have to have something to replace it, particularly for
detaching
Beyond that, ask your local freelancer you trust.
LOL, your local freelancer. I'm gonna remember that line!
Eelco
If you don't mind my asking - where are you from? And btw, you should have
just come straight to the South Island of NZ, that's much nicer than Ozi ;)
I'm Dutch, but live in the US (Seattle) now. My Australian adventures
where a life time ago :-) And NZ is definitively high on my list,
though
Hey guys,
I noticed that we still have a bunch of deprecations lying around.
When do you think we should remove those?
Eelco
Looks good to me. Maybe create a JIRA issue as well?
Eelco
On Wed, May 21, 2008 at 6:22 AM, Gwyn Evans [EMAIL PROTECTED] wrote:
Commit or not?
Index: src/main/java/org/apache/wicket/Page.java
===
---
[ x ] yes, accept kitten-captcha into Wicket
[ ] no, insert objection
Eelco
Basically, it depends on what Eelco was thinking when he originally wrote
this.
I have no idea, it's quite a while ago :-) Oh, and are you sure I
wrote it to start with? There are plenty of files with my author tag
that weren't written by me (or only the initial versions)...
Eelco
thats back from the day when eelco used to go around and claim all
files that did not have @author for himself so he could impress girls.
Yeah. Too bad it didn't work. I found out that switching deodorants
worked better.
Eelco
On Wed, May 14, 2008 at 12:01 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
no, igor doesnt want to do the rest. igor has enough going on at the
moment to keep him busy for several lifetimes.
LOL
[ x ] extensions
if it doesn't have any external dependencies and Jonathan plans to
maintain the project.
[ x ] separate project next to wicket-extensions/spring/ioc/velocity/etc
if it does have external dependencies and Jonathan plans to maintain
the project.
[ x ] wicket stuff project
i will not promise to maintain this.
Ok. So unless someone else of the committers wants to take
responsibility for at least the first few months, I think it should
start as a wicket-stuff project. And if it turns out it is relatively
bug (and feature request) free, we can consider to migrate
On Tue, May 13, 2008 at 1:10 PM, Eelco Hillenius
[EMAIL PROTECTED] wrote:
i will not promise to maintain this.
Ok. So unless someone else of the committers wants to take
responsibility for at least the first few months, I think it should
start as a wicket-stuff project. And if it turns
On Thu, May 8, 2008 at 3:48 AM, Maurice Marrink [EMAIL PROTECTED] wrote:
You could send a mail to the user list or contact the developers for
wicketstuff-lightbox directly, if you can find there email somewhere
:)
Or give us your sourceforge name so that we can add you and you can
apply
While sorting is most often done by the database, I don't think Wicket's
design should assume this is where sorting will be done. Wicket should leave
that up to the application developers.
Sure, we don't assume that. However, we do assume that you're not
using models for massive sorting
On Thu, May 8, 2008 at 3:46 PM, Miguel Munoz
[EMAIL PROTECTED] wrote:
I'm not using PropertyResolver. I said so in a previous post. My point was
that you shouldn't assume I don't know what I'm doing. Contrary to your
previous post, there are valid reasons for sorting the data after retrieving
Again, this would be an optional module of course.
Anything optional is fine, especially if it can be developed
independently (say as a wicket-stuff project).
And, adding
AspectJ to the build process in maven is simple. It's just another
build plugin.
Yeah, but we would also need to
Yes, I hoped I was making it clear that this wasn't a real-world test, it was
a stress test to exaggerate the inefficiencies. This makes them easier to
measure. Stress tests have their place.
Yeah, I got that idea :-) However,
While my code clearly wouldn't ever
see a case like this, we
It's very easy to say this, but the way Wicket is designed, we use property
names all over the place, so this forces us to use reflection when we sort.
There's nothing in Wicket's design that points to using property
models though. (Compound)PropertyModels are very convenient to use,
and
On Fri, May 2, 2008 at 8:45 AM, James Carman [EMAIL PROTECTED] wrote:
When I was reading the discussion about session.dirty
(http://www.nabble.com/What-is-session.dirty%28%29-for--td17021032.html#a17021032)
on the users list, I came up with an idea. Perhaps we could come up
with a set of
On Sat, May 3, 2008 at 7:59 AM, Jon Steelman [EMAIL PROTECTED] wrote:
You core commiter guys use TeamCity but I had the impression you guy use
Eclipse and not IDEA?
We don't have a policy of any kind for what IDE to use :-) We have
(had) at least two team members who use IDEA and quite a
The dataset I was sorting on was generated specifically to test the speed of
different comparators, and had a dataset of 100,000 elements, and I was
sorting using the standard sort method from the collections package,
accessed from Arrays.sort(). However, I now have data that times
[ ] servletapi 2.5 ftw!
[ x ] servletapi 2.4 ftw!
[ ] servletapi 2.3 ftw!
Eelco
[ x ] Release Apache Wicket 1.3.3
Eelco
In case you didn't get it: april fools'! :-)
On Tue, Apr 1, 2008 at 11:15 AM, Eelco Hillenius
[EMAIL PROTECTED] wrote:
Hi,
Now that half of the team is getting ready to work on Wicket 1.4,
which is all about supporting the Java 5 features, I think it is time
for the other half of the team
I thought the move to Scala was a pretty intriguing idea. It
was the logic in markup and the integration with Swing that
had me worried.
Yeah, I like Scala, or at least parts of it. And the joke had to be
somewhat believable :-)
Eelco
Yeah, thanks Nino,
Eelco
On Mon, Mar 31, 2008 at 11:04 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Guy's I've taken the liberty to use the wicket logo at the linkedin
group is it okay?
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
[ ] do it for 1.3
[ x ] do it for 1.4
Otherwise before you know we'll get on that slippery slope again of
what is important enough to warrant a break on a current release and
what is not.
Eelco
Did anyone try to contact the blogger directly?
Eelco
On Mon, Mar 17, 2008 at 6:43 AM, Toomas Römer [EMAIL PROTECTED] wrote:
Hello
ZeroTurnaround team has stumbled upon a blog post
http://d.hatena.ne.jp/mdgw/20080314/1205513596 with a title
Wicket+Spring+JavaRebel. The translated version
[ x ] +1, Wicket 1.4 is 1.3 + generics, drop support for 1.3
[ ] -1, I need a supported version running on Java 1.4
Eelco
true. otoh, a newbie may not know that. giving them a couple cancel button
subclasses would be very obvious.
The problem with providing easy components like this is not only that
it expands Wicket's surface area, but also that it doesn't encourage
people to think about extending components
+1
Eelco
On Wed, Mar 12, 2008 at 12:19 AM, Frank Bille [EMAIL PROTECTED] wrote:
Any other votes? I do have 3 binding +1 if I count myself, but sure would
like some more :-) I'l end this vote tonight at some point
Frank
On Sun, Mar 9, 2008 at 9:22 PM, Frank Bille [EMAIL PROTECTED]
I didn't notice any problems. You get the exact same posts multiple
times? Do other people experience this as well?
Eelco
On Mon, Mar 10, 2008 at 3:01 AM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
All,
I'm getting tired of the double/triple posts coming in from nabble. I
have contacted
As i wasnt on it for a longer time I wanted to ask first if its ok to
submit this to CVS; Eelco, youre in code as mainperson listed - is it ok?
Oh yeah, definitively. Thanks a lot! I'm not really active on that
project, nor am I using it, so it is great that others (you) use and
maintain it.
.
This model uses the type inference of generics together with a proxy
generator to bind to statically types property expressions.
I think this is awesome: we don't have to wait for Java 7 for this.
Martijn
On 2/6/08, Eelco Hillenius (JIRA) [EMAIL PROTECTED] wrote:
[
https
What is the meaning of setRequired(true) on a Checkbox? Some interpret
it as requiring that the Checkbox be checked. Some interpret that it
requires that the Checkbox have a value (which is always the case). See
http://www.nabble.com/%22required%22-for-Checkbox-ts14662131.html#a14680214
and
Yeah! Thanks for sharing Mark,
Eelco
On Jan 29, 2008 11:37 AM, Mark Derricutt [EMAIL PROTECTED] wrote:
Nice:
http://www.jroller.com/ferg/entry/wicket_with_resin_webbeans
Not sure if Scott's ResinApplicationFactory also handles the
ComponentInjector side of the IoC as well but I thought
Hi,
Had a little discussion here:
http://www.artima.com/forums/flat.jsp?forum=276thread=223133
James mentions that he found the fact that the examples' pages extend
base classes confusing. And I can actually imagine that.
WDYT, should we change part of our examples, or give more explanation
Another problem (I think) with sourceforge is that space is limited.
Wicket-stuff is registered as one project, but there are quite a few
projects under there.
Eelco
On Jan 18, 2008 11:47 AM, David Bernard [EMAIL PROTECTED] wrote:
The one on apache is not accessible/updatable by wicketstuff
On Jan 17, 2008 2:36 PM, saki [EMAIL PROTECTED] wrote:
In that case it is sakiss (login name).
Petr
You're in. Have fun!
Eelco
Hello Eelco,
thank you for your response. I've checked the FormComponentPanel, but if I
want to use it in forms I would have to reimplement all the functionality of
such components (eg. Button, CheckBox, TextField, ...), which would be
definitely reinventing the wheel. I'm looking for how to
On Jan 15, 2008 1:26 PM, Igor Vaynberg [EMAIL PROTECTED] wrote:
dont think so, you just check your stuff into svn. there is a
wiki/jira on wicketstuff.org. so set it up in the wiki, if you need a
jira project setup register for jira and let us know your username -
and we will create a jira
Yep, though scanning classpath seems to be the rage currently.
Yes, it seems to be:
http://bill.burkecentral.com/2008/01/14/scanning-java-annotations-at-runtime/
Thanks for the tip; looks like a good starting point.
Eelco
Hello,
would it be possible to make some little changes in component markup lookup,
which would allow to control if the markup is inherited or is in the html
file ? Currently if I want to specify for formComponent own lookup, I have
to extend Panel, which is little bit painful. I've created
On Jan 11, 2008 1:02 AM, Maeder Thomas [EMAIL PROTECTED] wrote:
I'd like to chime in on the conservative side here. I believe you should
only introduce a completely new way of doing things if there is a CLEAR
benefit to be had.
Exactly. See
On Jan 11, 2008 1:25 PM, Martijn Dashorst [EMAIL PROTECTED] wrote:
I think I have shared my part in writing about the pro's and con's I
see for the @Mount annotation, and all I got in return was I don't
like annotations.
Why does it have to be a HUGE improvement? Annotations *ARE* Java! Not
On Jan 11, 2008 11:53 AM, Martijn Dashorst [EMAIL PROTECTED] wrote:
I *still* haven't heard one single technical argument against using
annotations apart from Igor's concern that we would need to scan the
classpath.
You could turn that around just the same. I haven't heard a good
technical
Pro's:
- a long list of mounts becomes unmanagable
- easy to add a mount: work on a page, slap on the annotation and you
have your mount done
- locality of the configuration
Con's
- distributed configuration, so hard to see the 'big picture' (though
a mounts page listing all mounts
One comment I have about classpath scanning is that *if* it turns out
to be a nightmare, you could go the route of Hibernate where you have
to register what annotated pages you want to support. ex:
public class MyWebApplication extends Application {
public void init() {
Wicket currently provides RequestCycle#onRuntimeException with the
full exceptions, including the Wicket wrapped exceptions. Is this
something we should/could improve on?
For instance the thrown exception in this onclick handler:
add(new Link(foo) {
public void onClick() {
I suggest we take a look at annotations for:
* the mount with a page
A disadvantage to doing that imho is that you'll have those
definitions scattered throughout. Right now we steer people to do it
in one place.
Eelco
On Jan 6, 2008 12:15 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
we shold have a checkbox that sets a go-directly-to-old-website
cookie. no way i want to see this twice. also when the animation plays
there is no vertical scrollbar in the browser window, but when all the
text shows up there is
+1
Eelco
On Jan 1, 2008 7:06 PM, Martijn Dashorst [EMAIL PROTECTED] wrote:
Can we get some more votes please? This is a rather important release: it
will be plastered around the internets.
Martijn
On Dec 31, 2007 10:58 AM, Frank Bille [EMAIL PROTECTED] wrote:
I have now rebuild and
On Dec 16, 2007 10:27 PM, Igor Vaynberg [EMAIL PROTECTED] wrote:
hm, looks like you removed them in rev 3383
Duh! Back again now.
Eelco
On Dec 15, 2007 1:42 AM, Matej Knopp [EMAIL PROTECTED] wrote:
Err, I haven't went through the whole thread, but I don't think the
wicket-jetty-cluster is a right thing to put in core.
The pagestore can/will be clustered without any dependencies on
servlet container. And the
Add Rapid Prototyping Forms
The Idea of Alistair Maw and Jonathan Locke (ROR? No. Wicket on Wheels.)
should be included in next Wicket. A set of nice looking
Defaultformcomponents and a Beanresolver to automatically let create
forms from just the plain bean but still allow to customize it
i am fine with 1.4 being _just_ generics if after 1.4 comes out we
drop support for 1.3. otherwise it will be like what johan says:
most bugs will affect 1.3 and 1.4 since they are the same code base
sans generics. after 1.4 comes out we have to start 1.5 immediately
because 1.4 will be a
Hi,
We should also do a deprecation release. We could make our first
'final' release this (1.3.0), and remove all the finals and
deprecations etc with 1.3.1. Or would you prefer something else?
Eelco
On Dec 15, 2007 9:25 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
looks pretty cool. what is the scope of this meant to be? should it be
just an entry point into the main site or should it really have all
those tabs - kinda replacing some of the functionaliy of the main
site?
I guess if those
Hi,
Matej developed some cluster code that is optimized for Wicket (it has
for instance a clustered page store) + Jetty and that uses Tomcat
tribes for cluster communication. I've tweaked (mainly separated it in
3 projects to make the dependencies work) and tested it with
Teachscape. It looks
Does anyone disagree with this
https://issues.apache.org/jira/browse/WICKET-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel?
Eelco
I have been working on creating the AjaxCounter screencast and for the most
part I'm doing pretty well. I'm using wicket-1.3.0-rc1 trying to follow the
AjaxCounter example [0].
What is [0]?
When I attempt to write the Index.java file I get
hit with an error from this part of the code:
I'm starting the wicket contrib Active Widget project.
http://www.activewidgets.com.
It is not open source project, but full functional trial version is
asseccble for testing and evaluate purposes.
I've asked the author and he is not against if my project will be under
Apache license.
At
I guess I missed that item in the assignment list. I actually think
the logo that we have now (http://wicket.apache.org/) is quite ok. I
would suggest that we look for a revamp of the logo (little tweaks to
make it look better) rather than a full re-design.
Eelco
On Nov 28, 2007 9:05 PM, Jack
1 - 100 of 172 matches
Mail list logo
