To be fair, it's more than "a bit more work"... and I'm pretty sure we could get readable URLs out of the HistoryManager without a terrible amount of effort. Anyway, readable URLs aren't exactly a priority for us. Were there defects in the HistoryManager that Adobe didn't want to invest in fixing?
What about loadState and saveState? Those methods strike me as a little bit of genius. Is IHistoryManagerClient deprecated along with HistoryManager? --- In [email protected], Alex Harui <aha...@...> wrote: > > We want everyone to use the BrowserManager. It is a bit more work to setup, > but your customers will be happier because the URLs will be more readable. > > > On 8/18/10 10:58 AM, "t0ml33" <des...@...> wrote: > > > > > > > I've seen a post here on Flexcoders where Alex Harui has stated that "history > manager is more or less deprecated". I was wondering if anyone could shed > some light on why that is? I'd like to use it in my projects - it has some > handy features - but if it's going away, I'd have to write my own. > > In particular, I think that the loadState and saveState methods in > IHistoryManagerClient are useful - are these going away too? I really like > the idea of having these methods automatically called to load the state for a > view when the correct url is entered in the browser. > > > > > > > -- > Alex Harui > Flex SDK Team > Adobe System, Inc. > http://blogs.adobe.com/aharui >
