<snip> > > Craig Wrote: > > > > My current thinking is that we want the ability to have more than one > > > > active dialog, so you can "push" from one dialog to another, then > > > > "pop" back out. That's why I made it the dialog's responsibility to > > > > clean itself up. > > > > > > > > I don't like the fact that the dialog has to know the attribute name > > > > it is stored under (in session scope), but haven't figured out a way > > > > around it yet. > > > > > > > > > > > > Craig </snip>
In my experience, this sort of program, app, or whatever you want to call it, is better stored in application scope. That way there are no limits to the algorithms you can foster. Jack -- ------------------------------ "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ ----------------------------------------------- "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
