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 also imagine just having one file and having a json subtree provide the distinction. On Wed, Aug 26, 2009 at 1:11 PM, Ben Goodger (Google) <[email protected]> wrote: > > 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 Drissman<[email protected]> 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 >> obeyed, and I'm not sure to the extent to which it can be obeyed. So some >> questions: >> >> - Is "profile platform independence" a guiding principle? >> - To what extent do we work to make it reality? >> - In the cases where it can't be kept (e.g. download folder path) should we >> keep a copy for each platform? >> - Is it worth rewriting today's code that doesn't conform (e.g. extensions >> and themes which use full paths and platform path separators)? >> >> Avi >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
