I would like to have the ability to embed one screen into another. For example:
Home Screen might be:
The advantage of doing things this way is that I would be able to link to Screen A or Screen B from other places in the app apart from their presence in the Home Screen.
Não sei se entendi sua pergunta, mas acredito que sim. Divida sua tela inicial em quantas partes desejar, em cada parte coloque uma imagem que tenha link para outra tela correspondente ao interesse. Resumindo, use imagens!
The problem with taking snapshots of screens is that the contents of the screens are dynamic and a snapshot won’t solve what I want to do. The closest thing to this is to include an inline list component in page. The problem with just including an inline list is that none of the header and trailer components of the complete screen are included in the inline list component.
What header and trailer components do you mean? The details screen with multiple inline lists sounds like what you’d need.
Exato, primeiramente terá que usar a tela de detalhes. Depois poderá utilizar listas ou diversas imagens direcionadas as telas correspondentes.
Yes, now I understand. The only problem with inline lists is that you cannot toggle between list view and map view, and my walking tour app is more dependent on this capability than most apps.
Thank you for your advice. I am now headed in the right direction.
Regards,
– Harry
Pedro,
Thanks for your help. I am somewhat new to Glide and although a programmer for a long time, I have found it a bit difficult to understand the model of data and presentation templates supported by Glide, but I am mastering it slowly but surely.
Regards,
– Harry
P.S. I am thrilled that with the help of Google, I can now converse with someone who writes to me in Portuguese! – HF
That 2nd point is exactly what I set up for someone else ---- a choice component above the lists to filter two inline lists (one map view only, one list view only). The appearance of the choices above was more intuitive too and worked out really well.
Jeff,
First, did you forget to include the example after the ending : in this message? I’d like to see your example. Imitation is the sincerest form of flattery…
I would still like to defend my idea for a way to embed one screen in another. It is really nice to be able to build up structures so that you don’t have to repeat pieces of a template when you want to use the same combination of components in two places. For example, in my app (https://lexbyfandp.glideapp.io/) I wanted to include the list of available tours in both the home page as well as separately in a tab of its own. On the home tab, it can be included inline without having to go to another screen/tab. In its own tab, it can always be separably accessed to see what other tours are available without having to go through introductory information about the entire app. Since this could be a multicomponent object, there is a need for this – think of it a component which is like an inline-list, only it could be a list of components along with formatting from a template.
What do you think?
– Harry
No, didn’t forget the link. 
If you open the thread I shared in my post, it will open the entire post with the app link in the other thread where I had replied to you in one of your other posts.