Okay, done! It's now a skin in its own right, AND it should now work for everyone (famous last words?). The reason I say that is; I belatedly realized that not everyone has appTemp, nor do they necessarily want deltaT - both of which add some complexity to the installation.
appTemp and deltaT are still in there, they are available with some editing of skin.conf plus some low level head scratching; but if you install the skin and run it as is, you'll get windchill in place of appTemp, and deltaT will be ignored completely, all without touching skin.conf. All the required configuration values, for the default setup are picked up by the SLE. Database units don't matter (sort of, but you'll want to fix them if you're metric ) and the php file (wxobs.inc) doesn't need to be opened as all configuration is now done via the accepted skin.conf I've added the imperial conversion to the deltaT, but as its all done outside weewx and direct from the database then the group_units do need to be configured correctly - thus the head scratching. I can't say it's a truly barebones skin.conf, but if the defaults are accepted then nothing more needs to be changed. Everything that is needed is picked up by the SLE. After that well, with options comes complexity. Actually, I lie. The group_units will need enabling in skin.conf as it picks those up from weewx, and weewx defaults to imperial. So, if your station outputs metric units, you'll need to adjust those, as required. If it's a keeper and you want to integrate it with your skin, I'd leave it in its existing subdirectory. Make an empty template for your skin of choice and add *#include wxobs.inc *between the body tags, then edit the head area to point to the correct .js and .css file, and whatever else is required. That should be the easiest and quickest way. Enough... Where is it? Still at - https://github.com/glennmckechnie/weewx-wxobs Cheers Glenn rorpi - read only raspberry pi + weewx: now with scripts <https://github.com/glennmckechnie/rorpi-raspberrypi> On 6 September 2017 at 21:54, mwall <[email protected]> wrote: > lets say that you want to distribute a feature that is not a 'complete' > skin, but just some functionality that someone might add to another skin. > examples include the forecast extension (a service, search list extension, > and skin components), or your own data comparison (just a skin component). > > when you package that extension, include a 'skin' directory with a skin > that shows the functionality. that skin should be simple - probably > nothing more than a bare-bones skin.conf and a single index.html.tmpl, plus > whatever bits the feature needs. the index.html.tmpl should be bare-bones > too - just an illustration of how to put the functionality into a tmpl. > > when someone installs your extension, they get the skin(s). the installer > should *not* touch any other skins. > > in order to add the functionality to an existing skin, one must follow the > pattern of the included skin.conf and index.html.tmpl and manually insert > those bits into the skin that is receiving the feature. for example, there > will probably be some edit of the tmpl (hopefully just adding an #include > and possibly a .css inclusion), and there might be some edit of the > skin.conf (for example, adding to the CopyGenerator or adding a search list > extension package to the CheetahGenerator). > > doing automatic insertion into an existing skin cannot happen with the > current skin framework - there are too many ways it could break things, and > removal would be even more problematic. > > > -- > 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.
