On 3/7/06, klaas.holwerda <[EMAIL PROTECTED]> wrote:
> John Labenski wrote:
> >
> > The plot.i file should also go into it's own directory. I see messages
> > on wx-users that people seem to use the plot widget every once in a
> > while. Maybe we should keep that, if nothing else it shows how easy it
> > is to make a binding for a outside library.
> > bindings/wxplot
> > modules/wxbindplot
> >
> I also like this idea, it sets the right approach for things to come,
> when more modules from e.g. wxCode get wrapped.
I was thinking about wrapping some of my things in wxCode, but I think
the best solution is to put the binding in the wxCode project. If we
start to have bindings for projects not maintained by anyone using
wxLua or the wxCode project regularly we can get out of sync and it'd
be burden on the wxLua maintainers to keep things up to date. Take for
example the FL stuff, I've never used it and have no way to test or do
anything with it, so it just languishes.
It may be more troublesome for people who want to build wxLua
themselves to have to get the other bindings running, but they'll have
to already have the wxCode c++ code anyway.
Regards,
John Labenski
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Wxlua-users mailing list
Wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
