I'm a blind developer and I want to make applications for iPhone.
I preffer Java to write interfaces because interface builder isn't
accessible
Interface Builder isn't the only way to create Cocoa Touch user
interfaces. Every thing Interface Builder does is based on using
classes and calling methods in the Cocoa API. If IB can do it, so
can your code.
Programmatic creation of user interfaces is certainly possible in
Cocoa. This approach is uncommon when the UI is mostly static,
although many Cocoa newbies ask how to do it in order to avoid
learning IB. Programmatic creation is more common in games, or
situations where the UI itself is much more fluid or dynamic.
That said, I don't think this will be an especially easy task, mostly
due to fewer examples. However, programmatic creation of Cocoa Touch
user interfaces should still more achievable than getting Java to run
on iPhone.
Also, IB seems to work with VoiceOver, so it's unclear what you mean
by "interface builder isn't accessible". Since this list isn't for
discussing Interface Builder or accessibility, you might do better by
bringing it up on one of these Apple lists:
If you post on any of those lists, you might want to describe what
tools you use now, and their accessibility features, so respondents
have a better sense of what you need and how Interface Builder
doesn't meet those needs. Saying only "Interface Builder isn't
accessible" doesn't have enough details for anyone to suggest any
possible solutions.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
