flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Altomare <lost...@gmail.com>
Subject Re: Flex Portal considerations
Date Wed, 25 Jan 2012 16:32:27 GMT
It seems like this may be pretty well handled in Flex Mobile with View
states. Flex gives you some options for how to cash the current view state
as well as to write anything you need to a SharedObject.

I'm not sure how much of this is handled by the OS but in my experience it
has worked pretty well

On Wed, Jan 25, 2012 at 11:26 AM, Alex Harui <aharui@adobe.com> wrote:

> On 1/25/12 8:14 AM, "Nick Collins" <ndcollins@gmail.com> wrote:
> >
> > One of the major issues is that of persisting the state of the Flex
> > application. In a portal environment, one of the core concepts is the
> idea
> > of being able to bounce around between pages and having your portlets
> hold
> > their state so that when you go back to them, you can pick up right where
> > you left off. With a large Flex application, this is nay to impossible.
> > Sure there are all kinds of tricks you can do with LSO's, deep-linking,
> > etc. to simulate it, but I would like to see some of the more enterprise
> > focused functionality like this be brought into the framework, or at
> least
> > taken into consideration so that it is not quite so cumbersome.
> > Unfortunately, I also realize that in order to accomplish this in the
> most
> > elegant manner, we would likely need changes to the runtime itself. :-(
> How is this done in the HTML/JS/CSS stack?
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui

Francis Altomare,

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message