On Monday, February 5, 2018 at 9:47:45 AM UTC-5, Cycle London wrote:
>
> Done, but still nothing on the landing page.
>
> #include "../forecast/forecast_strip.inc"
>
> <script>
> populate_strip('wu_strip', 'WU');
> </script>
>
>
try putting the <script>...</script> block after the closing </body> but
before the closing </html>
> Is there some issue with the fact that the include file is in
> /home/weewx/skins/forecast whereas I am referencing it from
> /home/weewx/skins/Standard ? I am certainly using '../forecast...' to
> point to it, but would it be better if that include file were in with the
> Standard skin files?
>
if you intend to do any significant hacking, the preferred approach would
be to create your *own* skin instead of modifying the Standard skin. that
means:
1) create a place for it
mkdir skins/cycle
2) copy everything into it
rsync -arv skins/Standard/ skins/cycle
3) customize it
modify skin.conf, modify *.tmpl, copy in any *.inc files that you use
4) point to it in weewx.conf
[StdReport]
...
[[cycle]]
skin = cycle
...
that way you end up with a self-contained, standalone skin. weewx is smart
enough to not touch your skins when you install an extension or when you
update weewx itself. but this way you can always see how the original
'Standard' skin behaves if you botch something up.
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.
