wxlua-users Mailing List for wxLua

Oops wrong link:
http://www.xs4all.nl/~kholwerd/tmp/wxluacan.tgz
klaas.holwerda wrote:

Hi John,
Here i put a wxCanLua which has the smart pointerlist as i suggested.
I works oke.
In the top of the cansim.cpp its MyFrame::MyFrame you can how to use it.
http://www.xs4all.nl/~kholwerd/tmp/wxLua2.zip
The idea is that the object created in lua script are added to such a list.
And for instance wxlCanObj will be stored in such a list too.
Next it does not matter who deletes the lists/smartpointers first, the 
last one will simply delete the wxObject derived objects which we wanted 
to delete save.
I can make wxlCanLua so that it uses this list already, but that would 
really make sence if the m_pTrackedList would be of this type.
regards,
Klaas
klaas.holwerda wrote:
>
>
> Shall i prepare something like the above, next you can choose ;-)
>

On 2/21/06, klaas.holwerda <kho...@xs...> wrote:
> >> If so we might pay less attention to VC6 which is not to good i think.
> > I think MSVC6 is going to be completely 'deprecated' in few years...
> That is what i think too. But at the moment?
> > maybe we could:
> > a) move msvc6 project files in the new build\msvc6 folders
> > b) convert msvc6 project files and add them in the build\msvc7/8 folder=
s
> Good idea.
> >
> > Unfortunately AFAIK MSVC.NET and MSVC2005 use two different formats...
> > I'm going to see if I can add these formats to bakefile.
But, don't they both support converting from dsp files to their sln
files? I use 2005, the free one new and I've also used .NET (a few
years back) and both converted the dsp files just fine. You had to be
careful about deleting the sln files if you edited the dsp files, but
that wasn't a big deal.
> >> I myself get linking errors, etc. i wonder if this is because of VC6
> >> or soemthing else.
> I put the two logs files here.
>
> First i tried to make wxStedit which i downloaded at wxCode. ( I tried
> first CVS but had problems so i downloaded it eventually.)
> It is not clear yet from install.html which one i should get.
> That i tried to build without success.
> Next the log file for wxLua.
>
> http://www.xs4all.nl/~kholwerd/tmp/logs/
I've updated wxStEdit in wxCode's CVS to remove the warnings. I'm
sorry, I've never tried to compile wxWidgets as a DLL so I have no
experience on why you get so many unresolved function errors. Do you
have to cross link libraries to get it to work? Dunno.
John Labenski

On 2/21/06, k. holwerda <kla...@nl...> wrote:
> wx_object.cpp
> ..\..\..\modules\wxlua/include/wxlstate.h(184) : warning C4251:
> 'm_coroutineStates' : class 'wxArrayLuaState' needs to have
> dll-interface to be used by clients of class 'wxLuaStateRefData'
> ..\..\..\modules\wxlua/include/wxlstate.h(156) : see declaration
> of 'wxArrayLuaState'
> ..\..\..\modules\wxlua/include/wxlstate.h(190) : warning C4251:
> 's_wxHashMapLuaStateRefData' : class 'wxHashMapLuaStateRefData' needs to
> have dll-interface to be used by clients of class 'wxLuaStateRefData'
> ..\..\..\modules\wxlua/include/wxlstate.h(159) : see declaration
> of 'wxHashMapLuaStateRefData'
> ..\..\..\modules\wxluadebug/include/wxldebug.h(108) : warning C4275: non
> dll-interface class 'wxLuaDebugDataItemArray' used as base for
> dll-interface class 'wxLuaDebugData'
> ..\..\..\modules\wxluadebug/include/wxldebug.h(100) : see
> declaration of 'wxLuaDebugDataItemArray'
Fixed.
Regards,
 John Labenski

On 2/21/06, Francesco Montorsi <f18...@ya...> wrote:
> Hi,
>
> John Labenski ha scritto:
> > On 2/21/06, Francesco Montorsi <f18...@ya...> wrote:
> >> Hi John,
> >> I see there are various project files and Makefiles not
> >> bakefile-generated scattered among the wxLua tree... could we remove t=
hem ?
> >>
> >> If the makefiles are still up2date, I think we could keep them as
> >> 'safety' system in case bakefile-generated ones fail in some way.
> >
> > I use all the "old" Makefiles regularly and I would like them to stay.
> > They are based on wx-config and should work in linux on any system
> > that has wx-config in their path. They're also very easy to understand
> > so that I can add profiling and other temporary things easily.
> ok, sure.
> Just one question: is there anything in hand-written makefiles which you
> can't do with ./configure ?
Heh, I can understand the hand written ones and they're easy to
modify. The bakefile Makefiles are basically incomprehensible, there's
way too many conditions to make it parseable by a mortal at a glance.
If the existing makefiles conflict with something, we can rename them
to Makefile.wx-config.
-John Labenski

Hi,
Francesco Montorsi wrote:
>
>> If so we might pay less attention to VC6 which is not to good i think.
> I think MSVC6 is going to be completely 'deprecated' in few years...
That is what i think too. But at the moment?
> maybe we could:
> a) move msvc6 project files in the new build\msvc6 folders
> b) convert msvc6 project files and add them in the build\msvc7/8 folders
Good idea.
>
> Unfortunately AFAIK MSVC.NET and MSVC2005 use two different formats... 
> I'm going to see if I can add these formats to bakefile.
Arrg!
>
>
>> Did you both compile all flavours in batch build using 2005 ?
> > If so do they compile well?
> I don't like to do batch builds with IDE.
I know.
> I usually use makefiles for that and makefile.vc allowed me to compile 
> wxLua with any combination of options I've tried so far...
With project files we must get it too work too, this is what the general 
user will use.
Especially when debugging i prefer much to debug inside the linked 
libraries and all.
That is often how i understand where the problems are.
>
>
>
>> I myself get linking errors, etc. i wonder if this is because of VC6 
>> or soemthing else.
I put the two logs files here.
First i tried to make wxStedit which i downloaded at wxCode. ( I tried 
first CVS but had problems so i downloaded it eventually.)
It is not clear yet from install.html which one i should get.
That i tried to build without success.
Next the log file for wxLua.
http://www.xs4all.nl/~kholwerd/tmp/logs/
Let me know what i should do to test more,
Klaas

Hi,
John Labenski ha scritto:
> On 2/21/06, Francesco Montorsi <f18...@ya...> wrote:
>> Hi John,
>> I see there are various project files and Makefiles not
>> bakefile-generated scattered among the wxLua tree... could we remove them ?
>>
>> If the makefiles are still up2date, I think we could keep them as
>> 'safety' system in case bakefile-generated ones fail in some way.
> 
> I use all the "old" Makefiles regularly and I would like them to stay.
> They are based on wx-config and should work in linux on any system
> that has wx-config in their path. They're also very easy to understand
> so that I can add profiling and other temporary things easily.
ok, sure.
Just one question: is there anything in hand-written makefiles which you 
can't do with ./configure ?
Francesco

On 2/21/06, Francesco Montorsi <f18...@ya...> wrote:
> Hi John,
> I see there are various project files and Makefiles not
> bakefile-generated scattered among the wxLua tree... could we remove them=
 ?
>
> If the makefiles are still up2date, I think we could keep them as
> 'safety' system in case bakefile-generated ones fail in some way.
I use all the "old" Makefiles regularly and I would like them to stay.
They are based on wx-config and should work in linux on any system
that has wx-config in their path. They're also very easy to understand
so that I can add profiling and other temporary things easily.
> Project files I think are not maintainable by hand and thus should be
> removed...
Yes, I'll remove all the XXX_wx26.dsp files soon.
Regards,
 John Labenski

Hi John,
 I see there are various project files and Makefiles not 
bakefile-generated scattered among the wxLua tree... could we remove them ?
If the makefiles are still up2date, I think we could keep them as 
'safety' system in case bakefile-generated ones fail in some way.
Project files I think are not maintainable by hand and thus should be 
removed...
Francesco

Hi,
k. holwerda ha scritto:
>> Is there any other problem which must be solved before the release ?
>>
> What should compile in VC when using batch build?
> 
> ( I read that VC2005 is for free now, is it true?? )
the express edition is free but it has some limited features.
Nonetheless it's a great thing: something free from ms ;)
> If so we might pay less attention to VC6 which is not to good i think.
I think MSVC6 is going to be completely 'deprecated' in few years...
maybe we could:
a) move msvc6 project files in the new build\msvc6 folders
b) convert msvc6 project files and add them in the build\msvc7/8 folders
Unfortunately AFAIK MSVC.NET and MSVC2005 use two different formats... 
I'm going to see if I can add these formats to bakefile.
> Did you both compile all flavours in batch build using 2005 ?
 > If so do they compile well?
I don't like to do batch builds with IDE.
I usually use makefiles for that and makefile.vc allowed me to compile 
wxLua with any combination of options I've tried so far...
> I myself get linking errors, etc. i wonder if this is because of VC6 or 
> soemthing else.
> 
> Klaas
> 
> wx_object.cpp
> ...\..\..\modules\wxlua/include/wxlstate.h(184) : warning C4251: 
> 'm_coroutineStates' : class 'wxArrayLuaState' needs to have 
> dll-interface to be used by clients of class 'wxLuaStateRefData'
> ..\..\..\modules\wxlua/include/wxlstate.h(156) : see declaration 
> of 'wxArrayLuaState'
> ...\..\..\modules\wxlua/include/wxlstate.h(190) : warning C4251: 
> 's_wxHashMapLuaStateRefData' : class 'wxHashMapLuaStateRefData' needs to 
> have dll-interface to be used by clients of class 'wxLuaStateRefData'
> ..\..\..\modules\wxlua/include/wxlstate.h(159) : see declaration 
> of 'wxHashMapLuaStateRefData'
> ...\..\..\modules\wxluadebug/include/wxldebug.h(108) : warning C4275: 
> non dll-interface class 'wxLuaDebugDataItemArray' used as base for 
> dll-interface class 'wxLuaDebugData'
> ..\..\..\modules\wxluadebug/include/wxldebug.h(100) : see 
> declaration of 'wxLuaDebugDataItemArray'
these are warnings, what about the linking errors?
Francesco

Francesco Montorsi wrote:
>
> Is there any other problem which must be solved before the release ?
>
What should compile in VC when using batch build?
( I read that VC2005 is for free now, is it true?? )
If so we might pay less attention to VC6 which is not to good i think.
Did you both compile all flavours in batch build using 2005 ?
If so do they compile well?
I myself get linking errors, etc. i wonder if this is because of VC6 or 
soemthing else.
Klaas
wx_object.cpp
..\..\..\modules\wxlua/include/wxlstate.h(184) : warning C4251: 
'm_coroutineStates' : class 'wxArrayLuaState' needs to have 
dll-interface to be used by clients of class 'wxLuaStateRefData'
 ..\..\..\modules\wxlua/include/wxlstate.h(156) : see declaration 
of 'wxArrayLuaState'
..\..\..\modules\wxlua/include/wxlstate.h(190) : warning C4251: 
's_wxHashMapLuaStateRefData' : class 'wxHashMapLuaStateRefData' needs to 
have dll-interface to be used by clients of class 'wxLuaStateRefData'
 ..\..\..\modules\wxlua/include/wxlstate.h(159) : see declaration 
of 'wxHashMapLuaStateRefData'
..\..\..\modules\wxluadebug/include/wxldebug.h(108) : warning C4275: non 
dll-interface class 'wxLuaDebugDataItemArray' used as base for 
dll-interface class 'wxLuaDebugData'
 ..\..\..\modules\wxluadebug/include/wxldebug.h(100) : see 
declaration of 'wxLuaDebugDataItemArray'
-- 
Unclassified

On 2/20/06, Francesco Montorsi <f18...@ya...> wrote:
> Francesco Montorsi ha scritto:
> > Hi,
> > as you can see, I start to think to the first release of wxLua ;)
Thanks!
> > So, let's discuss this issue.
> >
> > I'd make a total of 4 releases:
> >
> > 1) a win32 MSI install package. This can be generated using InnoSetup
> > and it should distribute all wxLua tree including EXE, doxygen generate=
d
> > docs and .lib files, all built in release mode, possibly against a
> > static build of wxWidgets.
> I have created this package and added it to CVS.
> I also uploaded an experimental setup installer for win32 at
>
> http://wxlua.sourceforge.net/wxLua-2.6.2.1-setup.exe
>
> I've tried it out for a while and it works nice. If someone can test it
> and confirms it installs wxLua and that it works it would be good.
> However it needs:
>
> 1) to have all wxLua sample files to be renamed with .wxlua extension
> (.wx.lua extension is not good for windows when you need to associate a
> program to it - at least programmatically)
That will make syntax highlighting editors not be able to immediately
hilight it for lua. I'm not sure that's a good idea.
> 2) to have wxLuaEditor able to open .wxlua files which are passed to it
> as first parameter... John, can you do that ?
If you really think that that's a good idea, I don't think so.
> BTW I think that all wxLua samples should be reviewed as they look quite
> old and some doesn't work smoothly...
Heh, there are more samples from the original distribution, but I just
took the ones that work out of the box. But I do agree that they are
not very exciting.
> Is there any other problem which must be solved before the release ?
> Besides the website completion, obviously... (any help writing pages
> would be very appreciated ;))
I will try to put some text up there tomorrow.
-John Labenski