Thanks m, I'm confident enough with wee_extension to install a stand-alone skin, but a partial installation is beyond me. I can't get my head around adding the extras to an existing entry - in this instance the copy_once stanza in skin.conf...
[CopyGenerator] > > copy_once = (leave existing values) , datepicker.css, wxobs.css, > datepicker.js, links.inc > I tried it by duplicating the line with just my additions, but I got the dreaded "*report ignored. duplicate keyword error" :-) Hmm, Rereading your response suggests it could be acceptable to just do that copy_once appending manually? ie: package the bulk of it up as a skin (under install.py instructions) with a note of some handwork to complete the installation. Yes? My season installation is at http://203.213.243.61/weewx/ It's not a pristine version - there's a few additions and some shuffling involved eg: I prefer the widgets (summary blocks?) on the right side of the screen, just a small zig away from the scroll bar where I find the cursor spends most of its time. That action has possibly broken its resizing abilities - I only use it from my desktop though so I don't know. I've found it to be excellent for my needs, very easy to extend. Although I did come unstuck in the early days when I tried to use the index.html.tmpl as a template for my own pages, the image sizing in the body became a bit confronting :). Once I woke up to the culprit being the <div id="plot_group"> I was able to quickly move on though. The #includes make it very easy to propagate any extras (eg: links.inc, about.inc ) across multiple pages. Cheers Glenn rorpi - read only raspberry pi + weewx: now with scripts <https://github.com/glennmckechnie/rorpi-raspberrypi> On 6 September 2017 at 20:39, mwall <[email protected]> wrote: > glenn, > > this is very nice work! > > to make it easier for others to try, package it as an extension (see the > 'basic' skin in the examples directory for details of how to structure an > skin as an extension). > > some skins are complete, end-to-end affairs. others are just one or two > components that are intended to be integrated into other skins. either > way, when packaged as an extension they should work out-of-the-box. in the > latter case, the skin installed by the extension won't be a 'complete' > skin, but should illustrate functionality, and the readme should describe > how to integrate that functionality into another skin. > > i am interested in how you have integrated into the Seasons skin. > hopefully that skin is easier to extend than the Standard skin - that is > the intent of the summary blocks and the use of the #include directive. > > 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. > -- 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.
