inspection objects - LeFreq/Singularity GitHub Wiki
Inspection objects are for inspecting objects, probably in coordinate space which should change the appearance of the cursor in said space. From there they can click on any object and a pop-up should appear with all the methods they've programmed into the object. Get it`s name, perhaps it`s owner, checking on their behavior perhaps, or variables used.
Such objects could roam the netowrk, looking for data, nodes, or other and report all instances of location, date, time, whatever. Replication of such objects could jam the network, but the OS could automatically limit you tot he number of connections you allow on your own Node.
Automatic methods could have:
- get object name (should be available on all objects),
- Get owner node name (""), email (paypal email?), object cost to run?
- clone (system BEEP if not your own)
- Get size or number of objects within (a fuzzy number that is purposely obfuscated for security, the fuzziness dependent on your level of reputation, but one never really gets to know if it is precise).
- enter object ("insufficient privilege" or a system BEEP (firm) if not the owner of the object).
- get state (is running or insert something that should be queryable or should the object view already encode this through coloration?) (also a fuzzy result or perhaps a user-setable message for those not on the approved list "Contact owner at [email protected].").
Inspection objects have reflection in the the Cloud, rather than colors of their own (beyond the node originator and creator)?
The SecurityModel can or could allow users to specify what inspection primitives it allows (get variable names/state?) Users of their own objects can get variable names and variable states, enter into objects (and get descendant names).
The SET command can specify which users can enter your nodes, for example. Perhaps what data you want to send on a getstate query for users not given enter permission.