Also missing:
- OvmsEvent (raise)
- OvmsNotify (raise)
…these would be especially valuable for communication between
module and web plugins as well as MQTT listeners.
We also need an HTTP/HTTPS client accessable from scripts. Our
OvmsHttp implementation needs to be replaced by the IDF HTTPS
client.
Simple file I/O for scripts would also be valuable (e.g. scripts
writing custom data logs to SD).
Script access to protected config values could be granted by a
general API key mechanism, as planned for the web API
(/api/execute). I.e. the script needs to use a valid API token to
access protected configs. An API token could include a set of
specific grants & denies, so we can extend that as needed to
also cover other potentially critical stuff like network &
file access. Similar to App permissions on Android / iOS.
Regards,
Michael
Am 08.10.19 um 09:45 schrieb Mark Webb-Johnson:
Michael’s work has brought up an issue that we seem to be missing
some javascript integrations.
We have:
- OvmsCommand
- OvmsLocation
- OvmsMetrics
- OvmsVehicle
- PubSub (to ovms events)
Obvious ones missing are:
I can do OvmsConfig, but one question: Do we allow
scripts access to protected config values? I think not (as that
would void the entire protection system with a ’script eval
JSON.print(…)', but is a limitation). Comments?
It would be interesting to see scripts extend the
OvmsWebServer, so urls could be mapped to scripts - but not sure
of the practical use of that vs plugins.
Regards, Mark.
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev