On 1/31/07, Daniele Dellafiore <[EMAIL PROTECTED]> wrote:
> I will try to understand better how things works.
> What I really need is to get the new browser size after a search form
> has been submitted so I can try to send the size properties in the
> search form (as you do in thee postback form)
I will try to understand better how things works.
What I really need is to get the new browser size after a search form
has been submitted so I can try to send the size properties in the
search form (as you do in thee postback form) and then update the
ClientProperties in... some way.
This would
On 1/31/07, Daniele Dellafiore <[EMAIL PROTECTED]> wrote:
> ok, my project is using 1.3 shapshot in fact i can get the browser
> size properties.
> However, like you said, properties are refreshed just at the beginning
> of the session.
> I have tried to include the code found in BrowserInfoPage al
ok, my project is using 1.3 shapshot in fact i can get the browser
size properties.
However, like you said, properties are refreshed just at the beginning
of the session.
I have tried to include the code found in BrowserInfoPage all in the
1.3 snapshot quickstart project: I have inserted:
1)
> of course the change is only in the trunk.
Trunk and wicket-1.x.
> I see on jira that you
> marked it for 1.3 as well as for 2.0.
> As far as i know, trunk will go in 2.0. There will be a 1.3?
Yeah, 1.3 is actually the version that is most heavily under
development right now. It is basically 1
https://svn.apache.org/repos/asf/incubator/wicket/branches/wicket-1.x
i believe
-igor
On 1/30/07, Daniele Dellafiore <[EMAIL PROTECTED]> wrote:
great!
of course the change is only in the trunk. I see on jira that you
marked it for 1.3 as well as for 2.0.
As far as i know, trunk will go in 2
great!
of course the change is only in the trunk. I see on jira that you
marked it for 1.3 as well as for 2.0.
As far as i know, trunk will go in 2.0. There will be a 1.3?
My options right now are to build trunk and try to port my app from
1.2 to 2.0. But if exists a 1.3 branch I guess it should
Note, btw, that this polling is only done the first time you request
for the client properties object. You should use ClientProperties with
care, and if you really need to depend on the client window dimensions
(think twice about whether that is what you really want as well), you
may consider polli
I added the functionality, see: http://issues.apache.org/jira/browse/WICKET-248
You can use the example 'hellobrowser' from wicket-examples to track
what is going on and test whether it works for you.
Eelco
On 1/30/07, Daniele Dellafiore <[EMAIL PROTECTED]> wrote:
> I will be very happy to do t
I will be very happy to do that but I need some help cause I am really
a wicket newbie.
I am watching WebRequestCycle.newClientInfo() and WebClientInfo.init()
that, I suppose, get all the info we should need.
First, the BROWSER_WAS_POLLED_KEY metadata key is never used in the
#init() and so far i
hmm thought we already had that, guess we need to add it
feel free to file a jira issue for this, and def feel free to create a patch
:)
-igor
On 1/30/07, Daniele Dellafiore <[EMAIL PROTECTED]> wrote:
thanks for quick reply.
With this method I receive just the desktop window size and bit de
to be complete, this are the info i receive with java 1.5 under ubuntu
linux, running under maven 2 jetty plugin (6.1) and with firefox
2.0.0.1
On 1/30/07, Daniele Dellafiore <[EMAIL PROTECTED]> wrote:
> thanks for quick reply.
>
> With this method I receive just the desktop window size and bit de
thanks for quick reply.
With this method I receive just the desktop window size and bit depth
(i.e. 1280*800*24 for me) but what I need is the size of the browser
window.
On 1/30/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> pasted from eelco's reply to another thread ===
> Just FYI, in
pasted from eelco's reply to another thread ===
Just FYI, in case you need to know whether your client supports
JavaScript, can be determined with:
((WebClientInfo)getSession().getClientInfo()).getProperties().isJavaEnabled()
which works (best) when you do:
getRequestCycleSettings().se
Hi, I need to change the number of column in a table upon the client page size.
How do I get the size of the browser page? Consider that I receive a
request from a simple search form and I have to compute the number of
column after that request.
Is there a "wicket" way to get the size of the page
15 matches
Mail list logo
