Posted on November 21, 2014 at 19:41Progress!
Since the SSI tag <!--#input --> ends up looking like a comment in an HTML page, and the substitution that the SSI engine in the SPWF01S performs gives you results like ''<!--#input -->42'' (where your input was 42), the trick is to use javascript to grab a substring after trimming off the SSI tag, thus (ignore my lack of style, I've been working with javascript for 2 days now):
<!DOCTYPE html>
<html>
<head>
<title>#input parse test</title>
</head>
<script type=''text/javascript''>
window.onload = function() {
var blah = '<!--#input -->'.substr(14)
var value_display = document.getElementById(''value_display'');
value_display.value=blah;
document.getElementById(''slider'').value = value_display.value;
}
</script>
<body>
<input id=''slider'' type=''range'' min=''12'' max=''50'' value=''12'' step=''2'' id=''slider'' ><br>
Value: <input type=''text'' id=''value_display'' value=''12'' >
</body>
</html>
I believe that there is a basic problem with the SSI system in the SPWF01S modules though; if you need more than one value on a page you put in more than one <!--#input --> tag and the micro, on the serial port, will get prompted with an index indicating which value on the screen is asking for data. That's good, but what happens when you have more than one screen asking for data? The first tag on each screen will ask for data using the same index. You need to know the context of which screen is currently being displayed.
Could the firmware development group add a parameter to the #input tag so that I can control the index being sent on the +WIND:56 request for input? That way, when I use multiple web pages, the requests for input can be context free, making the parser on the micro side much easier.
