[Psi-devel] Customizable Roster Items (#167, #157)
Mircea Bardac (IceRAM)
dev.list at mircea.bardac.net
Sun Aug 22 09:14:17 PDT 2004
On Sun, 2004-08-22 at 11:52, Remko Troncon wrote:
> I think tackling the 'Customizable Roster Items (#167, #157)' should get a
> very high priority. Having to assign nicknames to all contacts is one of the
> main reasons why people really don't like Psi. Skazi has a patch for this
> which i assume implements the technicalities of this, but i would like to
> discuss the matter from a higher viewpoint: what fields will be allowed,
> how to represent fields, how will the options dialog look like, what the
> defaults should be, ...
> I'll give my thoughts on 2 approaches on this: the customizable
> approach, and the 'easier' approach.
> - All fields are denoted with '%' signs. This seems to be the most
> commonly used field representation.
If you choose this approach, please consider the extensibility of the
attributes. This means that I think that it would be better for the
fields to be used like class properties.
using the nickname from the VCard: User.VCard.Nick
using the status string of the user: User.Status.Text
(it would also need a % at the end, because you can't parse it
It is indeed longer but provides unlimited extensibility. Besides this,
it's easier to remember than some letters.
Please consider having a look over this thread I've started a long time
ago, because I also though that should be somehow highpriority.
> Either this, or a non-customizable, sensible, maybe with a checkbox or
> 2, setup. This actually is the way most clients do it i think. I would
> make this look like this [...]
Of course, this is easier to implement and it does provide enough
versatility when it comes to roster names for the average user.
If you consider plugins though, a nice framework for user properties (&
for Psi options) could be nice.
You can check on this matter FlySpray Task #215 (common.* must die)
which sugests using CVS:/neatstuff/options for the settings.
This way, you could have userspace properties (name,jid, vcard-subclass)
and program userspace (all options here). I think they could easily be
binded to the plugin (scripting) engine.
These are my 2 euro-cents (or 880 lei - Romanian currency) :p
Dream as if you'll live forever. Live as if you'll die today.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://listserver.dreamhost.com/pipermail/psi-devel-affinix.com/attachments/20040822/df3b7543/attachment.bin
More information about the Psi-devel-affinix.com