Cumulus Support

Another update. Gerrit has added KnobStyle (and fixed the centre knob positioning issue), and I have added the ability to change the compass pointer type dynamically (only types 1, 2, 3 are valid).

I think this is getting good enough to make up a 'proper' page - the browser support is an issue, but it is probably only me that will ever look at the page anyway! I want a nice dashboard that I can leave on a screen that is visible from a distance.

LOL well they are looking fine on my android tablet , only need my values

Funnily enough I'm just working on that!

I post a photo moment please

Problem: I based that page on my cumuluswebtags.js file, I'll convert it to using realtime.txt....

Well the photo isn't very sharp the page is loaded in landscape mode on a android 3.1 (honeycomb) tablet the browser is a chrome adattion from google

mcrossley wrote:Problem: I based that page on my cumuluswebtags.js file, I'll convert it to using realtime.txt....

Next problem will be the units and seperators

Ah, I can't use realtime.txt as it doesn't have todays max/min figures etc that I use sorry.

Well I can use the .js or not ?

mcrossley wrote:Ah, I can't use realtime.txt as it doesn't have todays max/min figures etc that I use sorry.

Which ones do you need?

The present incarnation using the following (the 0/1 indicates if it is realtime.txt or not)... Now we could probably live without some of them, but it seems quite a bit to add to realtime.txt.

I've thought this before, maybe we should have an 'official' realtimeExtras.txt file so that everyone uses the same extensions if and when required, at the moment everyone is doing their own thing which makes sharing ideas more difficult.

Or, have an option in Cumulus (I can hear Steve groaning from here ) that parses a realtimeExtras.txt file for webtags and appends a second line to realtime.txt with the additional values. Then you keep the first line as standard so new standard values can be appended in the future, and the second line contains the extras. This may well break some existing pages, but does mean you can readLine() the standard vales and the extras separately. This has the advantage the Cumulus only uploads one file, and client downloads one file, but the danger of breaking backward compatibility probably makes it a on-starter.

mcrossley wrote:I've thought this before, maybe we should have an 'official' realtimeExtras.txt file so that everyone uses the same extensions if and when required, at the moment everyone is doing their own thing which makes sharing ideas more difficult.

Yes, that's something I think about quite often. The original idea of the realtime.txt file was something very short with values that changed relatively frequently. So rather than keep adding to that with items that don't change very often, I think a second optional file would be better.

Even more efficient, only upload the extras file if a value in it changes, so all the max/min values will be pretty static for most of the day. Harder to do if you have an external template file, but an external file means additions are not dependent on Cumulus releases.

Oh, I think I forgot to mention it, but the gauges do render OK on the iPod/iPhone - so long as there aren't too many of them, otherwise you hit the max script runtime limit which seems to be somewhere around 5-10 seconds.

Here is a single temperature gauge that works fine on my daughters iPod:

http:weather.wilmslowastro.com/gaugesB/gaugeSmall.htm

Casualty on TV
If I make the default gauges use the more processor efficient design features of the gauges, all 8 gauges will display correctly on the iPod. The frame surrounds with 'shiny' radial effects are the worst culprits (CHROME, and SHINY_METAL).