For those of you that don't know me, I'm the Gaim developer to whom the Gaim XML smiley theme patch is assigned. I brought the proposal of a unified smiley theme to #kopete some time ago. I finally got around to following up with mattr again (sorry, been a busy summer at work!), and here we are. :)
On Thu, 2006-11-02 at 15:42 +0100, Martijn Klingens wrote: > On Thursday 02 November 2006 14:29, Matt Rogers wrote: > > > Is it possible that e.g. : ) in MSN yields another image than in ICQ? > > > > People will want this, so that they can make their emoticons per protocol > > look like the ones from the original clients. Indeed. I consider it an absolute requirement to support both protocol-independent and per-protocol smileys. When resolving a smiley, the per-protocol list for that protocol should be checked first, then the global list. > > IIUC, the patch on the tracker is just a proposal. While i'm sure that some > > discussion on gaim-devel took place, I don't read gaim-devel (i'm on enough > > MLs) so I am not aware of what they discussed > > Hmm, would be interesting to know though. I don't really recall any discussion about this on gaim-devel, and a quick search through my archives yields nothing. I don't know what that comment on the patch was all about. The patch is something proposed by a random contributor. I like the general idea for the following reasons (in no particular order): 1) Integrating an XML smiley theme would improve our support of smileys with spaces in the text -- "*THUMBS UP*", for example. Currently, in the 2.0.0 line, we support those with \ escaping, but that's messy. 2) The XML smiley theme would allow us to have mouse-over descriptions for smileys. 3) We use XML for our other files, and so XML is the logical choice for a standardized smiley theme format. 4) A standardized smiley theme would increase the number of smiley themes accessible to users and make it easier on people (and distros, if any of them care about smileys) looking to create a smiley theme. > > > Also, a long-standing wish that I eventually wanted to implement in > > > Kopete back when I was still working on it was to allow the engine to do > > > more sophisticated markup as well, like changing *bold* to <b>bold</b> > > > and /italic/ to <i>italic</i>, or even to support '/me' again. I'm clearly biased, since Gaim handles the /me case different, but I don't see how this is directly related to a smiley theme *format*. (In Gaim at least,) I'd rather see these implemented as UI, core, or plugin features independent of smileys. We currently have a text replacement plugin that does arbitrary, user-definable corrections (usually of typos and the like). If we're going to settle on a format that allows for text -> markup transformations, well, we might as well throw that into the mix as well, since it's just a text -> text transformation. If you really want to go there, I'd suggest we do a definition for smiley themes, then a separate text -> markup format specification, so they can be implemented independently. If the text -> markup specification isn't excessively complex, I'd definitely be willing to extend the text replacement plugin to handle those cases, and use the new format we design for its data storage. > More stuff that's needed in any case: > > - versioning on the root element <messaging-emoticon-map />, so old and new > themes can be distinguished I agree. > - consideration of KMail and possibly other apps who also use the themes I'm not a GNOME developer, but it looks like Evolution just has a few pre-defined smileys. If they decide to support the theme, I don't think we'll have a problem there. If anything, they can just have a special protocol like "e-mail" or something. Richard
signature.asc
Description: This is a digitally signed message part
_______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
