Opened 5 years ago

Last modified 4 years ago

#10887 assigned enhancement

Public API to get a "default icon"

Reported by: waddlesplash Owned by: waddlesplash
Priority: normal Milestone: Unscheduled
Component: Kits/Interface Kit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #1142
Has a Patch: no Platform: All

Description

Currently, icons are usually retrieved from an app's resource file. This shouldn't be the case for standard icons (like home, left, right, stop, info, warning, etc.), which should be retrievable.

I say this should go in "BControlLook" (icons embedded inside libbe.so), so we potentially could have different "BControlLook"s for different styles and have a separate icon set for each.

Blocking #1142 because currently, all the apps will have duplicate copies of icons for their toolbars...

Change History (6)

comment:1 Changed 5 years ago by jscipione

We already have a few icons in app server that apps can retreive and use such as the stop and warn icons used by alerts. Here's an example where I'm grabbing them from app_server and using them in Keymap preferences:

http://cgit.haiku-os.org/haiku/tree/src/preferences/keymap/ModifierKeysWindow.cpp#n147

comment:2 Changed 5 years ago by umccullough

Type: bugenhancement

At the very least, this is an enhancement, unless the public API for this existed already in BeOS R5.

comment:3 Changed 5 years ago by waddlesplash

@Urias, Oops, you're right. @John, no, that's not what I meant. One should be able to call be_control_look->GetIcon("edit-copy") and get an easy-to-use icon class (BIcon) and use it.

comment:4 in reply to:  3 Changed 5 years ago by bonefish

Replying to waddlesplash:

@Urias, Oops, you're right. @John, no, that's not what I meant. One should be able to call be_control_look->GetIcon("edit-copy") and get an easy-to-use icon class (BIcon) and use it.

I don't see a reason why #1142 or this ticket have the target milestone alpha5. While both is nice and useful functionality neither has been in BeOS R5, nor is there any other reason for urgent inclusion in R1.

comment:5 Changed 5 years ago by pulkomandy

Milestone: R1/alpha5Unscheduled

New APIs are out of R1 scope, moving out of alpha5 milestone.

comment:6 Changed 4 years ago by waddlesplash

Owner: changed from axeld to waddlesplash
Status: newassigned
Note: See TracTickets for help on using tickets.