Does anyone know if there is an open source project for an UIView element that acts in a similar way to the lock screen for the iPhone.
I am working on an app that has some sensitive data, and I want to add another layer of comfort for users, to be able to setup a 4 digit pin number on the app.
I've seen apps like LoseIt and Weightbot that have similar functionality.
There isn't any element for this in the UI Library from what I've been able to find, and was hoping some kind soul might have open sourced something similar to this.
Thanks in advance!!!
Thanks to Andiih above for the answer, because I found an open source version on GitHub based on the name of the one he found.
http://github.com/haroldthehungry/CPLockController
Its not a free component, but check out http://www.drobnik.com/touch/parts-store/ the DTPinLockController - I think this does what you want.
And another open source one (BSD license) is at:
https://github.com/Krishna/Lock-Screen
Related
I have been looking for the name of this UI element for a while now, but I cant come up with anything. What is the name of the round rect with 'Reloading Data' in it? I thought that I remembered using a view like this a while back, and there was some open source library that made its use much easier.
Screen shot of cydia.
The Apple API is private and cannot be used in AppStore apps. I and many others use MBProgressHUD: http://cocoadev.com/wiki/MBProgressHUD.
It's MBProgressHUD.
You will get more opensource controls on this link.
Why don't you just use a UIActivityIndicator? It essentially provides the same utility without the need to implement 3rd party code? Do you really need any custom behavior the class does not already provide? The simpler the better you know..? ;)
i'm looking to rebuild the MPMediaPicker from scratch (it's using my own song/artist data).
Does anyone know of an open source and free replacement for this? I'd really like to avoid creating all those views/etc
I've found PSMediaPicker, but it's $100.
I could have sworn I came across one - but I'm unable to find it anywhere.
If you are creating one for your own song/artist data then I would highly recommend just creating your own. If it is for music then it wouldn't really be much more than a modal view with some UITableViews in it, and since you know how the data is organized it shouldn't take long to get it up and running.
Bottom line - t will probably take you longer to find and integrate a suitable replacement than it would to just roll your own.
I am an Android newbie and I really require your help.
I'd like to develop an app , which its UI is persisted of three Tabs, and the first one a WebView.
since I am not familiar with all the required building blocks, can anyone give me a sample? a guide how to do so?
thanks a lot!
The Android API Demos include several (Tabs1 to Tabs2 sample files) examples. Install, try and have a look at them.
Regarding specifying the content of Tabs you have the possibilities to use Views or Activities. If you check some "Tab" related discussion here you will find that established users prefer to use Views (e.g. here). I took the 'Activity' way so far and feel quite comfortable - but did not go to deep into pros and cons. My current point of view is that you have to decide on each special case and can't give a general recommendation.
there is some tutorials on this page : http://developer.android.com/resources/tutorials/views/index.html
I am wising up and getting my internationalization act together. Right off the bat I am a bit swamped by all the docs Apple provides so I was wondering of someone could sketch a workflow for my situation.
Before I begin, I browsed some Apple example code and noticed this NIB file - MainWindow.xib - in the Resources folder:
alt text http://daturner.com/stackoverflow/nib.jpg
This clearly has something to do with internationalization/localization. Could someone please explain how this is created and where in the workflow it happens?
My app is fundamentally an imaging app with a few labels that I currently programmatically internationalize using NSLocalizedString(...). If I set all my labels programmatically and wrap all my strings with NSLocalizedString(...) can I completely ignore the NIB issues?
Thanks in advance,
Doug
To answer your last part of the question: Yes!
In my experience, it can be a pain to localize Nib's so if at all possible try to limit the localization effort to .strings files.
We we wondering what are some ways developers have added a help function to their apps. What are some techniques people have used?
One way we were thinking of is to us UIWebView to display a HTML file with help instructions.
Thoughts appreciated.
I'm using UIWebView right now which pretty much contains all the help in a single page, along with some JQuery things to display popups, etc. But I like the way iCab Mobile (et al.) are doing things which is a sectioned UITableView with each row a separate topic or section within their overall help information (complete with icons...) then in their bundle they have each section in its own html file, organized by localization.
Another thing in my queue for the next release is to provide a dynamic "News" view. The rough idea is as follows... I have on my server a file or CGI where I can place small bits of news I'd like to push out to users. On startup, my app checks for network availability and if present, start a thread to see if anything has changed on the server since last updating the News data. If changes present, post an alert letting user know, and asking if they'd like to read it now. At that point, the latest news is already downloaded and cached, so they can simply read it later if they want, and I won't post anymore alerts until the server file changes again. (And one could add a preference/setting to disable these alerts.)
I'm thinking this would be a good way to let people know that some nasty bug is known and fixed and an update is sitting in the queue, solicit beta testers, promote upcoming features or other apps, etc. I can see where constant alerts everytime I've got something new to promote would get annoying, so having a setting to disable them means the user never has to read them unless they want to. Although some kind of override to warn of recently discovered/fixed bugs seems sensible.
FWIW, the author of Mover+/Mover has just started doing a similar thing, though I think Emanuele is perhaps only showing one Notelet at a time, whereas I envision a bit more of a history (shown in UIWebView) until I decide to age stuff off the bottom of the stack.
I'm using a scroll/page view to show several images containing small notes. Each image then tells the user about the more advanced functions on a specific part of the app.
In my opinion the help should only contain information that isn't a 100% relevant for the use of the application. It should be things the advanced user should use to make more use of the app. It should contain gold for the power users. The "basics" should be so obvious that no help would ever be needed. If that's not the case, I think, you've failed as a developer on the iPhone platform.
(Here's a screen shot from my demo app)
I'm currently creating a fairly complicated app. I'm thinking of doing help as a semi-transparent overlay - help in text form is hard to swallow for users; it's much more helpful to just point at stuff and say "this does that".