<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Also missing:<br>
<ul>
<li>OvmsEvent (raise)<br>
</li>
<li>OvmsNotify (raise)<br>
</li>
</ul>
…these would be especially valuable for communication between
module and web plugins as well as MQTT listeners.<br>
<br>
We also need an HTTP/HTTPS client accessable from scripts. Our
OvmsHttp implementation needs to be replaced by the IDF HTTPS
client.<br>
<br>
Simple file I/O for scripts would also be valuable (e.g. scripts
writing custom data logs to SD).<br>
<br>
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.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
Am 08.10.19 um 09:45 schrieb Mark Webb-Johnson:<br>
</div>
<blockquote type="cite"
cite="mid:EDB9DCD3-8193-4730-B473-4D48CDB925FE@webb-johnson.net">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div class=""><br class="">
</div>
Michael’s work has brought up an issue that we seem to be missing
some javascript integrations.
<div class=""><br class="">
</div>
<div class="">We have:</div>
<div class=""><br class="">
</div>
<div class="">
<ul class="MailOutline">
<li class="">OvmsCommand</li>
<li class="">OvmsLocation</li>
<li class="">OvmsMetrics</li>
<li class="">OvmsVehicle</li>
<li class="">PubSub (to ovms events)</li>
</ul>
</div>
<div class=""><br class="">
</div>
<div class="">Obvious ones missing are:</div>
<div class=""><br class="">
<div class="">
<ul class="MailOutline">
<li class="">OvmsConfig</li>
<li class="">OvmsWebServer</li>
</ul>
</div>
</div>
<div class=""><br class="">
</div>
<div class="">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?</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.</div>
<div class=""><br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="144">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>