Bug 28526 - need a mechanism to embed pages
Summary: need a mechanism to embed pages
Status: RESOLVED FEATURE
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.1
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-03-29 16:56 UTC by George Cook
Modified: 2015-06-24 06:14 UTC (History)
7 users (show)

Tags: docs
Is this bug a regression?: ---
Last known good build:


Attachments
example of my nested navigation page, hacked together to work in forms (7.66 MB, application/zip)
2015-03-29 16:56 UTC, George Cook
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FEATURE

Description George Cook 2015-03-29 16:56:09 UTC
Created attachment 10547 [details]
example of my nested navigation page, hacked together to work in forms

We can't be limited to the content pages that coem with forms, and there is no documentation on how to make other custom ones, beyond the clipped image example on the xamarin forms, which doesn't really cover embedded pages.

This is known as "view controller containment" on iOS, and I believe that on android is just multiple activities, which is to say, it's an entirely common pattern that we would need to be able to create apps, in which we can choose which pages to display in the way we want, with our own gestures and chrome.

We need more examples on how to do this, better documentation, and even better of all, would be a view which we could drop into any other page, which we can set a view controller on.

this is a very common pattern I use in all my iOS apps, making the creation of highly custom navigation systems very trivial.

I think it's a huge oversight on Xamarin's behalf, and should be rectified asap, if you want to see the kind of high quality apps created with the framework which are only possible with more flexibility.

I've added an example of my own system I use
Comment 1 Parmendra Kumar 2015-03-30 11:45:45 UTC
I have checked this issue with attached sample and observed that the Back button is not working fine.

Screencast: http://www.screencast.com/t/yC533XWXb5

The other issue related the same : https://bugzilla.xamarin.com/show_bug.cgi?id=28525
Comment 2 George Cook 2015-03-30 11:50:47 UTC
this is not a duplicate.
the other issue is about the back button not working.

This issue is a FEATURE REQUEST, to allow us to easily embed pages inside pages.

The code example is only to show you the kind of feature we need. Please ignore the back button on this issue - I wanted you guys to see how I could do something like htis.

MyPageSubclass
--ChildPage1
--SomeChromeViews

To create custom navigation.
Comment 3 Jason Smith [MSFT] 2015-05-19 13:51:28 UTC
Thank you for your feature request, we have taken it into consideration.