Ramblings on Mike Kestner's Existence 2004-06-15T20:27:11-04:00 Mike http://primates.ximian.com/~mkestner/weblog/index.php mkestner@ximian.com tag:pivotpowered,2004:ramblingsonmikekestnersexistence Pivot Copyright (c) 2004, Authors of Ramblings on Mike Kestner's Existence Time wasting 2004-06-15T16:40:00-04:00 2004-06-15T16:40:00-04:00 tag:pivotpowered,2004:ramblingsonmikekestnersexistence.1 2004-06-15T16:40:00-04:00 Trying out pivot after Martin's glowing praise. It's not too bad of a conversion, although I messed with the stylesheet and templates considerably. I don't think it looks too horrible now, but I'm sure many of my css-skilled readers will disagree. ;-) I liked the clean, boring look of the default MT templates. Here's a helpful page for anyone considering a move from MT to pivot. The export/import of my MT entries worked like a charm. Time wasting mkadmin pivot after Martin's glowing praise. It's not too bad of a conversion, although I messed with the stylesheet and templates considerably. I don't think it looks too horrible now, but I'm sure many of my css-skilled readers will disagree. ;-) I liked the clean, boring look of the default MT templates.



Here's a helpful page for anyone considering a move from MT to pivot. The export/import of my MT entries worked like a charm.]]> Timing 2004-05-29T13:58:00-04:00 2004-05-29T13:58:00-04:00 tag:pivotpowered,2004:ramblingsonmikekestnersexistence.37 2004-05-29T13:58:00-04:00 My timing with a digital camera is impeccable... Timing mkestner


JR_ucap.JPG]]> Initialize this! 2004-05-17T23:10:00-04:00 2004-05-17T23:10:00-04:00 tag:pivotpowered,2004:ramblingsonmikekestnersexistence.36 2004-05-17T23:10:00-04:00 One of the interesting unsolved challenges in Gtk# is the burden of calling init functions on the underlying libraries. It would be nice if the framework had an easy mechanism to execute code when an assembly is loaded by the runtime. If I could write a class like: [AssemblyInitialization] public class MyInitializer : IAssemblyInitializer { public static void Initialize () { do_some_stuff (); } } to cause an initialization method to run automatically when an assembly is loaded, I'd be a happy hacker. A cleaner approach might be to have an attribute on the assembly itself that identified an IAssemblyInitializer implementor so that less reflection would need to be done at load time to identify whether an implementor exists. I've been thinking about this problem because of the receipt of another bug report for crashes in a gtkhtml-sharp application because the app wasn't calling the ObjectManager.Initialize method to register the assembly's GType mappings. In all fairness, it's completely unreasonable to expect anybody to know they would need to manually call that method. I've been wanting to automate that registration ever since the ObjectManager functionality was added. Lacking a nice clean mechanism like IAssemblyInitializer, I came up with a hack that generates .cctors which call the ObjectManager.Initialize method if an object's GType name is going to have to be registered with GLib.ObjectManager at runtime. This solution will most likely work for most users of gtkhtml-sharp, since a "new Gtk.HTML ()" statement is likely to be used pretty early, but it doesn't take much thought to come up with scenarios that will break it. Generating a ton of .cctors also isn't a reasonable solution for scenarios like the automatic invocation of gtk_init. We'd probably need something like the IAssemblyInitializer solution to correctly deal with that problem. Initialize this! mkestner 



[AssemblyInitialization]


public class MyInitializer : IAssemblyInitializer {


    public static void Initialize ()


    {


          do_some_stuff ();


    }


}


to cause an initialization method to run automatically when an assembly is loaded, I'd be a happy hacker. A cleaner approach might be to have an attribute on the assembly itself that identified an IAssemblyInitializer implementor so that less reflection would need to be done at load time to identify whether an implementor exists.



I've been thinking about this problem because of the receipt of another bug report for crashes in a gtkhtml-sharp application because the app wasn't calling the ObjectManager.Initialize method to register the assembly's GType mappings. In all fairness, it's completely unreasonable to expect anybody to know they would need to manually call that method. I've been wanting to automate that registration ever since the ObjectManager functionality was added.



Lacking a nice clean mechanism like IAssemblyInitializer, I came up with a hack that generates .cctors which call the ObjectManager.Initialize method if an object's GType name is going to have to be registered with GLib.ObjectManager at runtime. This solution will most likely work for most users of gtkhtml-sharp, since a "new Gtk.HTML ()" statement is likely to be used pretty early, but it doesn't take much thought to come up with scenarios that will break it.



Generating a ton of .cctors also isn't a reasonable solution for scenarios like the automatic invocation of gtk_init. We'd probably need something like the IAssemblyInitializer solution to correctly deal with that problem.]]>