This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
tutorial:custom_oses [2015/01/17 01:22] sangar added info on how to access component proxies in BIOS |
tutorial:custom_oses [2015/10/14 04:09] ultrahex [What's Available?] |
||
|---|---|---|---|
| Line 61: | Line 61: | ||
| coroutine.yield | coroutine.yield | ||
| + | debug.getinfo | ||
| debug.traceback | debug.traceback | ||
| Line 128: | Line 129: | ||
| component.methods | component.methods | ||
| component.proxy | component.proxy | ||
| + | component.slot | ||
| component.type | component.type | ||
| Line 135: | Line 137: | ||
| computer.energy | computer.energy | ||
| computer.freeMemory | computer.freeMemory | ||
| + | computer.getArchitectures | ||
| + | computer.getArchitecture | ||
| computer.getBootAddress | computer.getBootAddress | ||
| computer.maxEnergy | computer.maxEnergy | ||
| Line 140: | Line 144: | ||
| computer.pushSignal | computer.pushSignal | ||
| computer.removeUser | computer.removeUser | ||
| + | computer.setArchitecture | ||
| computer.setBootAddress | computer.setBootAddress | ||
| computer.shutdown | computer.shutdown | ||
| Line 161: | Line 166: | ||
| Accessing components in BIOS | Accessing components in BIOS | ||
| ----------------- | ----------------- | ||
| - | Unlike in OpenOS you don't have the primary system for components in BIOS. That means you cannot just write `component.redstone.setOutput`, you have to manually create your proxy for the component first. For several reasons the proxy system is provided via the machine itself, so you can still use that. To get a proxy, use the `component.proxy` method. It expects the address of the component to wrap. You can either write that down manually, or get the the list of components using `component.list` and go from there. | + | Unlike in OpenOS you don't have the primary system for components in BIOS. That means you cannot just write `component.redstone.setOutput`, you have to manually create your proxy for the component first. For several reasons the proxy system is provided via the machine itself, so you can still use that. To get a proxy, use the `component.proxy` method. It expects the address of the component to wrap. You can either write that down manually, or get the list of components using `component.list` and go from there. |
| For example, to get the first best redstone component, you can do the following: | For example, to get the first best redstone component, you can do the following: | ||