GWT-like

[kan <ka...@gmail.com>]

Is there any easy way to make wicket applications like GWT? I mean to
make a "heavy client side", so it will allow easy manage data
pre-loading and requests (AJAX too) caching. The aim is to minimize
amount of web-server requests.
Say, I have several tabs on a page. Some tabs should have all data
pre-loaded and switched immediately (no requests to server). Some tabs
are "big", so they do an AJAX request for data, but only if a tab is
opened first time.

-- 
WBR, kan.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: GWT-like

[Igor Vaynberg <ig...@gmail.com>]

i did not say it was a bad idea to embed js components, i said it was
a bad idea to try and build a gwt-like fat-client using wicket. for
that there is gwt.

-igor

On Wed, Apr 29, 2009 at 10:47 PM, Vladimir K <ko...@gmail.com> wrote:
>
> Igor, I believe it is not so bad idea to embed third-party JS components with
> ease (those who are capable to wrap existing div tag).
>
> 1. Wicket applications can be leveraged by many well designed and tested JS
> components
> 2. It reduces hardware requirements and imroves scalability due to smaller
> number of client-server roundtrips
> 3. There are the cases where it is better to design component is JS instead
> of Java, for instance imagine full calendar component (like MS outlook has),
> dynamic charts (including Gantt), rich text editor and so on. Even any
> drill-down component (menu, panel) is better to design in JS.
>
> Probably wicket should be capable of transferring js-component's client
> state to backing server-side component when handling the client event.
> Creating a hidden text input and serializing js-component state to it before
> submit will work. Just for synchronization. Concerning events it seems we
> just can use exising behaviors.
>
> I believe wicket ui in most cases is as fast as ajaxy js ui because in both
> cases we have to exchange some packages of data and access the database. And
> there should be the cases where wicket is faster because it can just apply
> innerHtml. JS has to parse the response and do something with dom.
> But there are the cases like tab control as mentioned, where we don't need
> server roundtrip to switch tabs. From the other hand we probably just need
> to optimize existing AjaxTabbedPanel to allow the settings on tab
> (ajax/static). Depending on this setting the appropriate links will be
> rendered on the tab captions.
>
> Concerning GWT ... just have a look at response times of Compiere 3.0 on
> latest Google Chrome. On my 2.4Ghz desktop it takes about 7 seconds between
> click on radio-button and see that selection is changed. GWT is out of the
> scope.
>
>
> igor.vaynberg wrote:
>>
>> dont try to make wicket into gwt. if you want a fat client then use
>> gwt, if you want a server-side app then use wicket.
>>
>> -igor
>>
>> On Wed, Apr 29, 2009 at 8:06 AM, kan <ka...@gmail.com> wrote:
>>> Is there any easy way to make wicket applications like GWT? I mean to
>>> make a "heavy client side", so it will allow easy manage data
>>> pre-loading and requests (AJAX too) caching. The aim is to minimize
>>> amount of web-server requests.
>>> Say, I have several tabs on a page. Some tabs should have all data
>>> pre-loaded and switched immediately (no requests to server). Some tabs
>>> are "big", so they do an AJAX request for data, but only if a tab is
>>> opened first time.
>>>
>>> --
>>> WBR, kan.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/GWT-like-tp23299279p23310287.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: GWT-like

[Vladimir K <ko...@gmail.com>]

Igor, I believe it is not so bad idea to embed third-party JS components with
ease (those who are capable to wrap existing div tag).

1. Wicket applications can be leveraged by many well designed and tested JS
components
2. It reduces hardware requirements and imroves scalability due to smaller
number of client-server roundtrips
3. There are the cases where it is better to design component is JS instead
of Java, for instance imagine full calendar component (like MS outlook has),
dynamic charts (including Gantt), rich text editor and so on. Even any
drill-down component (menu, panel) is better to design in JS.

Probably wicket should be capable of transferring js-component's client
state to backing server-side component when handling the client event.
Creating a hidden text input and serializing js-component state to it before
submit will work. Just for synchronization. Concerning events it seems we
just can use exising behaviors.

I believe wicket ui in most cases is as fast as ajaxy js ui because in both
cases we have to exchange some packages of data and access the database. And
there should be the cases where wicket is faster because it can just apply
innerHtml. JS has to parse the response and do something with dom.
But there are the cases like tab control as mentioned, where we don't need
server roundtrip to switch tabs. From the other hand we probably just need
to optimize existing AjaxTabbedPanel to allow the settings on tab
(ajax/static). Depending on this setting the appropriate links will be
rendered on the tab captions.

Concerning GWT ... just have a look at response times of Compiere 3.0 on
latest Google Chrome. On my 2.4Ghz desktop it takes about 7 seconds between
click on radio-button and see that selection is changed. GWT is out of the
scope.


igor.vaynberg wrote:
> 
> dont try to make wicket into gwt. if you want a fat client then use
> gwt, if you want a server-side app then use wicket.
> 
> -igor
> 
> On Wed, Apr 29, 2009 at 8:06 AM, kan <ka...@gmail.com> wrote:
>> Is there any easy way to make wicket applications like GWT? I mean to
>> make a "heavy client side", so it will allow easy manage data
>> pre-loading and requests (AJAX too) caching. The aim is to minimize
>> amount of web-server requests.
>> Say, I have several tabs on a page. Some tabs should have all data
>> pre-loaded and switched immediately (no requests to server). Some tabs
>> are "big", so they do an AJAX request for data, but only if a tab is
>> opened first time.
>>
>> --
>> WBR, kan.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/GWT-like-tp23299279p23310287.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: GWT-like

[Per Lundholm <pe...@gmail.com>]

Yeah but I have a really bad experience with GWT. If the number of
objects that are on a page goes up, performance decreases drastically
due to the use of Javascript. No wonder Google wrote a browser of
their own.

Take a look at AjaxLazyLoadPanel if it might do the trick for your
heavier parts.

Javadoc: "A panel where you can lazy load another panel. This can be
used if you have a panel/component that is pretty heavy in creation
and you first want to show the user the page and the replace the panel
when it is ready. "

/per

On Wed, Apr 29, 2009 at 9:11 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> dont try to make wicket into gwt. if you want a fat client then use
> gwt, if you want a server-side app then use wicket.
>
> -igor
>
> On Wed, Apr 29, 2009 at 8:06 AM, kan <ka...@gmail.com> wrote:
>> Is there any easy way to make wicket applications like GWT? I mean to
>> make a "heavy client side", so it will allow easy manage data
>> pre-loading and requests (AJAX too) caching. The aim is to minimize
>> amount of web-server requests.
>> Say, I have several tabs on a page. Some tabs should have all data
>> pre-loaded and switched immediately (no requests to server). Some tabs
>> are "big", so they do an AJAX request for data, but only if a tab is
>> opened first time.
>>
>> --
>> WBR, kan.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Varning! E-post till och från Sverige, eller som passerar
servrar i Sverige, avlyssnas av Försvarets Radioanstalt, FRA.

WARNING! E-mail to and from Sweden, or via servers in Sweden,
is monitored by the National Defence Radio Establishment.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: GWT-like

[Igor Vaynberg <ig...@gmail.com>]

dont try to make wicket into gwt. if you want a fat client then use
gwt, if you want a server-side app then use wicket.

-igor

On Wed, Apr 29, 2009 at 8:06 AM, kan <ka...@gmail.com> wrote:
> Is there any easy way to make wicket applications like GWT? I mean to
> make a "heavy client side", so it will allow easy manage data
> pre-loading and requests (AJAX too) caching. The aim is to minimize
> amount of web-server requests.
> Say, I have several tabs on a page. Some tabs should have all data
> pre-loaded and switched immediately (no requests to server). Some tabs
> are "big", so they do an AJAX request for data, but only if a tab is
> opened first time.
>
> --
> WBR, kan.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: GWT-like

[kan <ka...@gmail.com>]

Yes, I thought about jQuery, and even have found a WickeXt project.
But it doesn't give a flexibility - so I cannot easily mix and manage
pre-load/cache strategies.
And I don't know easy way to make AJAX requests cached, only by
explicit javascript, and it eliminates Wicket advantages.

2009/4/29 Jeremy Thomerson <je...@wickettraining.com>:
> That's the main difference between GWT and Wicket - so if you really
> NEED it all client-side, then use GWT.
>
> As far as your tab problem - sure, you can do this with Wicket.  The
> default (I believe - it's been a while since I used the tabbed panel)
> is to load the other tab via ajax.  But if you want some tabbed panels
> to preload everything, just use jQuery or dojo, etc to make that
> tabbed panel - IOW, output all of the markup with Wicket and add the
> tabs as a JS effect.  It eliminates the server callbacks.  Make this a
> reusable component and you can use it wherever you want it.
>
> Remember not to prematurely optimize.  Code maintenance costs more
> than operational costs.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Wed, Apr 29, 2009 at 10:06 AM, kan <ka...@gmail.com> wrote:
>> Is there any easy way to make wicket applications like GWT? I mean to
>> make a "heavy client side", so it will allow easy manage data
>> pre-loading and requests (AJAX too) caching. The aim is to minimize
>> amount of web-server requests.
>> Say, I have several tabs on a page. Some tabs should have all data
>> pre-loaded and switched immediately (no requests to server). Some tabs
>> are "big", so they do an AJAX request for data, but only if a tab is
>> opened first time.
>>
>> --
>> WBR, kan.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
WBR, kan.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: GWT-like

[Jeremy Thomerson <je...@wickettraining.com>]

That's the main difference between GWT and Wicket - so if you really
NEED it all client-side, then use GWT.

As far as your tab problem - sure, you can do this with Wicket.  The
default (I believe - it's been a while since I used the tabbed panel)
is to load the other tab via ajax.  But if you want some tabbed panels
to preload everything, just use jQuery or dojo, etc to make that
tabbed panel - IOW, output all of the markup with Wicket and add the
tabs as a JS effect.  It eliminates the server callbacks.  Make this a
reusable component and you can use it wherever you want it.

Remember not to prematurely optimize.  Code maintenance costs more
than operational costs.

--
Jeremy Thomerson
http://www.wickettraining.com




On Wed, Apr 29, 2009 at 10:06 AM, kan <ka...@gmail.com> wrote:
> Is there any easy way to make wicket applications like GWT? I mean to
> make a "heavy client side", so it will allow easy manage data
> pre-loading and requests (AJAX too) caching. The aim is to minimize
> amount of web-server requests.
> Say, I have several tabs on a page. Some tabs should have all data
> pre-loaded and switched immediately (no requests to server). Some tabs
> are "big", so they do an AJAX request for data, but only if a tab is
> opened first time.
>
> --
> WBR, kan.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org