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 57 and Version 58 of SoCAndBountyIdeas


Ignore:
Timestamp:
Sep 24, 2009, 5:38:31 AM (14 years ago)
Author:
Paradox
Comment:

Add the oft-requested "Sessions" and comment out the projects that were handled in GSoC2009

Legend:

Unmodified
Added
Removed
Modified
  • SoCAndBountyIdeas

    v57 v58  
    77[wiki:SummerOfCode2007 Information about some Summer of Code 2007 projects]
    88[[BR]][wiki:SummerOfCode2008 Information about some Summer of Code 2008 projects]
     9[[BR]][wiki:SummerOfCode2009 Information about some Summer of Code 2009 projects]
    910
    1011== Notes about the following ideas ==
     
    1718Now, on with the ideas:
    1819
     20{{{
     21#!comment
    1922== Write a Native User Interface for Microsoft Windows Based on libpurple ==
    2023The current version of Pidgin for Windows uses GTK+ 2.  While GTK+ 2 windows with the WIMP theme are designed to look like native Windows applications, they're not perfect.  This task is to create a complete IM program for Microsoft Windows using libpurple as the core component.
     
    3639
    3740This is a massive undertaking, and you should have a lot of experience creating native applications for MS Windows (experience with Visual Basic does '''''__not__''''' count here) as well as lots of experience with C.  Familiarity with the libpurple source and POSIX programming in general is also very important and extremely helpful.
     41}}}
    3842
    3943== Better chat log viewer ==
     
    6670Your mission is to understand what the official MySpaceIM client does at a protocol level, document what you've found [http://imfreedom.org/wiki/index.php/MySpaceIM here] (if not already documented), and implement it in libpurple.
    6771
     72{{{
     73#!comment
    6874== Telepathy prpl ==
    6975Currently, people wanting to use [http://telepathy.freedesktop.org Telepathy] have to switch from Pidgin to some other IM client (such as [http://live.gnome.org/Empathy Empathy]).  It would be nice to have a Telepathy prpl for Pidgin, presumably based on the `telepathy-glib` client API (and possibly on `libmissioncontrol`).  This would/could involve, depending on interest and time:
     
    7682
    7783(The astute will notice that this is the second half of 2007's [wiki:Telepathy] SoC project, which there wasn't time to start on.  Grab [wiki:resiak me] on IRC if you're interested.)
     84}}}
    7885
    7986== Topical Reference Tools ==
     
    95102Possibly by using a pre-existing library such as Gammu, KMobileTools or libgsm. You could also send by email using teleflip.com
    96103
     104{{{
     105#!comment
    97106== Webkit Message Views ==
    98107Webkit is a popular HTML rendering engine used in a number of browsers.  Adium uses it for their message windows as well.  Your task for this project is to rip out !GtkImHtml and replace it with Webkit.  This includes the input areas as well.
     108}}}
    99109
    100110== Web site translations ==
     
    107117 * Consider ways to provide translated versions of images and screen shots
    108118 * This particular idea may not be sufficiently complex to span a summer and it may be worthwhile to combine it with other web site or internationalization improvements to Pidgin or some other type of larger project.
     119
     120== libpurple detachable sessions ==
     121This is an often requested feature to which the response is often "run Finch in screen". Ideally, it would be possible for a user to run Pidgin and Finch simultaneously on a computer, with both programs sharing the same data and connections. This would allow users to leave Pidgin open, yet still access their IMs over SSH with Finch.
     122This requires an implementation of some sort of libpurple server, and a method for the clients to connect to that server, and access and display the buddy list, conversations, and chats.
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!