From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xaver4all To: development@lists.ipfire.org Subject: Re: [PATCH] actual system time and timezone info-bar to ipfire theme Date: Thu, 10 Sep 2015 00:13:41 +0900 Message-ID: <55F04CA5.40700@gmx.de> In-Reply-To: <1441808839.5798.40.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1632056693587567571==" List-Id: --===============1632056693587567571== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, Date: 2015.09.09 - 23:27:19 - From: Michael Tremer > Hi, > > On Wed, 2015-09-02 at 21:02 +0900, Xaver4all wrote: >> I'm sorry that this information is not useful for your workflow, >> but I don't want to waste your and my time, to explain you my working >> scenario. > you must accept a certain discourse about these things. If we would > accept every patch without considering it carefully, we might have > really messed up distribution after a while. Everything that is added > must make sense, must not harm the system and must be maintained by > someone. I accept the discourse and I also like the you (the developer) think twice before you accept patches. I didn't expect that this patch would go in the way it is now. I just wanted to express that this patch is not bound to my personal working scenario. Sorry that I may phrased it a bit harsh. >> But I will give two examples: >> I guess form your mail that you don't use the GUI to check the logs, >> because if you do so how do you tell how old is a given log entry. >> Or if you add a firewall rule which should only apply on workdays >> form 8-16 o'clock. >> So when you do something like this you have to connect via SSH and >> check the time >> and for the rest you use the GUI? IHO this is not very handy. >> Or do you just trust a system that is running 24/7 and you set the >> clock one's and believe that the time doesn't get messed up (even >> with an daily NTP update). There are Country's with daylight saving >> period so timezone offset could also get changed (at least on your >> workstation). > So this a point for showing the system clock I can agree to. I would > like to suggest to add it to the already existing bar at the top, > because I think that it will fit wonderfully to the right of the speed > -o-meter which can be made a bit more narrow to make the needed space. > > The time should definitely include the timezone. I am not sure if secon > ds must be included. A piece of JS that automatically updates the time > is nice, but must be optional for browsers that do not support JS. Like i have written in the forum, by end of month I will provide a different version. I agree to perhaps drop the seconds, as it's a good way to save space. > > Best, > -Michael > >> Kim >>> Hi, >>> >>> On Wed, 02 Sep 2015 04:03:26 +0200, Xaver4all >>> wrote: >>> >>>> But time and timezone (you do not always administrate a machine >>>> that is >>>> in the local timezone, or maybe use the UTC time for your >>>> network) >>>> should really be displayed in GUI. >>>> The Uptime should also be displayed, maybe only on the home site. >>>> I don't want to check the logs when was last reboot, or if I see >>>> uptime >>>> is short I can check the logs for the reason. >>> I don't understand why you need that information. When I want to >>> add a firewall rule or a VPN user, I couldn't care less for any of >>> that information. So, perhaps you want to explain how exactly this >>> is useful for your working scenario. >>> >>> >>> Lars >>> --===============1632056693587567571==--