Context Navigation

Changes between Version 48 and Version 49 of SoCAndBountyIdeas

Timestamp:: Jan 22, 2009, 5:27:29 AM (15 years ago)
Author:: John Bailey
Comment:: clear out some old cruft here

Legend:

: Unmodified
: Added
: Removed
: Modified

SoCAndBountyIdeas

-                      v48
+                      v49
   * Windows-specific conventions can be followed much more easily than can be done in Pidgin's GTK+ 2 UI
   * If developed using MFC instead of .NET:
+    * In theory, users of Windows 95 (there are still a surprising number of them!) should be able to use the application under some conditions
+    * Windows 98, Windows ME, and Windows 2000 users with older machines will have a more pleasant experience, as .NET applications tend to not run well (fast) enough on older, slower hardware where these Windows versions are prevalent
+    * Windows 2000 users with older machines will have a more pleasant experience, as .NET applications tend to not run well (fast) enough on older, slower hardware where Windows 2000 is prevalent
+    * If developed with Visual Studio .NET, glib and libpurple will need to be built with Visual Studio .NET as well, as explained below.  (Alternatively, it's apparently possible to reconfigure Visual Studio .NET to link against the system C/C++ runtime library to resolve the issues described below)
+    * If developed with Visual Studio 6, it's possible that the existing libpurple build system could be leveraged to reduce the amount of work necessary in the SoC project itself.
   * If developed using .NET:
     * The actual client development ''should'' be easier than with MFC.
     * Glib and libpurple will need to be built with Visual Studio .NET.  If they're not, there ''will'' be some obscure, unfixable bugs resulting from the mixing of two different versions of the Microsoft Visual C/C++ Runtime library.
       * [wiki:rekkanoryo]: I will assist the student if necessary with fixing the Glib project support files, whether or not I am the mentor of the project, as there are some minor tweaks necessary to make glib find its headers and such.
     * .NET is probably preferred.
+    * The overhead of .NET will be incurred, which will make the application extremely slow to launch on machines even just 2-3 years old.
+    * Glib and libpurple '''''must''''' be built with Visual Studio .NET.  If they're not, there ''will'' be some obscure, unfixable bugs resulting from the mixing of two different versions of the Microsoft Visual C/C++ Runtime library.
+    * .NET is probably preferred by most developers.
 This 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.
-== Write XMPP Transports Based on libpurple ==
-libpurple is our backend library that connects to AIM, MSN, Yahoo, etc.  An XMPP transport is an add-on component that allows XMPP users to talk to people using AIM, MSN, Yahoo, etc.  It should be possible to write a generic XMPP transport that supports all the same protocols supported by libpurple.  Familiarity with XMPP and libpurple would be a good idea here.
 == ICQ TLC ==
 …
   * Buddy list management is suboptimal
   * Message size restrictions are likely wrong (#4628)
+  * There are many open tickets about encoding issues.
 Your goal is to compare what libpurple does at a protocol level with what the official Windows ICQ client does, figure out where it differs, and to repair libpurple's implementation, extending Pidgin's, Finch's, and libpurple's capabilities where possible or necessary.
-== Yahoo! TLC ==
-Our Yahoo! implementation is currently substandard:
-  * File transfer support is limited to the server-proxied method.
-  * Our support for the newest protocol revision (version 15) is sub-standard.
-    * MSN interoperability isn't as good as it could be and we do not support adding buddies across the bridge at all.
-    * Our implementation doesn't understand all the new status keys sent over the wire in this protocol version, which may be responsible for a number of user complaints about buddy list errors and buddies from across the MSN bridge not showing as online.
-Your task is to compare what libpurple does at a protocol level with what the official Windows Yahoo! client does, figure out where it differs, and then repair libpurple's implementation.  If time permits, documentation of the protocol would be a huge win, as well.
 == MySpaceIM TLC ==
 …
 Your mission is to understand what the official MySpaceIM client does at a protocol level, document what you've found at  http://imfreedom.org/wiki/index.php/MySpaceIM (if not already documented), and implement it in libpurple.
-== Finch Improvements ==
- * A new window manager (or improvements to the existing ones). For example, a tiling window manager would be super awesome.
- * Improve the widget-packing in a container (!GntBox), may be even have a grid-like container.
- * Have a spell checker, which would add some way of indicating spelling errors, suggesting possible corrections, etc.
 == Telepathy prpl ==
 Currently, 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:
 …
 Familiarity with D-Bus would be a plus here.  You should either speak C, or enough of a ninja to write bindings for your favourite language in about seven seconds.
 (The astute will notice that this is the second half of last year's [wiki:Telepathy] SoC project, which there wasn't time to start on.  Grab [wiki:resiak me] on IRC if you're interested.)
+(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.)
 == Topical Reference Tools ==
 …
 implements RTP transmission and voice communication between contacts.
-== Master Password Support for Multiple Platforms ==
-An implementation of plugin(s) (in addition to the appropriate architecture modifications where applicable) to support gnome-keyring, kwallet, apple-keychain, and/or keepass.
 == Web site translations ==