Rename this package to Wpf.Forms?

[flyingxu]

I checked the package a little bit and found that the main purpose of it is to make Xamarin.Froms' WPF backend development easier. (of course others can also use this package).

On the market, there is already another wpf packages named wpf toolkit , which was popular some time ago.

To advertise Xamarin.Forms' WPF backend a little bit more, it will make more sense if this package is renamed to Wpf.Forms or something alike. It will also reduce the confusion that Xamarin.Forms.Wpf introduced a foreign 3rd package.

[mohachouch]

It's a very good idea.

I like Wpf.Forms, I will think about other possible name.

@davidortinau @jsuarezruiz What do you think?

[davidortinau]

If we use Forms without Xamarin in the name, WPF developers will likely conclude this is doing something with WinForms. 😆

Consider a XF or Xam prefix. You'll need to be careful not to use Xamarin.Forms in the name so it doesn't conflict now or later with our packages. We ran into a conflict last week related to this on NuGet.org.

I haven't looked at what all this kit does. Would it make sense to roll this work into the XamarinCommunityToolkit?

[mohachouch]

@davidortinau This library is inspired by Xamarin Forms but is really specific to WPF.

The problem of the WPF is that it lacks a large number of pages / functionnality to be identical to UWP. That's why I created WpfLightToolkit. WpfLightToolkit is a simple and light toolkit.

This library implements different pages (TabbedPage, MasterDetailPage etc.) for WPF.

For the name, I will think if you have any ideas do not hesitate.

[jsuarezruiz]

It is a good idea to make it easier to know that this Toolkit create in WPF some nice Controls in addition to being used in the Xamarin.Forms WPF backend. However, I'm with David. With that name I would be worried that it would confuse developers that has relation with Windows Forms, just the creation of forms, etc. Or even that this package was to work with Xamarin.Forms and WPF directly.
I'm not sure what would be the best name in this case, but something like WPF.XF.Toolkit, etc.

[flyingxu]

I'm open to any name but I'd like to explain a little bit why Wpf.Forms will not be an issue. When Xamarin decided to use the name of Xamarin.Forms, I assume they had already considered thoroughly the possibility to be confused with WinForms. Although I don't know their thoughts, I think we can just follow.