Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 6 and Version 7 of DesignGuidelines


Ignore:
Timestamp:
May 2, 2007, 5:33:57 AM (17 years ago)
Author:
MarkDoliner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DesignGuidelines

    v6 v7  
    99While Pidgin is a multiprotocol IM client, the goal is to hide protocols from the user as much as possible.  Obviously users have to know about individual protocols when they create or modify accounts, but in day-to-day communication and usage, the intent is that users don't have to think about protocols at all.  The workflow in Pidgin is intended to be "I would like to chat with Sean about wibbles", not "I would like to create an XMPP conversation with seanegan@pidgin.im".  The focus is on the goal, not the process.  In reaching toward this focus, we have chosen to paper over the differences between the various protocols and features as much as possible (without crippling or needlessly complicating things).  This has lead to decisions such as the removal of protocol icons from the buddy list and the implementation of contact-aware chats and logs. Sean has elaborated on this theme: [http://www.pidgin.im/~seanegan/cgi-bin/pyblosxom.cgi/identity.html]
    1010
     11== Simpler Is Better ==
     12
     13  ''Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.''  --Antoine de Saint-Exupery
     14
     15In general we try to keep things simple.  Especially when it comes to preferences in the user interface.  Pidgin should be as streamlined as possible.  It is an IM client, so messaging someone should be easy.  See [http://www106.pair.com/rhp/free-software-ui.html this essay] by Havoc Pennington for an explanation of some ideas that we try to follow.
     16
    1117== Clean Layering ==
    1218
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!