[chromium-dev] Re: [Linux folks] Splitting First Run into it's own process
On Fri, Aug 21, 2009 at 7:15 PM, Evan Martin wrote: > What's the motivation? > * Due to some technical limitations with the FF libraries, we need to load them in a separate process. It also doesn't seem like a good idea to run code out of an arbitrary library in the main process. * The first run dialog needs to be displayed very early on in the launch process since we need to display it before enabling stats and crash reporting so we can ask for the user's consent. The dialog is brought up before we've fully initialized Cocoa which is concerning in terms of it's interaction with the main app runloop, There are also UI artifacts - http://crbug.com/19643 Best regards, Jeremy > > On Fri, Aug 21, 2009 at 5:11 PM, Jeremy Moskovich > wrote: > > I'm looking at splitting the First Run UI & import machinery into it's > own > > process on OS X. > > I just wanted to sync up with people working on the Linux side of things > to > > make sure no-one else is working on the same thing in Linux-land? > > Best regards, > > Jeremy > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: [Linux folks] Splitting First Run into it's own process
On Mon, Aug 24, 2009 at 10:08 AM, Jeremy Moskovich wrote: > * Due to some technical limitations with the FF libraries, we need to load > them in a separate process. It also doesn't seem like a good idea to run > code out of an arbitrary library in the main process. Coincidentally, I was just chatting with an Epiphany (WebKit+Gtk) developer about Firefox import and he too was lamenting how complicated it is to get this data out of Firefox. I had suggested a utility process might be the best way. (Note: not a complaint about Firefox; it's likely it's even harder to import this sort of data out of us...) > * The first run dialog needs to be displayed very early on in the launch > process since we need to display it before enabling stats and crash > reporting so we can ask for the user's consent. The dialog is brought up > before we've fully initialized Cocoa which is concerning in terms of it's > interaction with the main app runloop, There are also UI artifacts - > http://crbug.com/19643 As far as I know there are no such issues on Linux, so we don't have anybody working on doing this split. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: [Linux folks] Splitting First Run into it's own process
What's the motivation? On Fri, Aug 21, 2009 at 5:11 PM, Jeremy Moskovich wrote: > I'm looking at splitting the First Run UI & import machinery into it's own > process on OS X. > I just wanted to sync up with people working on the Linux side of things to > make sure no-one else is working on the same thing in Linux-land? > Best regards, > Jeremy --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: [Linux folks] Splitting First Run into it's own process
AFAIK no one is working on it for Linux. On Fri, Aug 21, 2009 at 5:11 PM, Jeremy Moskovich wrote: > I'm looking at splitting the First Run UI & import machinery into it's own > process on OS X. > I just wanted to sync up with people working on the Linux side of things to > make sure no-one else is working on the same thing in Linux-land? > > Best regards, > Jeremy > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
