please co these projects from WICKET_1_2 branch:http://svn.sourceforge.net/viewvc/wicket-stuff/branches/WICKET_1_2/wicket-contrib-gmap-examples/
http://svn.sourceforge.net/viewvc/wicket-stuff/branches/WICKET_1_2/wicket-contrib-gmapthe code in trunk is broken, and i have to make it wicket
2.0
Hi Stefan,
wicket is nicely set up as a Maven multi module projekt and the parent
of all modules may be found in wicket-parent.
Build instructions may be found there:
https://svn.sourceforge.net/svnroot/wicket/trunk/wicket-parent/README.TXT
mvn -Pjdk1.4 clean install
should install the Java 1.4
Wicket is in 2.0 a Java 5 project, and the projects haven't yet been
altered to take advantage of maven's multi module support. I think
this will happen somewhere in the beginning of october when I have
finished my current chapter for WIA...
Martijn
On 9/17/06, Martin Funk [EMAIL PROTECTED]
i agree with igor. What does this really gain?How will versioning and then the undo to that version work???johanOn 9/17/06, Erik Brakkee
[EMAIL PROTECTED] wrote:
One of the things I was thinking of is actually sharing the same
CompoundPropertyModel but then requesting a child model of the
This is really weird. Can you please either check if current svn version
helps the problem or provide a quick start application so that I can
look at that?
From what I can see the response seems to be ok.
-Matej
Allen James wrote:
I've ran into a scenario where I can use the ModalWindow in
On 9/17/06, Johan Compagner [EMAIL PROTECTED] wrote:
i agree with igor. What does this really gain?How will versioning and then the undo to that version work???
Child components will not do versioning. Only the top-level parent will. The child components simply delegate to their parent.
Or is
I just looked a bit at the code for ModelChange.java in wicket 2. I see
the problem now. The CompoundPropertyModel is being cloned so if there
is another model referring to that model, it will always refer to the
wrong version of the model in case an old version of the page is
requested.
A
What is that ModelRegistry thing?Does that return a model? So models are not attached to components?That won't work in clustering or serialization of the http sessions.The only thing i can think of is having a method on an interface (that extends IModel)
that is something like: getChangeState()And
On 9/17/06, Johan Compagner [EMAIL PROTECTED] wrote:
What is that ModelRegistry thing?
That is something which I just thought of. The only thing that would manage is a mapping of model to ids.
Does that return a model? So models are not attached to components?
Models are still attached to
I think the book is a really good introduction to wicket. I actually
like it when the author first presents one way of doing something in a
big code example and then shows how to do this particular example in a
much shorter and cleaner way using another component. I think this is a
really smart
how is a model attached to the component if they have to be looked up from somewhere?Where i that lookup being done? And where is the looked up model comming from?remeber Models can also be used over more then one page.
i am still looking into a third alternative. And that is doing the
I successfully cheched out and built wicket from svn. I use a panel with
a form that contains
- a ListChoice
- a AutoCompleteTextField
Both works well in a normal page. But in a modal window both do not
work:
- the ListChoice is not displayed
- the AutoCompleteTextField triggers no event when a
On 9/17/06, Stefan Lindner [EMAIL PROTECTED] wrote:
- the ListChoice is not displayedselect tag had a problem in Model Dialogs in IE. But it should have been solved by now. Try to do a svn update to get the latest model window code.Frank
On 17/09/06, Erik Brakkee [EMAIL PROTECTED] wrote:
a component reference: Also the wicket site does not contain a full
reference. This is extremely importantant I think because if you want people
to find and use the components then they should be documented. The wicket
site itself is also not
ListChoice should be visible in modal window from current svn.
I can imagine autocomplete not working, perhaps the autocomplete div has
lower z-index. Anyway, if you need autocomplete/datepicker/other
javascript components that have absolute positioning, you may need to
use the modal window in
That doesn't really contain Erik was stating. At least not that I could find. If you look here, http://myfaces.apache.org/tomahawk/index.html and then on the left there is a Components section with information about each component. That's what Wicket needs for both the core and extension
If you look here:
http://www.wicket-library.com/wicket-examples/compref
you can see the components in live action. Perhaps not a complete
list, but certainly something worthwile (better than screenshots imo).
Each component has a short description and you can also look at the
source code using
On 9/17/06, Gregg Bolinger [EMAIL PROTECTED] wrote:
That doesn't really contain Erik was stating. At least not that I could
find. If you look here,
http://myfaces.apache.org/tomahawk/index.html and then on
the left there is a Components section with information about each
component. That's
On 9/17/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
At my company I'm trying to convince ourdesigner team to do a new version of the website, but they arereluctant to donate some time.Damn designers. :) Think they own the world and stuff.
Just tell them that if they spend that hour on making a
On 9/17/06, Frank Bille [EMAIL PROTECTED] wrote:
Just tell them that if they spend that hour on making a new design they will
have my eternal gratitude.
Done... :-D
Martijn
--
Download Wicket 1.2.2 now! New Ajax components: Tree, TreeTable and ModalWindow
-- http://wicketframework.org
On 9/17/06, Johan Compagner [EMAIL PROTECTED] wrote:
how is a model attached to the component if they have to be looked up from somewhere?Where i that lookup being done? And where is the looked up model comming from?
The model is attached to a component. It just has a unique id which
must be
On 9/17/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
If you look here:http://www.wicket-library.com/wicket-examples/comprefyou can see the components in live action. Perhaps not a complete
list, but certainly something worthwile (better than screenshots imo).Each component has a short description
On 9/17/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
If you look here:
http://www.wicket-library.com/wicket-examples/compref
you can see the components in live action. Perhaps not a complete
list, but certainly something worthwile (better than screenshots imo).
Each component has a
I'm currently using version 1.2.2. I've tried running against the head
revision of 1.x out of the Subversion repository, but the issue still
remains. One odd thing I noticed, I put the modal window link on my login
page and it will come up there as many times as I click on the link before I
It is working now, but I cannot tell you why. I deleted all my offline
cached content and cookies, and once that was done, everything works as
advertised. Not being too familiar with the javascript used for the modal
window, could there have been some incompatibility between 1.2.1 and 1.2.2
When we get an undo we go use our PropertyResolver to set all the properties back into the current model.
That only works if all manipulation is done through getters and setters. not exactly true. you can read and set fields, even if they are private (depending on the security manager which 99%
On a totally different note, generalizing a bit, what we are trying to
do is to version an object-graph (in-memory). Arent' there any tools
available that already do this? In particular, all we want to do is to
version the page object together with all components, models, and
instance variables it
On Mon, 22 May 2006 11:54:47 +0430, Ayodeji Aladejebi
[EMAIL PROTECTED] wrote:
Well here is the file...give it a try again. they are functional now and
look at the quick start before writing yours
wicket tell can not found package resource [name=.DS_Store ...]
so i delete following line
28 matches
Mail list logo
