Cheesebaron.MvxPlugins-master/Samples/FormsPresenters Upgrade or Fork VS2015RC about cheesebaron.mvxplugins

[Cheesebaron]

Fork and pull. I will merge it into another branch. Although I don't have VS2015 nor in the preview, so I won't be able to build it and create a nuget of the new stuff, maybe you can help here?

[PeterBurke]

Yes

I will work on it and keep in touch.

Best

Peter Burke

From: Tomasz Cielecki [mailto:[email protected]]
Sent: Tuesday, 9 June 2015 5:47 PM
To: Cheesebaron/Cheesebaron.MvxPlugins
Cc: peter j c. burke
Subject: Re: [Cheesebaron.MvxPlugins] Cheesebaron.MvxPlugins-master/Samples/FormsPresenters Upgrade or Fork VS2015RC (#51)

Fork and pull. I will merge it into another branch. Although I don't have VS2015 nor in the preview, so I won't be able to build it and create a nuget of the new stuff, maybe you can help here?

Reply to this email directly or view it on GitHubhttps://github.com//issues/51#issuecomment-110263124.

[PeterBurke]

Hi Tomaz

I have forked MvxPlugins and I have done an extensive analysis. I am in the process of pushing relatively minor changes up to the Fork as well as Pulling any of your changes, none so far.

Actually it seems that the changes I am making, primarily a change in PCL profile, will not break anything for people still on VS2013. I have put a lot of work into an MD file documenting the pull request that I will send to you, it explains what is happening in VS 2015 and why the changes are necessary.

In relation to the NuSpec I have determined something else that will require a different NuSpec for what I am trying to achieve.

Back in March I started with a zip clone of the entire MvxPlugins and what I wanted was MvvMCross working with Xamarin Forms that uses XAML rather than c# to define forms. I have been working with XAML for years and as far as I am concerned it is a big productivity boost once you get the hang of it. It is even better if you can also use Blend, but alas Xamarin XAML is not quite the same. They say the problem can be overcome with a different schema in Blend.

As an aside you should be aware that Microsoft released their "Universal App" spec a year or so back. The press is implying that it is for Windows 10, but it has been around long enough for it to already be on your machine running VS 2013. The XAML provides a way where you can target a wide range screen sizes and tell the layout engine to reposition elements say either underneath or to the right depending on the size of the screen. In HTML Css3.0 has a similar concept known as media queries. So as part of the VS 2015 RC, MS and Xamarin got together to add a new target that we should now support. This target is the Universal App, it will run on Windows 8 and also Windows Phone 8.1 without using Silverlight. Xamarin XAML support for UAP is rather patchy, but Xamarin are releasing another round of improvements next week. I will attempt to write a FormsPresenter and a Sample for this target in due course. Again it should still be possible to compile and test this new target from VS 2013.

OK so now for the NuSpec. When I started the NuSpec was creating problems for me and that is why I pulled down a Zip of your works and removed the NuGet references replacing them with a direct reference.

Now when I look at the NuSpec I noticed that it was copying source files like FirstPage.cs into the target. Unfortunately that is not going to be helpful when we are working in XAML. In fact I was bamboozled when I had everything working and seemingly without reason there compilation errors all over the place. Eventually I removed the additional files, but I had no idea where they came from.

Apart from that though, as I said the FormsPresenters work well with XAML, but I will need a second package NuSpec. Ideally within the root MvxPlugins.

Best

Peter Burke

From: Tomasz Cielecki [mailto:[email protected]]
Sent: Tuesday, 9 June 2015 5:47 PM
To: Cheesebaron/Cheesebaron.MvxPlugins
Cc: peter j c. burke
Subject: Re: [Cheesebaron.MvxPlugins] Cheesebaron.MvxPlugins-master/Samples/FormsPresenters Upgrade or Fork VS2015RC (#51)

Fork and pull. I will merge it into another branch. Although I don't have VS2015 nor in the preview, so I won't be able to build it and create a nuget of the new stuff, maybe you can help here?

Reply to this email directly or view it on GitHubhttps://github.com//issues/51#issuecomment-110263124.