4 ms·

Are frameworks allowed? I thought they banned anything third party.

WiseWeasel 16y ago
They're tolerated, until they're not. Realistically, though, as long as a million script kiddies don't start using it to flood the App Store submissions with crapware, you'll be OK. Thankfully, this one is targeted at serious developers, since it's for people coding in Objective C, so it's not much of a risk. Also, there's a huge difference between distributing an Objective C framework, which is a packaged bundle of obj-c code that a developer has full access to, and wrapping that framework with a limited scripting language front end that developers can't even touch, like Adobe Flash CS5. If anything, the standardization of Obj-C frameworks improves general application quality for people writing native apps the Right Way(TM), as bugs are minimized.
MWinther 16y ago
Of course you can use open source code in C, C++ and Objective C. A framework isn't anything special in and of itself.
pkaler 16y ago
Wow, this just goes to show how irrational some of the hate for Apple's policies are. A framework is very similar to a library in C. It can also include data such as strings and documentation. You can read the formal definition of what a framework is here: http://developer.apple.com/mac/library/documentation/cocoa/conceptual/ObjectiveC/Articles/ocGlossary.html#//apple_ref/doc/uid/TP30001163-CH5-SW1 http://developer.apple.com/mac/library/documentation/cocoa/c...
- derefr 16y ago
  I think more people here have heard "framework" in the context of "the Rails web framework" or "the SDL game development framework" than Apple's particular odd usage. Under most definitions, a "framework" implements an Inversion of Control pattern where the framework's code calls your own, and you're the one acting as the "library"—pretty much what Apple's seeking to stop people from relying on.
  - whyenot 16y ago
    The term as used by Apple dates back to the late 1980s and NeXTSTEP.
    - derefr 16y ago
      I was simply trying to explain that someone_here's original question was more likely inspired by ignorance at the meaning of "framework" than by the extreme belief that any and all library usage is disallowed by 3.3.1, and thus wasn't an example of "irrational ... hate for Apple's policies." I know both definitions of "framework", and can differentiate them by context of usage—but a good journalist avoids, in their writing, words with clashing jargon/non-jargon definitions (for example, "begs the question") even when using them correctly under the jargon sense—because people unfamiliar with the jargon will assume the general term, and get all sorts of confused.
- dangrover 16y ago
  Well, you can't really use .frameworks on the iPhone in the same way you can on Mac OS X. Only static linking for non-Apple frameworks is permitted.

They're tolerated, until they're not. Realistically, though, as long as a million script kiddies don't start using it to flood the App Store submissions with crapware, you'll be OK. Thankfully, this one is targeted at serious developers, since it's for people coding in Objective C, so it's not much of a risk. Also, there's a huge difference between distributing an Objective C framework, which is a packaged bundle of obj-c code that a developer has full access to, and wrapping that framework with a limited scripting language front end that developers can't even touch, like Adobe Flash CS5. If anything, the standardization of Obj-C frameworks improves general application quality for people writing native apps the Right Way(TM), as bugs are minimized.

MWinther 16y ago

Of course you can use open source code in C, C++ and Objective C. A framework isn't anything special in and of itself.

pkaler 16y ago

Wow, this just goes to show how irrational some of the hate for Apple's policies are. A framework is very similar to a library in C. It can also include data such as strings and documentation. You can read the formal definition of what a framework is here: http://developer.apple.com/mac/library/documentation/cocoa/conceptual/ObjectiveC/Articles/ocGlossary.html#//apple_ref/doc/uid/TP30001163-CH5-SW1 http://developer.apple.com/mac/library/documentation/cocoa/c...

derefr 16y ago
I think more people here have heard "framework" in the context of "the Rails web framework" or "the SDL game development framework" than Apple's particular odd usage. Under most definitions, a "framework" implements an Inversion of Control pattern where the framework's code calls your own, and you're the one acting as the "library"—pretty much what Apple's seeking to stop people from relying on.
- whyenot 16y ago
  The term as used by Apple dates back to the late 1980s and NeXTSTEP.
  - derefr 16y ago
    I was simply trying to explain that someone_here's original question was more likely inspired by ignorance at the meaning of "framework" than by the extreme belief that any and all library usage is disallowed by 3.3.1, and thus wasn't an example of "irrational ... hate for Apple's policies." I know both definitions of "framework", and can differentiate them by context of usage—but a good journalist avoids, in their writing, words with clashing jargon/non-jargon definitions (for example, "begs the question") even when using them correctly under the jargon sense—because people unfamiliar with the jargon will assume the general term, and get all sorts of confused.
dangrover 16y ago
Well, you can't really use .frameworks on the iPhone in the same way you can on Mac OS X. Only static linking for non-Apple frameworks is permitted.