These are resources, IDR_FOLDER_CLOSED_RTL, IDR_FOLDER_CLOSED,
IDR_FOLDER_OPEN_RTL, IDR_FOLDER_OPEN in
ui/views/resources/views_resources.grd.
One approach is to just provide different files on Mac (maybe there are
some already in use elsewhere in Cocoa that are the right things).
Another approach is to hook in "somehwere" and provide assets in
tree_view.cc by going through +[NSImage NSImageNamed:]
Yet another option is to implement assets from scratch as vector icons,
since most of Chrome is going that way already.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
chro...@googlecode.com
unread,
Jan 17, 2016, 11:03:31 PM1/17/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Chrome's Cocoa UI retrieves some image assets from the System using APIs
such
as +[NSImage imageNamed:key]. To support this under toolkit-views, provide a
ui::ResourceDelegate on Mac that can transparently map some IDR_ resource
IDs
to a system-provided asset. Initially do this for folder icons in
views::TreeView to provide a folder icon that is consistent with the running
OSX version.
The following resource ids are currently intercepted - IDR_FOLDER_OPEN,
IDR_FOLDER_CLOSED, IDR_FOLDER_OPEN_RTL and IDR_FOLDER_CLOSED_RTL. Although
IDR_FOLDER_CLOSED is in ui/resources (and not ui/views/resources), it is
currently unused on Mac (chrome://syncfs-internals/ refers to it in its CSS,
but doesn't actually use that style anywhere in its html or js). Hence this
CL, does not alter any icons on Chrome Mac, except under Views.