On Tue, Dec 23, 2008 at 2:52 AM, Graham Perrin <[email protected]> wrote: > Yes, but the things are not related to processors services. Let's > shift attention to the thread on provider services :)
Perhaps if you'd describe what you're actually interested in doing, we could give better answers. The Mac Chromium browser UI has not yet been written, but as described, we're planning to use Cocoa and support all conventional Mac OS X features. This includes copy & paste, drag & drop, and system services. As a service requester, the application doesn't have to distinguish between "processor services" and "provider services"--as long as the UI supports the cocoa pasteboard API (which Chromium will), both types of service should work. The concerns you raise regarding Firefox aren't really applicable, since Chromium and Firefox have very, very different approaches to implementing the UI. As a service provider, are there particular services you think Chromium should provide? We're likely to concentrate on Chromium as a requester rather than as a provider, but if there are particular services you think a browser should provide, we can certainly talk about those. --Amanda --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
