Apache Wicket › Users forum

Single page wicket app

Classic

List

Threaded

11 messages Options

bobj

Single page wicket app

We are creating a large single page wicket based application using tabs and ajax to replace portions of the page when needed.

Does anyone know of any large single page wicket apps out there, or any issues we need to address?

thanks!

Martin Grigorov-4

Re: Single page wicket app

Hi,

I think the biggest concern here is the back button support.
What are your requirements about this ?

On Tue, May 15, 2012 at 6:06 PM, bobj <[hidden email]> wrote:

> We are creating a large single page wicket based application using tabs and
> ajax to replace portions of the page when needed.
>
> Does anyone know of any large single page wicket apps out there, or any
> issues we need to address?
>
> thanks!
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Single-page-wicket-app-tp4634756.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Jürgen Lind-2

Re: Single page wicket app

In reply to this post by bobj

What do you mean by "large"? Many users or many dialogs/components? I have developed
three more or less (which means that a new page was only needed when basically the entire
structure changed - which occured seldomly) single page apps with wicket and I have not
run into real problems. But as Martin mentiones in the next post, the Back-Bitton support
is mostly gone...

J.

On 15.05.2012 18:06, bobj wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

W Mazur

Re: Single page wicket app

I would add Wicket Session size.
See: http://www.small-improvements.com/blog/technical/tuning-wicket-session-size

Regards

2012/5/15 Jürgen Lind <[hidden email]>:

> What do you mean by "large"? Many users or many dialogs/components? I have
> developed
> three more or less (which means that a new page was only needed when
> basically the entire
> structure changed - which occured seldomly) single page apps with wicket and
> I have not
> run into real problems. But as Martin mentiones in the next post, the
> Back-Bitton support
> is mostly gone...
>
> J.
>
>
> On 15.05.2012 18:06, bobj wrote:
>>
>> We are creating a large single page wicket based application using tabs
>> and
>> ajax to replace portions of the page when needed.
>>
>> Does anyone know of any large single page wicket apps out there, or any
>> issues we need to address?
>>
>> thanks!
>>
>> --
>> View this message in context:
>> http://apache-wicket.1842946.n4.nabble.com/Single-page-wicket-app-tp4634756.html
>> Sent from the Users forum mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Martin Grigorov-4

Re: Single page wicket app

On Tue, May 15, 2012 at 9:03 PM, W Mazur <[hidden email]> wrote:
> I would add Wicket Session size.
> See: http://www.small-improvements.com/blog/technical/tuning-wicket-session-size

Can you be more specific ?
How single-page app is different in this respect to a normal app ?

>
> Regards
>
> 2012/5/15 Jürgen Lind <[hidden email]>:
>> What do you mean by "large"? Many users or many dialogs/components? I have
>> developed
>> three more or less (which means that a new page was only needed when
>> basically the entire
>> structure changed - which occured seldomly) single page apps with wicket and
>> I have not
>> run into real problems. But as Martin mentiones in the next post, the
>> Back-Bitton support
>> is mostly gone...
>>
>> J.
>>
>>
>> On 15.05.2012 18:06, bobj wrote:
>>>
>>> We are creating a large single page wicket based application using tabs
>>> and
>>> ajax to replace portions of the page when needed.
>>>
>>> Does anyone know of any large single page wicket apps out there, or any
>>> issues we need to address?
>>>
>>> thanks!
>>>
>>> --
>>> View this message in context:
>>> http://apache-wicket.1842946.n4.nabble.com/Single-page-wicket-app-tp4634756.html
>>> Sent from the Users forum mailing list archive at Nabble.com.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

bobj

Re: Single page wicket app

Thanks for the replies!

By large I mean lots of tabs and panels, not lots of users say 100s not 1000s.
By single page app, I mean there is only one page and the user never navigates to another page. Panels come and go as required.

I do not expect to support the back button, with ajax and panel replacements.

Thanks for the link on session state.

Since the users will stay on a single page for a long time, and never go to a different page, do I need to be concerned with wicket not saving/serializing the page state?

thanks,
Bobj

Martijn Dashorst

Re: Single page wicket app

Administrator

On Thu, May 17, 2012 at 6:36 PM, bobj <[hidden email]> wrote:
> Since the users will stay on a single page for a long time, and never go to
> a different page, do I need to be concerned with wicket not
> saving/serializing the page state?

It would be a drag for users that they would need to build up the
state (i.e. navigate through all panels and such) when you restart the
server (for any reason: code change, configuration change etc).

So in my opinion you should care about that stuff.

It is also rather difficult for people to bookmark parts of your
application (although you can build your own custom in-app
bookmarks/favorites for that) when you create a single page app.

I am not yet a big fan of building single page apps but also don't
necessarily like the 1000+ page apps either.

Martijn

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Martin Grigorov-4

Re: Single page wicket app

In reply to this post by bobj

On Thu, May 17, 2012 at 6:36 PM, bobj <[hidden email]> wrote:

> Thanks for the replies!
>
> By large I mean lots of tabs and panels, not lots of users say 100s not
> 1000s.
> By single page app, I mean there is only one page and the user never
> navigates to another page. Panels come and go as required.
>
> I do not expect to support the back button, with ajax and panel
> replacements.
>
> Thanks for the link on session state.
>
> Since the users will stay on a single page for a long time, and never go to
> a different page, do I need to be concerned with wicket not
> saving/serializing the page state?

The page is serialized in Ajax request!
The difference with non-Ajax is that Wicket wont create a new page id
for the new state, so the new bytes will override the old ones. That's
why there is no history. You always have the latest state.

>
> thanks,
> Bobj
>
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Single-page-wicket-app-tp4634756p4643219.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

Alec Swan

Re: Single page wicket app

Our app uses one-page-ajax-panel-swap approach and I ran into an issue
with versioned pages described here
http://markmail.org/thread/q3ewso5dnf2wjsol

Alec

On Thu, May 17, 2012 at 11:12 AM, Martin Grigorov <[hidden email]> wrote:

> On Thu, May 17, 2012 at 6:36 PM, bobj <[hidden email]> wrote:
>> Thanks for the replies!
>>
>> By large I mean lots of tabs and panels, not lots of users say 100s not
>> 1000s.
>> By single page app, I mean there is only one page and the user never
>> navigates to another page. Panels come and go as required.
>>
>> I do not expect to support the back button, with ajax and panel
>> replacements.
>>
>> Thanks for the link on session state.
>>
>> Since the users will stay on a single page for a long time, and never go to
>> a different page, do I need to be concerned with wicket not
>> saving/serializing the page state?
>
> The page is serialized in Ajax request!
> The difference with non-Ajax is that Wicket wont create a new page id
> for the new state, so the new bytes will override the old ones. That's
> why there is no history. You always have the latest state.
>
>>
>> thanks,
>> Bobj
>>
>>
>> --
>> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Single-page-wicket-app-tp4634756p4643219.html
>> Sent from the Users forum mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

armhold

Re: Single page wicket app

In reply to this post by bobj

Ajax calls do save the page state. I think the real issue for you is
that if users have the page open but idle for a long time (longer than
session expiration... 30 mins?) the Ajax links won't work for them
when they decide to start using the page again.

You could perhaps use a AjaxSelfUpdatingTimerBehavior to keep the
session open, if you can afford to have a session running for every
user with an open tab.

> Since the users will stay on a single page for a long time, and
> never go to a different page, do I need to be concerned with wicket
> not saving/serializing the page state?

Martin Grigorov-4

Re: Single page wicket app

On Fri, May 18, 2012 at 4:12 PM, armhold <[hidden email]> wrote:
> Ajax calls do save the page state. I think the real issue for you is
> that if users have the page open but idle for a long time (longer than
> session expiration... 30 mins?) the Ajax links won't work for them
> when they decide to start using the page again.

If the page is mounted with #mountPage()/MountedMapper then clicking
on an AjaxLink that leads to an expired page will create a new
instance of the same type and will *not* execute #onClick() for that
link (because the link is gone with the first page).
But the user will be able to proceed with his work.

>
> You could perhaps use a AjaxSelfUpdatingTimerBehavior to keep the
> session open, if you can afford to have a session running for every
> user with an open tab.
>
>> Since the users will stay on a single page for a long time, and
>> never go to a different page, do I need to be concerned with wicket
>> not saving/serializing the page state?
>
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Single-page-wicket-app-tp4634756p4644559.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>