am using
wicket-1.3.5.
+Leena
skatz wrote:
I have the same problem using 1.3.5, but not when using 1.3.3. I spent
some time tracing the source code and it seems related to the addition of
this line:
getTreeState().selectNode((TreeNode)item.getModelObject(), false);
at the very
I have the same problem using 1.3.5, but not when using 1.3.3. I spent some
time tracing the source code and it seems related to the addition of this
line:
getTreeState().selectNode((TreeNode)item.getModelObject(), false);
at the very end of the function (line 835):
() as a test and the Ajax Console still
disappeared.
Timo Rantalaiho wrote:
On Wed, 07 Nov 2007, skatz wrote:
The Ajax debug console disappears before I can read what it is saying,
and
Hmm, I think that normally the ajax debug console should
stay there for javascript executions and ajax
I have created an anonymous innner class of AjaxFallbackLink this overrides
onClick and getAjaxCallDecorator as such:
...
@Override
protected IAjaxCallDecorator getAjaxCallDecorator() {
return new AjaxCallDecorator() {
Is there a way to get an enclosure to work with a repeater. Perhaps I am
missing something, but I can't get:
...
ul class=someclass
wicket:enclosure child=item
li wicket:id=repeater /li
/wicket:enclosure
/ul
to work. What I get is an exception telling me there is no component
matching
Thats odd, when I posted, the anchor tag inside the list item tag does not
show up.
li wicket:id=repeatersomething wicket:id=item/something/li
skatz wrote:
Is there a way to get an enclosure to work with a repeater. Perhaps I am
missing something, but I can't get:
...
ul class
Hi,
Could someone give me some insight into the use of WebMarkupContainers with
repeaters. In particular, I was wondering how come there does not need to
be markup that has the id of the interposed WebMarkupContainer? (Also, a
pointer to the code, if it exists, where repeaters do special
Hi,
The examples seem to use the deprecated constructor for Fragment. Is there
an example/explanation of the non-deprecated ones?
--
View this message in context:
http://www.nabble.com/Pointer-to-example-use-of-non-deprecated--Fragment-contructor-tf4704754.html#a13448026
Sent from the Wicket
Can anyone give me some pointers on debugging a problem with the JavaScript
that gets appended and sent to the browser when you call ModalDialog#close?
I'm getting TypeError exceptions.
--
View this message in context:
More information. It works as expected in IE7. The problem occurs with
Firefox 2.0.0.7
skatz wrote:
I am trying to use the ModalWindow as a confirmation dialog and it works
fine on one page but the same code on a different page produces the above
error.
Closing the ModalWindow
I am trying to use the ModalWindow as a confirmation dialog and it works fine
on one page but the same code on a different page produces the above error.
Closing the ModalWindow with the X in the corner work fine. The error
occurs when the AjaxCallbackLink onClick handler calls
Boston, MA
Dan Syrstad-2 wrote:
In what area of the world and what are you looking to do?
-Dan
On 9/18/07, skatz [EMAIL PROTECTED] wrote:
Hi,
Can anyone provide me with pointers to individuals or companies providing
Wicket consulting/contracting or outsourced personnel?
TIA
Hi,
Can anyone provide me with pointers to individuals or companies providing
Wicket consulting/contracting or outsourced personnel?
TIA,
skatz
--
View this message in context:
http://www.nabble.com/Wicket-consulting-contracting-outsourcing-tf4476525.html#a12764265
Sent from the Wicket
13 matches
Mail list logo
