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 22 and Version 23 of MonoLoader


Ignore:
Timestamp:
Jul 29, 2007, 5:51:49 PM (17 years ago)
Author:
ecoffey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MonoLoader

    v22 v23  
    1010  * ~~Re-examing and possibly re-implement signal-glue and API -glue code.~~  The glue code is now gone.  The use of !DllImport has made it all pretty much obsolete.
    1111  * ~~Give .NET Purple objects the ability to actually update their C counterpart (or create one).~~
    12   * Would be nice if we could explicitly state what Delegates expect, e.g. {{{ OnBuddyStatusChanged(Buddy b, Status s) }}}.  Possible solution is to pass Event an array of Types.  Then Signal.connect registers its own handler.  When that gets invoked it feeds the IntPtrs to the proper constructors based on the array of Types and then invokes the plugin provided Delegate.
    13   * Possibly utilize an object cache in the api, and to manage the mappings between .net objects and their c struct counterparts so we're not constantly (re)building objects.
    14   * Use native event type instead of Event.cs
     12  * ~~Would be nice if we could explicitly state what Delegates expect, e.g. {{{ OnBuddyStatusChanged(Buddy b, Status s) }}}.  Possible solution is to pass Event an array of Types.  Then Signal.connect registers its own handler.  When that gets invoked it feeds the IntPtrs to the proper constructors based on the array of Types and then invokes the plugin provided Delegate.~~
     13  * ~~Possibly utilize an object cache in the api, and to manage the mappings between .net objects and their c struct counterparts so we're not constantly (re)building objects.~~
    1514  * [http://reaperworld.com/htdocs/monoloader.html grim provided gameplan]
    1615
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!