Stateful page feedback

[Bob Schellink <sa...@gmail.com>]

Hi all,

I've recently worked on a project that made use of stateful pages and have come to the conclusion
that they lead to very hard to maintain applications. In addition not all controls and services work
properly with with stateful pages.

In hindsight I believe we made a mistake adding support for stateful pages and would like to rectify
the situation by dropping support in a future release. Instead of stateful pages I think a better
approach would have been to add state support to individual controls such as Table, TabbedPanel etc.

I'd like to gauge some feedback on how many folk uses stateful pages and how they are used. Also how
difficult do you think it will be to convert the stateful page to a stateless page?

Kind regards

Bob

Re: Stateful page feedback

[Axel Morgner <ax...@morgner.de>]

 Hi Bob,

I discarded using stateful pages again. In most of my use cases I don't
need the complete page to be stateful, but only a table with pager or
so. I would appreciate the design change.

Kind regards

Axel

-- 
Axel Morgner

Creative Solutions - Software Engineering
GUI & UX Design - Project Management

c/o inxire GmbH
Hanauer Landstr. 293a
60314 Frankfurt
Germany

Phone	+49 179 1046080
E-mail	axel@morgner.de
Web	http://morgner.de

Advice in how to integrate Apache Click and Restlet Webservice in the same Tomcat Server

[Andre Gustavo Lomonaco <lo...@ipplus.com.br>]

Hi guys,

I have my Web Application running today with Apache Click using Cayenne with 
HSQLDB.
Now I wanna install the Restlet WebService in the same Tomcat Server to 
permit access the HSQLDB Data via Android

Someone has already did that to help me the best way to change the WEB.XML 
file

Thanks in Advanced

My Best Regards

Andre Lomonaco

Re: Stateful page feedback

[Andrei Ionescu <ai...@yahoo.com>]

>> Yes, I used stateful pages in most of my applications - and for some of
>> them even heavily (e.g. 1 moved from Tapestry and  1 from JSF).
>
> Hi,
>
> Can you provide us some examples on how you used stateful pages in your applications? What sort of
> use cases were you facing that you needed a stateful page instead of a stateless one?
It's not that "I needed" :), more that it was used in projects all over, 
possibly because of:

  - migration of apps from other stateful web frameworks.
  - rewriting of desktop apps to web. For this, "Click + stateful + JS 
libs" is close to Swing in many respects. Other find it even quite close 
to VB productivity levels if there were have some sort of GUI builder :).
  - "perceived simplicity" if everything is stateful. It takes lots of 
effort for average developers to get used to the HTTP stateless model, 
especially if they were doing desktop apps before.
  - business people (the mighty "domain specialists" :) ) who also 
"code" prototypes instead of just doing proper requirements and mockup 
screens. They can't get the stateless model, and Velocity as at the 
limit, but fortunately Click has both - yet :).

So to cut a long story short, our main use case is for intranet apps, 
with known and limited number of users. It is not a problem to force the 
latest browser version or the use of only one window per app, to have 
that MDI l&f that users like in desktop apps.

regards,
Andrei.

Re: Stateful page feedback

[Bob Schellink <sa...@gmail.com>]

On 20/07/2010 01:44, Andrei Ionescu wrote:
> Yes, I used stateful pages in most of my applications - and for some of
> them even heavily (e.g. 1 moved from Tapestry and  1 from JSF).

Hi,

Can you provide us some examples on how you used stateful pages in your applications? What sort of
use cases were you facing that you needed a stateful page instead of a stateless one?

Kind regards

Bob

Re: Stateful page feedback

[Andrei Ionescu <ai...@yahoo.com>]

> I'd like to gauge some feedback on how many folk uses stateful pages and how they are used. Also how
> difficult do you think it will be to convert the stateful page to a stateless page?
Yes, I used stateful pages in most of my applications - and for some of 
them even heavily (e.g. 1 moved from Tapestry and  1 from JSF).

The Click functionality for stateful isn't perfect (would love if all 
components would work properly), it could be further improved, but so 
far it was very helpful.

I think it would be quite difficult to convert existing applications :(, 
and for some of them simply impossible (e.g. for projects where I left, 
but the customer is upgrading to newer click versions and does small 
improvements - but not such a big conversion).

As Jahid, I would also prefer an external project too that would still 
keep (or even improve) this functionality for Click applications.

regards,
Andrei.

Re: Stateful page feedback

[Andrei <gm...@gmail.com>]

This sounds good

On Mon, Jul 19, 2010 at 2:51 AM, Bob Schellink <sa...@gmail.com> wrote:
> Hi all,
>
> I've recently worked on a project that made use of stateful pages and have come to the conclusion
> that they lead to very hard to maintain applications. In addition not all controls and services work
> properly with with stateful pages.
>
> In hindsight I believe we made a mistake adding support for stateful pages and would like to rectify
> the situation by dropping support in a future release. Instead of stateful pages I think a better
> approach would have been to add state support to individual controls such as Table, TabbedPanel etc.
>
> I'd like to gauge some feedback on how many folk uses stateful pages and how they are used. Also how
> difficult do you think it will be to convert the stateful page to a stateless page?
>
> Kind regards
>
> Bob
>

Re: Stateful page feedback

[WarnerJan Veldhuis <wa...@qprcostcontrol.com>]

Hey Bob,

I have never used stateful pages, so I can't really comment on them 
being useful or not. I do think however that creating and maintaining 
state is not too hard to write yourself, and that having stateful 
components is a good alternative.

Cheers,

WarnerJan


-------- Original Message  --------
Subject: Stateful page feedback
From: Bob Schellink <sa...@gmail.com>
To: user@click.apache.org
Date: 07/19/2010 09:51 AM
> Hi all,
>
> I've recently worked on a project that made use of stateful pages and have come to the conclusion
> that they lead to very hard to maintain applications. In addition not all controls and services work
> properly with with stateful pages.
>
> In hindsight I believe we made a mistake adding support for stateful pages and would like to rectify
> the situation by dropping support in a future release. Instead of stateful pages I think a better
> approach would have been to add state support to individual controls such as Table, TabbedPanel etc.
>
> I'd like to gauge some feedback on how many folk uses stateful pages and how they are used. Also how
> difficult do you think it will be to convert the stateful page to a stateless page?
>
> Kind regards
>
> Bob
>