Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).
I don't exactly see the use of it as there will be considerable time lapse between this and the actual use of the tag somewhere in the code which picks it up.
No doubt somebody sees its use and asked for it. Could you explain?
2) Would it be possible to design a mechanism by which one could ask for the value of (a) tag(s) i.s.o. making a file, running it at a certain frequency through Cumulus' process mechanism. The result would be the value(s) either async or sync, but with an 'immediate' timing meaning a value when needed. Of course not randomly external, but by the user running Cumulus and not through a command line interface. So I am thinking about IPC. I see use for it as it makes it possible to program alongside Cumulus without being dependent on it, apart for the fact that it is active.
I don't exactly see the use of it as there will be considerable time lapse between this and the actual use of the tag somewhere in the code which picks it up.
No doubt somebody sees its use and asked for it. Could you explain?
Maybe to attribute an accurate time to the data (extracted from other tags) that is being displayed?
HansR wrote: ↑Tue 14 Apr 2020 1:02 pm2) Would it be possible to design a mechanism by which one could ask for the value of (a) tag(s) i.s.o. making a file, running it at a certain frequency through Cumulus' process mechanism. The result would be the value(s) either async or sync, but with an 'immediate' timing meaning a value when needed. Of course not randomly external, but by the user running Cumulus and not through a command line interface. So I am thinking about IPC. I see use for it as it makes it possible to program alongside Cumulus without being dependent on it, apart for the fact that it is active.
freddie wrote: ↑Tue 14 Apr 2020 1:21 pm
Could you pop this one in the appropriate subforum, please?
Ah, misplaced, yes.
You are the forum manager, could you replace or do you expect to ask the same question twice?
freddie wrote: ↑Tue 14 Apr 2020 1:21 pm
Maybe to attribute an accurate time to the data (extracted from other tags) that is being displayed?
There is a whole Date & Time section on the wiki page of the webtags.
How accurate do you want to be in a weather app? It's not rocket science you know.
It's not about astronomy either although there are a lot of practitioners of that around
freddie wrote: ↑Tue 14 Apr 2020 1:21 pm
Could you pop this one in the appropriate subforum, please?
And maybe you could put this board under the MX boards at the top of the front page within the Cumulus frame. Two frames about the same item (being Cumulus) seems a bit too much.
That would be more logical than at the bottom, unless that is the place of wanted developments
Like all the current date tags, it stamps the time the record was created. But date time strings are a really poor way of transferring time information between programs, they are subject to parsing and time zone issues. Using a JavaScript (or Unix, divide by 1000) timestamp allows much simpler transfer of the information that is also tz independent.
So I'm not thinking text based (html say) use of the tags for displaying to the end user here, rather think JSON type data, where it is almost the norm to use Unix timestamps.
freddie wrote: ↑Tue 14 Apr 2020 1:21 pm
Maybe to attribute an accurate time to the data (extracted from other tags) that is being displayed?
There is a whole Date & Time section on the wiki page of the webtags.
Indeed there is. I was just thinking of a potential use.
HansR wrote: ↑Tue 14 Apr 2020 1:42 pm
How accurate do you want to be in a weather app? It's not rocket science you know.
To reflect your update interval, I guess. If you have a 5-min update interval and you are looking at data that is nearly 5 minutes old then it would be nice to know when the data was read, rather than assuming it is for now.
freddie wrote: ↑Tue 14 Apr 2020 1:21 pm
Could you pop this one in the appropriate subforum, please?
And maybe you could put this board under the MX boards at the top of the front page within the Cumulus frame. Two frames about the same item (being Cumulus) seems a bit too much.
That would be more logical than at the bottom, unless that is the place of wanted developments
