giD v0.9.6: WebKit web browser engine binding, GObject property support, and improved docs

[Luna]

On Tuesday, 29 April 2025 at 09:28:09 UTC, Dejan Lekic wrote:
> On Monday, 28 April 2025 at 21:01:52 UTC, Luna wrote:
>>
>> My personal recommendation would be to follow the GLib naming 
>> standard instead; so instead of ObjectWrap, or ObjectG; just 
>> call it GObject, for Pango call it PangoFont, etc.
>> That makes it consistent with existing GLib documentation for 
>> cases where you're gidgen'ing your own API bindings, etc.
>
> Problem is that GObject is already there - the C type. 
> ObjectWrap wraps it. It was named ObjectG before, but Element 
> Green gave it a more meaningful name that automatically tells 
> is what the type is about...
Given that the type name itself does not matter for ABI I’d say 
just name the C types like _GObject_t; and call the D classes 
things like GObject. Ideally users will be using your D interface 
and basically never touch the C stuff; so having that interface 
be the focus for naming etc. is the way to go imho.