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 104 and Version 105 of SoCAndBountyIdeas


Ignore:
Timestamp:
Jan 24, 2014, 8:03:57 AM (10 years ago)
Author:
MarkDoliner
Comment:

Remove GObjectification from this list. We still need to merge in the plugin changes, but I think that'll happen and I think we probably don't need another SoC project for it.

Legend:

Unmodified
Added
Removed
Modified
  • SoCAndBountyIdeas

    v104 v105  
    9797> This sounds suspiciously like the (abandoned) [http://www.nat.org/dashboard/ Dashboard] project – maybe some ideas from there could be adopted? —[wiki:resiak]
    9898
    99 == Gobjectification Projects ==
    100  * Adopt a decent segment of the Pidgin source and begin to remodel it around the Gobject, such as the buddy list, the conversation interface, or something else significant and modify libpurple and Pidgin and/or Finch related objects to handle or exist as Gobjects as well.
    101    * [wiki:rekkanoryo]: Plugins should become gobjects and prpl's should be implementations of a !PurpleProtocolIface (or similarly named interface) as a mandatory requirement of gobjectification.
    102    * [wiki:gillux]: If that’s any motivation for anyone interested by this project, I’d like to point out that any improvment made on the gobjectification side will allow the old [wiki:GSoC2010/DetachableLibpurple detachable session project] to ~~resuscitate~~ improve and eventually get to a usable state.
    103    * [wiki:grim]: I need to take a look at the docbook and get it up to date.  Also we could pull my [http://bitbucket.org/rw_grim/gplugin GPlugin] library in now too (still needs to be packaged for distros, but better than rewriting the entire plugin api)
    104 
    10599== Web site translations ==
    106100 * Produce a translation system for Pidgin's web site (at least the main static content)
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!