On Wed, Aug 26, 2009 at 7:48 PM, PhistucK phist...@gmail.com wrote:
Bearing the upcoming Chrome OS in mind, this should be taken into account
quite strongly.
I don't think it's appropriate to speculate on what will and will not be
useful for Chrome OS until more details about it are made
On Wed, Aug 26, 2009 at 7:48 PM, PhistucKphist...@gmail.com wrote:
Bearing the upcoming Chrome OS in mind, this should be taken into account
quite strongly.
Regular programs will probably not move cleanly and nicely from Windows to
Chrome OS, but, at least, Google products should migrate
On Wed, Aug 26, 2009 at 10:23 AM, Avi Drissmana...@google.com wrote:
I've heard people proclaim the principle of being able to copy a profile
across systems as being a deciding factor for certain changes (e.g. the
history epoch change). However, it doesn't seem to be universally held or
I think this is one of those things that aren't worth the effort. Brett's
change was also to fix other bugs, so it wasn't just for this. I'd be
surprised if people spend time to fix bugs solely for this.
On Wed, Aug 26, 2009 at 10:23 AM, Avi Drissman a...@google.com wrote:
I've heard people
On Wed, Aug 26, 2009 at 10:23 AM, Avi Drissman a...@google.com wrote:
I've heard people proclaim the principle of being able to copy a profile
across systems as being a deciding factor for certain changes (e.g. the
history epoch change). However, it doesn't seem to be universally held or
On Wed, Aug 26, 2009 at 12:28 PM, Darin Fisherda...@chromium.org wrote:
I've heard people proclaim the principle of being able to copy a profile
across systems as being a deciding factor for certain changes (e.g. the
history epoch change). However, it doesn't seem to be universally held or
On Wed, Aug 26, 2009 at 10:23 AM, Avi Drissmana...@google.com wrote:
- Is profile platform independence a guiding principle?
[...]
- Is it worth rewriting today's code that doesn't conform
It didn't seem to be when I asked about password storage a while back.
Passwords aren't even portable
Then password management would also fall under the category of can't be
made portable and that's fine.
It's just that I've heard profile platform independence tossed around as
being a guiding principle and I was surprised that some people treated it as
so.
Avi
/who wonders how it fits into
On Wed, Aug 26, 2009 at 12:16 PM, Brett Wilson bre...@chromium.org wrote:
On Wed, Aug 26, 2009 at 10:23 AM, Avi Drissmana...@google.com wrote:
I've heard people proclaim the principle of being able to copy a profile
across systems as being a deciding factor for certain changes (e.g. the
On Wed, Aug 26, 2009 at 12:59 PM, Jeremy Orlowjor...@chromium.org wrote:
I really like the idea of being able to move people between
operating systems and just bringing the profile along
without having to export and import...
(seems to me there are online services that offer that
On Wed, Aug 26, 2009 at 12:41 PM, Darin Fisher da...@chromium.org wrote:
On Wed, Aug 26, 2009 at 12:16 PM, Brett Wilson bre...@chromium.orgwrote:
On Wed, Aug 26, 2009 at 10:23 AM, Avi Drissmana...@google.com wrote:
I've heard people proclaim the principle of being able to copy a profile
On Wed, Aug 26, 2009 at 12:48 PM, Dan Kegel d...@kegel.com wrote:
On Wed, Aug 26, 2009 at 12:28 PM, Darin Fisherda...@chromium.org wrote:
I've heard people proclaim the principle of being able to copy a profile
across systems as being a deciding factor for certain changes (e.g. the
Is the OS in the user-agent string?
Mozilla/5.0 (*Windows*; U; Windows NT 6.0; en-US) AppleWebKit/532.0 (KHTML,
like Gecko) Chrome/3.0.195.6 Safari/532.0
There's a chance that http resource caches will contain data tweeked per OS.
Maybe for cosmetic purposes... to make it look more OSX'y or
BTW we have two separate prefs files, Preferences and Local State
to support this sort of thing in the pref system at least.
Whether or not people put the right settings in the right data stores
is another question.
-Ben
On Wed, Aug 26, 2009 at 10:23 AM, Avi Drissmana...@google.com wrote:
FWIW, I think this distinction is confusing without good use cases
backed by tests to enforce the two separate files. I think we should
just merge them for now (which would simplify the code and be one less
file to read on startup) and re-split once we know what the use cases
are.
You could
On Wed, Aug 26, 2009 at 2:31 PM, Ben Goodger (Google) b...@chromium.orgwrote:
Note that even upgrading Windows OS from XP to Vista involves changing
paths:
c:\Documents and Settings - c:\Users
Do we ever write paths such as this?
Yes.
From my Preferences file on Windows:
id:
On Wed, Aug 26, 2009 at 1:20 PM, Dan Kegel d...@kegel.com wrote:
On Wed, Aug 26, 2009 at 12:59 PM, Jeremy Orlowjor...@chromium.org wrote:
I really like the idea of being able to move people between
operating systems and just bringing the profile along
without having to export and
On Wed, Aug 26, 2009 at 2:37 PM, Avi Drissman a...@google.com wrote:
On Wed, Aug 26, 2009 at 2:31 PM, Ben Goodger (Google)
b...@chromium.orgwrote:
Note that even upgrading Windows OS from XP to Vista involves changing
paths:
c:\Documents and Settings - c:\Users
Do we ever write paths
+ chromium-dev (this time, sorry for the resend)
Is the OS in the user-agent string?
Mozilla/5.0 (*Windows*; U; Windows NT 6.0; en-US) AppleWebKit/532.0 (KHTML,
like Gecko) Chrome/3.0.195.6 Safari/532.0
There's a chance that http resource caches will contain data tweeked per OS.
Maybe for
Note that even upgrading Windows OS from XP to Vista involves changing paths:
c:\Documents and Settings - c:\Users
Do we ever write paths such as this?
Local state should be data that can be thrown away without much loss
of user experience. Generally these things include window positions,
file
Bearing the upcoming Chrome OS in mind, this should be taken into account
quite strongly.Regular programs will probably not move cleanly and nicely
from Windows to Chrome OS, but, at least, Google products should migrate
seamlessly, without any data loss (and passwords are a very important part,
21 matches
Mail list logo
