From: Francesco M. <f18...@ya...> - 2006-03-06 23:09:17
|
Hi, the website FAQ has been completed. Please feel free to propose changes, more Q&A or anything else. I've also completed the install.html file and autopackage spec file. One thing I think still needs to be done is: 1) remove bindings/wxwidgets/fl.i 2) remove samples/fldemo.wx.lua I mean: FL is old and unmaintained. And it's not built together with wx. Currently it doesn't work with wxLua (since it should be moved to bindings/wxfl and a new module should be created, isn't it?) so I think it's best to just remove it... Francesco |
From: John L. <jla...@gm...> - 2006-03-06 23:45:42
|
On 3/6/06, Francesco Montorsi <f18...@ya...> wrote: > Hi, > the website FAQ has been completed. Please feel free to propose > changes, more Q&A or anything else. > > I've also completed the install.html file and autopackage spec file. > > One thing I think still needs to be done is: > 1) remove bindings/wxwidgets/fl.i > 2) remove samples/fldemo.wx.lua > > I mean: FL is old and unmaintained. And it's not built together with wx. > Currently it doesn't work with wxLua (since it should be moved to > bindings/wxfl and a new module should be created, isn't it?) so I think No it would work just like wxstc before we separated it, it's turned off using wxLUA_USE_FL 0. So if you turned it back on in wxluasetup.h you'd get linker errors if you didn't link to wxfl.lib or whatever it's called. > it's best to just remove it... You're probably right. I hate to remove stuff like that since it's a lot of work to put it back, but the FL has been dead for some time now. I keep seeing messages of something new on wx-dev, but I haven't checked to see if that's materialized yet. 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 can do both of these things tonight, I can just clear out the files (so it'll still compile) like I did before and when you rebake you'll just have to remove the empty files. -John Labenski |
From: Francesco M. <f18...@ya...> - 2006-03-07 10:52:28
|
John Labenski ha scritto: > On 3/6/06, Francesco Montorsi <f18...@ya...> wrote: >> Hi, >> the website FAQ has been completed. Please feel free to propose >> changes, more Q&A or anything else. >> >> I've also completed the install.html file and autopackage spec file. >> >> One thing I think still needs to be done is: >> 1) remove bindings/wxwidgets/fl.i >> 2) remove samples/fldemo.wx.lua >> >> I mean: FL is old and unmaintained. And it's not built together with wx. >> Currently it doesn't work with wxLua (since it should be moved to >> bindings/wxfl and a new module should be created, isn't it?) so I think > > No it would work just like wxstc before we separated it, it's turned > off using wxLUA_USE_FL 0. So if you turned it back on in wxluasetup.h > you'd get linker errors if you didn't link to wxfl.lib or whatever > it's called. yes: when I said it doesn't work I meant that putting wxLUA_USE_FL to 1 yields to linking errors... > >> it's best to just remove it... > > You're probably right. I hate to remove stuff like that since it's a > lot of work to put it back, but the FL has been dead for some time > now. I keep seeing messages of something new on wx-dev, but I haven't > checked to see if that's materialized yet. wxAUI is pretty good and there are also wxIFM and wxDockIt. wx developers have put the wxIFM patch in pending status: they want to see which library (wxAUI or wxIFM) is more used and then they will integrate the winning one... > > 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 yes, I agree > > I can do both of these things tonight, I can just clear out the files > (so it'll still compile) like I did before and when you rebake you'll > just have to remove the empty files. ok, sure. Just a tip: you can cvs remove -f the files directly instead of just empting them. Then I'll just update bakefiles and run bakefile_gen... Francesco |
From: klaas.holwerda <kho...@xs...> - 2006-03-07 16:26:49
|
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. Klaas |
From: John L. <jla...@gm...> - 2006-03-07 19:30:25
|
On 3/7/06, klaas.holwerda <kho...@xs...> 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 |
From: John L. <jla...@gm...> - 2006-03-07 22:17:10
|
On 3/7/06, John Labenski <jla...@gm...> wrote: > On 3/7/06, klaas.holwerda <kho...@xs...> wrote: > > John Labenski wrote: > > > > > > The plot.i file should also go into it's own directory. I see message= s > > > 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 i= t > > > 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 didn't have the heart to delete fl.i, so I moved all the override.hpp code for it into fl.i and removed it from the wx_rules.lua with a note at the top saying that it's not maintained. I think that if Ray Gilbert was using it and if he wanted to get back into wxLua he'd want it. I think it's best to keep it as a starting point for anyone with the time/interest to get it working again. I did remove plot.i since it was basicly empty. Everything was remmed out and I don't think it was worth saving since you could remake what little was there in a few minutes. I'd rather not bother with making a wrapper for wxPlot right now since I don't use it and don't have the time to write/test it. I emptied out modules/wxbind/src/plot.cpp modules/wxbind/src/fl.cpp Francesco could you delete them and rebake. I looked at the cvs delete -f, but I don't think I understand it completely. What if a person (me) had to do a new checkout, they wouldn't get the files and when you try to build it you'd get errors. Sorry about making you have to rebake all the time. Could you also delete bin2c.c, the Makefile in that dir, and the bakefile stuff for it (just leave util/bin2c/bin2c.lua). Thanks, John Labenski |
From: Francesco M. <f18...@ya...> - 2006-03-08 19:51:29
|
John Labenski ha scritto: > On 3/7/06, John Labenski <jla...@gm...> wrote: >> On 3/7/06, klaas.holwerda <kho...@xs...> 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 didn't have the heart to delete fl.i, so I moved all the > override.hpp code for it into fl.i and removed it from the > wx_rules.lua with a note at the top saying that it's not maintained. I > think that if Ray Gilbert was using it and if he wanted to get back > into wxLua he'd want it. I think it's best to keep it as a starting > point for anyone with the time/interest to get it working again. > > I did remove plot.i since it was basicly empty. Everything was remmed > out and I don't think it was worth saving since you could remake what > little was there in a few minutes. I'd rather not bother with making a > wrapper for wxPlot right now since I don't use it and don't have the > time to write/test it. > > I emptied out > modules/wxbind/src/plot.cpp > modules/wxbind/src/fl.cpp > Francesco could you delete them and rebake. I looked at the cvs delete > -f, but I don't think I understand it completely. What if a person > (me) had to do a new checkout, they wouldn't get the files and when > you try to build it you'd get errors. > > Sorry about making you have to rebake all the time. Could you also > delete bin2c.c, the Makefile in that dir, and the bakefile stuff for > it (just leave util/bin2c/bin2c.lua). done |