Welcome new user! You can search existing questions and answers without registering, but please register to post new questions and receive answers. Note that due to large amounts of spam attempts, your first three posts will be manually moderated, so please be patient.
We have moved to a new forum at http://jevois.usc.edu, please check it out. The forum at jevois.org/qa will not allow new user registrations but is maintained alive for its useful past questions and answers.
Welcome to JeVois Tech Zone, where you can ask questions and receive answers from other members of the community.

Plans for making "Info" tab content easy to create?

0 votes
Do you have plans of making future releases of Inventor able to read Html code created outside of  the JeVois environment? For example, if I create it using MS Word, then save it in .html format with the proper name, will Inventor be able to display it? Would it be possible to supply a template file that can be copied and filled in, then placed in the folder with the associated script?

If not, are there plans to make creating the content of the Info tab as easy as it currently is to create custom code to run on JeVois?
asked Jul 21, 2018 in Programmer Questions by Billbo911 (1,110 points)
edited Jul 22, 2018 by Billbo911

1 Answer

+1 vote

yes, the easiest is:

- create a new python module in JeVois inventor (CTRL-N)

- fill in all the info and create the module

The module will have a stub modinfo.html stored to microSD as part of the creation process. Look on the microSD under JEVOIS:/modules/VENDOR_YOU_CHOSE/MODULE_YOU_CHOSE/modinfo.html

In there, search, towards the end, for "This module was created with JeVois Inventor". This is the HTML that will appear in the Info panel. So just paste your new HTML and it should show up in the inventor.

Caveat: there is some stuff in the stub HTML that has incorrect values and that is not parsed yet by the inventor. The incorrect values are here as placeholders. You can ignore them, but keep them so the parser does not choke in the future if we decide to start looking for them. Those are: whether the module supports USB video or headless, and the list of supported video mappings.

Below is the stub used by the Inventor. The Inventor replaces variables @MODULE@, @VENDOR@, etc in there by the values provided when creating the new module. Whatever you edit, make sure you do not insert extra line endings, spaces, etc that could prevent the parser state machine described in the previous post from finding the start and end tags it is looking for.

<html><head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META HTTP-EQUIV="Content-Language" CONTENT="en-US"><META NAME="robots" CONTENT="index, follow">
<META NAME="rating" CONTENT="General"><META NAME="distribution" CONTENT="Global">
<META NAME="revisit-after" CONTENT="15 days"><META NAME="author" CONTENT="Laurent Itti, JeVois">
<META NAME="description" CONTENT="JeVois Smart Embedded Machine Vision Toolkit - module DemoEyeTracker">
<link href='http://fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,600italic,700italic,800italic,400,300,600,700,800' rel='stylesheet' type='text/css'>
<link rel='stylesheet prefetch' href='https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.4.0/css/font-awesome.min.css'>
<link rel="stylesheet" type="text/css" href="/modstyle.css">
</head> <body>
<table class=modinfo><tr><td>
<table class=modinfotop><tr><td><a href="/moddoc/@MODULE@/modinfo.html"><img src="/moddoc/@MODULE@/icon.png" width=48></a></td>
<td valign=middle><table><tr><td class=modinfoname>@MODULE@</td></tr>
<tr><td class=modinfosynopsis>@SYNOPSIS@</td></tr></table></td></tr></table></td></tr>
<tr><td width=100%><table class=modinfoauth width=100%><tr><td>By @AUTHOR@</td><td align=center>@EMAIL@</td><td align=center>@WEBSITE@</td><td align=right>@LICENSE@</td></tr></table></td></tr>
<tr><td><table class=videomapping><tr><td class=videomapping>
<table class=moduledata><tr><td class=moduledata>&nbsp;Language:&nbsp;@LANGUAGE@</td><td class=moduledata align=center>Supports mappings with USB output:&nbsp;Yes</td><td class=moduledata align=right>Supports mappings with NO USB output:&nbsp;Maybe&nbsp;</td></tr></table>
</td></tr>
<tr><td class=videomapping><small><b>&nbsp;Video Mapping: &nbsp; </b></small><tt>GREY&nbsp;640&nbsp;480&nbsp;30.0&nbsp;YUYV&nbsp;640&nbsp;480&nbsp;30.0&nbsp;JeVois&nbsp;DemoEyeTracker</tt></td></tr>
<tr><td class=videomapping><small><b>&nbsp;Video Mapping: &nbsp; </b></small><tt>GREY&nbsp;320&nbsp;240&nbsp;60.0&nbsp;YUYV&nbsp;320&nbsp;240&nbsp;60.0&nbsp;JeVois&nbsp;DemoEyeTracker</tt></td></tr>
<tr><td class=videomapping><small><b>&nbsp;Video Mapping: &nbsp; </b></small><tt>GREY&nbsp;176&nbsp;144&nbsp;120.0&nbsp;YUYV&nbsp;176&nbsp;144&nbsp;120.0&nbsp;JeVois&nbsp;DemoEyeTracker</tt></td></tr>
</table></td></tr>
<tr><td><div class=container>
<div class=galleryItem><a href="screenshot1.png"><img src="screenshot1.png"></a></div>
  </div></td></tr><tr><td class=modinfodesc><h2>Module Documentation</h2><div class="textblock"><p>This module was created with JeVois Inventor. Full documentation parsing is not yet supported.</p>
</div></td></tr>
</table>
</body></html>

answered Jul 23, 2018 by JeVois (46,580 points)
...