Re: GDNative thick binding design

[Per Sandberg <per.s.sandberg@bahnhof.se>]

Real good work.

And especially that you started with a "game" that way you usually get a 
better feeling for what is needed, and to start to explore from the game 
side with the focus How do to get an Ada api not a C api written i Ada 
is a realy good path.

But I still think that the binding is kind of upside down with the 
Low-level stuff on the top visible for everyone and the think bindings 
highlighted as such instead of the other way around.

And on the project structure, for the "library project Adventure"  I 
would have used and exended project 'library project Adventure extends 
"../../gdnative_ada.gpr" is', by doing that it's possible to move the 
methods in engine_hooks up to the root project and only have the "game" 
stuff in the adventure project.

/Regards
/P

On 26/10/2020 04:38, Michael Hardeman wrote:
> On Wednesday, October 21, 2020 at 7:23:39 PM UTC-4, Luke A. Guest wrote:
>> On 21/10/2020 23:08, Michael Hardeman wrote:
>>
>>> Hey Luke,
>>>
>>> I managed to figure it out: https://ideone.com/H9sV55
>>>
>> I'm fairly sure that's almost right. I think the idea is that you only
>> need to pass the parameters to a single function which then dispatches
>> to the correct constructor for you.
> 
> Hey Luke,
> 
> https://github.com/MichaelAllenHardeman/gdnative_ada
> I've done an initial pass on the thick binding. Do you think you could give me some pointers on where I could do better?
> I have a feeling there is a way to do GDNative.Thick.Objects better
> 
> Still, as is it's pretty nice to use. It only takes just a tiny bit of user code to get an object registered and running a function on each frame.
> https://github.com/MichaelAllenHardeman/gdnative_ada/tree/master/examples/adventure_game/src
>