On Monday, February 5, 2018 at 11:36:16 AM UTC-5, Cycle London wrote:
>
> I can't see anything in the 'debugger' but then I'm not a web dev.
>
you need to create a div for the javascript to populate.
somewhere in the html hierarchy do this:
<div id="wu_strip"></div>
the strip data will be inserted into that div when
populate_strip("wu_strip", "WU") is invoked
the syntax for populate_strip is:
populate_strip(div_id, data_id, display_settings)
where div_id is the id of the div that will receive the data, data_id is
the identifier of the data set that contains the data, and display_settings
is an option override of any parameters such as orientation, show_tides,
show_snow, etc.
by convention, the data id is the forecast source identifier. in this case
'WU'
to summarize: you must first include the strip .inc file, then you must
create a div with an id of your choosing, then you must invoke the
populate_strip function with the div id and the data id.
including table display is somewhat easier - there is just the .inc
inclusion, since it is not javascript. this is why there are xxx.html.tmpl
files in the default forecast skin, so that there will be fully functional,
minimal examples from which to copy.
suggestions about how to improve database query performance,
javascript/html rendering performance, and/or simplification of the
install/customize process would be very much appreciated.
m
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
