-
-
Notifications
You must be signed in to change notification settings - Fork 122
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.
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
Update to XF 3.5 #350
Update to XF 3.5 #350
Conversation
Yes, if we can reuse the existing classes, we do. |
I didn't had time to check XF 3.5 in details. In the case of XXXCollection, Fabulous will expose a |
Great! Thanks for your feedback :)! |
I think i got everything... |
@SergejDK Do you know why CollectionView/CarouselView/Shell are in XF 3.5? |
They are already in 3.5 but only allowed to use when setting: global::Xamarin.Forms.Forms.SetFlags("Shell_Experimental"); https://docs.microsoft.com/de-de/xamarin/xamarin-forms/app-fundamentals/shell?tabs=android The question why it is in 3.5 I think because of earlier feedback from the devs.
https://blog.xamarin.com/5-things-youll-love-xamarin-forms-3-5/ |
@TimLariviere the fail on travis - is it the error where it only needs to rerun? |
Seems like it. |
@TimLariviere |
Apparently they changed their targeting framework with Xamarin.Forms 3.5. So the links in both the samples app and the templates are no longer valid. For example: <Reference Include="Xamarin.Forms.Core">
<HintPath>..\packages/Xamarin.Forms.XamarinFormsSdk/lib/MonoAndroid10/Xamarin.Forms.Core.dll</HintPath>
</Reference> will become <Reference Include="Xamarin.Forms.Core">
<HintPath>..\packages/Xamarin.Forms.XamarinFormsSdk/lib/MonoAndroid90/Xamarin.Forms.Core.dll</HintPath>
</Reference> |
Thanks for looking into it! Could not do it when I was at work... |
Could you add an example of how to use the new controls in the AllControls samples? |
Would it not be better to have a project for shell and not include it in AllControls? And with the Shell it mabye easier to work on: #242 |
I think we should still add the new controls to AllControls, it's more a smoke test than a sample anymore. That way, we can check the new controls are working and we don't break them later. Though indeed, Shell would be easier to use in a new project and provides a good structure for new samples. |
I will add simple parts in the allcontrols. |
Thanks! |
Because Shell seems to be only available on Android and iOS I have to ask for the platform. This is just a note that you won't be suprised about the addition to ask for android and ios. |
@TimLariviere FormsAppCompatActivity.TabLayoutResource <- TicTacToe.Droid.Resources.Layout.Tabbar
FormsAppCompatActivity.ToolbarResource <- TicTacToe.Droid.Resources.Layout.Toolbar Else it should give an error. If I am correct then there is only CarouselView/CollectionView to make examples in allcontrols? Last thing: I am still trying to figure out what is wrong with the items updateCode. If you have any hint I would appreciate it!! |
Yes, I think you're right.
Yes, there seems to be only 3 new controls: Shell, CarouselView and CollectionView. |
Added examples for carousel and collectionview but I think there is something wrong. |
@SergejDK The You need to do something like the
That way, when you add a |
@TimLariviere great explanation! Thanks! As far as I see I can nearly copy everything except changing some names and inherited classes. Am I right? |
Yes, it should mostly work as-is. |
It seems like everythign can be used. So maybe inherit from view directly? The difference to ListView is that listview uses |
@SergejDK You can inherit from ContentView and append the ViewElement's control to the |
Seems to work but it does not display anything. It gets created correctly though... |
The Labels seems to be created but not shown in the ui: Is there still sth. wrong within |
Got time again.
|
@TimLariviere will test for android part. |
@TimLariviere So maybe it is okay to merge here even though the examples for the 3 parts are currently not working. For those example we can open each issue and work on the updates so we can catch up there and afterwards test the examples again. What do you think? |
@SergejDK Alright. I'll add a note for these controls in the docs saying that while we provide an initial support, there may be some issues with them. |
@TimLariviere |
@TimLariviere |
@SergejDK Thank you for your work in this long running PR. :) This evening I'll be releasing this in a new version on NuGet. |
@TimLariviere what do you think about making the step to 3.6 ? Maybe I can make it before evening and you could release it with 3.6? |
That would be awesome! |
The following list shows which are missing right now. Will work on this the next days.
The questionmark behind few classes there I do not know if they are needed.
Interfaces, enums, abstract classes and static classes are not included.
I think that the Attributes and EventArgs do not need to be included, too ???
@TimLariviere could you maybe provide me with some hints for the classes below and the question above? I appreciate your help!
ScrolledToRequest
ScrollTo
ItemsSource
ItemTemplate
OnClearPlaceholderClicked
OnItemSelected
OnQueryChanged
OnQueryConfirmed
GoToAsync
fix #329
Differences:
https://www.fuget.org/packages/Xamarin.Forms/3.5.0.129452/lib/netstandard2.0/diff/3.4.0.1009999/