I'm trying to use the CocoaPod version of Material with Swift 3.
However, when I open the project after installed Material 1.42.9 I cannot convert it to Swift 3 without making a lot of changes by my own.
Will their be a clean Swift 3 version in the near future?
As can be seen in the github issue page, Swift 3 support is in the development branch.
https://github.com/CosmicMind/Material/issues/516
Related
I want to configure the Kotlin bytecode inspector code in AS 3.5 to use an older version of the Kotlin compiler. Is it possible?
Currently I have a Kotlin 1.1 project, and I'm interested in seeing what the bytecode looked like for certain features when Kotlin 1.1 was new. My problem is that it seems like the Kotlin bytecode inspector always compiles the source code according to the newest version of the Kotlin compiler.
I basically want to reproduce the results of this experiment.
Incase you can't configure the bytecode inspector to use an old version of kotlinc, is there another convenient way to reproduce the results of the experiment?
When I download a skin from the Component store, then try to use it, I am doing it using the Unified/Universal layouts/platform. I am getting this error:
MTOUCHTASK: error MT2002: Failed to resolve "System.Void UIKit.UINavigationBar::SetTitleTextAttributes(UIKit.UITextAttributes)" reference from "Xamarin.iOS, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065"
It is happening with all skins. What am I doing wrong?
Here is my solution: https://dl.dropboxusercontent.com/u/41261911/testForUIChange.zip
Based on the dates (Jan 11th) you were probably using an beta version of XI 8.6 along with the component from the store (which always target stable, 8.4).
There were some difference between the unified preview (in 8.4) and the final version of the API (shipped with 8.6). That make it harder to find the right binary component to match.
As of today (Jan 12th 2015) Xamarin.iOS 8.6 is stable, has the final unified API and the component store has updated most of the components (some 3rd parties might not yet be available right now) to the final unified API.
IOW there's a good chance you can update your components (if you were already on 8.6) or all your software (if you were not on 8.6) and get a working build.
I'm on version 3.0.3.5 of MonoDevelop and was looking at the Pluralsight tutorials for MonoTouch where John Sonmez uses a few refactoring Tools/methods in the ViewController that isn't available in my version of MonoDevelop. For example - Refactor->Override/Implement members... , Encapsulate fields... and a few more. The only Refactoring tool I have available in my popup-window is Rename :)
Is there an additional download available with more refactoring tools?
Thanks for any help, I'm still new to MonoDevelop :)
From Sebastien, in response to this question
Some of the refactoring features were reorganized or removed (for now)
in the rewrite of the code code completion engine that took place for
MD 3.0.
In XCode 4, how do I access the "Copy Method Implementation to the Clipboard", which was available in XCode 3?
See Generate code for core data attributes in xcode 4 for the answer – XCode 4 made this feature much harder to find, unfortunately.
Is it possible to mix them? I'm asking because I have a big project that uses Subsonic 2.x generated classes (in a compiled dll) but would like to start using 3.x for new stuff.
I tried it last night with a project where I had references to both subsonic.dll and subsonic.core.dll but that didn't work with ambiguous references, etc. So removed 2.x and then got an issue with my older compiled subsonic generated classes in that they needed Subsonic 2.1 to run.
Hmm... I think there's a small chance that you might be able to do this, but you'd need to use the full qualifying class names (namespace.class) for a lot of code because there might be naming conflicts. It wouldn't be easy to do and definitely not recommended. (It might not can even be done.)
You can't move from 2.x to 3.x without doing a lot of recoding. I have a bunch of big projects in 2.2 and after trying to update to 3.0, I ran into some issues so I've decided to keep them in 2.2. I'd love to upgrade to 3.0 and use the new stuff, too, but I don't have the time (right now) to recode the stuff that changed between 2.x and 3.0.
I do recommend updating to 2.2. There shouldn't be any backwards compatibility issues between 2.1 and 2.2. I was able to update to 2.2 by just changing out my reference.
Just curious, are you using ActiveRecord or Repo implementation?
You only have 2 options:
stay in 2.1/2.2
update your code to 3.0
Thought I'd follow up here and let people know that I was able to get this to work. What i chose to do was to edit the Subsonic 2 source code and put it into a Subsonic2 namespace (everything), recompile to subsonic2.dll, etc. Had to modify the web.config slightly, then went and modified my old code to reference subsonic2, etc.
Am now able to mix both Subsonic 2 and 3 in the same project.
Gerry
Jim--I'm using ActiveRecord. The 2.x is in one namespace and 3.x would be in another. However, I guess the question is whether the 2.x can be compiled to run with the 3.x runtime.
Thanks,
Gerry