This content has been marked as final. Show 10 replies
Looks like a rehash of the help examples.
What I would like is people's experience with deep linking.
Does it work? Is it of real value? Or is it one of the aspects of Flex that might work in some circumstances, but is not ready for real-world wide-spread use.
I've also thought some about this. That is a good question - is it of real value.
It seems like deep linking's primary prupose is to send a link to someone else, or bookmark the "page" or view whatever you want to call it. To me the best way to do this is with query string parameters, just like a dynamically loaded html page.
On each View of your flex app, you could include a link that you build based on the content. Then let the user copy it. It doesn't need to show in the browser address bar, in my opinion. As long as the UI makes it apparent that the user needs to use whatever component you place on the screen in order to get a link, and not the address bar value.
Then in your app, just include code that looks for the parameters, and if they are there load up that view.
I like this because then the link work more like a regular web page. I haven't tried the Flex way of deep linking , but if I were involved in an app that required deep linking, I think what I've described here is how I would attempt it first.
I just posted an answer regarding this topic:
Deep Linking is quite challenging to implement, IMO, but the results are worth it. I did it recently in an app and the result is waaaay cooool. You're right, Adobe could provide better examples, though.
That was what I suspected, that is it cool, but hard at the moment. Thanks for your contribution to understanding this.
If it's useful to anyone, I've attached code which should get you up and running with Deep Linking. I copied it out of my application and made edits to generalize it, so hopefully it makes sense and is not too specific to my app.
Put these functions into an ActionScript class, add that to your main app, and you're ready to try it out.
It has a function to place the state, a view stack index and a page title in the address bar as a URL Fragment. Site visitors can bookmark at this point. Then there is a function to read that back into the app when the visitor returns, where you can use it to set restore the sate Flex was in by setting the state, viewstack index and the page title.
Great code and resources. Thanks very much.
"John Hall" <email@example.com> wrote in message
> Hi Greg. If you haven't already, you might want to read Theo's blog
I love that blog...it always twists my outlook on Flex :-)
I used to think the same thing about deep linking, until I read the last chapter of "programming flex 3" which shows a real world example of how to implement it in an application, as a design pattern, it makes a lot of since the way they described it. Instead of objectA telling objectB to do something, objectB listens for the URL change, and objectA changes it.