c) as well, except I don't think it's that good idea to release a beta
before that. It certainly ain't beta if we expect the code to change
that significantly. So imho either call it alpha or release it
afterwards we commit the changes.
-Matej
Eelco Hillenius wrote:
Hi,
It looks like the
I didn't have much time in the recent to actually work on apps based
on Wicket, neither 1.x not 2.x. Thus I have no experience wih either
and no preference regarding the constructor change. I go with what the
experts decide.
In 2.x there two more changes which have not yet been backported into
Hi
I am not a committer so I can't really estimate the feasibility of the
various scenarios, but I'd prefer C as it sounds like the fastest road to a
stable release including generics.
Cheers,
Wilko
Eelco Hillenius wrote:
Hi,
It looks like the discussion around reverting the
Hello,
as a purse user of Wicket 1.2, I would like to see option c) happen. I'm
really looking forward on upgrading my current app to use some of the
new features, and to do things more elegantly.
Also, I'd like to see Generics support as soon as possible; IModel makes
so much more sense with
Hi,
- OK, I will red it clearly
*[Wicket-user] Design questions: Use of controllers
and wicket models
*
*
*- there should be a method on Item like getIndex()
ICellPopulator#populateItem(Item cellItem, String
componentId, IModel
rowModel)
but it is cellItem it return index of column, not
index
Jean-Baptiste Quenot schreef:
* Arnout Engelen:
So far it seems either Apache2, mod_caucho or Resin (2.1.16) is eating
the POST body parameters. Has anyone ever seen something like this? Any
idea where to look?
Is POST followed by a redirect?
Yes, the response to the POST is a
Currently my development environment is downright ugly when it comes the
edit - test changes cycle. I'm using:
Maven
Jetty plugin
Intellij Idea
As it currently stands, here's my cycle:
1. Make a change (doesn't matter if it's to a template or page class)
2. Wait for the entire application
Not using IDEA I can only comment on the Java stuff.
Wicket doesn't impose any special thing on the server and runtime
environment. Therefore hotswap should be functioning. My experience
with Eclipse is that running the application in debug mode allows
hotswap to occur, and typically doesn't
Second, I ran across the JIRA issue, WICKET-126:
https://issues.apache.org/jira/browse/WICKET-126
This seems to describe some changes in the 1.3 base that would enable much
easier hot-redeployment of classes. The discussion in the issue went back
and forth, but it's a little hard to tell
this bug has been fixed in 1.2.5. what problems did you have in 1.2.5? most
of them have been fixed and you can build the branch yourself until we
release 1.2.6
-igor
On 3/10/07, Arnout Engelen [EMAIL PROTECTED] wrote:
Jean-Baptiste Quenot schreef:
* Arnout Engelen:
So far it seems either
The nice part about wicket is that it does not limit your presentation
skills. Regarding menu, the best menu for me by now is a jQuery plugin wrote
by Jonathan Sharp: http://jdsharp.us/code/jQuery/plugins/jdMenu .
It uses a simple ul-li markup, supports unlimited levels and is completely
* Matt Welch:
Hello Matt,
Second, I ran across the JIRA issue, WICKET-126:
This seems to describe some changes in the 1.3 base that would
enable much easier hot-redeployment of classes.
That's right, with this new feature you don't need to restart your
webapp in most cases.
The
Is it possible to substitute properties into other properties? I tried the
Ant-like syntax:
Page1.properties:
my.label=My homepage
my.other.label=${my.label} is neat.
Is there a syntax which would render my.other.label as 'My homepage is
neat.'?
--
View this message in context:
Thanks for all of the information and links. I'll be diving into this on
Monday and I'll reply here with my results.
On 3/10/07, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote:
* Matt Welch:
Hello Matt,
Second, I ran across the JIRA issue, WICKET-126:
This seems to describe some changes in
On 10/03/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
a) focus on stabilizing 1.3 first, meanwhile keep supporting 2.0
(though only for bugfixes). 1.4 will be the release with backports of
the currently missing 2.0 features, and 1.5 will be 1.4 + the Java 5
features (including generics).
b)
Take a look at StringResourceModel. It should do what you want.
On 3/10/07, Jonathan Cone [EMAIL PROTECTED] wrote:
Is it possible to substitute properties into other properties? I tried the
Ant-like syntax:
Page1.properties:
my.label=My homepage
my.other.label=${my.label} is neat.
Is
I don't think we support that. Feel free to open a feature request,
though personally, while I see the fun factor, I don't think it is
something we can't live about. So, please provide a patch if you care
about such a feature :)
Eelco
On 3/10/07, Jonathan Cone [EMAIL PROTECTED] wrote:
Is it
Oops. I didn't read his email very closely.
On 3/11/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
I don't think we support that. Feel free to open a feature request,
though personally, while I see the fun factor, I don't think it is
something we can't live about. So, please provide a patch if
18 matches
Mail list logo
