GMT

[Lucio Diaz]

>  While attempting to guess the location isn't going
> to
> be successful 
> 100%
> of the time, it would probably be better then the 99%
> incorrect that 
> you
> get with always defaulting to 1 set zone.
> Also, are there any other user-set preferences that
> come before the
> date/time page (How do you call the different parts 
of >Setup?) that
>  might help determining location? 
It seems a pain in the @ss to code the whole thing,
taking in acount ALL the countries and their probable
timezones(countries with diferent timezone areas) for
something as easy to the user as to look at his watch
and set the time. I dont mind what standard (if GMT -8
or GMT 0) you chose, but i believe that making it more
elaborate does not worth today when many other things,
quite more important, are waiting to be implemented
(like Networking). I am sure that time will come for
those details.


		
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es

[K McI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lucio Diaz wrote:
| It seems a pain in the @ss to code the whole thing,
| taking in acount ALL the countries and their probable
| timezones(countries with diferent timezone areas) for
| something as easy to the user as to look at his watch
| and set the time. I dont mind what standard (if GMT -8
| or GMT 0) you chose, but i believe that making it more
| elaborate does not worth today when many other things,
| quite more important, are waiting to be implemented
| (like Networking). I am sure that time will come for
| those details.

Here, I have the perfect idea, that I got @ 4A this morning in bed.
Instead of GMT 0 or GMI-8 or anything, let's default it to something
like "Please select your timezone...", which then disappears when
someone selects the drop down menu. This way we don't show preference to
any one zone, prevent ppl from just hitting "Next >" and getting the
wrong zone, and can wait on the more elaborate country/language2zone
attempt code.

Ideas? RFC.

~        -uniQ

PS. Should we also add a section on there for setting up NTP, like, just
a "ReactOS can automatically determine the correct time by querying an
NTP server, select "Settings..." to set this up or change the defaults"
under the "Time" part of "Date and Time" ?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFBqclj7mze81O92HkRAmonAJ97cidUXwBFNb6a93pXGYxFcpMNwQCdGmp4
> dH6AIFTLFL5LFOUURk4OCEE=
> =nwGf
> -----END PGP SIGNATURE-----

[Adam Babcock]

K McI wrote:
>   Here, I have the perfect idea, that I got @ 4A this
> morning in bed.
>  Instead of GMT 0 or GMI-8 or anything, let's default it to something
>  like "Please select your timezone...", which then disappears when
>  someone selects the drop down menu. This way we don't show preference to
>  any one zone, prevent ppl from just hitting "Next >" and getting the
>  wrong zone, and can wait on the more elaborate country/language2zone
>  attempt code.
>  
>  Ideas? RFC.
>  
>  ~        -uniQ
>  
>  PS. Should we also add a section on there for setting up NTP, like, just
>  a "ReactOS can automatically determine the correct time by querying an
>  NTP server, select "Settings..." to set this up or change the defaults"
>  under the "Time" part of "Date and Time" ? 

That seems like the perfect solution actually, now if only we could get 
Redmond to do the same... IMHO NTP should be setup after the initial ROS 
is installed, this way they can test their settings without having to 
load all the network drivers during installation. If I understand what 
you are saying here you want to use the NTP query to determine the 
timezone? The problem with this is that I believe that if no timezone is 
given to the NTP server it guesses based on IP, which is not always 
accurate. I say stick with the "Please select your timezone..." and then 
have the user setup NTP if they so choose after ROS is installed.

[K McI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Adam Babcock wrote:
| That seems like the perfect solution actually, now if only we could get
| Redmond to do the same... IMHO NTP should be setup after the initial ROS
| is installed, this way they can test their settings without having to
| load all the network drivers during installation. If I understand what
| you are saying here you want to use the NTP query to determine the
| timezone? The problem with this is that I believe that if no timezone is
| given to the NTP server it guesses based on IP, which is not always
| accurate. I say stick with the "Please select your timezone..." and then
| have the user setup NTP if they so choose after ROS is installed.

No I mean give them the message, but in a separate subsection of the
"Time" part of the panel, have an option to configure NTP, like Enabled
or not, the server (If there's a custom one), when to update the time,
etc, etc, so you can set it up in Setup, and not have to wait until
you're @ the desktop.

Sorry if I got the 2 confused, I'd be happy to just let the timezone
default to nothing until someone gets around to making a good guessing
algorithm (If that ever happens ;)).

Any better?

~          -uniQ
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFBqgVN7mze81O92HkRAjHAAJ972v5zEt+EjGXx/oeceS16ZqbIIgCeJkph
> 7aeSSR/1u4IWAG5Ib0EEsxM=
> =egFR
> -----END PGP SIGNATURE-----

[Adam Babcock]

K McI wrote:

>   Any better? 
Much, I misunderstood you on that one. So, it is settled? Default to 
nothing?

[Alex Ionescu]

Adam Babcock wrote:

>  
>  That seems like the perfect solution actually, now if only we could 
>  get Redmond to do the same... IMHO NTP should be setup after the 
>  initial ROS is installed, this way they can test their settings 
>  without having to load all the network drivers during installation. If 
>  I understand what you are saying here you want to use the NTP query to 
>  determine the timezone? The problem with this is that I believe that 
>  if no timezone is given to the NTP server it guesses based on IP, 
>  which is not always accurate. I say stick with the "Please select your 
>  timezone..." and then have the user setup NTP if they so choose after 
>  ROS is installed.
>  
Windows does automatically set up NTP after installation already. For 
the timezone argument, I just thought about the fact that Windows users 
have been living with the Redmond default for ages. I even have a reflex 
to press the up arrow the exact number of times it takes me to get to 
EST, I don't even look at the combo box anymore.

Best regards,
Alex Ionescu

[K McI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Ionescu wrote:
| Windows does automatically set up NTP after installation already. For
| the timezone argument, I just thought about the fact that Windows users
| have been living with the Redmond default for ages. I even have a reflex
| to press the up arrow the exact number of times it takes me to get to
| EST, I don't even look at the combo box anymore.

I know, I was just thinking that maybe we could let the installer
configure NTP settings during install, since it IS part of "Time and Date".

We could maybe have "Please select..." be in the same "location" as
-8
on the list, so that when you hit up or down it still resolves itself
like normal, but is slightly different, looks more neutral, and isn't a
valid choice. What's say ;)?

~     -uniQ
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFBqh1R7mze81O92HkRAn6GAJ9VCl35HlqOmXU4ipcauF0clUrbywCgonM0
> 7qh2C3+LSDwOOzr19FfGc1g=
> =I3mE
> -----END PGP SIGNATURE-----