Hi, I just updted MyMidNite with the latest changes and features prior to release. Please let me know if you have any issues. At this point I think all features are frozen for the moment and I am concentrating on getting the site solid enough for folks to use.
Here is the list:
- make sure new accounts have help and unassigned warning enabled by default
- fix time handling â€" sometimes the graph comes up as 1970 â€" something wrong with “today†function in msdifc_system.
- need to do data export to csv file.
-add system is now broken???
- add contact webmaster form (maybe with auto generation of userID, device IDs and system ids for easy identification)
- daily accumulation running for 7 days instead of for “testerdayâ€
- daily totals â€" manage different timezones problem (basically save update until Australia wraps)
- user fields: I need to properly add the help and unassigned fileds to the user profile so they work correctly. At the moment there is only one show unnassigned warning and one show help shared between all users.
- add device doesn't add device to current page or load data from server (force page reload if possible would do the trick)
SOrry, my kids are swarming now wanting to type in their names, so if there's anything weird looking on the list I'm blaming them.....
Thanks for all your help and suggestions.
-A
Andrew,
Time zone still not correct. Display changes to new day ay Midday, 12 noon, instead of 12 hours previously at Midnight. eg its now 11.13am 23 July here BUT graph is still at 22 July. Data for 23 July is squeezed to right edge of graph window.
Duplicated the Show unassigned warning and SHow Help prompts below the Personal contact form box.
dgd
Thanks Dgd!
Time zone change is still rubber ducked, changes at midday instead of 12 hours earlier at midnight.
So no current day graph data if mymidnite used before midday.
What happened to the alerts associated with each Classic? Great idea but removed? :-\
Sorry but CSV file dump facility is not a valid replacement for the node14/15 displays. This was a backward step. Can't do it anyway on ipad but could display nodes. Is there some sort of mental blockage or just stubbornness about providing a node14 type list for each classic?
If MN can't do it then can Ryan re-enable it on another server somewhere? (And I actually liked his weather station reports as well!)
My general feeling is that we didn't get anything for a weeks outage and in fact moved backwards as more was removed for the sake of 'release'
Dgd
The weeks outage had nothing to do with features. It was partly because the scripts where not in place to auto update classics as they are built, People where mad because they could not register there NEW classic so we took down My MidNite during the duration of the work on the back end.
Again this is still a work in progress and the good thing is we all can write our own programs as well so if My MidNite is moving to slow there is still a solution.
I can tell you Andrew is working steady on this and there is a lot people do not see or understand. This is being built for more than Classics so this adds a lot of back end work that may have nothing to do with what you see or use on My MidNite now. As far as Node 14 or 15 the issue is huge amounts of data. I do see a tab on each individuals account labeled "Tabular" or something and this would be the data only no graphs.
We could take it completely off line while the finishing touches are put on but that seems foolish as it is such a powerful wonderful tool so I ask that we all have a little patience and understanding.
Ryan
Ok, thanks for explanation, I will just await progress.. although as you hinted, I may be better just developing my own monitoring software.
Dgd.
Node 14 and 15 were really for our internal use only. You have Node 15 data available on your page at the moment. Each Classic has a "last updated" field on the badge which is the node 15 information of your classics. You have no right to see when other peoples' devices have called in. The same is true of node 14.
This has nothing to do with stubbornness and personal attacks are not appreciated on this forum. We have a limited amount of time and a very long list of features and bug fixes for a long list of people. This Beta forum is for helping us move in the right direction, but I'm afraid we can't implement every whim of a few customers. If a feature hasn't been implemented it is because it was deemed too much work or time to do so before general release. Many of everyone's suggestions are on the list of features to be implemented as we move forward.
Alerts were removed in favor of fixing scripts so other customers could log onto the site. I will implement this feature fully when I get time to do so. I have worked hard the last few years to get this thing up and running. I'm sorry if anyone finds the site unusable in its current form but everyone is free to use it or not.
I will look further into the timezone issues once I have cleaned up some other issues.
Quote from: atop8918 on August 02, 2013, 02:15:06 AM
Node 14 and 15 were really for our internal use only. You have Node 15 data available on your page at the moment. Each Classic has a "last updated" field on the badge which is the node 15 information of your classics. You have no right to see when other peoples' devices have called in. The same is true of node 14.
The value of the node15 display was seeing a text list of the last 2 to 3 hours connection info, something the current graph display does not do.
Seeing other people's data was of no interest.
Quote
This has nothing to do with stubbornness and personal attacks are not appreciated on this forum.
Sorry you take offence BUT the node 14/15 type text list was asked for by several users AND it was already available but not via the mymidnite graph display SO was it impossible to make each Classic's last few hours of connection info available as a text list. Methinks not.
Quote
We have a limited amount of time and a very long list of features and bug fixes for a long list of people. This Beta forum is for helping us move in the right direction, but I'm afraid we can't implement every whim of a few customers. If a feature hasn't been implemented it is because it was deemed too much work or time to do so before general release. Many of everyone's suggestions are on the list of features to be implemented as we move forward.
Whims? Ok, my enthusiasm is now well blunted... I give up
Dgd