This is a page with the info on how to create a Pacakge that can be uploaded into an OeM server so that it can be installed inside OeM compatible devices.
As of the initial release, you'll want to upload mostly notecards for scripting and configuration, however in the future it will be possible to create your own devices and have them interact with our controller. These products will be able to be updated via our controller, There will be a page coming up about how to do this in the future.
The installer object must be the name of the Software in the following format:
<Name>_<version>
- Name: Must not contain an underscore ( "_" )
- Version: two numbers separated by a dot (".")
The installer should contain all the scripts that wants to be uploaded, aswell as a notecard that must be the same name as the installer, but begining with a "-"
Inside this notecard, it will be divided by tags. Tags are public "names" for devices, denoted by double square brackets ( [[example]] ) .
Currently these are the tags OeM supports. You can create your own and use OeM as a software manager:
oem_controller (for anything that wants to be installed inside our HUD)
AccessPanel ( for anything that wants to be installed in our backpacks/AccessPanels)
Inside each tag, line by line, should be the name of the scripts, objects, notecards, sounds and textures that the tag should receive, except for this notecard itself. If some content is not listed in this notecard, it won't be uploaded to the controller. If some content is listed, but can't be found in the installer, the installer will notify you, and will not work until you fix the issue.
Installer name: HypnoApp_6.1
UpdaterScript
HypnoApplication_v6.1
Triggers
Info Notecard
((Mandatory Notecard)): -HypnoApp_6.1
[[AccessPanel]]
HypnoApplication_v6.1
Info Notecard
[[HypnoGoogles]]
Triggers
(there will be an example notecard in the future)
With this you can install/update anything in the same prim as the updater script. If you want to update things outside of that prim, it's slightly more complex. The notecard structure is pretty much the same with the slight difference that those objects that have to be installed in other prims must be followed by "->" and the description of the prim the installation goes into.
element->description
So if we want to install the element "pic" in the prim whose description is "frame":
pic->frame
If the element is a script, that's all there is to it.
If the element is anything else, you have to have a script in that same prim as those objects. This script is in charge of deleting the objects when it receives the linked message whose number is: 108. The message of the linked message is the name of the inventory while the key is the id of the linked prim that contains it.