[Pidgin Plugins] #304: Ignorance plugin needs some more TLC

[Pidgin Plugins]

#304: Ignorance plugin needs some more TLC
-----------------------------+----------------------------------------------
  Reporter:  jbailey         |       Owner:  jbailey 
      Type:  FeatureRequest  |      Status:  assigned
  Priority:  5               |   Milestone:          
 Component:  PluginPack      |     Version:          
Resolution:                  |    Keywords:          
   Pending:  0               |  
-----------------------------+----------------------------------------------
Changes (by jbailey):

  * pending:  => 0

Old description:

> Ignorance needs some major TLC:
>
>  * Move to using either an XML file, or (preferably) Gaim's preference
> API.
>  * Rework the configuration dialog so that it's not so cramped...ideas
> welcome
>  * Since I removed the /commands a new way to get the configuration
> dialog might be a good idea--a new /command, a button in the menutray, or
> something along those lines.
>  * Ideally I'd like to have (if it's possible) one core ignorance plugin
> and two frontends--one for Gaim and one for gaim-text.  I'm thinking have
> the core plugin just act according to preferences, and have the frontend
> plugins modify the preferences.  Thoughts?

New description:

 Ignorance needs some major TLC:

  * Move to using either an XML file, or (preferably) Gaim's preference
 API.
  * Rework the configuration dialog so that it's not so cramped...ideas
 welcome
  * Since I removed the /commands a new way to get the configuration dialog
 might be a good idea--a new /command, a button in the menutray, or
 something along those lines.

 --Ideally I'd like to have (if it's possible) one core ignorance plugin
 and two frontends - one for Gaim and one for gaim-text.  I'm thinking have
 the core plugin just act according to preferences, and have the frontend
 plugins modify the preferences.  Thoughts?--

Comment:

 I'm going to attempt to tackle this plugin after I'm finished rewriting
 smartear.  I have a few ideas though:
  * hook into the blistnode menu to add an "Ignore This Person" option.
  * offer client-side ignore where we don't have adequate server-side
 support, such as for ICQ
  * work with the (crappy) privacy api where possible
  * add regex support after the most important features are done
  * if, and only if, configuration becomes too difficult should there be
 UI-specific helper plugins.
    * if it comes to that mark the libpurple plugin as hidden and make the
 UI plugin depend on it.
    * if UI plugins exist, have no defaults configured in the libpurple
 plugin, instead configuring defaults with the UI plugins.

-- 
Ticket URL: <http://plugins.guifications.org/trac/ticket/304#comment:4>
Pidgin Plugins <http://pidgin.guifications.org/>
Plugins for the Instant Messaging client Pidgin and its backend library libpurple