This UIElement appears when a user presses one of the hardware volume controls...the UI element is a black translucent square with rounded corners. In legacy versions of the Twitter app for iPhone, this element used to appear when a user would Follow, Unfollow, Retweet, etc. I would really love to use this element in my apps, can anyone let me know which element it is?
Best...SL
It is a popup. There are a few open source projects that will make implementing easier:
https://github.com/samvermette/SVProgressHUD
https://github.com/matej/MBProgressHUD
That UIElement is a simple transparent UIViewwith a animation in it. The animation is like "fade in, show for a given time, fade out".
Related
I got an app that allows users to add content to a canvas. I would like to be able to offer the user an ability to move, rotate, resize, reflect this content. Currently I'm doing this with gestures, but would like to know if there is some sort of open-source widget that draws a box around the view and adds 4 buttons to do these functions:
rotate 90 degrees
rotate freely
resize
delete
Can anyone think of an open source framework that I can add to my project to create controls like the ones displayed?
I can probably build this by hand, but debugging gesture recognizers and view rotation is not the most fun thing, so I'm looking for something more polished.
Thank you!
Here's a link to an open source control on cocoa controls that looks like something you could use: TDResizerView.
"TDResizerView is used to resize and rotate an imageview with single finger"
Sounds like a good place to start from, even if you need to modify it.
I've never used this particular control though, so take my word for what it's worth.
edit: Also keep in mind that on iOS, users generally expect gestures. Forcing them to use the handles instead of pinching or rotating may be bad for your user experience, depending on why you want the handles instead.
In the Path iphone application, on the bottom left corner, there is a + sign button. When pressing it, it performs an animation (the + rotates and a bunch of other buttons emerge outwards).
For those that have seen these types of animations, how is this accomplished? Is this done via CAAnimations?
Thank you!
You would definitely want to use either Core Animation, or UIView's animation methods (which use Core Animation under the hood).
Check out https://github.com/levey/QuadCurveMenu to see one attempt to reimplement it.
In my IPhone application, I have five buttons with background image set.
At any time one button is active an the other one is inactive.
I want to display the five buttons in 3d style such that the active image is in front and the others are at the back but visible.
When the user clicks the inactive button, it should come to the front and the the other one should go back, with all the buttons rotating like 3d effect.
Can anyone suggest an idea?
Cocos2d might be worth a look, it is very good (and not to hard) to make fancy things like this. http://www.cocos2d-iphone.org/
Hope this helps.
I am creating an application with call functionality, I want to have the phone image on the right hand side and the name of the contact on the left hand side. Currently this has been implemented by placing the 2 buttons side by side, hence if the user clicks on any of the buttons, the same functionality (calling the contact) happens.
Is this allowed according to Apple HIG? Please let me know.
Thank You,
Ashvin
I don't think anything in the HIG specifically disallows this, but it seems like a bad idea, for a couple of reasons:
If there are two buttons side-by-side, users will assume the buttons do different things, and will be confused when they don't.
It wastes screen real-estate that could probably be put to better use.
From your description it is hard to tell exactly what this looks like, but it sounds like something that needs to be re-designed.
Overlapping buttons?
It might not give you an intuitive UI, as the content of the overlapped button might get truncated by the overlapping button.
As Kristopher has explained, it will result in a bad user experience.
It is possible, that your app might get rejected because of the truncations as the user will not be readily able to perceive the content.
If look of the button is what you are concerned about, then you can just set one image (whether odd shaped or not) to one button, as long as the user is able to perceive that it is a button.
In the odd shaped image, you should also ensure that the functionality does not get triggered when the user touches the transparent area of the image, otherwise it might confuse the user.
Hope these points help!
Is there any mention about overlapping the buttons? Suppose for better design/look and feel, I have to place two buttons which partially overlaps each other, is it disallowed? Still the screen looks good and there will not be any confusion about the buttons. But only point is they are two different buttons, which assumes same functionality and has overlapped.
Adding some more information on the about query.
The buttons are overlapping as one is just a graphics and another is a rounded rectangle button whose Title changes dynamically.
If they can not be overlapped, can we have an odd shape button on the screen as long as user feels that they are buttons?
Thanks.
Straight forward question. I'm trying to understand UI design more and how to make it work with code. In particular there used to be an app that went through several design sessions, named Where To? by Tap Tap Tap. They had a table which they turned into a radio dial, screenshot:
(source: taptaptap.com)
My question is, is this nothing more than 22 or so images, with different states put together on top of a UIView? Each UIImageView is a button? How would something like this be put together? I'd love a tutorial on programmatically turning images into actual actions. If there's any book or blog which describes the process, that would be an ideal answer for me.
Any insight into how the above is done?
I actually think it's a single image that has it's layer rotated in response to touch events and then calculates which is the active button based on the radial distance from the original position. It's not horribly complicated code (touchset change is left or right and rotate in response to that, modify the hittest method to respect the radial deltas) but the math is more than I can do before six cups of coffee.