I want to implement auto complete feature like "Google" for example, I'm open for suggestions to use native controls or recommendations for third party controls.
I just want a text field that will take an array of strings and display suggestions according to what is written
I couldn't find cocoa pods controls for what i want in Swift 2.
I have tried this control: Auto complete Cocoa pods but no luck its implemented in a way that does not fit my needs "He is depending on xib file" and also tried UISearchBar with Content. But couldnt find a proper tutorial for it on swift 2
Your support is highly appreciated
Related
I'm making an iPad app that lets me write swift code into a text box and save it to a document. It doesn't do any compilation or any complicated stuff like that, so I'm just looking for a way to format the code correctly in the text box (ex: code autocomplete, autoindent if possible, and maybe syntax highlighting). In short, I'd like my app's text field and keyboard to look similar to those of Swift Playgrounds.
If Apple's provided the code (or a built-in keyboard option that can do even some of this), I'd appreciate a link to it. Otherwise, how would I go about building a custom keyboard and text field (or at least disable the features like autocomplete that would get in the way)?
Thanks.
As far as I know the only way to do what you describe is to build a Swift Playgrounds app that presents a code editor window. Apple does provide documentation on creating third party iPad Swift playgrounds. I suggest looking it up on Apple's site.
Hi all I would like to make a horizontal scroll bar like below in iOS APP.
I read through lots of iOS programming book, none of them teaches me how to do custom UI. Can someone tell me, what knowledge I should learn in order to make this?
Thank you.
You should be using UICollectionView to make your life easier. There are many tutorials on that in which you probably just want to lay out your cells in one row and many columns to achieve the horizontal scrolling effect. Otherwise you may want to employ external libraries like this if you prefer a plug and play solution.
I am developing a survey app using Xamarin and Mvvmcross. Can some one help with suggesting a way to build a View to display questionnaire. These questionnaire will be supplying from my View Model as a List of question with Question Text, Answer options. Based on a flag I need to prompt the questionnaire with input type as drop down or Text boxes. Number of questions can be vary.
In Android I achieved it using MvxGridView and Layout templates. But not sure how to do it in iOS.
You could look up UITableView or UICollectionView and UITextFields and UIPickerView
Wellcome to Xamarin, about your question you can just take look the code I wrote for others, it's a tableview include custom cell to display images, you can just modify the MyTableCell.cs class to display anything you want.
Custom cell tableview(Xamarin.iOS)
If you still need some help, just leave it here, I will check latter.
Hope it can help you.
From iOS 8 it is possible to add custom keyboard from our application which can be used system wide.
I need to create such a keyboard which can be used to input custom characters(a new language). I have these characters as images.
How can I use these images to input as characters from the keyboard into a textfield?
Please suggest any tips, link, methods etc..
Thanks in advance
You cannot put custom images in text fields because they are used to input text, not images.
The only possibility is custom font with images, but it will not be available system-wide and text fields are under control of the host app. For the available methods to insert characters see this documentation page
Try to follow this guide. Actually I've found plenty of similar guides using google.
Also Apple's custom keyboard guidelines might be helpful
I want to design my own custom input view keyboard using a custom keyboard extension in swift. The existing Xcode 6.1 default set of keyboards do not fit my app needs. What I want is an enhanced number pad which I would modify, like in the Soulver app in the iOS app store. http://www.acqualia.com/soulver/iphone/
Ultimately I do not need a custom keyboard extension to offer to other apps but I do not mind if my app offers one. It looks to me like custom keyboards are the right place to start for for a custom input view keyboard.
I finally just about have digested constraints in the editor and would like to make use of a storyboard or xib.
I do need to be able to programmatically select the keyboard extension within the app.
The keyboard/custom view needs to be available to the app that contains it without activation in iOS settings.
Can this be done as an extension given the requirements, or can the custom keyboard extension be easily converted to a custom input view? Can you illustrate either one or point out sample Swift code I missed when searching? Thank you.
I am writing a keyboard extension in Swift right now and highly recommend not doing the same. Both Swift and the Keyboard Extension API are brand new, not well documented, creating significant learning curves, and both have significant bugs or weird implementation details to work around.
From the way you phrased your question it doesn't sound like you are very experienced in iOS development, and attempting to learn too many things at once is a recipe for disaster. If I could do my current project over, I would have done it in Objective C just to vastly simplify what I was learning.
But the good news is that you don't need the keyboard to run in other apps. This is good news because writing a custom input keyboard class within your own app is very simple and easy, and a great place to start. There is a good deal of existing documentation on how to do so, including this excellent post on stack overflow.
How do I retrieve keystrokes from a custom keyboard on an iOS app?
More detail:
The standard custom input view API in cocoa is very powerful, the one in the keyboard extension is almost entirely neutered, so you can do far more with a custom input view than you can with a keyboard Extension. To activate a keyboard extension requires getting the user to turn it on in their iPhone settings, there is no way around that and no way to pick which keyboard they choose within your app (other than to not allow custom keyboard extensions at all).
If you need to access the internet or data within your app for any reason (tracking usage information, activating an in-app purchase, accessing preferences) you must also convince your user to turn on "Full Access", which presents an incredibly scary alert that reads to users as if turning it on means you will be able to spy on them and steal their passwords
Getting back to why you don't want to use Swift in an extension. First, Objective C doesn't cause Xcode's code parser to crash many times a day, while developing in Swift does, sometimes crashing Xcode itself. In Objective C the debugger is almost always correct, in the current version of Swift often you can't see array or dictionary contents, sometimes what it shows is inaccurate, and when stepping through code often takes nonsensical routes. Developing in Objective Code means you won't have to update your code because of changes to Objective C itself, with Swift it's pretty much guaranteed they'll make significant syntax changes every major release (the last one in September did).
Developing a keyboard extension means sometimes your extension won't load for mysterious reasons, and you'll need to waste hours debugging why. My Swift keyboard extension is sometimes debugged solely with println() statements because I can't get the debugger to load. Since Apple's tools don't yet work well with Keyboard extensions, and also don't yet work well with Swift, using them together are multiplying your pain exponentially.
The end result is if you don't need to use this keyboard outside of your own application it's foolish to build it using the Keyboard extension API. If you do need to use the Keyboard extension API it's foolish to do it in Swift. This is written by a fool working full time trying to ship a Swift based keyboard extension.
If you want to use the standard cocoa custom input view API, then using Swift is probably fine. You will still have to deal with additional problems because it's such a young language, but you won't have lose so many days to mysterious, seemingly insoluble problems trying to figure out if they were caused by Swift, the Keyboard Extension API, failures in Xcode and it's debugger, or your own blunder.