Re: svn commit: r531285 - /incubator/wicket/releases/apache-wicket-1.3.0-incubating-beta1/
On 4/23/07, Eelco Hillenius [EMAIL PROTECTED] wrote: Why didn't you just roll back to the previous revision? Or asked me to do this? I wouldn't have committed if I knew you wanted to create a release for 1.3 this weekend as well. Because I didn't know what the script solved. It was there for a reason and the issue was not resolved. Instead of pushing for a release until 2am I figured sleep was more important. :-) 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://wicketframework.org
Re: svn commit: r531285 - /incubator/wicket/releases/apache-wicket-1.3.0-incubating-beta1/
Why didn't you just roll back to the previous revision? Or asked me to do this? I wouldn't have committed if I knew you wanted to create a release for 1.3 this weekend as well. Because I didn't know what the script solved. It was there for a reason and the issue was not resolved. Instead of pushing for a release until 2am I figured sleep was more important. :-) Very true :) Issue is fixed now. Eelco
Re: Ext js
Guys, have someone played with Ext-js? It appears to be an impressive collection of UI Ajax components. http://extjs.com/deploy/ext/docs/index.html Among the other things controls are skinnable with a theme and you can choose the underling library between Yahoo UI Library or jQuery or Prototype + Scriptacolus. What do you think about it? Could be interesting having a Ext-contrib ?! Looks nice. Might be good for a wicket-stuff project if someone wants to pick it up. It's LGPL licenced though, so we can't use it in the core projects. Eelco
Re: bug?
Could you please open up a JIRA issue to avoid that this gets lost in the archives (and let's hope it doesn't get lost in JIRA either, looking at our current back log). Even if it turns out to be not a bug, we can use JIRA as our TODO list. Eelco On 4/20/07, fattymelt [EMAIL PROTECTED] wrote: sorry, but this seems strange enough that it may be a bug... http://www.nabble.com/Strange-Popup-Behavior-After-Logout-Session.invalidate%28%29-tf3620694.html If not, I apologize for the cross-post. -- View this message in context: http://www.nabble.com/bug--tf3621746.html#a10113675 Sent from the Wicket - Dev mailing list archive at Nabble.com.
Typo on home page regarding 1.2.6
FYI - The last bullet from the first list on the Welcome section on the home page says Download Wicket 1.2.5 when it should say 1.2.6. Jon
Re: Typo on home page regarding 1.2.6
Thx, should be fixed now. Martijn On 4/23/07, Jon Steelman [EMAIL PROTECTED] wrote: FYI - The last bullet from the first list on the Welcome section on the home page says Download Wicket 1.2.5 when it should say 1.2.6. Jon -- 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://wicketframework.org
[vote] Release Apache Wicket 1.3.0-incubating-beta1
This is a vote to release our first official incubator release into the wild. The intent is to release Apache Wicket 1.3.0 beta1 to the general Wicket community. Most API breaks are in, and we expect no major changes in the final stages of this release. With any release done inside the Apache Foundation, we should be very diligent and ensure the release is 'up to standards'. However, since this release is done under the umbrella of the Incubator and thrown out into the wild, it will be under considerable scrutiny. I therefore kindly request that you take extra time and check this release for any unresolved legal issues, quality and/or documentation issues. See [1] for the checklist as the Incubator PMC expects. I know this is not a space shuttle launch, but we will be investigated vigorously. A positive vote from the IPMC will bring us so much closer to graduation! Also, please check with the comments on our first release attempt to see if anything is missing. The goodies: The distribution: http://people.apache.org/~dashorst/releases/apache-wicket-1.3.0-incubating-beta1/dist The maven 2 repository: http://people.apache.org/~dashorst/releases/apache-wicket-1.3.0-incubating-beta1/m2-repo/ The subversion tag: https://svn.apache.org/repos/asf/incubator/wicket/releases/wicket-1.3.0-incubating-beta1/ The key used to sign this release: https://svn.apache.org/repos/asf/incubator/wicket/common/KEYS The vote: [ ] Yes, ask the IPMC to ratify the 1.3.0-incubating-beta1 release [ ] No, don't ask the IPMC This vote will run for 72 hours and is by majority (PPMC members have binding votes, everybody is free to vote). It requires at least three binding +1 votes to pass. [2] Martijn [1] http://incubator.apache.org/guides/releasemanagement.html [2] http://www.apache.org/foundation/voting.html -- 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://wicketframework.org
what is the use case for IFormProcessingListener
Hi, I've searched the mailing list for this, and looked at implementing classes etc, but I fail to see the use case for IFormProcessingListener. Can anyone enlighten me and give me a concrete example of where this is useful AND needed (meaning that it is utterly impossible to implement it without the interface)? Eelco
Style id instead wicket:id ?
I couldn't find any thread related to this in the archives, probably because the terms id, style and wicket:id :) But, did anyone ever asked to Wicket just use the style id instead wicket:id to bind components? If yes, where is the thread? If not, ... why not allow this? :D Cheers! PS: I posted an article in my blog about Wicket (in portuguese) at blog.brunoborges.com.br -- Bruno Borges Summa Technologies Inc. www.summa-tech.com (48) 8404-1300 (11) 3055-2060
Re: Style id instead wicket:id ?
there are a lot of reasons for this. the few that come to mind are: designers want control over the id attribute for css styling wicket:id allows duplicates in markup while id doesnt, so validation would fail. link wicket:id=aspan wicket:id=a/span/a is allowed. it is cleaner to use our own namespaced attribute to avoid interference. -igor On 4/23/07, Bruno Borges [EMAIL PROTECTED] wrote: I couldn't find any thread related to this in the archives, probably because the terms id, style and wicket:id :) But, did anyone ever asked to Wicket just use the style id instead wicket:id to bind components? If yes, where is the thread? If not, ... why not allow this? :D Cheers! PS: I posted an article in my blog about Wicket (in portuguese) at blog.brunoborges.com.br -- Bruno Borges Summa Technologies Inc. www.summa-tech.com (48) 8404-1300 (11) 3055-2060
