Updates:
        Status: Started
        Owner: [email protected]
        Cc: [email protected]
        Labels: -OS-All OS-Mac

Comment #1 on issue 19073 by [email protected]: Implement extension  
toolstrips for mac
http://code.google.com/p/chromium/issues/detail?id=19073

I have started looking into this, but haven't done too much yet (I have an  
empty shelf
that has the add/remove item callbacks hooked up. When creating the
RenderWidgetHostViews for the items, stuff lock horribly up at the moment.

Pam, Aaron says you'd like to look at this. How far along are you? Should I  
stop
looking at this because you've got this under control? Or do you want to  
look at my
work-in-progress CL and take over? Or something else altogether?

Also, related to this bug, erikkay says:

"""
> When I talked with Aaron, he said porting the shelf to OS X isn't
> something I should tackle unless I'm _really_ running out of things to
> do, since they're not even sure they're going to keep it. Has this
> changed, or is the situation different on linux for some reason?

Yes, extension UI is in a fair amount of flux, so some of this isn't
really worth diving into.  However, there are pieces of that work that
are relatively safe to bite off (which Pawel has mostly done for
Linux):
- ExtensionView - a way to display a RenderViewHost outside of a
TabContents in Chrome's UI
- a basic implementation of ExtensionShelf (essentially just drawing a
list of ExtensionViews based on an order specified by the
ExtensionShelfModel).  This is mostly just so you have a place to test
and use your ExtensionView.

Anything more than that (grab handles, dragging, moles, etc.) I'd
advise against.
"""

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to