possible extension of current offerings for templates into a system for third party addons #989
Replies: 3 comments
-
oc_chimera_system. It describes it but it is a bit heavy maybe, just a thought :) |
Beta Was this translation helpful? Give feedback.
-
Public Domain: This means anyone can use this script for any purpose, it is not licensed. We have a few of these but they are limited only to link code so that third party creators can link their own devices to an OpenCollar menu without having to set their device to open source. |
Beta Was this translation helpful? Give feedback.
-
i have been thinking about it and i think capsule might work better than standalone oc_capsule_addon since its a wrapper for oc_plugin to work as an addon/standalone |
Beta Was this translation helpful? Give feedback.
-
Phidoux, with coding and testing help mostly from Yosty and Ping, has been working on a template for addons that would do considerably more than just serve as the link code between an external device and oc_addons menu.
This concept would basically create a simplified version of the oc core, to be dropped into other devices. These devices could then connect to AddOns, or be usable without wearing the collar (analogous to how the AO now works). There are currently three scripts in development: oc_standalone_core, oc_standalone_states and oc_standalone_dialog.
I see some advantageous in producing such a system. First, it would allow users to easily adapt a lot of older devices out there to work with addons and avoid triggering the Highlander code (which is what we call the code that generates a forcible detach for a second device with opencollar code). Second, it might solve our problem with generating multiple leashes and leashpoints.
I have three questions I would like to work toward consensus on, assuming all bugs can be worked out.
Beta Was this translation helpful? Give feedback.
All reactions