From: klaas.holwerda <kho...@xs...> - 2005-06-04 20:53:06
|
Hi John, I think this #1 looks good. About the bindings and wrapping, oke too. A soon a there is a flexible way to extend the default wxWidgets wrapping with the app or other library its wrappings, all will be oke. I imagine this will be by making it possible to registers groups ( one table per lib/app). Or maybe Ray already has something better. I think we will be able to generate a wxluaXXX.lib in static and shared. But all that is for later, since it has no impact on the structure as you say. John Labenski wrote: > ============================== > 1.) Use a module approach > /modules/ > /build/ - to have build files for all of this > /lua/ -- lua itself > /include/ > /src/ > /the rest of lua.../ > /wxlua/ - the wxlua library itself > /include/ = internal.h, interp.h, library.h > /src/ = internal.cpp, interp.cpp, library.cpp > /wxluasocket/ - lua to cpp sockets (the current lua sockets) > /include/ = debugio.h, socket.h /src/ = > debugio.cpp, socket.cpp > /wxluadebug/ - mechanism for getting/showing info from lua > /include/ = debug.h, stacktree, splittree > /src/ = debug.cpp, stacktree, splittree > /xmlrpc/ - is is a generic lib right? so don't prepend wxlua to > it? > /include/ = ... Rays stuff > /src/ = ... Rays stuff > /debuggernub/ - this is a generic lib for xmlrpc? don't > prepend wxlua to it > /include/ = ... Rays stuff > /src/ = ... Rays stuff > /wxluadebugger/ - this depends on wxlua so prepend wxlua to it > /include/ = ... Rays stuff > /src/ = ... Rays stuff > > I think Klaas is suggesting that a user will set the include path to > wxLua/modules and then in a cpp file do > #include "wxlua/include/xxx.h" > Exactly! And of course all other in a simular way like: #include "wxluasocket/include/xxx.h" #include "wxluadebug/include/xxx.h" > I vote #1. > > Me too. So i hope the others will respond quickly, so things can start ;-) Regards, Klaas |