Using Xamarin Storyboard Editor to edit XIBs - xamarin.ios

Just wanted to know if it is possible to open regular XIB files from new Xamarin's storyboard editor? Switching back and forth between Xamarin and Xcode is a bit inconvenient, and the new editor looks really nice; however, Storyboards have a few drawbacks and it is a pain to use them for our projects.
Any ideas re availability of this?

The plan is to add support for editing .sib files in future versions of Xamarin Studio.This will likely not happen in time for the first release with the iOS Designer (i.e. version 4.2), but I think it would be reasonable to expect that version 4.4 will have support for editing .xib files.

As of right now, no. I think it might be because of the complexity of the underlying XML but I'm not 100% sure. You can always create or upvote it on uservoice: http://xamarin.uservoice.com/forums/144858-xamarin-suggestions/suggestions/2700302-a-monotouch-xib-editor.

Using stand-along Xib files is now available, you can learn how to do it here -
Using Xamarin Storyboard Editor to edit XIBs

Related

How to disable multi preview feature introduced in Android-Studio 3.6

Is there a way to disable the new multi preview of layout added in Android-Studio 3.6?
I think it takes too much time to load.
Last but not least, it seems not possible to change the local and the theme applied to the preview, as it was possible before.
Seems that it gets better in AndroidStudio 4.0
Also this setting is useful:

Does Android Studio have the equivalent of view debug like xcode?

I am trying to quickly learn a new code-base (android-based) and a great way of doing that in iOS is using xcode's view debugger.
I do not know where to place break-points right now as there are way too many classes. Thanks!
Not 100% identical but you can use Layout inspector
https://developer.android.com/studio/debug/layout-inspector

Force Xamarin Studio view layout to stay the same

I'm currently using Xamarin Studio and have a comfortable enough setup so that I can put my various pads (output, unit tests, solution tree, etc.) on different screens. I like it and I'd like it to stay the same wether I'm debugging, running tests or coding.
But right now, xamarin studio handles it himself and switches to the Debug view layout when debugging, which changes everything to their default (since I've never really changed it).
Is it possible to tell Xamarin Studio to either :
- Never switch layouts?
- Set which layout is used for each situation (and I would just use my custom layout)
I've tried deleting all layouts and XS just recreates them. No dice here.
I've tried switching to my layout when debugging, hoping it would remember "this is my debug layout now". No chance either.
And I'm hoping I won't have to change each separate layout, because first it'll take a stupid amount of time, and also because if I ever decide to make a change, i'd have to set it up over 5 different view layouts which is just ridiculous.
Note : I'm using the latest version of Xamarin of the stable channel.
So, does anyone know a way to keep one single layout for all situations?
Unfortunately, no, it is not possible with the current version of Xamarin Studio.
I read through both the preferences as well as the documentation. I even tried to create my own custom layout by navigating to "View" -> "Save Current Layout". Then I selected my new custom layout when I started a debugging session, hoping it would persist to the next one. But alas, the "Debug" view was chosen automatically.
This would probably be something you could bring forth as a suggestion of improvement to the Xamarin team. You can do so using their bugzilla.

Any way to circumvent inbuilt auto save in android studio?

The current Android Studio version has inbuilt auto save. Which means if you close a file, it will automatically save the changes.
This is inconvenient, it means when experimenting with code, all changes need to be noted as there's no option to have a dialog requesting to save changes on closing a tab or the project, as in many other ides.
According to documentation IntelliJ IDEA 15.0 Help/Saving and Reverting Changes:
When does IntelliJ IDEA auto save changed files?
Autosave is initiated by:
Compiling a project, a module or a class
Starting a run/debug configuration
Performing a version control operation such as pull, commit, push, etc.
Closing a file in the editor
Closing a project
Quitting the IDE
.../...
Note that those are optional autosave triggers, and you cannot turn off autosave completely.
These are the auto save settings that can be changed in Android Studio:
TLDR
Is there any work around to circumvent this autosave?
These questions are related, but do not acknowledge that this intended behaviour of the ide and are rather asking for fixes within the ide.
Related:
How to disable Auto Save save in Android Studio
How turn off autosave in Android Studio?
If you want to experiment, use the revert button at the top right. This works especially well if you are using a VCS (like git...) as it will revert to the last committed version. And since commits are still manual, this will soon replace your traditional save.
If you are not using a VCS the point in time to which it reverts is a little more arbitrary, but in my experience it takes a pretty good guess. If that doesn't suffice, you can use the history button next to the revert button, which keeps track of every version IntelliJ saved, and you can then go back to any point in time you like. :)
Android Studio as a software is very much based on the JetBrains software solutions such as IntelliJ (used for Java) and PHPStorm (used for PHP, as its name shows).
As a concept in itself, JetBrains have implemented this feature and as a company believe that it's much more efficient and productive than manual save. Hence, there is no way to disable this behavior or enable any confirmations in Android Studio either.
Taken from JetBrains FAQ for IntelliJ:
Because IntelliJ IDEA has the ability to change so many files simultaneously in large refactoring actions, and change them without ever opening them, single file saves don't make very much sense. In recognition of this, IntelliJ IDEA reserves the right to save any of your files literally whenever it wishes. It's actually quite nice to never have to worry about your file's save statuses, once you get used to it.
Having said that, and encountering this issue myself too as a developer, I agree that it would be a good idea if the Manual Save feature were enabled by the Android Engineers (or JetBrains themselves). After all it is up to the developer to choose whether he needs this feature or not.
To Jetbrain's defence, they have a very good Undo function through their Ctrl + Z shortcut keys, letting the developer go back many steps and find where a certain error has occured.
All IntelliJ based products nowadays save any opened or modified files whenever they wish - read this as "immediately".
I would suggest you give up on trying to disable it (trust me, it's not possible to hack it) and either change your work flow or work on copies of the files.
As background I should mention that I am a plugins author for IntelliJ (with 3 publicly released plugins in the JetBrains repository) and thus have a reasonable understanding of the internal IntelliJ architecture.

MonoTouch and Xcode 4

Now that the Xcode 4 GM seed has been released, will MonoDevelop eventually interact with it somehow for XIB editing? I'm currently manually setting the "Open With..." on each of my XIBs to the old Interface Builder, but there are two problems with this: I have to remember to do it; and any XIB editing enhancements Apple makes in Xcode 4 aren't available.
Support was previewed here: http://mjhutchinson.com/journal/2011/05/preview_xcode_4_support_monotouch
Given the current status of MonoTouch, I think it's safe to assume you will not see this in MonoTouch as it exists now. Presumably this development will be carried over into the new iPhone/Mono product from Xamarin (http://www.xamarin.com/).
Xcode 4 GM is under NDA, so nothing can be discussed about it publically.
Adding outlets and actions is no longer there. XCode 4 now integrates these in code directly, but that is Objective C only, not C#.

Resources