[Ovmsdev] Registering / Web pages for Scripted Implementation

[Michael Geddes]

With this talk about running out of space on the devices, I wanted to open
up a discussion about how we might organise a vehicle implementation in
Duktape.

To clarify - I'm not sure about all these pieces- they are just suggestions
that I would love some feedback on.


   -  Have a special 'Duktape' vehicle that then can be set to load up a
   special folder location containing all the pieces
      - Add in an extra folder for events? (cf requiring DukTape event
      registration)
   - Be able to set the vehicle name (for the menu)
   - Allow adding the standard battery monitor page (I have code for
   updating the bms code nearly ready to ship)
   - Adding custom configuration pages (I'm thinking a call-back to fetch
   the page layout or a callback object or something?)
   - Defining ranges for the main dashboard
   - Can already add duktape implemented commands - should there be a
   specific folder for vehicle implementation or leave as-is?

What other pieces are we missing to be able to handle new vehicles in
duktape?

//.ichael

.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20260207/916c47d3/attachment.htm>