Opened 12 years ago

Last modified 10 years ago

#2428 new enhancement

Idea for XMPP UI improvements in Pidgin

Reported by: cdmarcus Owned by: deryni
Milestone: Component: pidgin (gtk)
Version: 2.1.0 Keywords:
Cc:

Description

When Pidgin added Google Talk as an option for protocols, I had mixed feelings about it. On the plus side, it makes Google Talk easier to use in Pidgin. However, it gives preferential status to it over other XMPP providers such as Jabber.org, LJ Talk, and Gizmo Project. I suggest that a dropdown menu be added to the Add Account dialog when XMPP is suggested, that allows the user to choose between several popular XMPP providers, and a manual option. When one is selected, the fields are filled out automatically. Services that I suggest should be included are Google Talk, LJ Talk, Jabber.org, and Gizmo Project. Also, anything that shouldn't be changed when using a particular XMPP provider should be greyed out.

It would also be nice if the Screen Name and Domain fields were combined into one JID field, since screen name and domain aren't terms normally used by Jabber users. As far as I know, the domain can't be different from the part of the JID after the @ sign. However, if this isn't the case, then clearly that combination of the fields can't be done.

Change History (5)

comment:1 Changed 12 years ago by lithium

I like your idea very much. Those XMPP "variants" should also be able to define overrides for some features, such as being able to specify a set of emoticons for Google Talk for example (using the official client's emoticon codes) or enableing/disableing features (not) supported by the XMPP Provider

comment:2 Changed 12 years ago by cdmarcus

I don't think that Google Talk should be treated differently from any other XMPP services... the only differences between the Google Talk option and the XMPP option should be that the servers are already configured for you with the Google Talk option. One thing that came about with the release of Pidgin 2.0.0 was an increased focus on abstraction, keeping the protocol's specificities away from the user. As a result, icons changed from protocol-based to status-based, and the individual protocol emoticons were scrapped in favor of a newly made emoticon set.

comment:3 Changed 12 years ago by lithium

"and the individual protocol emoticons were scrapped in favor of a newly made emoticon set" => usage of the original icons (which usage was illegal anyway I guess) was replaced by a new set of tango icons. But still pidgin tries to show the right emoticon for a given character sequence. This is where XMPP services can differ: as there is no official list of emoticon codes for XMPP, all the clients can implement their own. In case of a special application for a service (gtalk and a few others), there are special emoticon lists for that service... which we don't support yet :/

comment:4 Changed 10 years ago by Afief

XMPP supports custom smiley(XEP 0231 I think) and it already works in Pidgin, so I don't really see why not everything can be sent as a custom smiley?

comment:5 Changed 10 years ago by deryni

  • Owner set to deryni
Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!