Help needed: iPad developer issue(s)
wb4jfi at knology.net
wb4jfi at knology.net
Thu Mar 15 16:22:40 CDT 2012
Thanks for the feedback Mike. We both have signed up as individual
developers already, so that step is accomplished.
There's a lot to ingest here, before getting much up and running. We wanted
to take baby steps by testing what is written so far on real, actual
hardware. Therefore, we want to be able to share/collaborate. Mel is doing
the iPad part, and I am doing some ethernet-connected hardware. We are at
the point that we want to test whether we can turn on an LED on the hardware
via the iPad. But, since Mel has worked on the iPad software, he has all
that code at his house, while I have the hardware at my house.
This is the reason why we want to share files/projects. We want to be able
to have Mel email/send me iPad code that I can build here at my house and
test with the actual hardware device. So far, it appears that we cannot do
that simple thing. I must drive my hardware to Mel's house, or he must
build his app at his house, and then drive his iPad over here to test. Of
course, if either part does not work at first, we cannot simply change
something and rebuild. Instead, we must drive back to our respective
houses, try to figure out what went wrong, rebuild the app (or my hardware's
firmware), then drive back together to try again. Very much a pain and a
waste of precious fuel.
The simple answer would be to be able to build both parts at both locations.
Alas, Mel does not have the hardware platform that I am working on yet, so
doing it that way is out.
How hard is it to build an app at Mel's, and share the files for that app's
project with me, so I can build it as well? Why would this plan violate
some Apple policy?
From: Mike O'Dell
Sent: Thursday, March 15, 2012 11:00 AM
To: Terry Fox
Cc: tacos at amrad.org
Subject: Re: Help needed: iPad developer issue(s)
the simplest thing to do is for both people to join
the developer program as individuals. you will both want
all the dev stuff and without question, the $99 will be
very well spent by each of the parties. all the stuff
dev stuff does automatic updating and fighting
that so you're just out one $99 is Just Not Worth It.
in fact, you will very likely never make it work right.
(Don't feel bad - when I first became a Mac developer
is was a couple of hundred dollars a year and that
was in 1985 dollars)
that way you can send stuff back and forth with many
fewer tears and hassles.
you REALLY need all the Dev support stuff.
you WILL NOT be able to do something from a
blank sheet of paper. there's just way, way
too much stuff you have to get right before
anything useful will happen (except maybe
jump into the debugger) and *nobody* i've
ever heard of has managed to do the blank-sheet
startup. there's just too much technology.
you *really* want to start using the automatic
storage management stuff from the beginning.
automatic garbage collection has been eons
coming for Objective-C, made possibly only
by moving to the LLVM C compiler technology,
and it makes a dramatic difference in the number
of insanely-painful nuisance "brain-o bugs"
you have to deal with.
the iThing emulator that runs on the Mac under xcode
is how all the apps you see are developed. only very late
in life do they see the inside of an iThing.
Tacos mailing list
Tacos at amrad.org
More information about the Tacos