On Jan 22, 8:31 pm, Bryan wrote:
> Hi Marius,
>
> I would like the conversations contained within each tab. If I were
> to use just a Session variable then the user's state/data would
> "collide" and therefore cause unexpected behavior.
It would not if you use different SessionVar for each "c
Bryan,
On Thu, Jan 22, 2009 at 10:54 AM, Bryan wrote:
>
> That type of Wizard would be nice, though I am not a big fan of XML.
There will be no XML in Lift. All Lift code is in Scala. Java did not
allow for DSL creation, so in SmartMode we used XML. Scala allows for very
flexible DSL creati
That type of Wizard would be nice, though I am not a big fan of XML.
Thank you for your willingness to come up with a solution, but I don't
have a specific need for it right now. There is a project I may be
working on in the future that is similar to the hotel website featured
in that document I
Bryan,
There's no much in Lift to support what you're looking to do.
For 1.1, there will be something like SmartMode Wizard (see
https://www.lostlake.org/wizard.wmv )
If you can tell us something about your application, requirements, use
cases, whatever, we'll work to tailor a solution for you.
Hi Marius,
I would like the conversations contained within each tab. If I were
to use just a Session variable then the user's state/data would
"collide" and therefore cause unexpected behavior.
This link does a better job of describing how conversations solve this
problem:
http://www.informit
The conversation context could be kept in a SessionVar. When your
context terminates (say user clicked a button). You can attach a
cleanUp function to the SessionVar (see registerCleanupFunc) so when
your context terminates you can just call remove() on your SessionVar
Would that help or I'm jus
