-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Conversation
Not everything in the gallery sample app works. List below screenshot of progress so far. If you want to help out, I'd like help with the below unchecked items. Checked = it is working, message after with issue if it's not
|
Really glad to see that someone is making the effort to support to UWP, and I am sure many others are as well. Just wondering if there is any sense of when this would make it into a preview/release? |
We're hoping to do a live-streamed code-review next week |
Any updates? Really at a WAIT AND SEE attitude with Xamarin Forms until there is equal ground development footing for Windows platforms (UWP) alongside XF iOS and XF Android. |
When can this project update this feature to the visual studio template? |
@dgerding sorry we're a little delayed. I'm overwhelmed and hard to find common time do the PR Review. |
Hey guys! Wondering what the status of this is. |
Is there any ETA for Shell in UWP? |
I'm sorry this haven't moved faster. I hit some regressions when syncing up with master, and I've been completely swamped with work and family-related stuff, so just haven't had much time to really sit down and try and address it. However I'm more than happy to take PRs for my branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh! My dirty laundry!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of small changes, it works fine locally.
Hi All, Thanks again for all the hard work. |
@dgerding just follow the steps here https://docs.microsoft.com/en-us/xamarin/xamarin-forms/platform/windows/installation/ to add a UWP project We'll have the UWP project as part of the VS templates at some point in the nearish future |
Thanks @PureWeen |
I have a new VS2019 16.3 Xamarin Forms solution using the standard project template and have added a UWP project. Thanks to help from @PureWeen I've got it running. I know UWP support is going to take time and wasn't sure where the right place to report a likely bug. Short version: The "Add" button in the upper right corner of the Items page in the stock project isn't showing up in UWP... but it does for the Android project. (Can't test iOS yet without a new build machine. ) I'll poke at it a bit more. Any guidance on reporting this in right place appreciated. |
@dgerding If you could log a new issue here https://github.com/xamarin/Xamarin.Forms/issues/new/choose with a sample that would awesome!! We merged the larger body of work so that we can start breaking out the work to be done into smaller issues that we and the community can collectively address. Just log everything you find that you think is incorrect. |
Posted a bug report here, #7735, but for those interested, there is a zipped solution attached to that report that anyone can use as a temporary quick start for Xamarin Forms + Shell +UWP. |
* Some basics to get started * more renderers * Fix titlebar color * More shell stuff working * Hacked some more UI in * Fix null ref issue * Move renderer registration outside common code (for now) * Re-write of the renderers to better use a cleaner UWP approach * Moved functionality around, bug fixesetc * Added null check * Added null-check on appearance and use default colors as fallback * Handle change in flyout behavior to correctly turn the flyout on/off * Handle the TabBarIsVisible property * code formatting * Ensure FlyoutHeader isn't show if the app starts up with a minimal pane * Throw if used on versions lower than Windows 10 1809 * Added null-check for when ShellContent isn't set * Support tabs in FlyoutItems with Display AsMultipleItems by using the generated FlyoutGroupings instead * Improve pane behavior and styling * Undo Android change used during testing * Fix platform support check * Use FileImageSourcePathConverter on NavigationViewItem instead of a custom control (so I deleted ShellNavigationViewItemRenderer which is no longer needed). Ensure `FileImageSourcePathConverter` won't throw if it didn't get a FileImageSource. Move the flyout data templates into a resource so they can be overridden and compiled. * Delete renamed file * Use a resource instead of parsing a string template * Handle search box property changes * Update page title on property change * Update bottombar when shellitems change * Guard against API usage not present * Platform check comments * Fix problem running in release mode (use Bindable to generate XamlMetadata * Trigger rebind of menu items source when collection changes * Added support for Toolbar * Fix searchbox behavior (still lacks expand/collapse feature) * Add overload for defining the navigation transition * Use different navigation transitions based on navigatin direction * Hides header with show / hide nav command * collapses header area on hide nav * Move to use WinUI * Fix runtime issues after merge. * - rebase fixes * - rebase fixes * - fix spaces/tabs * - flags, hide apis, delete assembly info * - set flag on UWP CG * - expose renderer creations and make them all public * - formatting fixes * - address PR comments * - fix header so it's full width and swappable
* Some basics to get started * more renderers * Fix titlebar color * More shell stuff working * Hacked some more UI in * Fix null ref issue * Move renderer registration outside common code (for now) * Re-write of the renderers to better use a cleaner UWP approach * Moved functionality around, bug fixesetc * Added null check * Added null-check on appearance and use default colors as fallback * Handle change in flyout behavior to correctly turn the flyout on/off * Handle the TabBarIsVisible property * code formatting * Ensure FlyoutHeader isn't show if the app starts up with a minimal pane * Throw if used on versions lower than Windows 10 1809 * Added null-check for when ShellContent isn't set * Support tabs in FlyoutItems with Display AsMultipleItems by using the generated FlyoutGroupings instead * Improve pane behavior and styling * Undo Android change used during testing * Fix platform support check * Use FileImageSourcePathConverter on NavigationViewItem instead of a custom control (so I deleted ShellNavigationViewItemRenderer which is no longer needed). Ensure `FileImageSourcePathConverter` won't throw if it didn't get a FileImageSource. Move the flyout data templates into a resource so they can be overridden and compiled. * Delete renamed file * Use a resource instead of parsing a string template * Handle search box property changes * Update page title on property change * Update bottombar when shellitems change * Guard against API usage not present * Platform check comments * Fix problem running in release mode (use Bindable to generate XamlMetadata * Trigger rebind of menu items source when collection changes * Added support for Toolbar * Fix searchbox behavior (still lacks expand/collapse feature) * Add overload for defining the navigation transition * Use different navigation transitions based on navigatin direction * Hides header with show / hide nav command * collapses header area on hide nav * Move to use WinUI * Fix runtime issues after merge. * - rebase fixes * - rebase fixes * - fix spaces/tabs * - flags, hide apis, delete assembly info * - set flag on UWP CG * - expose renderer creations and make them all public * - formatting fixes * - address PR comments * - fix header so it's full width and swappable
@edamreed it's still experimental on the UWP side (hence the flag) We've merged this larger PR in so that we can start addressing the smaller issues more aggressively with more PRs :-) So if you could log your issue then we can put it out there for someone (or us) to resolve and get merged in |
Thanks PureWeen, are the details I entered above enough to log a issue with? |
Thanks |
Any advance? |
This is a replacement PR of #5936 (I messed up the rebase). There's some good discussions in that PR though.
Description of Change
This is the first stab at adding UWP renderers for Shell
Issues Resolved
#2415
API Changes
Known issues while it's a draft-PR:
3. Release builds fail to render the side pane (this one got me stumped, as no errors are reported - it's just completely missing anything but the contents from the visual tree)4. Toolbar not implementedIt might be worth considering adding the WinUI dependency. This would mean 16299 can be continued to be used, but it does require one extra setup step to add a theme resource to App.xaml, as well as adding the dependency. In the future though, this library is where all new UWP components will be added, so sooner or later that's going to happen anyway.
Platforms Affected
Behavioral/Visual Changes
None
Before/After Screenshots
Before:
After (Gastropods, Default Shell Template, Xappy):
Note:
Testing Procedure
Use @davidortinau's Gastropods sample. It seems fully functional from what I can tell.
You can also use this repo: https://github.com/dotMorten/Xamarin.Forms.UWPShell.Sample
(the sub-module points to this PR) which includes 3 different Shell samples, as well as the gallery sample.
PR Checklist