Re: GDNative thick binding design

[Michael Hardeman <mhardeman25@gmail.com>]

On Monday, October 26, 2020 at 9:53:52 AM UTC-4, Michael Hardeman wrote:
> > 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
> Hey Persan, 
> 
> Thanks for the words of encouragement. 
> Those changes don't sound too difficult. I'm not sure if I'll be able to truly hide the engine hook stuff. I'll try it out on a branch today.

I've done a pass pulling the Thick bindings up a level and pushing the thin bindings down a level. Right now they are on a separate branch. There is some stuff I can clean up that would make me happier about it. I still don't see how to move the engine_hooks stuff into the library level code because the External_Names names that need to be exported for those functions have a prefix "adventure_" that is configured at the project level. I think I could get away with it maybe if I use gnatprep preprocessor in some way https://gcc.gnu.org/onlinedocs/gcc-4.1.2/gnat_ugn_unw/Integrated-Preprocessing.html#Integrated-Preprocessing

https://github.com/MichaelAllenHardeman/gdnative_ada/tree/architecture-refactor