I actually don't know. It seems like just simple state gathering but it might be more.
The big concern is that it fits our model but no one else's. Everyone else is OK with the UI asking the renderer questions directly, and as that's more efficient than doing status updates that are going to be ignored 99.44% of the time, I'm not sure they have incentive. I need to land my first pass at copy/paste and then I'll be looking into this exact question. Avi On Mon, Mar 9, 2009 at 1:28 PM, Ojan Vafai <[email protected]> wrote: > On Mon, Mar 9, 2009 at 10:12 AM, Avi Drissman <[email protected]> wrote: > >> On Mon, Mar 9, 2009 at 12:02 PM, Evan Martin <[email protected]> wrote: >> >>> Maybe a better option is to have the renderer send "FYI, >>> cut/copy/paste state is now x/y/z" messages up to the UI whenever it >>> changes? (I guess paste is out of webkit's hands, but I can imagine >>> other booleans like whether "select all" should be enabled.) >>> >> >> That would make sense, but right now WebCore is set up for the UI to poll >> rather than push updates. I suppose that glue could know when the state >> might change, poll WebCore, and push updates, but that's a bit ugly. (Still >> investigating...) >> > > Would changing this be a significant code change? WebKit folk might just be > OK with changing it to be push-based. > > >> >> Avi >> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
