You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by splitshade <ma...@googlemail.com> on 2011/04/30 23:36:43 UTC
Ajaxifying existing application
Hi,
i have a general question,
we have an exisiting application, that now needs to be ajaxified (no page
reloads etc..).
This has never been a requirement, so the application is not prepared at all
for this.
The biggest problem we see is that we have many different pages, but how
shall we do page switches using ajax?
I look forward to any hints on this.
Thank you very much.--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajaxifying-existing-application-tp3486615p3486615.html
Sent from the Users forum 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: Ajaxifying existing application
Posted by Igor Vaynberg <ig...@gmail.com>.
if all your pages extend a base page then you can change the base page
to extend a panel instead.
than s/setResponsePage/setResponsePanel/
create a page that has the necessary infra to swap content panels and
wire in the new setResponsePanel to use that.
-igor
On Sat, Apr 30, 2011 at 2:36 PM, splitshade
<ma...@googlemail.com> wrote:
> Hi,
>
> i have a general question,
> we have an exisiting application, that now needs to be ajaxified (no page
> reloads etc..).
> This has never been a requirement, so the application is not prepared at all
> for this.
>
> The biggest problem we see is that we have many different pages, but how
> shall we do page switches using ajax?
>
> I look forward to any hints on this.
>
> Thank you very much.--
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajaxifying-existing-application-tp3486615p3486615.html
> Sent from the Users forum 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: Ajaxifying existing application
Posted by meduolis <me...@gmail.com>.
Use ajax with responsibility. To much ajax can make bad things :]. I can not
undestand, why you would like to change page to panel, and rerender it all,
just like setResponcePage does. Try to sit and decide, which parts of page
should be ajaxified and which should be left as it is.--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajaxifying-existing-application-tp3486615p3488474.html
Sent from the Users forum 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: Ajaxifying existing application
Posted by splitshade <ma...@googlemail.com>.
Hi James, yes, thats exaclty what I meant.
The Problem is, we have an existing infrastructure, that depends on pages.
The idea to change everything to a "setResponsePanel"-Method seems to be
very good, I think we could realize that very cheaply, thanks for the hint!
Would that be something that could be of interest for the framework itself?
Would it be possible/reasonable to integrate that into an
AbstractAjaxWebPage or something?
I did not try this out, but it seems to be a good idea that could be of
interest to many people?
Regards
Martin
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajaxifying-existing-application-tp3486615p3488304.html
Sent from the Users forum 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: Ajaxifying existing application
Posted by James Carman <ja...@carmanconsulting.com>.
I think he meant that rather than using a page-oriented design, that
they'd need to switch to more of a one page, switch panels design?
On Sun, May 1, 2011 at 4:09 AM, meduolis <me...@gmail.com> wrote:
> Why do you want to switch page using ajax? :D If you redownload all page
> contents, do not use ajax :), it only complicates everything. Use ajax, when
> you want to refresh only some of page components, like table, other
> containers--
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajaxifying-existing-application-tp3486615p3487445.html
> Sent from the Users forum 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: Ajaxifying existing application
Posted by meduolis <me...@gmail.com>.
Why do you want to switch page using ajax? :D If you redownload all page
contents, do not use ajax :), it only complicates everything. Use ajax, when
you want to refresh only some of page components, like table, other
containers--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajaxifying-existing-application-tp3486615p3487445.html
Sent from the Users forum 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: Ajaxifying existing application
Posted by splitshade <ma...@googlemail.com>.
It´s not as if I have a choice, whether this requirement should be
implemented or not:(...
I´m not a big ajax fan, i like the application the way it is today, but ajax
is hype today,
and every customer wants more of it...
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Ajaxifying-existing-application-tp3486615p3489746.html
Sent from the Users forum 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: Ajaxifying existing application
Posted by James Carman <ja...@carmanconsulting.com>.
On Sat, Apr 30, 2011 at 5:36 PM, splitshade
<ma...@googlemail.com> wrote:
> Hi,
>
> i have a general question,
> we have an exisiting application, that now needs to be ajaxified (no page
> reloads etc..).
> This has never been a requirement, so the application is not prepared at all
> for this.
>
So, why is this a requirement now? If it ain't broke, don't fix it.
Why does it *have* to be "ajaxified"?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org