Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366741 - how should extension points specify images?
Summary: how should extension points specify images?
Status: CLOSED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 7.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-14 13:42 EST by Susan McCourt CLA
Modified: 2015-05-11 15:54 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2011-12-14 13:42:29 EST
I thought we had a bug for this, because I remember a discussion in one (probably when I was working on sprites).

We have several extension points that specify images.

orion.navigate.command
orion.edit.command
orion.file.contenttype

Currently those images are specified by URL.
We had discussed and dimissed the idea of using a CSS class because of the security risks of letting a plugin contribute CSS.

We considered using a data URI so that the icon could be embedded.  The downside is that a plug-in has to take an extra step to generate one.

We also considered leaving the spec as a URL.  We could run some code to see if there is data, and if there is not, we could generate a data URI from the plugin's image.  The downside is complexity on our side, and the time spent doing so.

Whatever we do I think these three extensions should use the same technique.  I left them all as image URL's for now, which are fed to an image.src
Comment 1 Anton McConville CLA 2015-05-08 10:20:13 EDT
This has evolved, and I don't believe is a problem area anymore.