Rework of Xamarin Studio/MonoDevelop Addin #3361
Conversation
|
Note all the templates are now Nuget based. But we do include the nuget package in the addin so it will work offline if required (this is how Xamarin Studio handles nuget). I will also look at packaging this addin with the Pipeline Mac installer. |
Will this then replace the mpack we have for MonoDevelop then? |
|
It can replace the mpack. I think having a proper Mac installer is more important now (same for linux) |
|
On linux I made it so that the path where the pipeline will be installed can be changed during the installation, but launching /bin/monogame-pipeline will always launch monogame pipeline(or typying monogame-pipeline in terminal). Hope it helps. |
|
@tomspilman Sorry for asking again, but can you make mac server do the build of linux files, If you can, then I can make a proper linux installer, if not, the PR I submitted is closes thing to installer I can make windows build(without cygwin). |
|
@cra0zy could you add a script to run the mgcb as well? e.g /bin/mgcb |
|
@dellis1972 already did |
|
@cra0zy awesome :) |
Great! |
|
@tomspilman ok some more changes. First is the location of the Pipeline.Installer.pkg it will now be in Installers/Pipeline.Installer.pkg Now given that it now includes installing the Xamarin Studio Addin, I'm thinking of renaming the file to just MonoGame.Installer.pkg … comments? I also moved the building of the installer into the Installers directory default.build file which makes more sense. I had to make some changes to the start up code of the Pipeline app on mac because it was always getting a arg like -psn_0_xxxxxx which was messing up the auto open. The integration with XS is done, if you have a .mgcb file in a project and double click on it , it will open in the Pipeline app :) The new Templates have all been moved to the IDE/MonoDevelop folder. I have done, Mac, Android, iOS, iOS+Android+Shared, there is a Windows/Linux project as well. All the new templates use nuget to get the binaries. We ship the current stable nuget package with the addin so it will work offline. A Video of the XS integration is over at http://www.screencast.com/t/ygygS0JOw |
|
Still have a few bits to tidy up then we can look at merging this in |
Seems great to me.
I guess that means that the Xamarin Studio templates are still an IDE extension? |
|
Yes, and extension is the only way to do templates in XS and MonoDevelop :-/ -----Original Message----- thinking of renaming the file to just MonoGame.Installer.pkg … comments? |
|
@dellis1972 I'm guessing I should add installation of xs addin to pipeline installer for linux, just 1 quick question, did you just setup copying the addin to xs addin folder or did you do something more? |
|
@dellis1972 - How long before you think this can be ready? |
|
@tomspilman its a bit of a catch 22. It is relying on Nuget packages, but we need the new ones now especially since iOS is now Unified rather than classic as the framework versions changed from MonoTouch to Xamarin.iOS. We need to coordinate a Nuget release at the same time so we can make sure this all works. So we'll need to chat with @DDReaper so make sure I get the package names right etc. |
I'm confused. How is this an installer for Mac if it depends on NuGet? Are the assemblies coming from the installer or from NuGet? |
|
The new XS templates are designed to use Nuget to get their references. XS has built in support for Nuget so the new templates use that, but to We could go down the route of putting MonoGame in If we want this in the 3.3 release but not with Nuget, I'll have to put in |
Added SharedProject PCL for iOS and Android
Fixed MonoGame Template to include the OpenTK config files
|
@dellis1972 I think you should put this PR up for merging. If there are bugs you won't be the only one who will have to solve them, you would get help. |
|
This is ready for merging I think, just waiting on @tomspilman or @KonajuGames to review and merge it :) |
|
Oh, can't wait for this to get merged :D |
|
|
||
| namespace ${Namespace} | ||
| namespace ${ProjectName}.Droid |
There was a problem hiding this comment.
Why the .Droid addition to the namespace? It just necessitates the additional using statement above it, and "Droid" is not an abbreviation that Google approve of for "Android".
Also, a project name might not be a valid namespace if I remember correctly.
|
The Android splash screen is very low resolution and dull grey. Can it use the same white splash as the VS Android template? And default the project to landscape as all other templates do. I would like to remove the small "mono for Android" logo from the lower-left though. |
| [assembly: AssemblyConfiguration ("")] | ||
| [assembly: AssemblyCompany ("")] | ||
| [assembly: AssemblyProduct ("")] | ||
| [assembly: AssemblyCopyright ("Dean")] |
There was a problem hiding this comment.
Is this the assembly info for the plug-in or the template for new projects? If for the plug-in, the copyright should be "MonoGame Team" like our standard file header. If for a template, it should be the token so the IDE fills it in as appropriate for the user.
|
That is a /lot/ of files and changes to look through. :) |
|
Closing this PR, reopened a new one |
Includes new templates and new Shared Projects support
Includes Pipeline Tool support
Removes old ProjectTemplates
This is just a Test PR for now to check for any build issues.
Also worth noting that once this is in , the old MonoDevelopContent addin will no longer be needed and will also be removed probably as part of the PR as well. This is because we don't want to support the old xna content projects moving forward , only the .mgcb ones which this new addin will take care of.
I do need some guidance on where the Pipeline.exe will be installed on linux.. so we can start it correctly from the IDE.