|
Tasks |
Use's MS |
Possible Mac OS Porting Time |
Notes |
|
Setting up Development Environment & Compile Code |
1.5 |
||
|
Mac OS Startup code |
0.5 |
||
|
Operating System Dialogs |
0-2 |
This is dependant on number of OS specific dialogs and complexity |
|
|
Getting System Information |
Yes |
None |
No work required. |
|
2D Engine code |
Yes |
None |
No work required. |
|
3D Engine Code |
Yes |
None |
No work required. |
|
Texture manipulation code |
Yes |
None |
No work required. |
|
Offscreen/Bitmap code |
Yes |
None |
No work required. |
|
Graphical Engine Performance tuning |
None |
"No work required. As your game engine was already tuned for the PC, and as the Mac OS Direct-X is tuned to get the most of the user's machine |
|
|
Movie playback |
1 |
Convert to QuickTime. |
|
|
Sounds Effect code |
Yes |
None |
No work required. |
|
Music Playback as: - |
|||
|
Sample Looping |
Yes |
None |
No work required. |
|
CD/MP3 playback |
0-1 |
Use QuickTime if required. |
|
|
Midi playback |
0-1 |
Convert to QuickTime if required. |
|
|
Byte Swapping code |
1 |
This is dependant on how much code requires byte swapping and identifying the problem areas. |
|
|
Keyboard Support |
Yes |
None |
No work required. |
|
Joystick Support |
Yes |
None |
No work required. |
|
Mouse Support |
Yes |
None |
No work required. |
|
ANSI code |
None |
No work required. Good on you to use ANSI functions |
|
|
OS Specific code |
1-3 |
This can be dependant on how involved the OS code is. |
|
|
Assembly Functions (if any) |
None-3 |
"Depends on amount, but there are tools available to do this for you." |
Approximate porting
time 7 to 12 days
This shows the possible porting time of your product to the Mac OS platform using the Mac OS Direct-X API.
"Depending on how much your code falls into the above categories, you might have to additional time."
Download this table
as an excel file.