Re: Accessible Developement Taking a new spin
Re: Accessible Developement Taking a new spin
- Subject: Re: Accessible Developement Taking a new spin
- From: Travis Siegel <email@hidden>
- Date: Tue, 14 Oct 2008 09:39:09 -0500
We could code the main app in nearly anything, including C or C++,
it's the graphical interface that is offering the trouble. Cocoa is
designed specifically to handle this task, but we can't use it
adequately.
As mentioned before, Java could be used in some cases, but it's
certainly not an overall solution, as there's just some things that
just plain won't work well.
And, besides that, the documentation on tying java into other
languages on the mac isn't exactly the most explanatory documentation
I've ever read, it leaves a lot to be desired, and makes the
assumption that you're going to tie it with cocoa only, which again
doesn't work if we're trying to tie things like perl, python, or some
other scripting language into the code.
The problem is, folks see cocoa, they use cocoa, and 3rd-party
development products are sadly lacking on the OSX platform.
On windows, we have things like powerbasic, visual basic, visual C,
delphi, and the list goes on and on. On the mac side, xtools and
ibuilder are pretty much all there is minus a few half-hearted
attempts by others to bring their languages to the mac os, but there's
nowhere near the variety of development languages available for the
mac that there is on other platforms, and this also limits what we can
work with.
Those few options that are made available by third-party developers
(such as fpc, gpc, and D, are so tightly integrated into cocoa
frameworks, that it's almost not worth the effort to install and use
them, because we're still restrained by the same problems that plague
us using cocoa itself.
Add to that, the fact that apple tends to point to Next step
documentation a *lot* for doing things like we're trying to do (I.E.
build interfaces from scratch) telling us to look at next step
programming guides, which is (imo) unacceptable, since it's cocoa
we're trying to program in, not next.
Yes, I know, that's where it originated and all that, but telling us
to go look up bsd calls when we're trying to write something for osx
isn't exactly wildly embraced by the general community either, (though
I've seen posts saying to do just that) , so there should be no reason
for us to have to go back to what amounts to a beta version of cocoa
just to do something that we should be able to do out of the box.
This is why there is very little development done on the osx platform
by vi programmers, it's just too complicated, and highly error-prone.
Until something happens to make accessibility to the programming tools
better, the sad fact is: it's simply easier to work in the windows
world, and I for one, would really love to change that.
On Oct 13, 2008, at 10:53 PM, Alex Jurgensen wrote:
Hi,
YOu could use CammelBones to code the back end in Perl, and Then
handmake Coco App frontends with Coco.
What do you think?
Thanks for listening,
Alex,
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (Accessibility-
email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden