Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

👩‍💻📞 WinUI Community Call #2 (November 27) #1651

Closed
jesbis opened this issue Nov 21, 2019 · 40 comments
Closed

👩‍💻📞 WinUI Community Call #2 (November 27) #1651

jesbis opened this issue Nov 21, 2019 · 40 comments
Assignees
@jesbis
Labels
community-call discussion General discussion

Comments

@jesbis
Copy link
Member

jesbis commented Nov 21, 2019 •
edited

Update:

Thanks everyone!

The call recording is available here:
https://1drv.ms/v/s!AiwORAw49JWcgfshJXoU3UvhWjZjeg?e=ulfPcY

We'll hopefully have a better streaming setup in the new year.
There's also a .vtt captions file available in the same folder.

Hi all -

The November WinUI Community Call will be next week!

We had a great time with the first community call last month and really appreciated the interest from everyone who sent questions, called in, live-tweeted or even wrote articles while the call was still going, and watched the recording!

I'd also like to thank everyone who took the survey so far, which we're using to plan some improvements to the format, content and streaming setup - we can talk more about that during the call next week.

Details

Date: Wednesday November 27
Time: 17:00-18:00 UTC (9:00-10:00am Pacific)

Teams link to call in:

Join Microsoft Teams Meeting
+1 425-616-0754 United States, Seattle (Toll)
Conference ID: 281 065 415#
Local numbers | Learn more about Teams

Anyone and everyone is welcome - no pre-registration is required.
This will be an informal online call directly with members of our engineering team.

Please leave questions/topics/feedback!

We'd like to spend part of the time answering your questions again, so please leave comments about any questions or topics you'd like us to cover next week!

If you've tried out the WinUI 3 Alpha then we'd also love to talk about any feedback you might have so far.

Agenda for next week's call

  1. WinUI 2.3 release
  2. WinUI 3.0 Alpha update
  3. New feature discussions / demos
  4. Q&A - we'll answer your questions from this issue (leave a comment!) and live from the Teams chat
  5. Updates on how we'll be improving streaming and recording based on your feedback from call #1 last month

This will be the last community call for 2019 but we'll be back (and better) in January!
@jesbis jesbis added hot discussion General discussion labels Nov 21, 2019
@jesbis jesbis self-assigned this Nov 21, 2019
@msft-github-bot msft-github-bot added the needs-triage Issue needs to be triaged by the area owners label Nov 21, 2019
@jesbis jesbis pinned this issue Nov 21, 2019
@salmanmkc
Copy link
Contributor

Am I the only one who has been getting calendar notifications like 15 days in advance? (from the last calendar invite)

@kmgallahan
Copy link
Contributor

kmgallahan commented Nov 21, 2019 •
edited

I'm not sure if the call should be used in this way, but can we advocate for support of other MS projects that are related to WinUI and would provide value to the devs here?

In particular, VS App Center is currently building out a data sync system for Cosmos DB. However, they are only focused on Android and iOS developers right now, and UWP/.NET work doesn't appear to have even been started. ~At least it is listed as a stretch goal...

Related issues that could use upvotes and feedback:

@jesbis
Copy link
Member Author

jesbis commented Nov 21, 2019

@salmanmkc as far as I know the previous .ics invite didn't have a default reminder set - does your calendar app let you change it? The recurring .ics didn't work very well for some people so we're likely going to take a different approach in the future - we'll briefly talk more about that next week.

@kmgallahan I think that's a great type of topic to discuss and raise awareness about!
Also cc @LyalinDotCom, @LucasHaines FYI RE: App Center

@jevansaks jevansaks added hot and removed hot needs-triage Issue needs to be triaged by the area owners labels Nov 21, 2019
@kmgallahan
Copy link
Contributor

@kikisaints

Maybe you could release the latest version of the Fluent XAML Theme Editor during/for the call (as seen in this MS Ignite session @27:15). Not sure if that code is already in the repo and just needs to be released to the Store or something else.

Could also ask aloud for thoughts regarding the ColorPicker bug.

@mdtauk
Copy link
Contributor

mdtauk commented Nov 21, 2019

@kikisaints

Maybe you could release the latest version of the Fluent XAML Theme Editor during/for the call (as seen in this MS Ignite session @27:15). Not sure if that code is already in the repo and just needs to be released to the Store or something else.

Could also ask aloud for thoughts regarding the ColorPicker bug.

There is a branch for the updated editor, but its not yet complete, as it has no font options right now, but it does have the corner radius properties.

image

image

image

@kmgallahan
Copy link
Contributor

kmgallahan commented Nov 21, 2019 •
edited

@jesbis

I don't know if it would necessarily have a net positive impact, but the audience would probably increase in size if the call were mentioned on the Windows Developer blog.

@jesbis
Copy link
Member Author

jesbis commented Nov 21, 2019

I don't know if it would necessarily have a net positive impact, but the audience would probably increase in size if the call were mentioned on the Windows Developer blog.

Definitely agree and we'll be doing that starting in the new year!

@shaheedmalik
Copy link

Is the replay for this up? I missed it.

@jesbis
Copy link
Member Author

jesbis commented Nov 22, 2019

@shaheedmalik the recording from October is posted here. The November call is next week - hope you can make it!

@shaheedmalik
Copy link

Don't mind me, I am an idiot. I thought call 2 was yesterday.

@marcelwgn
Copy link
Contributor

A few questions:

  • Will the project (structure) change a lot with WinUI 3.0?
  • How does Windows deal currently with changes in WinUI (e.g. the Settings app) and how will this change with WinUI 3.0?
  • Beside XCG, Fluent XAML Theme Editor and the Windows Community Toolkit Sample App, what are apps that you can recommend/develop for developers?

@salmanmkc
Copy link
Contributor

@salmanmkc as far as I know the previous .ics invite didn't have a default reminder set - does your calendar app let you change it? The recurring .ics didn't work very well for some people so we're likely going to take a different approach in the future - we'll briefly talk more about that next week.

@kmgallahan I think that's a great type of topic to discuss and raise awareness about!
Also cc @LyalinDotCom, @LucasHaines FYI RE: App Center

For some reason it had 24 days as the reminder time, so I've been getting a reminder every day since haha
image

@Felix-Dev Felix-Dev mentioned this issue Nov 25, 2019
Closed
@kmgallahan
Copy link
Contributor

This should probably be addressed:

https://blogs.windows.com/windowsdeveloper/2019/11/25/developing-for-the-new-category-of-dual-screen-devices-built-for-mobile-productivity/

  1. Embrace dual-screen experiences: introducing a common model
    The excitement for this new device category creates a great opportunity for developers to innovate and reach new customers – enabling them to be more productive and engaged while on-the-go. We are in the process of identifying key postures and layouts across dual-screen and foldable PCs so that you can take advantage of both.

For native app developers, our goal is to develop a common model layered onto existing platform-specific tools and frameworks for Windows and Android. Of course, APIs to access this model will be tailored to the developer platform for each operating system. For example, you can use APIs to enhance your apps to use dual-screen capabilities and features like the 360-degree hinge.

@mdtauk
Copy link
Contributor

mdtauk commented Nov 25, 2019

This should probably be addressed:

https://blogs.windows.com/windowsdeveloper/2019/11/25/developing-for-the-new-category-of-dual-screen-devices-built-for-mobile-productivity/

  1. Embrace dual-screen experiences: introducing a common model
    The excitement for this new device category creates a great opportunity for developers to innovate and reach new customers – enabling them to be more productive and engaged while on-the-go. We are in the process of identifying key postures and layouts across dual-screen and foldable PCs so that you can take advantage of both.

For native app developers, our goal is to develop a common model layered onto existing platform-specific tools and frameworks for Windows and Android. Of course, APIs to access this model will be tailored to the developer platform for each operating system. For example, you can use APIs to enhance your apps to use dual-screen capabilities and features like the 360-degree hinge.

While some value being able to deliver a UI that adapts to the target platform's UI - and others are happy to develop web apps - There is a group who want to develop one app, with one UI, that looks the same on all platforms.

Windows developers who bet on dotNET and investments in Windows Apps - could expand their audience if they can develop once, and run everywhere.

WinUI being extracted from Windows, could be the start of a Cross Platform UI platform.

@harvinders
Copy link

Some questions for the call @jesbis

  1. Can we expect monthly release cadence for the alpha/beta/preview releases?
  2. When does the controls developed in WinUI 2.x moves to WinUI 3 releases? Are only released controls going to be in WinUI previews or in preview controls in WinUI2.x can also be expected to be in WinUI 3 previews?
  3. Milestones, I understand the first priority is to open source WinUI 3. What comes next, any plans to share more details. When can we expect a WinUI preview with Win32 app model?

@riverar
Copy link
Contributor

riverar commented Nov 27, 2019 •
edited

Would like to hear how Win32/.NET apps can modernize with WinUI. We keep hearing it's the future but it's still not possible to align an app's look and feel with Windows 10. Microsoft does not provide guidance/resources for Win32 or .NET app alignment, and WinUI + XAML Islands is insufficient (for things like AcrylicHostBrush) due to airspace issues.

@atrauzzi
Copy link

atrauzzi commented Nov 27, 2019 •
edited

I'd like to know if there is active work to ensure that all of this can be leveraged from react-native-windows.

*And if the documentation, paths for adoption and learning from react-native-windows will be fully detailed out.

@robloo
Copy link
Contributor

robloo commented Nov 27, 2019 •
edited

I will miss the call today; however, it would be nice to know how WinUI 3.0 is going to get migrated into the existing WinUI repository. Will controls just be pulled over one at a time like the ProgressBar?

NumberBox architecture for Value -> Text conversion seems like an issue in the V1 control. Developers need control of how the double value is converted to text and a good internal architecture would make that easy. I won't be on the call to defend my ideas though :)

#483 (comment)

@atrauzzi
Copy link

There a recording? :)

@riverar
Copy link
Contributor

riverar commented Nov 27, 2019

@atrauzzi Looks like Teams is saving it to file right now. Standby!

@patware
Copy link

patware commented Nov 27, 2019

Thanks again for this Community Call, great format and subject. Two "technical notes" about the call:

  1. The Microphone was picking up keyboard hits.
  2. The screen had a label "Calling..." in the middle.

image

@jesbis
Copy link
Member Author

jesbis commented Nov 27, 2019 •
edited

Thanks again everyone who could make it!

Also a big special thanks to @sonnemaf for joining us to talk about his NumberBox control proposal and walking us through an example of porting an app to run on the WinUI 3 Alpha!

The call recording is available here:
https://1drv.ms/v/s!AiwORAw49JWcgfshJXoU3UvhWjZjeg?e=ulfPcY

We'll hopefully have a better streaming setup in the new year.
There's also a .vtt captions file available in the same folder.

If we didn't get to your question then please feel free to ask it again in this thread, or open a new issue.

Some other links from the call:

@StefanKoell
Copy link

The call recording isn't working anymore: "The person sharing the video exceeded the sharing limits"

Can you provide this video as a download somewhere?

Thanks!

@jtorjo
Copy link

jtorjo commented Nov 28, 2019

Hi guys: just to understand - can anyone participate, do you need to fill anything ?
I would certainly like to participate in the next call if it's allowed.

@Felix-Dev
Copy link
Contributor

@jtorjo
image

You only need a MS Teams account. Nothing else required.

@shaheedmalik
Copy link

@jtorjo
image

You only need a MS Teams account. Nothing else required.

You don't even need a Teams account. Guess login via web.

@Felix-Dev
Copy link
Contributor

Indeed! Just checked it and you don't even need an account as Shaheed said.

@jtorjo
Copy link

jtorjo commented Nov 28, 2019

@Felix-Dev @shaheedmalik Thanks guys, that's what I wanted to know :)

@deanchalk
Copy link

The call recording isn't working anymore: "The person sharing the video exceeded the sharing limits"

Can you provide this video as a download somewhere?

Thanks!

me too - thanks

@riverar
Copy link
Contributor

riverar commented Nov 28, 2019

Here's a mirror for folks having trouble: https://www.youtube.com/watch?v=e4C3jAMpUX8

@mariorancic01
Copy link

mariorancic01 commented Dec 3, 2019 via email

@jesbis
Copy link
Member Author

jesbis commented Dec 5, 2019

@mariorancic01 we don't have many samples yet but you can find one in this Scroller test page that's part of one of our test apps. You can find more info on running the test app under the developer guide.

Another option that might be easier would be to clone the Xaml Controls Gallery repo:
https://github.com/microsoft/Xaml-Controls-Gallery/

Then just update the ItemsRepeaterPage.xaml examples to use Scroller instead of ScrollViewer.

@mariorancic01
Copy link

mariorancic01 commented Dec 6, 2019 via email

@RBrid
Copy link
Contributor

RBrid commented Dec 6, 2019

Hello @mariorancic01, thanks for trying out the new Scroller control!

Because the new Scroller and ScrollViewer controls are still in preview mode, you can only use them in a preview nuget package like 2.3.191127001-prerelease.

You can run the MUXControlsTestApp as a standalone app. You just need to compile and deploy the MUXControls.sln solution and that will install the MUXControlsTestApp test app on your machine. It has a bunch of test pages for the Scroller and ScrollViewer controls. Those controls are very likely going to be renamed shortly, just to let you know.

Mouse-wheel-based scrolling should just work by default. You can easily turn off mouse-wheel scrolling by setting the IgnoredInputKind property to InputKind.MouseWheel.
Note that I can think about one difference between the old ScrollViewer in Windows.UI.Xaml.dll and the new Scroller/ScrollViewer in the nuget regarding mouse-wheel scrolling: the mouse wheel does not let you scroll horizontally in the new controls. In the old control, when vertical scrolling is turned off, the mouse wheel scrolls horizontally.

Could you please elaborate on the problem with zooming? We have no known issue with it. Thanks.

Jevan or Jesse may provide more info about the 2.4 release timing.

@jesbis jesbis unpinned this issue Dec 9, 2019
@mariorancic01
Copy link

mariorancic01 commented Dec 9, 2019 via email

@RBrid
Copy link
Contributor

RBrid commented Dec 9, 2019

Thanks @mariorancic01, I am not sure what you meant with "But while I tried to zoom it i quickly lost it." and I don't have the zip file for the complete app, but I tried your XAML fragment and a modified version worked fine for me:

<muxPrimitives:Scroller
  Background="BlueViolet"
  HorizontalScrollRailingMode="Disabled"
  VerticalScrollRailingMode="Disabled"
  ZoomMode="Enabled"
  MinZoomFactor="0.01"
  MaxZoomFactor="10"

  Height="500" Width="500" ContentOrientation="Vertical">

  <muxControls:ItemsRepeater
    x:Name="repeater01"
    Height="55000"
    Margin="0,0,12,0"
    HorizontalAlignment="Stretch"
    Layout="{StaticResource UniformGridLayout2}"
    ItemTemplate="{StaticResource MyDataTemplateSelector}"/>
</muxPrimitives:Scroller>

I also added this line of code in the page constructor:
repeater01.ItemsSource = Enumerable.Range(0, 500);

Maybe that is what you meant to do.

@mariorancic01
Copy link

mariorancic01 commented Dec 9, 2019 via email

@mariorancic01
Copy link

mariorancic01 commented Dec 9, 2019 via email

@RBrid
Copy link
Contributor

RBrid commented Dec 10, 2019

@mariorancic01, some more comments below:

"Actually I didn't wanted to do this. My Scroller is only element inside
Grid and I wanted it to occupy whole width and height of the screen,"
No problem, you can do that as well.

"Also I wanted ItemsSouce to be at least 10000 elements so I can test better virtualization."
No problem with that either. I should work the same.

"By "lost it" I meant soon after pinch it with two fingers to zoom I just
saw BlueViolet background and I could not go back to the elements."
Maybe that was the result of using a large content height 55000 and MinZoomFactor="0.01" MaxZoomFactor="10". The scrollable area can get real big. It's always a good idea to print out the current HorizontalOffset, VerticalOffset, ZoomFactor, ViewportWidth, ViewportHeight, ScrollableWidth and ScrollableHeight properties of the Scroller to get an idea of what it is supposed to show. Also the ContentOrientation property may play a role in your observations. Thanks.

@mariorancic01
Copy link

mariorancic01 commented Dec 10, 2019 via email

@jesbis jesbis closed this as completed Jan 17, 2020
@krschau krschau removed the hot label Jul 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jesbis jesbis

Labels
community-call discussion General discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests