20 Oct
2010
20 Oct
'10
10:59 a.m.
On Oct 20, 2010, at 10:07 AM, Thomas Mortagne wrote:
On Tue, Oct 19, 2010 at 18:57, Vincent Massol
<vincent(a)massol.net> wrote:
I thought about this too but I didn't like it too much since it means silk becomes an
"API" and we cannot remove it as otherwise we'll break people's pages.
Thanks
-Vincent
Hi devs,
I'd like to propose 3 things:
1) Add support for symbols/emoticons using our new system in XWiki Syntax 2.1, i.e.
image:symbol:<symbol name>
Another possibility is: image:icon:<icon name>
+1 for icon
ex: image:symbol:success (for the success symbol)
2) Use the existing silk icon library and be able to reference all icons using their file
names as the symbol name.
For ex, image:symbol:thumb_up
3) Modify the Box macro to accept a ResourceReference as its image parameter so that all
valid image resource references can be specified (including the new symbol/icon scheme).
+1
WDYT?
This will solve the emoticon/symbol need + the generic way of adding a box with any
symbol.
Open questions:
A) Do we need to handle icon size? If so, how? (answer: with an image parameter)
B) Do we want to expose all silk icons? What if we use another library later on, will we
be able to support all existing silk symbols? Thus, do we need to pick a subset and settle
on names independent from the underlying library?
For A) IMO we don't need it now and we can always use an image param later on if need
be.
In a case of a list of well known icon you find find in many places i
think it's better to always download the same and not resize it server
side, that way it will be in the browser cache most of the time. And
you can still resize it client side.
For B) I'm tempted to think that a set of
well-known symbols independent from the underlying library is better (but more work since
we need to define that set and the names).
Another possibility is to have image:silk:somesilkifilename.