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.
- Timestamp:
-
Apr 15, 2007, 5:46:18 AM (17 years ago)
- Author:
-
ecoffey
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v2
|
v3
|
|
1 | | == Mono Loader Development Notes == |
| 1 | == Mono Loader SoC Development Notes == |
| 2 | |
| 3 | '''SoC Goals and Milestones''' |
| 4 | |
| 5 | * Completely wrap libpurple API in .NET bindings. |
| 6 | |
| 7 | * Fix the Mysterious Seg Fault On Exit (tm). |
| 8 | |
| 9 | * Re-examine and possibly re-implement signal-glue and API -glue code. |
2 | 10 | |
3 | 11 | '''Loader Internals:''' |
4 | 12 | |
5 | | * There must be a better way for having the loader handle signals on behalf of .net plugins (will document the current implementation here). |
| 13 | * There must be a better way for having the loader handle signals on behalf of .net plugins (will document the current implementation here). |
6 | 14 | |
7 | | * 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) }}} |
| 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) }}} |
8 | 16 | |
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!