19,041
edits
History of Mac Oni: Difference between revisions
updating wording for latest Oni build, experimenting with two-column layout to avoid the Omni Get Info window from intruding on, or creating a large space before, the Feral section
m (wording) |
(updating wording for latest Oni build, experimenting with two-column layout to avoid the Omni Get Info window from intruding on, or creating a large space before, the Feral section) |
||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
:''For the overall history of Oni's development, see [[Oni]].'' | :''For the overall history of Oni's development, see [[Oni]].'' | ||
| Line 15: | Line 14: | ||
In 2000, Bungie was merging into Microsoft, and Take-Two was assuming command of the Oni IP. Having been in development years before OS X released, Mac Oni would initially have been built as a "Classic" app, referring to the Classic Mac OS (anything before 10.0). Given the circumstances, the best that Bungie could do for compatibility before Oni released in January 2001 was to build the Oni application as a "Carbon" app. Carbon apps could be written primarily for OS 9 and still run on OS X. Unfortunately, the Carbon build of Oni was not without issues in the OS X environment. | In 2000, Bungie was merging into Microsoft, and Take-Two was assuming command of the Oni IP. Having been in development years before OS X released, Mac Oni would initially have been built as a "Classic" app, referring to the Classic Mac OS (anything before 10.0). Given the circumstances, the best that Bungie could do for compatibility before Oni released in January 2001 was to build the Oni application as a "Carbon" app. Carbon apps could be written primarily for OS 9 and still run on OS X. Unfortunately, the Carbon build of Oni was not without issues in the OS X environment. | ||
<div class="div-col columns column-count column-count-2 style="-moz-column-count:2; -webkit-column-count:2; column-count:2;"> | |||
==Carbon to Cocoa== | ==Carbon to Cocoa== | ||
[[Image:Omni Oni Get Info window.png|thumb|Omni Group's Cocoa PPC port of Oni for Mac OS X.]] | [[Image:Omni Oni Get Info window.png|thumb|The Omni Group's Cocoa PPC port of Oni for Mac OS X.]] | ||
Then, at the end of 2001, [http://www.omnigroup.com Omni Group] [http://www.omnigroup.com/mailman/archive/omni-press/2001/000008.html released] a "Cocoa" (native OS X) build of the game which they had produced for free. This became known as the Omni build (now usually referred to as the PPC build). Their new builds (released through 2003) kept Oni stable for several years. The last Omni build is still available [http://www.insidemacgames.com/news/story.php?ArticleID=7003 here] and [http://www.omnigroup.com/ftp/pub/software/MacOSX/10.1/Oni-1.0v1.36.dmg here]. However, as computers advanced, a critical bug appeared in both Windows and Mac Oni; the game would immediately crash while querying the graphics card at startup. Once the patch was figured out in Windows, it was carried over to the PPC build. Other patches were made in time to the PPC build; see [[AE:OMNI|HERE]] for details. | Then, at the end of 2001, [http://www.omnigroup.com The Omni Group] [http://www.omnigroup.com/mailman/archive/omni-press/2001/000008.html released] a "Cocoa" (native OS X) build of the game which they had produced for free. This became known as the Omni build (now usually referred to as the PPC build). Their new builds (released through 2003) kept Oni stable for several years. The last Omni build is still available [http://www.insidemacgames.com/news/story.php?ArticleID=7003 here] and [http://www.omnigroup.com/ftp/pub/software/MacOSX/10.1/Oni-1.0v1.36.dmg here]. However, as computers advanced, a critical bug appeared in both Windows and Mac Oni; the game would immediately crash while querying the graphics card at startup. Once the patch was figured out in Windows, it was carried over to the PPC build. Other patches were made in time to the PPC build; see [[AE:OMNI|HERE]] for details. | ||
<br clear="all" /> | |||
==PPC to Intel== | ==PPC to Intel== | ||
In 2006 Apple began their '''third''' major Mac transition: the [[wikipedia:Apple's_transition_to_Intel_processors|switch to Intel processors]], back to CISC architecture and moving away from the PowerPC chip for which both Bungie and Omni Group had built Oni. For a while, PPC apps could be run on Intel Macs using [[wikipedia:Rosetta_(software)|Rosetta]], but support for the old architecture was expected to eventually phase out. In 2009, [http://www.feralinteractive.com/en/ Feral Interactive] (Oni's Mac distributor outside of North America) [http://oni.bungie.org/community/forum/viewtopic.php?id=848 expressed an interest] in putting out an Intel-native build of Oni. They obtained the source code from Omni Group, who had begun porting it to Intel, and | [[Image:Feral_Oni_Get_Info_window.jpg|thumb|Feral's Intel port of Oni for Mac OS X.]] | ||
In 2006 Apple began their '''third''' major Mac transition: the [[wikipedia:Apple's_transition_to_Intel_processors|switch to Intel processors]], back to CISC architecture and moving away from the PowerPC chip for which both Bungie and The Omni Group had built Oni. For a while, PPC apps could be run on Intel Macs using [[wikipedia:Rosetta_(software)|Rosetta]], but support for the old architecture was expected to eventually phase out. In 2009, [http://www.feralinteractive.com/en/ Feral Interactive] (Oni's Mac distributor outside of North America) [http://oni.bungie.org/community/forum/viewtopic.php?id=848 expressed an interest] in putting out an Intel-native build of Oni. They obtained the source code from The Omni Group, who had begun porting it to Intel, and began releasing Intel builds of Oni shortly before Apple did away with Rosetta in Mac OS X 10.7. This build incorporates a number of changes requested by fans, detailed [[AE:FERAL|HERE]]. | |||
</div> | |||
[[Category:Oni history]] | [[Category:Oni history]] | ||