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 9 and Version 10 of MonoLoader


Ignore:
Timestamp:
Apr 15, 2007, 6:48:26 AM (17 years ago)
Author:
ecoffey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MonoLoader

    v9 v10  
    44
    55'''SoC Goals and Milestones'''
    6 
    76  * Completely wrap libpurple API in .NET bindings.
    8 
    97  * Fix the Mysterious Seg Fault On Exit (tm).
    10 
    11   * Re-examine and possibly re-implement signal-glue and API -glue code.
    12 
     8  * Re-examing and possibly re-implement signal-glue and API -glue code.
    139  * Give .NET Purple objects the ability to actually update their C counterpart (or create one).
    14 
    15 '''Loader Internals:'''
    16 
    17   * There must be a better way for having the loader handle signals on behalf of .net plugins (will document the current implementation here).
    18 
    19   * Right now delegates are invoked and just given an array of their data.  Would be nice if we could explicitly state what they expect, e.g. {{{ OnBuddyStatusChanged(Buddy b, Status s) }}}
    2010
    2111'''Mentor Goals/Objectives ([http://guifications.org/trac/wiki/grim grim])'''
    2212 * Implement signal chaining in Mono so Pidgin's signal handling doesn't get eaten up by the Mono runtime.  See [http://bugzilla.ximian.com/show_bug.cgi?id=75990 Mono Bug 75990].
    2313 * Fix the build system so that make can be run successfully with multiple jobs.
     14
     15'''Loader Internals:'''
     16  * There must be a better way for having the loader handle signals on behalf of .net plugins (will document the current implementation here).
     17  * Right now delegates are invoked and just given an array of their data.  Would be nice if we could explicitly state what they expect, e.g. {{{ OnBuddyStatusChanged(Buddy b, Status s) }}}
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!