• OmnivosPluginIdeas

Plugin Ideas

• Reflect server computer stats like cpu load, ram, disk, temperature sensors, etc. in properties.
• Sync to filesystem.
  • Windows Common Internet File System ?

  • FuseFs

  • Alfresco has a feature called Alfresco Intelligent File System
  • Use Samba (SMB: Windows filesharing protocol)?

• Read inputs from a parallel port (see ParaPin for Linux) or another input device (PC speaker is aparently available as a Linux input device), and update VOS properties with new values. Then other plugins or scripts on the site can listen to those values and make stuff happen in the virtual world.

• Reflect a ServiceDirectory on the web (with HyperVos): script or plugin running on the hypervos site to create webpages about services. this can then show currently active worlds, all worlds ever created, worlds created in the last N days, with metadata; forms for users to leave ratings and comments.

• Magnetic behavior, and/or or switchable "sticking" to nearby objects. E.g. you could make virtual Legos: when certain faces on an object get close enough to certain faces on another object they begin a rigid constraint behavior to stick together unless you explicitly ask them to detach. For complex behaviors, need a resolver to take requests from multiple listeners and choose one requested result to effect or a way to mix the requested results/actions.
• plugin that fetches exchange rates periodically from the web and saves them in properties along with metadata including time fetched and where from.

• VisualizationToolIdeas

• Plugin that monitors information in an SQL database and updates vobjects. Database selections should be somewhat configurable. Not meant to store all VOS information (like sqlpersist does), but should basically keep a vobject for each row returned by the query, and put column values in child properties.

Omnivos Feature Ideas

• In addition to specifying a full plugin module file name, a seperate option to load a plugin by giving its base name. Omnivos would then search it's list of plugin directories for a plausible shared library to load. E.g. if given "hypervos" then a file named "libomniplg_hypervos.so" would be loaded if found.
• Ability to remotely query a vosapp:config vobject for a list of available plugin module base names (for building configs using mesh or a future GUI editing app.)