Here’s what passes for normal conversation around here:
- Me
- Would you expect my components to get horked if I tried to export them both from the same FLA?
- Marc
- Uh, no. Why?
- Me
- Darn. They each have their own component name in the resulting SWC, but they end up having the same class name.
- Marc
- Are you using the same classes in them or something?
- Me
- I’m using some of the same classes, but the components themselves each have their own class. If I right-click on Export SWC File… in the library, both components are in the SWC, but with the same class name. And I can’t just export one component and then the other, because you get two copies of each, presumably only one of which works.
- Marc
- That’s weird.
- Me
- Did I mention that I was using an Adobe product?
Weblog |
Tagged Adobe, AS3, Flash, Flex | Permalink
| No Comments
Posted
March 20, 2008
at 3:16 pm
Since I posted predictions, I feel like I have to post a post-game summary as well:
- Code Signing
-
Mostly correct. Your code must be signed to be distributed through iTunes, and Apple does intend to prevent you from distributing your app through any other channel. The difference is that you get your certificate as part of your (paid) iPhone Developer Program membership — and for less than you can usually get a code signing certificate.
- Student / Hobbyist Developers
-
The text of my prediction was correct, but the spirit of it was wrong. You can, technically, develop your application without paying a penny to anyone — but only if you don’t intend to test it on a device.
- Paid and Displayed
-
Same as above, basically. Apple created a new paid developer program, which wasn’t really what I meant.
- Xcode
-
Partially correct. There are new tools, and some of the existing ones do get new tricks — but Apple seems to be throwing the whole mess of tools into this endeavor. Sure, Interface Builder isn’t in the current beta, but I totally didn’t expect Instruments to be included.
- What’s in a name?
- This was from a list of additional predictions I had that I thought weren’t worth posting an update or sequel post. This OS does get an official name — it’s referred to all through the docs as “iPhone OS”.
Here are some other interesting points from my reading so far:
- Xcode has its own list of devices (perhaps not surprising) that you have to add you device to by plugging it in with Xcode running.
- You create your code signing certificate using the Certificate Utility in Keychain Access, and then upload it to Apple’s servers (once you’ve joined the program), and then download the signed one and add it to Xcode.
- While you’re downloading stuff, you’ll need to download your Profile as well — to me this strongly implies that the exact nature of the restrictions is negotiable (at least they are for the really big fish).
-
I love really specific qualifiers on informational pages:
The iPhone Developer Program will initially be available to a limited number of developers in the U.S. and will expand to other countries in the coming months.
Limited? I know your developer.apple.com totally screwed from the load after the announcement, but still. In the coming months? Gosh. Is that the same timeframe for when most of us would actually be permitted to join?
Weblog |
Tagged ADC, iPhone, Predictions, SDK | Permalink
| No Comments
Posted
March 7, 2008
at 10:55 am