about using library tools in cocoa [closed] - cocoa

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
which library tool(round textured,textured button,etc) shall i use for
displaying boxes at right corner of uploaded image,also please give me the list of different tools shall i use for all those data(multilined text,clear logs,small images at left corner, etc) from uploaded image.
please reply

You mean the buttons? There's no exact match because Mac OS is not Windows. Use standard buttons with standard appearances.
FWIW, the list of available UI widgets is one of the easiest things to learn about Cocoa. Open Interface Builder and look through the Cocoa library palette. The Cocoa equivalent of everything in your image is there (with the exception of the hyperlinked labels - don't use these in Mac OS applications anyway as they're non-standard and quite unattractive).
Posting a complete list of all the controls and their various settings here is an unnecessary waste of effort when all it takes is for you to drag a button onto a window in Interface Builder and start playing with settings (or looking in the documentation at the various NSButton styles).

Related

Good OSX development tutorials which do NOT use interface builder? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am an iOS developer. I'm porting an app from iOS to OSX and need some good tutorials to help me get up to speed with OSX coding. This question has been asked a few times, but all the answers reference tutorials which depend heavily on Interface Builder. I do not want to use interface builder (Please don't hijack my question by asking why I don't want to use IB). Ideally I'd like to find some tutorials that assume you already have objective-C/iOS experience.
Thanks!
Interface buildier for developing OSX is close to essential in my opinion. You are going to waste so much time setting everything up yourself in code. Just remember on iOS you have a single window, and at any one time you have a single view controller on screen (generally). On the Mac this isn't true and not only that you need to think about the menus too.
This do it all yourself mindset is great when you're learning and want to understand all the ins and outs but, it sounds like you are on a real project... I mean, you probably have a deadline. Embrace IB.
If you still want to get a kick start of using cocoa without IB then I think this should be a good read.
http://lapcatsoftware.com/blog/2007/05/16/working-without-a-nib-part-1/

Pivot or Panorama for my WP7 books app? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have to build a library Windows Phone 7 app to list books by author, editor, period.
I've not clear if it's better to use Panorama or Pivot control: i've seen that both would be good so i don't really understand the best component to use.
Can anyone help me?
A panorama control is great for showing a summary or a few top items you want to display in your app in a visually pleasing manner, but isn't suitable for showing large quantities of data.
A pivot is good for switching between categories such those you mention (author, editor, period). However you will have to ensure that you don't end up trying to show so much information in your pivot pages at once that your performance starts to suffer.
Another control you probably want to look at for this kind of app is the LongListSelector from the Silverlight Toolkit (link here). This control is similar to the one used on the People Hub of the phone.

Mac Menu Bar Tutorial? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have seen many apps in the Mac App Store that are simple apps that shows you the mobile version of FaceBook or Google Reader in the menu bar.
I am not sure where to start though, so I'm asking you guys.
I would like the app to display a mobile version of FaceBook in a dropdown style window (coming from the menu bar) when the toolbar icon is pressed. Any links on how to get started will be greatly appreciated.
I think NSStatusItem is what you're looking for.
Check the following tutorial:
Creating a Standalone StatusItem Menu
Another nice example project:
Using MAAttachedWindow with an NSStatusItem

HTML5 based node-graph editor? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm looking for an in browser click-n-drag type editor for editing directed labeled graphs.
All I need is a widget to support the editing and the ability to submit (AJAX, form, whatever) the resulting set of origin/label/terminus tuples. It's not what I need it for, but a GUI editor for simple GraphViz cases would be nearly ideal. This UML widget is kinds along the right track.
And I'm kind of restricted to open source, freeware and public domain.
Some other close, but not quite options:
arbor.js (view, not edit. And I don't need the auto layout.)
springy (ditto.)
You could try using Znode. A simple open source flow chart editor I created over the christmas break. It uses jQuery and Raphael. It doesn't really make use of html5 features because I wanted high browser compatability - I've tested in firefox, safari, chrome and ie6-8. It's still in development but it's stable.
Here is more info:
http://www.zreference.com/znode/

Generic Question: Thoughts on soft keyboard UI for mobile devices [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Yo, so I was curious about your thoughts about your preferences on soft keyboards for mobile devices. Are there any particularly innovative ones that you like?
By the way, my ulterior motive for asking this question was to look up one particular instance that I heard about, oh 10-ish months ago. Basically, you type with your finger constantly on the keyboard. Based on your direction changes and speed, the keyboard is supposed to be a much better predictor of keys. I'd really appreciate it if you
Pardon me for using this as a search for information, but it apparently made a much smaller smash in the gadget news sources, and implementations haven't come out yet.
I feel that it is much easier to type on keyboards that display the letter you are pressing as you press it. Also that the said letter is not put in until you lift your finger off of it. Like seen on the iPod and iPhone, and my current phone the LG Dare.
This is really good if you are working with a small space for the keyboard. If you are developing a keyboard I suggest using this method.

Resources