Deep Linking: How to?

[mcbl]

In http://docs.sencha.com/touch/2-0/#!/guide/apps_intro you speak about Deep Linking: "share deep links that open any screen in your app, just like linking to a web page"

Please tell me how to link different pages/panel/containers/views to let user navigate, in Architect 2.

(If you can't give a holistic universal example, take two panels: {xtype: 'panel'} and {xtype: 'form panel'})

[mcbl]

This question is important, it's about navigation!

Please take some time to answer.

[allisterf]

The documentation can leave you scratching your head a bit, for sure! I could try to put up 'simple' project example to follow tomorrow, if that would help?

Allister

[mcbl]

Oh yes, you're a sweet sympathetic programmer, it would be amazing!

Thanks in advance!

[allisterf]

Not getting to this. Maybe Aaron can knock something up?

Over to you Aaron.
Allister

[hotdp]

Deeplinking is not that hard.
The only thing you have to do is use routing in the correct way and thats it!

[CaliLuke]

Give us a few days, we are creating new examples to illustrate how to use this and other features but there's only so much we can do with our time... this will come soon.

Thanks.

[mcbl]

8 days after... and nothing.

Can you recheck it?

Is this still on the (private! =( /&%ç*&/=()) roadmap?

[CasualNetworks]

Is this what your looking for information on how to do? ("Select Linked Class") This allows you to deeply nest an instance, and then go to the direct parent class.

[allisterf]

"Select Linked Classes". It's probably part of it.

I think what people are really craving is some good examples that also have examples of the kind of code snippets that need to go into controllers to navigate around app components.

Sencha Architect a GREAT tool - let me get that on record. And it's a tool which has the potential to attract users who don't come from geeky coding background... but I think Sencha would convince many, many more people to give up $399 if there were more examples (done in explicitly Architect, not just giving out references the original sencha2 codebase), for people to examine and learn from. Architect is meant to be a visual tool - so we need visual clues and teaching, not just api references. I know many hard core coders are going to look down their noses at such ridiculous foolishness, but, frankly, Architect isn't being made for you: you already can do it all with the pure sencha framework. Architect, on the other hand, is a tool to intuitively pull it all together for us.

Still, it's early days with probably the hope that people will be willing to stick around to wait and see.

Again - it still get's my vote. Well done guys - but PLEASE, many, many more actual examples. Maybe you could create a repository that more advanced users could add to?

Allister