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 4 and Version 5 of MonoLoader


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

--

Legend:

Unmodified
Added
Removed
Modified
  • MonoLoader

    v4 v5  
    33'''SoC Goals and Milestones'''
    44
    5 * Completely wrap libpurple API in .NET bindings.
     5  * Completely wrap libpurple API in .NET bindings.
    66
    7 * Fix the Mysterious Seg Fault On Exit (tm).
     7  * Fix the Mysterious Seg Fault On Exit (tm).
    88
    9 * Re-examine and possibly re-implement signal-glue and API -glue code.
    10 
     9  * Re-examine and possibly re-implement signal-glue and API -glue code.
    1110
    1211'''Loader Internals:'''
    1312
     13  * There must be a better way for having the loader handle signals on behalf of .net plugins (will document the current implementation here).
    1414
    15 * There must be a better way for having the loader handle signals on behalf of .net plugins (will document the current implementation here).
     15  * 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) }}}
    1616
    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) }}}
    18 
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!