>From a cold start (deleting public_html) oldskin: Nov 12 18:52:10 nuc wee_reports[6707]: cheetahgenerator: Generated 15 files for report StandardReport in 0.68 seconds Nov 12 18:52:11 nuc wee_reports[6707]: genimages: Generated 49 images for StandardReport in 0.92 seconds
newskin: Nov 12 18:52:59 nuc wee_reports[6721]: cheetahgenerator: Generated 5 files for report StandardReport in 0.41 seconds Nov 12 18:53:00 nuc wee_reports[6721]: genimages: Generated 53 images for StandardReport in 0.99 seconds Clearly you gain a little bit doing javascript overlays. This is on an Intel NUC. The command lscpu gives: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 69 Model name: Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz Stepping: 1 CPU MHz: 1299.987 CPU max MHz: 2600.0000 CPU min MHz: 800.0000 BogoMIPS: 3791.01 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 3072K More later. Getting called to dinner! -tk On Sat, Nov 12, 2016 at 6:45 PM, mwall <[email protected]> wrote: > On Saturday, November 12, 2016 at 9:34:46 PM UTC-5, Tom Keffer wrote: >> >> Not sure what sort of feedback you're looking for. I assume this is a >> work-in-progress? >> > > my intent is to replace Standard with something more modern, more > functional (wrt sensors and out-of-box experience), and with less > copy/paste throughout. > > so any feedback is appreciated, from look-and-feel to implementation. > > it would be nice to know how long newskin Standard takes to generate > compared to master Standard, on various hardware. > > > >> Why the decision to break out some of the labels, (e.g. >> $Extras.Labels.celestial_title) but not all of them? >> >> Why the decision to use $Extras.show_extraTemp1 instead of just >> autodetecting ? If we want a user to manually toggle whether extra sensors >> are shown, we should probably create a special tag such as >> $showSensor.extraTemp1. >> > > this part is definitely in progress. > > labels: translation is a pain, mostly because one must hunt and peck > through each file to find the strings that must be translated. the use of > $obs.label.* is an attempt to do it all using the labels specified in > skin.conf, especially for self-contained parts such as the hilo include. > however, while that makes sense for observations, it might not make sense > for thinks like the celestial stuff. that would require a different > pattern, such as putting the labels in Extras. > > conditional inclusion: the skin should require no configuration, so it > should autodetect data/sensors. however, there are cases where we know > some people do not want to display certain data. inside temp/hum is one > example. > > hopefully neither of these will be an obstacle to the primary goal of a > Standard refresh. > > m >
