Let´s see, I am developing an app which uses some ModalViewCotrollers.
When I show any of these modals, everything is going OK, I can work with it and interact with his content. The problem comes when I try to do:
[self dismissModalViewControllerAnimated:YES];
This problem, only happens in lower version than iOS 5.0
The modals are called from my DetailViewController (in Master-Detail app).
Any suggestion??
Thanks everybody in advanced!!!
Have you tried if you are dismissing from the correct view controller??
Like this:
[self.parentViewController.parentViewController dismissModalViewControllerAnimated:YES];
Anyway, I found a couple of good links which could be helpful for you:
Modal view controller won't dismiss itself
dismissModalViewControllerAnimated: (and dismissViewControllerAnimated) crashing in iOS 5
Related
I have been looking into using MvvmCross as our solution to cross platform development, with previous development being solely targeted at iOS. I have come to really like how storyboards encompass all the views together along with the flow between them.
I know Monotouch supports their usage with the storyboard projects which I have been able to work with, however I have not been able to find any reference/example to it being using with MvvmCross.
Is this currently supported? or can someone provide me some tips as to how I can get this setup. The initiation seems to be the issue as in the storyboard projects the FinishedLaunching method in the AppDelegate is usually empty
Is this currently supported?
I don't believe it is.
I've never used Storyboards to build anything other than a demo app - so I'm not an expert.
However, from what I know I think there are 3 problems that you would need to overcome.
1. Storyboards don't have code in FinishedLaunching
This is easy to solve I think - you can just add an override to FinishedLaunching which calls an MvvmCross Setup class in order to initialise IoC, Plugins, your App, etc.
2. MvvmCross vNext requires you to override the constructors to forms like
public DetailViewController (MvxShowViewModelRequest request) {
}
while Storyboards require the use of forms like:
public DetailViewController (IntPtr handle) {
}
Overcoming this is harder... but the good news is that it should be a lot easier in v3 - one of the stated aims of v3 is to somehow support storyboards - see http://slodge.blogspot.co.uk/2013/02/mvvmcross-v3.html
3. Clash of concepts
If you are using Storyboards, then the navigation logic is tied to the Storyboard and to the UIViewController.
If you are using MvvmCross, then the navigation logic is tied to the ViewModels.
Overcoming this would be relatively straight-forward - you can easily mix and match concepts - but you might find your ViewModels and Views feeling 'a bit odd' as a result.
Summary
Doing this today is possible but would require some hours of hacking.
A beta of v3 is due very soon (within weeks - just depends on my spare time). Once that is available I think you'd be able to get started much quicker.
iOS Spotify API.
I read the documentation on the browse.m example which seems to contain what i am looking for.
But i really don't know how to use it.
When the list of the playlists is called how do i display it in a UITableView ?
If i could joust get started i can probably figure out and accomplish what i want.
So basically i need a "kickstart" help code, and i'll be on my way (Figure of speech).
( Btw, yes i have the AppKey.c needed and i successfully #imported the API)
See the sample projects included with CocoaLibSpotify for a general idea on how to interact with the library.
As for displaying playlists, well, playlists are stored in an NSArray and each have a name property, etc, so you'd put them into a table view just like you would any other list of data in the iOS SDK.
I have an application that will need to better support tablets in the future. I have seen some apps already created with UP1 and ExtLib Mobile Controls but I was wondering if anyone knows of specific functionality that simply is too challenging to even consider bringing to a mobile device?
For example, are there partial refresh issues on specific devices? Can managed beans still be used behind the scenes? Is dynamic content totally viable on mobile?
I'd be interested in hearing what big challenges/functions people had to give up when they mobilized their existing XPage apps.
There isn't really anything in XPages that would prevent building mobile web apps as with other web app dev models. In other words: Everything you can do with web apps on mobile you should be able to do with XPages.
XPages 8.5.3 UP1 comes with Dojo Mobile 1.6.1. However that does not prevent developers from using other frameworks like JQuery or anything else.
There are some advantages in general for native apps and hybrid apps. But personally I think most of the typically rather simple business apps can be built with mobile web apps. If you need local data/offline that might be different though.
You can use Xpages to do anything that is possible with mobile web developement. Dynamic content may not be the way to go for everything, but it will run just fine. In ITANA available for free on openntf.org, i created a simple replication engine to replicate notes tasks from the local device using sqlite to the domino server. This makes it run very fast and allows the app to run offline as well.
So i believe anything you want to try will work, you can make the Xpage output anything you want, from html, to xml, or json, to accomplish your tasks.
I know that XPages was totally incompatible with older Blackberry's. I assume that's not the case these days but back at OS 5.0 I think even buttons wouldn't work. So if you're doing anything with BB make sure it's modern and tested.
We're not really getting tablet support in ext. library until the next dojo rev I think. But there is a preview of tablet support somewhere that you can get. I've not looked yet but it was mentioned at Lotusphere. so if you want to hit tablets you might want to roll your own right now until that comes available.
Tablets are a little more challenging as the mobile controls are designed for the mobile phone size devices. That said with a little trial and error you can get a nice navigator split screen and still use the one page app mobile controls to streamline it, with records opening in their own page just like the phone version. Type ahead as I'm discovering should be handled differently if you are using the iPhone themes from oneui2.1
The oneui2.1 gives your navs and views nice styling. The forms may need a bit of custom styling.
Split your design into custom controls then you can use a server ate xpage for mobile devices and straight web. Or if you forgo the use of mobile single page controls you can always just have a seperate style sheet to accommodate the iPad. Really depends on the functionality needed. Good luck
My suggestion for anyone wanting to do tablet specific development using XPages is to move to Notes 9.0 and dojo 1.8 asap. Dojo 1.8 has an experimental control called ScreenSizeAware. This is miles ahead of anything else either the Extension Library Mobile controls or Dojo provides for Tablet development.
I had a bunch of apps that worked great in iOS 4. None of them work in iOS 5 (thanks Apple). I haven't been developing recently, and I don't have the time or knowledge to make my apps compatible with iOS 5. My question is, is there a way to make the apps available only to people running iOS 4? or do I have to just remove them from the app store? I don't want people to download my apps and have them not work. Thanks.
I believe you can set such restriction for people who are downloading your app from a computer (the app won't show up in iTunes). However, if the user is viewing the store through their iDevice, I think they can find your app and download it nonetheless.
It should suffice to simply put in the description that the app won't work with iOS 5.
Or, perhaps you should take a little look into why is your app not working. Normally the problem is not so big.
I have a page layed out with EZ-CSS. On this page I have a Telerik MVC Grid. It works just fine except that column resizing and reordering is not working. Also Ajax databinding does not work. It always uses server binding.
The same grid worked perfectly on a page not layed out with EZ-CSS. So it seems that EZ-CSS did something that is not compatible with the grid.
Any ideas?
Well, I have to apologize to the EZ-CSS guys. I figured out that the problem was that I also changed to a newer jQuery version. My fault - never do multiple changes at once. Ok, here my findings: Telerik's MVC Grid works with jQuery 1.5.1. I upgraded to 1.6.2 and that is not compatible with the grid. After going back to jQuery 1.5.1 all worked fine together with EZ-CSS.