Re: [Wicket-user] modal window image resources
NateBot20002 wrote: Can you explain how the image resources in the ModalWindow package work? Here is an answer to this question: http://www.thinksharp.org/?cat=16 http://www.thinksharp.org/?cat=16 NateBot2000 -- View this message in context: http://www.nabble.com/modal-window-image-resources-tf4014448.html#a11770901 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] modal window image resources
There is more of it in the archives, this one might be most relevant http://www.nabble.com/Magic-to-replace-ModalWindow-images-tf3811156.html#a10788038 -Matej On 7/24/07, NateBot2000 [EMAIL PROTECTED] wrote: NateBot20002 wrote: Can you explain how the image resources in the ModalWindow package work? Here is an answer to this question: http://www.thinksharp.org/?cat=16 http://www.thinksharp.org/?cat=16 NateBot2000 -- View this message in context: http://www.nabble.com/modal-window-image-resources-tf4014448.html#a11770901 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window and Page Expired - SOLVED
Ok, my bad...
Cutting out the details, the page that included a ref to the modal window
had a piece of javascript, which generated an IMG tag with a src attribute
starting with a '#' (this is some code ported from a JSF version of the
application). The browser was then trying to fetch the page again looking
for the (inexistent) bookmark, hence the double hit to the page.
Now, I'm wondering if it is normal that the framework evicts the page when
removing one of the 2 versions of that page from the access stack since the
other version is still there and may be referenced again. But I don't know
wicket enough to make a valid statement on this.
Many thanks for the helps here and there though.
Laurent.
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Laurent
Brucher
Sent: vendredi 13 juillet 2007 22:42
To: wicket-user@lists.sourceforge.net
Subject: [Wicket-user] Modal Window and Page Expired.
Hi all,
There was a post last December about the same problem that I'm facing right
now, which is getting a page expired error page after I close a modal
window.
The post was called Firefox and ModalWindow and seemed to talk about the
issue for FF only.
I've encountered the problem first with FF (2.0.0.4). After reading the
post, I tried with IE7 and it worked ok (that was this afternoon).
This evening, neither IE7 or FF work anymore. Darn! Clearing cookies and
stuff don't change a thing.
Oh, and of course, the Ajax ModalWindow example works just fine (my code is
heavily inspired from that example)...
I'm using Wicket 1.2.6, Tomcat 5.5.20, Jdk1.6u2.
Have you guys shed any light on this issue at all?
I've tried to trace the code, but as I'm rather new to Wicket, I couldn't
really figure out what's going on...
Anything I can do to help address this?
Below is the code I use, just in case.
Reagrds,
Laurent.
// Page containing the modal window
public class MainPage extends WebPage {
public MainPage()
{
...
add( new PreferredStationsDialog(prefStationsDialog) );
...
}
}
// The modal window impl.
public class PreferredStationsDialog extends ModalWindow {
public PreferredStationsDialog(String id)
{
super(id);
setTitle(xyz);
setCookieName(prefStationsDialog);
setPageMapName(prefStationsDialogPageMap);
setPageCreator( new ModalWindow.PageCreator() {
@Override
public Page createPage() {
return new
PreferredStationsDialogPage(PreferredStationsDialog.this);
}
});
setCloseButtonCallback(new ModalWindow.CloseButtonCallback() {
public boolean onCloseButtonClicked(AjaxRequestTarget target) {
return true;
}
});
}
}
// The content of the modal window, as a Page
public class PreferredStationsDialogPage extends WebPage
{
public PreferredStationsDialogPage( final PreferredStationsDialog dialog
)
{
super();
add( new AjaxLink(button.save) {
@Override
public void onClick(AjaxRequestTarget target) {
dialog.close(target);
}
}.add( new Label(text, Save)) );
add( new AjaxLink(button.cancel) {
@Override
public void onClick(AjaxRequestTarget target) {
dialog.close(target);
}
}.add( new Label(text, Cancel)) );
}
}
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window and Page Expired - SOLVED
On 7/19/07, Laurent Brucher [EMAIL PROTECTED] wrote:
Ok, my bad...
Cutting out the details, the page that included a ref to the modal window
had a piece of javascript, which generated an IMG tag with a src
attribute
starting with a '#' (this is some code ported from a JSF version of the
application). The browser was then trying to fetch the page again looking
for the (inexistent) bookmark, hence the double hit to the page.
Now, I'm wondering if it is normal that the framework evicts the page when
removing one of the 2 versions of that page from the access stack since
the
other version is still there and may be referenced again. But I don't know
wicket enough to make a valid statement on this.
well, the idea here is that we can evict it because it is no longer
reachable via the browser. for example you go to page A then go to page B,
then click back and go to page C. you can no longer access page B via the
browser, so wicket evicts it from pagemap since at that point its just
wasting space. however when you have the kinds of problems you have it
becomes a pita to figure out whats going on.
-igor
Many thanks for the helps here and there though.
Laurent.
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Laurent
Brucher
Sent: vendredi 13 juillet 2007 22:42
To: wicket-user@lists.sourceforge.net
Subject: [Wicket-user] Modal Window and Page Expired.
Hi all,
There was a post last December about the same problem that I'm facing
right
now, which is getting a page expired error page after I close a modal
window.
The post was called Firefox and ModalWindow and seemed to talk about the
issue for FF only.
I've encountered the problem first with FF (2.0.0.4). After reading the
post, I tried with IE7 and it worked ok (that was this afternoon).
This evening, neither IE7 or FF work anymore. Darn! Clearing cookies and
stuff don't change a thing.
Oh, and of course, the Ajax ModalWindow example works just fine (my code
is
heavily inspired from that example)...
I'm using Wicket 1.2.6, Tomcat 5.5.20, Jdk1.6u2.
Have you guys shed any light on this issue at all?
I've tried to trace the code, but as I'm rather new to Wicket, I couldn't
really figure out what's going on...
Anything I can do to help address this?
Below is the code I use, just in case.
Reagrds,
Laurent.
// Page containing the modal window
public class MainPage extends WebPage {
public MainPage()
{
...
add( new PreferredStationsDialog(prefStationsDialog) );
...
}
}
// The modal window impl.
public class PreferredStationsDialog extends ModalWindow {
public PreferredStationsDialog(String id)
{
super(id);
setTitle(xyz);
setCookieName(prefStationsDialog);
setPageMapName(prefStationsDialogPageMap);
setPageCreator( new ModalWindow.PageCreator() {
@Override
public Page createPage() {
return new
PreferredStationsDialogPage(PreferredStationsDialog.this);
}
});
setCloseButtonCallback(new ModalWindow.CloseButtonCallback() {
public boolean onCloseButtonClicked(AjaxRequestTarget target)
{
return true;
}
});
}
}
// The content of the modal window, as a Page
public class PreferredStationsDialogPage extends WebPage
{
public PreferredStationsDialogPage( final PreferredStationsDialog
dialog
)
{
super();
add( new AjaxLink(button.save) {
@Override
public void onClick(AjaxRequestTarget target) {
dialog.close(target);
}
}.add( new Label(text, Save)) );
add( new AjaxLink(button.cancel) {
@Override
public void onClick(AjaxRequestTarget target) {
dialog.close(target);
}
}.add( new Label(text, Cancel)) );
}
}
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window and Page Expired - SOLVED
Problem is that we evict it also on refresh. But then you still can go
to the page B. Anyway, there are more problems then this with
HttpSessionStore. I think that upgrade to 1.3 is really recommended,
as the default SecondLevelCacheSessionStore doesn't suffer from this
problem any more.
-Matej
On 7/20/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
On 7/19/07, Laurent Brucher [EMAIL PROTECTED] wrote:
Ok, my bad...
Cutting out the details, the page that included a ref to the modal window
had a piece of javascript, which generated an IMG tag with a src
attribute
starting with a '#' (this is some code ported from a JSF version of the
application). The browser was then trying to fetch the page again looking
for the (inexistent) bookmark, hence the double hit to the page.
Now, I'm wondering if it is normal that the framework evicts the page when
removing one of the 2 versions of that page from the access stack since
the
other version is still there and may be referenced again. But I don't know
wicket enough to make a valid statement on this.
well, the idea here is that we can evict it because it is no longer
reachable via the browser. for example you go to page A then go to page B,
then click back and go to page C. you can no longer access page B via the
browser, so wicket evicts it from pagemap since at that point its just
wasting space. however when you have the kinds of problems you have it
becomes a pita to figure out whats going on.
-igor
Many thanks for the helps here and there though.
Laurent.
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Laurent
Brucher
Sent: vendredi 13 juillet 2007 22:42
To: wicket-user@lists.sourceforge.net
Subject: [Wicket-user] Modal Window and Page Expired.
Hi all,
There was a post last December about the same problem that I'm facing
right
now, which is getting a page expired error page after I close a modal
window.
The post was called Firefox and ModalWindow and seemed to talk about the
issue for FF only.
I've encountered the problem first with FF (2.0.0.4). After reading the
post, I tried with IE7 and it worked ok (that was this afternoon).
This evening, neither IE7 or FF work anymore. Darn! Clearing cookies and
stuff don't change a thing.
Oh, and of course, the Ajax ModalWindow example works just fine (my code
is
heavily inspired from that example)...
I'm using Wicket 1.2.6, Tomcat 5.5.20, Jdk1.6u2.
Have you guys shed any light on this issue at all?
I've tried to trace the code, but as I'm rather new to Wicket, I couldn't
really figure out what's going on...
Anything I can do to help address this?
Below is the code I use, just in case.
Reagrds,
Laurent.
// Page containing the modal window
public class MainPage extends WebPage {
public MainPage()
{
...
add( new PreferredStationsDialog(prefStationsDialog) );
...
}
}
// The modal window impl.
public class PreferredStationsDialog extends ModalWindow {
public PreferredStationsDialog(String id)
{
super(id);
setTitle(xyz);
setCookieName(prefStationsDialog);
setPageMapName(prefStationsDialogPageMap);
setPageCreator( new ModalWindow.PageCreator() {
@Override
public Page createPage() {
return new
PreferredStationsDialogPage(PreferredStationsDialog.this);
}
});
setCloseButtonCallback(new ModalWindow.CloseButtonCallback() {
public boolean onCloseButtonClicked(AjaxRequestTarget target)
{
return true;
}
});
}
}
// The content of the modal window, as a Page
public class PreferredStationsDialogPage extends WebPage
{
public PreferredStationsDialogPage( final PreferredStationsDialog
dialog
)
{
super();
add( new AjaxLink(button.save) {
@Override
public void onClick(AjaxRequestTarget target) {
dialog.close(target);
}
}.add( new Label(text, Save)) );
add( new AjaxLink(button.cancel) {
@Override
public void onClick(AjaxRequestTarget target) {
dialog.close(target);
}
}.add( new Label(text, Cancel)) );
}
}
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
This SF.net email is sponsored
Re: [Wicket-user] Modal Window and Page Expired.
Five modal windows? At the same time? It might be that you are running
out of pagemaps.
This is very weird, hovewer, seems to be reproducable. Can you post a
quickstart? Also, could you check if this is working with wicket 1.3?
-Matej
On 7/18/07, Laurent Brucher [EMAIL PROTECTED] wrote:
Cookies have been cleared many times, without any success ;-)
But I found out what is causing (directly or indirectly) the problem:
In the page that includes the ajax button that is used to bring up the modal
window, there is a wicket:head section at the top of the page.
If I remove this wicket:head section, there is no problem with the modal
window anymore.
The page globally looks like:
html
head
...
/head
body
wicket:head.../wicket:head
wicket:extend
/wicket:extend
/body
/html
Somehow, I've noticed that including the wicket:head triggers an
additional HTTP request to the same URL (that is, the URL to display the
above page).
Dunno why this is happening but the end result is that the pagemap then
contains 2 versions for the same page ID.
Then, when I hit the button that brings up the modal window, the framework
is trying to access the above page, version 0. This has the effect of
putting that page's version at the top of the pagemap's access stack
(PageMap.access() method). By doing this, the version 1 of the page is
removed from the access stack, but also the page itself (call to
PageMap.remove(Page)).
Thus, once the modal window gets closed and the original page needs to be
rendered, we get a page expired since it was removed from the cache.
That's as far as I can describe what I've seen understood tracing the
code.
I'm not sure where the problem lies: second request because of the
wicket:head or incorrectly evicting the page.
Maybe there is something funky in my own code but I don't see what. Or maybe
there is an issue here.
Any input would be helpful at this point.
Thanks!
Laurent.
_
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: mercredi 18 juillet 2007 8:50
To: [EMAIL PROTECTED]; wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Modal Window and Page Expired.
On 7/13/07, Laurent Brucher [EMAIL PROTECTED] wrote:
Hi all,
There was a post last December about the same problem that I'm facing right
now, which is getting a page expired error page after I close a modal
window.
The post was called Firefox and ModalWindow and seemed to talk about the
issue for FF only.
I've encountered the problem first with FF (2.0.0.4). After reading the
post, I tried with IE7 and it worked ok (that was this afternoon).
This evening, neither IE7 or FF work anymore. Darn! Clearing cookies and
stuff don't change a thing.
Oh, and of course, the Ajax ModalWindow example works just fine (my code is
heavily inspired from that example)...
I'm using Wicket 1.2.6, Tomcat 5.5.20, Jdk1.6u2.
Have you guys shed any light on this issue at all?
I've tried to trace the code, but as I'm rather new to Wicket, I couldn't
really figure out what's going on...
Anything I can do to help address this?
i wonder, clear cookies in firefox and try again. i know there was a similar
problem if you didnt set the cookie name in the modal window using
setcookiename(), but looks like you did that. still, try clearing the
cookies.
-igor
Below is the code I use, just in case.
Reagrds,
Laurent.
// Page containing the modal window
public class MainPage extends WebPage {
public MainPage()
{
...
add( new PreferredStationsDialog(prefStationsDialog) );
...
}
}
// The modal window impl.
public class PreferredStationsDialog extends ModalWindow {
public PreferredStationsDialog(String id)
{
super(id);
setTitle(xyz);
setCookieName(prefStationsDialog);
setPageMapName(prefStationsDialogPageMap);
setPageCreator( new ModalWindow.PageCreator() {
@Override
public Page createPage() {
return new
PreferredStationsDialogPage(PreferredStationsDialog.this);
}
});
setCloseButtonCallback(new ModalWindow.CloseButtonCallback() {
public boolean onCloseButtonClicked(AjaxRequestTarget target) {
return true;
}
});
}
}
// The content of the modal window, as a Page
public class PreferredStationsDialogPage extends WebPage
{
public PreferredStationsDialogPage( final PreferredStationsDialog dialog
)
{
super();
add( new AjaxLink(button.save) {
@Override
public void onClick(AjaxRequestTarget target) {
dialog.close(target);
}
}.add( new Label(text, Save)) );
add( new AjaxLink(button.cancel ) {
@Override
public void onClick(AjaxRequestTarget target) {
dialog.close(target
Re: [Wicket-user] Modal Window and Page Expired.
I want to descript the context.
Some one write a web application based on wicket.Many pages uses ajax.
I encoutered a strange problem.
After 5 ajax modal windows are poped up.The brower will give me a warming
dialog to tell me that the current browse page will be closed.Then the page is
redirected to a login page.Sure ,this means the session is out.
I tries someway:
1 Clear the IE cookies.
2 Clear the tomcat workdir
3 force the tomcat use url-rewrite mode.
4 close the IE cookies.
Then the application works fine.
Maybe you need close the browse cookie and use tomcat url-rewrite both.
Try it.
- Original Message -
From: Igor Vaynberg [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; wicket-user@lists.sourceforge.net
Sent: Wednesday, July 18, 2007 2:49 PM
Subject: Re: [Wicket-user] Modal Window and Page Expired.
On 7/13/07, Laurent Brucher [EMAIL PROTECTED] wrote:
Hi all,
There was a post last December about the same problem that I'm facing
right now, which is getting a page expired error page after I close a modal
window.
The post was called Firefox and ModalWindow and seemed to talk about the
issue for FF only.
I've encountered the problem first with FF (2.0.0.4). After reading the
post, I tried with IE7 and it worked ok (that was this afternoon).
This evening, neither IE7 or FF work anymore. Darn! Clearing cookies and
stuff don't change a thing.
Oh, and of course, the Ajax ModalWindow example works just fine (my code
is heavily inspired from that example)...
I'm using Wicket 1.2.6, Tomcat 5.5.20, Jdk1.6u2.
Have you guys shed any light on this issue at all?
I've tried to trace the code, but as I'm rather new to Wicket, I couldn't
really figure out what's going on...
Anything I can do to help address this?
i wonder, clear cookies in firefox and try again. i know there was a similar
problem if you didnt set the cookie name in the modal window using
setcookiename(), but looks like you did that. still, try clearing the
cookies.
-igor
Below is the code I use, just in case.
Reagrds,
Laurent.
// Page containing the modal window
public class MainPage extends WebPage {
public MainPage()
{
...
add( *new* PreferredStationsDialog(prefStationsDialog) );
...
}
}
// The modal window impl.
public class PreferredStationsDialog extends ModalWindow {
*public* PreferredStationsDialog(String id)
{
*super*(id);
setTitle(xyz);
setCookieName(prefStationsDialog);
setPageMapName(prefStationsDialogPageMap);
setPageCreator( *new* ModalWindow.PageCreator() {
@Override
*public* Page createPage() {
*return*
*new*PreferredStationsDialogPage(PreferredStationsDialog.
*this*);
}
});
setCloseButtonCallback(*new* ModalWindow.CloseButtonCallback() {
*public* *boolean* onCloseButtonClicked(AjaxRequestTarget
target) {
*return* *true*;
}
});
}
}
// The content of the modal window, as a Page
public class PreferredStationsDialogPage extends WebPage
{
*public* PreferredStationsDialogPage( *final* PreferredStationsDialog
dialog )
{
*super*();
add( *new* AjaxLink(button.save) {
@Override
*public* *void* onClick(AjaxRequestTarget target) {
dialog.*close*(target);
}
}.add( *new* Label(text, Save)) );
add( *new* AjaxLink(button.cancel) {
@Override
*public* *void* onClick(AjaxRequestTarget target) {
dialog.*close*(target);
}
}.add( *new* Label(text, Cancel)) );
}
}
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2
Re: [Wicket-user] Modal Window and Page Expired.
Cookies have been cleared many times, without any success ;-)
But I found out what is causing (directly or indirectly) the problem:
In the page that includes the ajax button that is used to bring up the modal
window, there is a wicket:head section at the top of the page.
If I remove this wicket:head section, there is no problem with the modal
window anymore.
The page globally looks like:
html
head
...
/head
body
wicket:head.../wicket:head
wicket:extend
/wicket:extend
/body
/html
Somehow, I've noticed that including the wicket:head triggers an
additional HTTP request to the same URL (that is, the URL to display the
above page).
Dunno why this is happening but the end result is that the pagemap then
contains 2 versions for the same page ID.
Then, when I hit the button that brings up the modal window, the framework
is trying to access the above page, version 0. This has the effect of
putting that page's version at the top of the pagemap's access stack
(PageMap.access() method). By doing this, the version 1 of the page is
removed from the access stack, but also the page itself (call to
PageMap.remove(Page)).
Thus, once the modal window gets closed and the original page needs to be
rendered, we get a page expired since it was removed from the cache.
That's as far as I can describe what I've seen understood tracing the
code.
I'm not sure where the problem lies: second request because of the
wicket:head or incorrectly evicting the page.
Maybe there is something funky in my own code but I don't see what. Or maybe
there is an issue here.
Any input would be helpful at this point.
Thanks!
Laurent.
_
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: mercredi 18 juillet 2007 8:50
To: [EMAIL PROTECTED]; wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Modal Window and Page Expired.
On 7/13/07, Laurent Brucher [EMAIL PROTECTED] wrote:
Hi all,
There was a post last December about the same problem that I'm facing right
now, which is getting a page expired error page after I close a modal
window.
The post was called Firefox and ModalWindow and seemed to talk about the
issue for FF only.
I've encountered the problem first with FF (2.0.0.4). After reading the
post, I tried with IE7 and it worked ok (that was this afternoon).
This evening, neither IE7 or FF work anymore. Darn! Clearing cookies and
stuff don't change a thing.
Oh, and of course, the Ajax ModalWindow example works just fine (my code is
heavily inspired from that example)...
I'm using Wicket 1.2.6, Tomcat 5.5.20, Jdk1.6u2.
Have you guys shed any light on this issue at all?
I've tried to trace the code, but as I'm rather new to Wicket, I couldn't
really figure out what's going on...
Anything I can do to help address this?
i wonder, clear cookies in firefox and try again. i know there was a similar
problem if you didnt set the cookie name in the modal window using
setcookiename(), but looks like you did that. still, try clearing the
cookies.
-igor
Below is the code I use, just in case.
Reagrds,
Laurent.
// Page containing the modal window
public class MainPage extends WebPage {
public MainPage()
{
...
add( new PreferredStationsDialog(prefStationsDialog) );
...
}
}
// The modal window impl.
public class PreferredStationsDialog extends ModalWindow {
public PreferredStationsDialog(String id)
{
super(id);
setTitle(xyz);
setCookieName(prefStationsDialog);
setPageMapName(prefStationsDialogPageMap);
setPageCreator( new ModalWindow.PageCreator() {
@Override
public Page createPage() {
return new
PreferredStationsDialogPage(PreferredStationsDialog.this);
}
});
setCloseButtonCallback(new ModalWindow.CloseButtonCallback() {
public boolean onCloseButtonClicked(AjaxRequestTarget target) {
return true;
}
});
}
}
// The content of the modal window, as a Page
public class PreferredStationsDialogPage extends WebPage
{
public PreferredStationsDialogPage( final PreferredStationsDialog dialog
)
{
super();
add( new AjaxLink(button.save) {
@Override
public void onClick(AjaxRequestTarget target) {
dialog.close(target);
}
}.add( new Label(text, Save)) );
add( new AjaxLink(button.cancel ) {
@Override
public void onClick(AjaxRequestTarget target) {
dialog.close(target);
}
}.add( new Label(text, Cancel)) );
}
}
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2
Re: [Wicket-user] modal window image resources
Use the search! http://www.nabble.com/forum/Search.jtp?query=how+to+customize+modalwindow+images+csslocal=yforum=13974 Martijn -- Wicket joins the Apache Software Foundation as Apache Wicket Apache Wicket 1.3.0-beta2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal window warning message
You should use AjaxSubmitButton and submit the form using Ajax. -Matej On 5/17/07, Nikhil Gahlot [EMAIL PROTECTED] wrote: Hi, I am using Modal Window with a form. But whenever I click Submit button on this window to submit a form I am getting an alert message Are you sure you want to navigate away from this page? Reloading this page will cause the modal window disappear. Press OK to continue, or Cancel to stay on the current page. Now I want to prevent this alert message from getting displayed. Is there any way to do that? Thanks Nikhil -- View this message in context: http://www.nabble.com/Modal-window-warning-message-tf3770780.html#a10661044 Sent from the Wicket - User mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window Bug (important)
You don't need to remove the line. The bug is very difficult to reproduce, I can't even describe how to trigger it. The default behavior in newer version will be setCookieName(null), so the window position will not be persisted. Unless you manually call setCookieName(someCookieName); -Matej Carfield Yim wrote: Where can I get more information about this bug? I use ModalWindow for a few place and this look fine to me, how can I trigger this bug? By the way, should I remove this line once I update wicket library? On 1/30/07, Matej Knopp [EMAIL PROTECTED] wrote: Hi, It seems that quite a lot of people are using ModalWindow lately. I just want to inform you that there is a bug in modal window that can cause it to eat all your browser's cookies. The bug is fixed in svn, but not in the last release (1.2.4). Fortunately, preventing this bug is fairly easy. All you have to do is call setCookieName on your modal window. So either setCookieName(null) - if you don't want it to remember size in cookies or setCookieName(myModalWindowName) - if you want it to remember the size -Matej - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window Bug (important)
was this in jira? fixed in 1.2.x? if its not could you enter it so it shows up on 1.2.5 release notes... thanks, -igor On 1/29/07, Matej Knopp [EMAIL PROTECTED] wrote: Hi, It seems that quite a lot of people are using ModalWindow lately. I just want to inform you that there is a bug in modal window that can cause it to eat all your browser's cookies. The bug is fixed in svn, but not in the last release (1.2.4). Fortunately, preventing this bug is fairly easy. All you have to do is call setCookieName on your modal window. So either setCookieName(null) - if you don't want it to remember size in cookies or setCookieName(myModalWindowName) - if you want it to remember the size -Matej - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window Bug (important)
Where can I get more information about this bug? I use ModalWindow for a few place and this look fine to me, how can I trigger this bug? By the way, should I remove this line once I update wicket library? On 1/30/07, Matej Knopp [EMAIL PROTECTED] wrote: Hi, It seems that quite a lot of people are using ModalWindow lately. I just want to inform you that there is a bug in modal window that can cause it to eat all your browser's cookies. The bug is fixed in svn, but not in the last release (1.2.4). Fortunately, preventing this bug is fairly easy. All you have to do is call setCookieName on your modal window. So either setCookieName(null) - if you don't want it to remember size in cookies or setCookieName(myModalWindowName) - if you want it to remember the size -Matej - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] modal window is closed when form inside content panel is submitted
Can you please check your log? Probably there will be an exception. Can
you post the stacktrace?
-Matej
Nili Adoram wrote:
I tried replacing the original SubmitLink in the form with an
AjaxSubmitLink:
public class AdvancedSearchForm extends Form {
private static final String id = advanedSearchFrom;
public AdvancedSearchForm(IModel model) {
super(id, model);
add(new TextField(name));
add(new TextField(user));
// old code:
//add(new SubmitLink(submitSearch));
add(new AjaxSubmitLink(submitSearch,AdvancedSearchForm.this){
@Override
protected void onSubmit(AjaxRequestTarget target, Form form) {
ModalWindow.close(target);
}});
}
}
However the modal window did not open and the following errors were
displayed:
Firefox Error console:
Error: no element found
Source File:
http://nilia/provision?wicket:interface=:9:simpleSearchPanel:advancedSearch::IBehaviorListenerwicket:behaviorId=0random=0.6456663530703572
Line: 1, Column: 54
Source Code:
?xml version=1.0
encoding=UTF-8?ajax-response-^
Error: no element found
Source File:
http://nilia/provision/plugins/request-provision/ProvisioningRequests
Line: 1, Column: 54
Source Code:
?xml version=1.0
encoding=UTF-8?ajax-response-^
Wicket Ajax Debug window:
-
?xml version=1.0 encoding=UTF-8?ajax-response
ERROR: Error while parsing response: Could not find root ajax-response
element
INFO: Invoking post-call handler(s)...
INFO: Invoking failure handler(s)...
When I replace the AjaxSubmitLink back with a SubmitLink the modal
window properly appears.
Thanks
Nili
Matej Knopp wrote:
You have to use AjaxSubmitLink and call Window.close(target) inside the
onSubmit(AjaxRequestTarget...) method.
-Matej
Nili Adoram wrote:
Hi all,
I have a panel (named AdvancedSearchPanel) containing a Form with a
SubmitLink.
I open this panel inside a modal dialog:
final ModalWindow modal;
add(modal = new ModalWindow(modalAdvancedSearch));
final AdvancedSearchPanel searchPanel = new
AdvancedSearchPanel(modal
.getContentId());
modal.setContent(searchPanel);
When the form is submitted, a message is displayed (Reloading this
page will cause the modal window disappear.) and the modal window is
closed.
However, the CloseButtonCallback and WindowClosedCallback are not called.
These callbacks are only called if the close button is clicked.
What causes the submit button to close the window?
How can verify that these callbacks are invoked whenever the window is
closed?
Thanks,
Nili
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] modal window is closed when form inside content panel is submitted
Indeed there was an error since I put an input tag for the
AjaxSubmitLink inside the markup instead of a tag.
I fixed the markup and now the form is submitted, the modal window is
closed and the window closed callback is invoked.
Thank you,
Nili
Matej Knopp wrote:
Can you please check your log? Probably there will be an exception. Can
you post the stacktrace?
-Matej
Nili Adoram wrote:
I tried replacing the original SubmitLink in the form with an
AjaxSubmitLink:
public class AdvancedSearchForm extends Form {
private static final String id = advanedSearchFrom;
public AdvancedSearchForm(IModel model) {
super(id, model);
add(new TextField(name));
add(new TextField(user));
// old code:
//add(new SubmitLink(submitSearch));
add(new AjaxSubmitLink(submitSearch,AdvancedSearchForm.this){
@Override
protected void onSubmit(AjaxRequestTarget target, Form form) {
ModalWindow.close(target);
}});
}
}
However the modal window did not open and the following errors were
displayed:
Firefox Error console:
Error: no element found
Source File:
http://nilia/provision?wicket:interface=:9:simpleSearchPanel:advancedSearch::IBehaviorListenerwicket:behaviorId=0random=0.6456663530703572
Line: 1, Column: 54
Source Code:
?xml version=1.0
encoding=UTF-8?ajax-response-^
Error: no element found
Source File:
http://nilia/provision/plugins/request-provision/ProvisioningRequests
Line: 1, Column: 54
Source Code:
?xml version=1.0
encoding=UTF-8?ajax-response-^
Wicket Ajax Debug window:
-
?xml version=1.0 encoding=UTF-8?ajax-response
ERROR: Error while parsing response: Could not find root ajax-response
element
INFO: Invoking post-call handler(s)...
INFO: Invoking failure handler(s)...
When I replace the AjaxSubmitLink back with a SubmitLink the modal
window properly appears.
Thanks
Nili
Matej Knopp wrote:
You have to use AjaxSubmitLink and call Window.close(target) inside the
onSubmit(AjaxRequestTarget...) method.
-Matej
Nili Adoram wrote:
Hi all,
I have a panel (named AdvancedSearchPanel) containing a Form with a
SubmitLink.
I open this panel inside a modal dialog:
final ModalWindow modal;
add(modal = new ModalWindow(modalAdvancedSearch));
final AdvancedSearchPanel searchPanel = new
AdvancedSearchPanel(modal
.getContentId());
modal.setContent(searchPanel);
When the form is submitted, a message is displayed (Reloading this
page will cause the modal window disappear.) and the modal window is
closed.
However, the CloseButtonCallback and WindowClosedCallback are not called.
These callbacks are only called if the close button is clicked.
What causes the submit button to close the window?
How can verify that these callbacks are invoked whenever the window is
closed?
Thanks,
Nili
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions
Re: [Wicket-user] modal window is closed when form inside content panel is submitted
I just get the problem, solved by using ajax form button, you can see how I solve it at http://www.nabble.com/Submit-a-form-at-ModalWindow-cause-the-ModalWindow-close.-tf2912895.html#a8139020 On 1/9/07, Nili Adoram [EMAIL PROTECTED] wrote: Hi all, I have a panel (named AdvancedSearchPanel) containing a Form with a SubmitLink. I open this panel inside a modal dialog: final ModalWindow modal; add(modal = new ModalWindow(modalAdvancedSearch)); final AdvancedSearchPanel searchPanel = new AdvancedSearchPanel(modal .getContentId()); modal.setContent(searchPanel); When the form is submitted, a message is displayed (Reloading this page will cause the modal window disappear.) and the modal window is closed. However, the CloseButtonCallback and WindowClosedCallback are not called. These callbacks are only called if the close button is clicked. What causes the submit button to close the window? How can verify that these callbacks are invoked whenever the window is closed? Thanks, Nili - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] modal window is closed when form inside content panel is submitted
You have to use AjaxSubmitLink and call Window.close(target) inside the onSubmit(AjaxRequestTarget...) method. -Matej Nili Adoram wrote: Hi all, I have a panel (named AdvancedSearchPanel) containing a Form with a SubmitLink. I open this panel inside a modal dialog: final ModalWindow modal; add(modal = new ModalWindow(modalAdvancedSearch)); final AdvancedSearchPanel searchPanel = new AdvancedSearchPanel(modal .getContentId()); modal.setContent(searchPanel); When the form is submitted, a message is displayed (Reloading this page will cause the modal window disappear.) and the modal window is closed. However, the CloseButtonCallback and WindowClosedCallback are not called. These callbacks are only called if the close button is clicked. What causes the submit button to close the window? How can verify that these callbacks are invoked whenever the window is closed? Thanks, Nili - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] modal window is closed when form inside content panel is submitted
I tried replacing the original SubmitLink in the form with an
AjaxSubmitLink:
public class AdvancedSearchForm extends Form {
private static final String id = advanedSearchFrom;
public AdvancedSearchForm(IModel model) {
super(id, model);
add(new TextField(name));
add(new TextField(user));
// old code:
//add(new SubmitLink(submitSearch));
add(new AjaxSubmitLink(submitSearch,AdvancedSearchForm.this){
@Override
protected void onSubmit(AjaxRequestTarget target, Form form) {
ModalWindow.close(target);
}});
}
}
However the modal window did not open and the following errors were
displayed:
Firefox Error console:
Error: no element found
Source File:
http://nilia/provision?wicket:interface=:9:simpleSearchPanel:advancedSearch::IBehaviorListenerwicket:behaviorId=0random=0.6456663530703572
Line: 1, Column: 54
Source Code:
?xml version=1.0
encoding=UTF-8?ajax-response-^
Error: no element found
Source File:
http://nilia/provision/plugins/request-provision/ProvisioningRequests
Line: 1, Column: 54
Source Code:
?xml version=1.0
encoding=UTF-8?ajax-response-^
Wicket Ajax Debug window:
-
?xml version=1.0 encoding=UTF-8?ajax-response
ERROR: Error while parsing response: Could not find root ajax-response element
INFO: Invoking post-call handler(s)...
INFO: Invoking failure handler(s)...
When I replace the AjaxSubmitLink back with a SubmitLink the modal
window properly appears.
Thanks
Nili
Matej Knopp wrote:
You have to use AjaxSubmitLink and call Window.close(target) inside the
onSubmit(AjaxRequestTarget...) method.
-Matej
Nili Adoram wrote:
Hi all,
I have a panel (named AdvancedSearchPanel) containing a Form with a
SubmitLink.
I open this panel inside a modal dialog:
final ModalWindow modal;
add(modal = new ModalWindow(modalAdvancedSearch));
final AdvancedSearchPanel searchPanel = new
AdvancedSearchPanel(modal
.getContentId());
modal.setContent(searchPanel);
When the form is submitted, a message is displayed (Reloading this
page will cause the modal window disappear.) and the modal window is
closed.
However, the CloseButtonCallback and WindowClosedCallback are not called.
These callbacks are only called if the close button is clicked.
What causes the submit button to close the window?
How can verify that these callbacks are invoked whenever the window is
closed?
Thanks,
Nili
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] modal window with form
you would put all this into a base page, and your markup inheritance to template it for the rest of the pages. -igor On 1/8/07, Nili Adoram [EMAIL PROTECTED] wrote: Hi all, I want to implement the following: All application pages should contain some Search button. When the user clicks this button, a modal dialog with Search Form will be displayed. Once the user submits the form the modal dialog should be closed and Search Results Page will be displayed. What would be the best practice to implement this? Thanks Nili - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal window with form
Can you please use the latest SVN version (or wait until 1.2.3 is out) to see if any of those issues persist? -Matej Marc-Andre Houle wrote: I got problems with a form in a Modal Window. In IE, it is not possible to pass from one field to the other with the tab key. Step to reproduce : - get the quickstart package from the wicket site - Replace source file with what is given in this mail - Build, deploy, open in IE, click to open the modal window - Try to navigate in the form using the tab and shift-tab key. Is it a browser limitation or it is in the way wicket implement the modal window? Also, related to this issue, when you are in Firefox, it is impossible to see the cursor in the edit box. The tab key work, but there is no cursor associated. Thanks in advance. Marc Show modal dialog with panel field1: field2: - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal window with form
Problem solved in the latest build.Thanks a lot.On 10/26/06, Marc-André Houle [EMAIL PROTECTED] wrote: Yeah, sorry to not have said it before, I use wicket 1.2.2.How long until 1.2.3?If it is a matter of days, I'll wait to integrate with our application.If long, I'll check the svn versionwith the example I submitted here.MarcLe 06-10-26 à 03:13, Matej Knopp a écrit : Can you please use the latest SVN version (or wait until 1.2.3 is out) to see if any of those issues persist? -Matej Marc-Andre Houle wrote: I got problems with a form in a Modal Window. In IE, it is not possible to pass from one field to the other with the tab key. Step to reproduce :- get the quickstart package from the wicket site- Replace source file with what is given in this mail - Build, deploy, open in IE, click to open the modal window- Try to navigate in the form using the tab and shift-tab key. Is it a browser limitation or it is in the way wicket implement the modal window? Also, related to this issue, when you are in Firefox, it is impossible to see the cursor in the edit box.The tab key work, but there is no cursor associated. Thanks in advance. Marc - --- Show modal dialog with panel - --- field1: field2: - --- - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel? cmd=lnkkid=120709bid=263057dat=121642 - --- ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel? cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window
Okay, this is how it is in current svn. For 1.x, hashCode is used to generate id. For 2.0, getClassRelativePath() is used, as the place in component hierarchy is already known in constructor. hope it helps. -Matej samyem wrote: Thanks. That was helpful, but it seems to be more difficult than it needs to be. I think the default behaviour should have been to use different cookie names per instance of the modal window, but apparently the same cookie name were used for all instances. I tried to use getClassRelativePath() for the modal window. I guess a simple fix of using distinct cookie name per modal window instance would solve the problem in general. Matej Knopp wrote: Modal window width and height is stored in a cookie. First time initial width and height is used, and after that the width and height from the cookie is used. What you need to do is set different cookie id for different modal windows. Or disable cookies at all (setCookieId(null)). -Matej samyem wrote: If the modal window is resizable, why is it ignoring the window size, and what should be done if I do need to supply a width and height? At the moment, I can set an initial width and height, but after I close the window and go to another page with another modal window, instead of using the initial width/height set for the modal window, it uses the last known width/height values. For non-resizable modal windows, this behaviour does not occur. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window
Modal window width and height is stored in a cookie. First time initial width and height is used, and after that the width and height from the cookie is used. What you need to do is set different cookie id for different modal windows. Or disable cookies at all (setCookieId(null)). -Matej samyem wrote: If the modal window is resizable, why is it ignoring the window size, and what should be done if I do need to supply a width and height? At the moment, I can set an initial width and height, but after I close the window and go to another page with another modal window, instead of using the initial width/height set for the modal window, it uses the last known width/height values. For non-resizable modal windows, this behaviour does not occur. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window
Thanks. That was helpful, but it seems to be more difficult than it needs to be. I think the default behaviour should have been to use different cookie names per instance of the modal window, but apparently the same cookie name were used for all instances. I tried to use getClassRelativePath() for the modal window. I guess a simple fix of using distinct cookie name per modal window instance would solve the problem in general. Matej Knopp wrote: Modal window width and height is stored in a cookie. First time initial width and height is used, and after that the width and height from the cookie is used. What you need to do is set different cookie id for different modal windows. Or disable cookies at all (setCookieId(null)). -Matej samyem wrote: If the modal window is resizable, why is it ignoring the window size, and what should be done if I do need to supply a width and height? At the moment, I can set an initial width and height, but after I close the window and go to another page with another modal window, instead of using the initial width/height set for the modal window, it uses the last known width/height values. For non-resizable modal windows, this behaviour does not occur. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Modal-Window-tf2268885.html#a6309891 Sent from the Wicket - User forum at Nabble.com. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window
I'll think about it. The behavior you have suggested might be the right default behavior. Would you please be so kind as to fill a feature request so that I won't forget about it? Thanks. -Matej samyem wrote: Thanks. That was helpful, but it seems to be more difficult than it needs to be. I think the default behaviour should have been to use different cookie names per instance of the modal window, but apparently the same cookie name were used for all instances. I tried to use getClassRelativePath() for the modal window. I guess a simple fix of using distinct cookie name per modal window instance would solve the problem in general. Matej Knopp wrote: Modal window width and height is stored in a cookie. First time initial width and height is used, and after that the width and height from the cookie is used. What you need to do is set different cookie id for different modal windows. Or disable cookies at all (setCookieId(null)). -Matej samyem wrote: If the modal window is resizable, why is it ignoring the window size, and what should be done if I do need to supply a width and height? At the moment, I can set an initial width and height, but after I close the window and go to another page with another modal window, instead of using the initial width/height set for the modal window, it uses the last known width/height values. For non-resizable modal windows, this behaviour does not occur. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window
Hi Samyem, If you have concrete suggestions to improve components, it works best to create feature requests for them at http://sourceforge.net/tracker/?group_id=119783atid=684978. That way, they won't get lost in the email archives. Eelco On 9/13/06, samyem [EMAIL PROTECTED] wrote: If the modal window is resizable, why is it ignoring the window size, and what should be done if I do need to supply a width and height? At the moment, I can set an initial width and height, but after I close the window and go to another page with another modal window, instead of using the initial width/height set for the modal window, it uses the last known width/height values. For non-resizable modal windows, this behaviour does not occur. -- View this message in context: http://www.nabble.com/Modal-Window-tf2268885.html#a6297354 Sent from the Wicket - User forum at Nabble.com. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Modal Window
And of course, if you have concrete code (patches), that will even increase the chance of the request being honored and quickly so. Eelco On 9/13/06, Eelco Hillenius [EMAIL PROTECTED] wrote: Hi Samyem, If you have concrete suggestions to improve components, it works best to create feature requests for them at http://sourceforge.net/tracker/?group_id=119783atid=684978. That way, they won't get lost in the email archives. Eelco On 9/13/06, samyem [EMAIL PROTECTED] wrote: If the modal window is resizable, why is it ignoring the window size, and what should be done if I do need to supply a width and height? At the moment, I can set an initial width and height, but after I close the window and go to another page with another modal window, instead of using the initial width/height set for the modal window, it uses the last known width/height values. For non-resizable modal windows, this behaviour does not occur. -- View this message in context: http://www.nabble.com/Modal-Window-tf2268885.html#a6297354 Sent from the Wicket - User forum at Nabble.com. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
