Difference between revisions of "Talk:IOS"

From WiiBrew
Jump to navigation Jump to search
m
(fixed misspelling, added comment)
Line 21: Line 21:
 
I sugest that we move the information from the wiki into an application designed to track APIs, in order to make these things easier to be done right.  
 
I sugest that we move the information from the wiki into an application designed to track APIs, in order to make these things easier to be done right.  
 
--[[User:Henke37|henke37]] 11:43, 16 March 2008 (PDT)
 
--[[User:Henke37|henke37]] 11:43, 16 March 2008 (PDT)
 +
 +
* I think the basic idea behind pages like this is that if you're one of the developers who are going to be working with/improving these functions, you'll already understand them, and just need these references. These IOS functions are not final, it seems, and many of them won't necessarily be interacted with by the average developer once libogc is completed for Wii.  If libogc and functions like these weren't being so actively updated and developed, it might make sense for these guys to stop and document them more, but these are really just being assimilated into better libogc/devkitpro code, which is what is really going to need documenting in the end, and I'm not sure Wiibrew is the place for that information. [[User:ProdigySim|ProdigySim]] 20:13, 16 March 2008 (PDT)

Revision as of 04:13, 17 March 2008

Descriptions

I think that we should add something about how the Broadway code interacts with the IOS on this page, like describing the basic methods of communication and so on.--henke37 04:15, 17 February 2008 (PST)

Useful info

I find a huge lack of usable information here. So what if there is a IOS_FOOBAR function? We don't know what it does or how to properly use it. I only request that any further edits to the related pages tries to at the very minimum list these things:

  • Name of the call
  • What it does
  • Indata
    • Format
    • Use
  • Outdata
    • Format
    • Use
  • Usage rules, like things that may not be done

Yes, I do know that not everything is known, but seriously, the information that I list is known for some things, just not on the wiki. I sugest that we move the information from the wiki into an application designed to track APIs, in order to make these things easier to be done right. --henke37 11:43, 16 March 2008 (PDT)

  • I think the basic idea behind pages like this is that if you're one of the developers who are going to be working with/improving these functions, you'll already understand them, and just need these references. These IOS functions are not final, it seems, and many of them won't necessarily be interacted with by the average developer once libogc is completed for Wii. If libogc and functions like these weren't being so actively updated and developed, it might make sense for these guys to stop and document them more, but these are really just being assimilated into better libogc/devkitpro code, which is what is really going to need documenting in the end, and I'm not sure Wiibrew is the place for that information. ProdigySim 20:13, 16 March 2008 (PDT)