This feature should go somewhere in the core of Psi, because lots of the features could depend on it.
I started a separate thread from the Summary of new features request for 0.9 to allow the users to comment uppon this feature request and not clutter the thread.
Idea started in:
http://psi.affinix.com/forums/index.php?ac...t=499#entry2994
> Roster items could be defined by something like: %IconUserStatus %StringUserRosterName %StringUserJID (%StringUserNoResources) %IconUserStatusString %IconUserPGP %IconUserTransport
This could be translated to:
(status icon) (user name) (userJID) (number of resources if different than 1) (PGP secured contact - icon) (info icon - the blue one I've seen as a patch around here to show status) (icon for the transport - assuming that there will be something in the future)
Result: (yellowstar) My Contact (jabber@my.contact.org) (3) (PGPicon) (infoIcon)
- of course this is kind of a paranoid over filled roster display, but it ilustrates the posibility of using these formated strings in the roster
> Auto-status strings could be something like: "Auto-away/XA: Last action: %TimeLastAction - Idle for %TimeIdle"
Of course, there should be some kind of dictionary for this strings or, at least, a method of building them:
%(item_category)(category)[(subcategory)](string_format_name)
item_category = {Icon, String, Time - I know this is also a string but it should be separated, VCard(?) }
category = {Status, User etc. }
string_format_name = { JID, LastActivity etc.}
Icons: IconUserStatus, IconUserStatusString, IconUserTransport, IconUserPGP
Strings: StringUserJID, StringUserRosterName, StringUserNoResources, StringStatusMessage, StringStatusType (Away, XA, DND...)
Time: TimeNowHHMMSS - this should be somehow defined, TimeLastActivity, TimeIdle
Strings with the same subcategory: StringUserStatusString, StringUserStatusType (Away, XA, DND...)
> Oh, not to metion some format specifiers like: %b (bold) %i (italic) %cRRGGBB (HTML hex style) or %c_colorname
> %n - for newline
> Now that I think of it, these formated strings could help the users define what they want to see in the tooltip when hovering over the contacts. If somebody would want a small tooltip, with little information, they will certainly have the posibility of choosing what to display in it.
Some format strings should work only in some windows/text boxes etc. to prevent crashes, unexpected behaviour etc.
(Probably these string format routines will help the development of the scripting support. As far as I know, this kind of "global/user variables" are used by mIRC in the scripting language.)
Displaying the formated strings could increase a little the CPU Usage but will bring with it a lot more functionality and versatility.
I started a separate thread from the Summary of new features request for 0.9 to allow the users to comment uppon this feature request and not clutter the thread.
Idea started in:
http://psi.affinix.com/forums/index.php?ac...t=499#entry2994
> Roster items could be defined by something like: %IconUserStatus %StringUserRosterName %StringUserJID (%StringUserNoResources) %IconUserStatusString %IconUserPGP %IconUserTransport
This could be translated to:
(status icon) (user name) (userJID) (number of resources if different than 1) (PGP secured contact - icon) (info icon - the blue one I've seen as a patch around here to show status) (icon for the transport - assuming that there will be something in the future)
Result: (yellowstar) My Contact (jabber@my.contact.org) (3) (PGPicon) (infoIcon)
- of course this is kind of a paranoid over filled roster display, but it ilustrates the posibility of using these formated strings in the roster

> Auto-status strings could be something like: "Auto-away/XA: Last action: %TimeLastAction - Idle for %TimeIdle"
Of course, there should be some kind of dictionary for this strings or, at least, a method of building them:
%(item_category)(category)[(subcategory)](string_format_name)
item_category = {Icon, String, Time - I know this is also a string but it should be separated, VCard(?) }
category = {Status, User etc. }
string_format_name = { JID, LastActivity etc.}
Icons: IconUserStatus, IconUserStatusString, IconUserTransport, IconUserPGP
Strings: StringUserJID, StringUserRosterName, StringUserNoResources, StringStatusMessage, StringStatusType (Away, XA, DND...)
Time: TimeNowHHMMSS - this should be somehow defined, TimeLastActivity, TimeIdle
Strings with the same subcategory: StringUserStatusString, StringUserStatusType (Away, XA, DND...)
> Oh, not to metion some format specifiers like: %b (bold) %i (italic) %cRRGGBB (HTML hex style) or %c_colorname
> %n - for newline
> Now that I think of it, these formated strings could help the users define what they want to see in the tooltip when hovering over the contacts. If somebody would want a small tooltip, with little information, they will certainly have the posibility of choosing what to display in it.
Some format strings should work only in some windows/text boxes etc. to prevent crashes, unexpected behaviour etc.
(Probably these string format routines will help the development of the scripting support. As far as I know, this kind of "global/user variables" are used by mIRC in the scripting language.)
Displaying the formated strings could increase a little the CPU Usage but will bring with it a lot more functionality and versatility.

IceRAM
Show profile
Link to this post