[Wxlua-users] Moved files to module structure

[John L. <jla...@gm...>]

I've moved the files to the new structure, supposing that it was
suitable for everyone. It currently builds cleanly in linux using
wxWidgets 2.6. I have not moved or modified my xxx_wx26.dsp VC6
project files or tested it in msw.

Currently we're still using the wrapper method where a giant
wxluawrap.cpp file is generated in the src directory of any program
using it. I've decided to move wxLuaPrinting/HtmlWindow into the
wrapper directory and added %inlinefile to the wxluawrap.lua. This tag
will directly include the given file "as is." It works nicely for
these two files since all they do is provide a means to use c++
virtual functions in lua for specific classes. I cannot think of any
reason why a user would want to include their headers. They're also
trivially small compared to the wrapper file itself, so they don't add
much more bloat over what we've already got.

I've broken the library into three parts:
wxlua - the base and this should be able to be used as is (not currently th=
ough)
wxluadebug - a library for showing the stacktree and maybe other debug stuf=
f
                    hopefully this can be made to only require wxlua.
wxluasocket - the socket library that the wxlua app uses, this
requires the above.
I've not added Rays stuff yet.

It's not done yet and you have to link them all together currently,
but this should be possible. Anyway, I hope that with a good build
system and some samples for testing people can make changes and easily
see if they've broken anything.

See wxLua/docs/dirs.txt for a description of how it's supposed to
work... You can compile wxLua by going into apps/wxlua/src and running
make (maybe twice, I'll have to see about that).

Francesco, I have given you cvs access, but let me get my project
files working and make sure it works in VC6 so when you test it you're
not struggling with build problems. I suggest that we keep the current
Makefiles since they're very readable and simple to maintain. I don't
think we need configure for now and it'll add unnecessary complexity.
Unless of course, it can be made to work out of the box.

Feel free to comment on the structure, positive or negative, we've got
to all be happy with this.

Regards,
    John Labenski