So, Ritchie wrote a generator in Ruby, which
produced a C file containing over 2300 functions. Now, as you know, the C source of a Neko library is
only half of the undertaking. The rest of the work involves creating a haXe framework that will allow
any user of the library to access its functionality in a friendly object - oriented way. Knowing this, Ritchie
avoided creating classes to contain all 2300 of his newly created functions and instead devised a proxy
system that allows dynamic access to the functions on an as needed basis. This meant that very few of
the functions were then hard coded into the haXe classes and were instead stored within a SQLite
database file to provide a safe lookup facility.
Okay, so where does this leave the developer wishing to use hxGtk ? Well, the long - term plan for the
hxGtk library is to eventually create all of the classes necessary to wrap the entire GTK library. Indeed, a
certain amount of this class framework already exists, but at the time of writing this book, it is still very
young and will likely change frequently before a finalized framework is available.
Pages:
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926