Cumulus Support

I have just noticed that the web tag parser allows for parameters! This means that specifying the format for the date and/or time tags would be possible, e.g <#YearTempHT format=hh:mm:ss>, and Cumulus could generate the time in whatever format was specified. I was proposing to allow the format of web tag dates and times to be configurable in Cumulus, but this way is more flexible and probably easier to implement.

Does anyone have any other ideas for parameters for existing web tags, other than the date and time ones?

For those that want it - could it cope with eg.
<#YearTempHT format=hh:mm ' on ' dd mmm> ?

What (if any) sort of parsing would be available for 'string' output ?

Might become a bit of a headache !

beteljuice wrote:For those that want it - could it cope with eg.
<#YearTempHT format=hh:mm ' on ' dd mmm> ?

Yes, but with spaces, it would just have to be enclosed in quotes:

<#YearTempHT format="hh:mm on dd mmm">

I'd just use the standard Delphi date/time format strings, which allow for any non-formatting text to be included.

What (if any) sort of parsing would be available for 'string' output ?

Do you have something specific in mind?

So Steve, would last rain rain tip be something like <#LastRainTipISO format="hh:mm dd mmm yyyy"> ????

I like it.

I really don't like the words on and at in webtags because these can't be translated.

captzero wrote:So Steve, would last rain rain tip be something like <#LastRainTipISO format=hh:mm ' on ' dd mmm yyyy> ????

Yes, but again, the whole parameter value would need to be in double quotes as it contains spaces:

<#LastRainTipISO format="hh:mm on dd mmm yyyy">

nitrx wrote:I really don't like the words on and at in webtags because these can't be translated

I thought the same once I looked at it and edited my post

nitrx wrote:I really don't like the words on and at in webtags because these can't be translated.

Well, yes, that's the whole point. You put whatever you want in the parameter.

Sounds good, I'd use it. It allows more flexibility.

I suppose PPL may also use it to display their long and lat in decimal degrees ie <#longitude=27.0004.....>

steve wrote:

nitrx wrote:I really don't like the words on and at in webtags because these can't be translated.

Well, yes, that's the whole point. You put whatever you want in the parameter.

Oh sorry I misunderstood I thougt the string was fixed

Captzero - don't edit posts that have been answered - It doesn't make sense to the reader !

Steve - presumeably this can only be applied to <#webtags> that contain a single item of data ?
eg. a timestamp
... and could not be applied to something that is already a formatted construct ?

eg. "7.4 C" could NOT become "7.4 Celcius" NOR "7 C" ?

beteljuice wrote:Captzero - don't edit posts that have been answered - It doesn't make sense to the reader !

Sometimes you are all just too fast for my very bad typing skills. (that took me 5 mins to type)

beteljuice wrote:eg. "7.4 C" could NOT become "7.4 Celcius" NOR "7 C" ?

I don't think there are many that are like that? The all-time record dates have 'on' and 'at' in them, and cloudbase always has ' ft' or ' m' on the end. These could become the defaults, and if a parameter was supplied, that could override the default. For example:

<#cloudbase> would give: 1020 ft
but
<#cloudbase displayunits=n> would give: 1020

You could also override the units for the data. So, if you were using Celsius in Cumulus

<#temp> would give 5.4
but
<#temp units=F> would give 41.7

Hmmm. I'm making a lot of work for myself here

captzero wrote:Hmmm. I'm making a lot of work for myself here

Yeah... and what about wind...knots, m/s, kph, mph.

You are a glutton for punishment.

Hi Steve,
should the new "format" option work in all time records
I just unsuccesfully try this : <#TtempH format="à hh:nn le dd mmmm yyyy"> in recordT file