wxlua-users Mailing List for wxLua (Page 4)

is it ok then to make wxLua 2.8.0.0 release saturday morning ?

For doing releases I think it's better IM than emails (to solve any 
eventual problem coming out at the last moments - they never are 
missing); so:

  - if you want to contact me through IM you can use my email address 
for Yahoo messenger or fr...@ho... with MSN messenger.

  - I'll also be available through #IRC at wxWidgets chat room.

Francesco


Francesco Montorsi ha scritto:
> Hi all,
>     is it if we try to make wxLua 2.8.0.0 release before 25 december?
> It would be a nice Christmas gift for some of my friends which asked me 
> a nice interpreted language for GUI apps ;)
> 
> Francesco
> 
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

klaas.holwerda ha scritto:
> Hi,
> 
> stc library is not located anymore, because -llua5.1 is not on my system.
> It should not be required at this stage.
> It looks like Francesco had lua installed on his system, i don't.
right - sorry. Fixed.

Francesco

Hi,

stc library is not located anymore, because -llua5.1 is not on my system.
It should not be required at this stage.
It looks like Francesco had lua installed on his system, i don't.

Klaas

configure:6931: result: no
configure:6980: checking if wxSTC contrib is available
configure:7005: g++ -o conftest  -g3 -O0 -Wall -Wundef 
-Wno-ctor-dtor-privacy  
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__  conftest.cpp  -llua5.1 -L/usr/local/lib 
-pthread   /usr/local/lib/libwx_gtk2d_stc-2.8.a 
/usr/local/lib/libwx_gtk2d_xrc-2.8.a 
/usr/local/lib/libwx_gtk2d_html-2.8.a 
/usr/local/lib/libwx_gtk2d_adv-2.8.a 
/usr/local/lib/libwx_based_net-2.8.a 
/usr/local/lib/libwx_based_xml-2.8.a 
/usr/local/lib/libwx_gtk2d_core-2.8.a /usr/local/lib/libwx_based-2.8.a 
-lexpat -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 
-lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 
-lXinerama -lXxf86vm -lSM -lpng -ljpeg -ltiff -lz -ldl -lm  >&5
/usr/bin/ld: cannot find -llua5.1
collect2: ld returned 1 exit status
configure:7011: $? = 1
configure: failed program was:

Hi,

Can't compile on linux. The lua.h is not found, very likely missing an 
include path now.
This is from wxlstate.h

Klaas

I like the logo with the "shiny" wxWidgets blocks in the center with
the blue lua circling it that's on the website now.

It could be a little cleaner, there's a little blur on the Lua circle
and dashed circle that you can only see when you blow it up pretty
big, and it uses a lot of colors so it's not suited to be converted
into an xpm, but I'm not complaining.

-John Labenski

On 12/20/06, Francesco Montorsi <f18...@ya...> wrote:
> John Labenski ha scritto:
> >
> > Ok, another problem, using VC 2005 and batch build it's puts Debug DLL
> > Multilib lua5.1.dll into lib/vc_lib not lib/vc_dll.
> I should have already solved 2-3 hours ago.... it was a typo in lua_dll
> template.

Works now, thanks.

> > ==============================
> >
> > Ahh... what about this? After a build you copy the bin/[build]/*.exe
> > to just bin/*.exe and overwrite them. The originals still would exist
> > in the build dir. Is this easy to do or even make sense or would it be
> > too confusing?
> well, I don't know... it's easy to do but maybe unexpect by the user...
>
> Why would we want it? So that the DLL can be copied to just "bin" and
> not "bin\vc*" ?

So that you can run genwxbind.lua easily. It's probably not important,
never mind.

-John Labenski

John Labenski ha scritto:
> On 12/19/06, Francesco Montorsi <f18...@ya...> wrote:
>>> If you just copy wxlua_mswXXX_lua.lib to lua5.1.lib the luamodue works.
>> I was aware - it should be fixed now as our lua library is now named
>> lua5.1 and creates an interpreter called exactly "lua".
>>
>> This is more coherent I think from the previous situation where the lua
>> libraries are called lua5.1 (because the lua module _must_ be linked
>> against a DSO called exactly lua5.1) but then the interpreter were
>> called "wxlua-lua".
> 
> Ok, another problem, using VC 2005 and batch build it's puts Debug DLL
> Multilib lua5.1.dll into lib/vc_lib not lib/vc_dll. 
I should have already solved 2-3 hours ago.... it was a typo in lua_dll 
template.


>>> I had to copy all of the dlls from
>>> wxWidgets/lib/vc_dll/*.dll and the sample/luamodule.wx.lua into the
>>> dir that I ran $wxlua-lua.exe from.
>> I know. that's why I created copy-dlls.bat but now that we use different
>> dirs for different builds also for bin\*.exe that script is not so useful...
> 
> Heh, I added some really ugly batch file code to genwxbind.bat to get
> it to work for a few cases.
good


> ==============================
> 
> Ahh... what about this? After a build you copy the bin/[build]/*.exe
> to just bin/*.exe and overwrite them. The originals still would exist
> in the build dir. Is this easy to do or even make sense or would it be
> too confusing?
well, I don't know... it's easy to do but maybe unexpect by the user...

Why would we want it? So that the DLL can be copied to just "bin" and 
not "bin\vc*" ?

Francesco

On 12/20/06, Francesco Montorsi <f18...@ya...> wrote:
> klaas.holwerda ha scritto:
> > Hi,
> >
> > I read lua5.1.lib was needed. So this exe renaming is not a mistake??
> > I keep changing pack and forth, i don't know any what is right :-(
> > Will it hopefully be  the same naming on Unix?
> very sorry about that.
>
> "lua" is now the definitive name (unless others find problems with it)
> of the lua interpreter which gets built together with wxLua.
>
> In this way, if the user does not have Lua installed and he compiles and
> installs wxLua, he end up with an "official" (i.e installed in the
> standard paths and with standard naming) lua + wxLua.
> In fact lua libraries are now called lua5.1 and are installed in
> $LIBDIR. Exactly like lua packages would do.

Sounds good to me.

John Labenski

On 12/19/06, Francesco Montorsi <f18...@ya...> wrote:
> > If you just copy wxlua_mswXXX_lua.lib to lua5.1.lib the luamodue works.
> I was aware - it should be fixed now as our lua library is now named
> lua5.1 and creates an interpreter called exactly "lua".
>
> This is more coherent I think from the previous situation where the lua
> libraries are called lua5.1 (because the lua module _must_ be linked
> against a DSO called exactly lua5.1) but then the interpreter were
> called "wxlua-lua".

Ok, another problem, using VC 2005 and batch build it's puts Debug DLL
Multilib lua5.1.dll into lib/vc_lib not lib/vc_dll. See
modules/build/msw/modules_mod_lua.dsp

!ELSEIF  "$(CFG)" == "mod_lua - Win32 DLL Debug Multilib"
...
# ADD LINK32 /nologo /dll /machine:i386
/out:"..\..\..\lib\vc_lib\lua5.1.dll"
/implib:"..\..\..\lib\vc_lib\lua5.1.lib"

> Now installing wxLua you get installed also a vanilla lua5.1 using all
> standard names. And since it's now available a USE_SYSTEM_LUA option to
> disable the built-in lua, I think this is the best we can do.

Great.

> > By the way, is there a way to combine all of wxWidgets and wxLua into
> > the wx.dll?
> no easy ways I'm aware of. To get a single DLL with all wxWidgets and
> wxLua we'd need a giant library which contains all wx sources and wx lua
> sources.
>
> IIRC there was a system, maybe with borland, to merge different DLLs
> into a single one. I'll have a look at it.

I found a program that sounded like it might work by googling, but it
had a commercial license, I forget what it was.

> Anyway I don't think it's a problem but rather a (small) advantage:
> instead of a single huge DLL we have a smaller set of DLLs and with a
> bit of luck, when we run a wxLua app, some of them may be already loaded
> in the RAM by other processes, thus allowing for the OS to avoid to load
> all the DLLs from hard disk.

Fair enough.

> > I had to copy all of the dlls from
> > wxWidgets/lib/vc_dll/*.dll and the sample/luamodule.wx.lua into the
> > dir that I ran $wxlua-lua.exe from.
> I know. that's why I created copy-dlls.bat but now that we use different
> dirs for different builds also for bin\*.exe that script is not so useful...

Heh, I added some really ugly batch file code to genwxbind.bat to get
it to work for a few cases.

==============================

Ahh... what about this? After a build you copy the bin/[build]/*.exe
to just bin/*.exe and overwrite them. The originals still would exist
in the build dir. Is this easy to do or even make sense or would it be
too confusing?

Regards,
    John Labenski

klaas.holwerda ha scritto:
> Hi,
> 
> I read lua5.1.lib was needed. So this exe renaming is not a mistake??
> I keep changing pack and forth, i don't know any what is right :-(
> Will it hopefully be  the same naming on Unix?
very sorry about that.

"lua" is now the definitive name (unless others find problems with it) 
of the lua interpreter which gets built together with wxLua.

In this way, if the user does not have Lua installed and he compiles and 
installs wxLua, he end up with an "official" (i.e installed in the 
standard paths and with standard naming) lua + wxLua.
In fact lua libraries are now called lua5.1 and are installed in 
$LIBDIR. Exactly like lua packages would do.

Francesco

Hi,

I read lua5.1.lib was needed. So this exe renaming is not a mistake??
I keep changing pack and forth, i don't know any what is right :-(
Will it hopefully be  the same naming on Unix?

Klaas

Francesco Montorsi wrote:
>> I only saw a gray background on the logo, maybe because of old browsers.
>> But still i think there is to much in it. A logo for me needs to abstract without text.
>>     
> I don't agree. Take as example, wxWidgets logo, wxPython logo, apache 
> logo, etc. There are a lot of examples of logos with text. I think only 
> most important OSS can avoid the text in the logo: linux, gnu, few 
> others maybe.
>   
http://en.wikipedia.org/wiki/Logo

I think next must be minimal, that does not mean that on the top of the 
page it can not be mentioned. But being part of the logo is something else.

> Without the text, if the user sees the logo but he doesn't know the 
> project to which that logo refers, your projects does not get advertised! ;)
>   
If you think wxLua should in it, why not combine it with the word lua in 
the lua logo. Like putting just Wx behind the drawing or in front of the 
word lua somehow.
>
>   
>> So only the drawing part. And there i see the lua logo, which is i think a moon in front of the earth. And those two are 
>> orbiting wxWidgets. While i understand the lua logo, meaning lua is meant to orbit applications. This is idea is 
>> duplicated in the second circle.
>>     
> sorry - which second circle?
>   
I meant the second orbit. Moon around the earth is the first, the circle 
is those two around wxWidgets.
>   
>> "Easy power" i think should be removed, 
>>     
> why? it's a nice slogan I'd say... Python has the "batteries included" 
> slogan. We have "Easy power". We are clearly the winners :D
>   
I have the feeling it is not clear what a logo is. To me it can have 
text, but very little.
Like at the buttom of this page http://www.wxpython.org/
Slogans should not be part of it.
>  >and the "wxLua" in it, is a replication of what is in the drawing.
> my teachers were used to say "repetita iuvant" ;)
> also, people may not always look at the logos very carefully: some of 
> them may not infer from the logo (if there were no text) that it's the 
> wxLua logo.
> With wxLua written there, there's no problem
>   
Oke, but somehow integrate it with the drawing in artistic manner.
>   
>> Your turn to critici the old one :-)
>>     
> well, I think we already strived to put there the most antialiased 
> version - and it was not looking so antialiased after all.
No that is not the case. I attached two which are already much better, 
and where still on  my disk.
>  Plus the new 
> one is SVG based and thus can be used at any resolution without loosing 
> details.
>   
What we have in illustrator format and can be saved in svg if you want.
> And yes, the text is for me an advantage over the old one :)
> It's a matter of tastes obviously.
>
> Let's see what others vote.
>   
Fine,

Klaas

Klaas Holwerda ha scritto:
> Francesco Montorsi wrote:
> 
>> Are you sure you are looking at the very latest version (I've posted it 
>> 1-2 hours ago) ? I had to hit refresh at least 5-6 times on Firefox 
>> before the last version was loaded. I attach a small screenshot which 
>> shows how it should look.
> 
> Looks much better.
great

> I only saw a gray background on the logo, maybe because of old browsers.
> But still i think there is to much in it. A logo for me needs to abstract without text.
I don't agree. Take as example, wxWidgets logo, wxPython logo, apache 
logo, etc. There are a lot of examples of logos with text. I think only 
most important OSS can avoid the text in the logo: linux, gnu, few 
others maybe.

Without the text, if the user sees the logo but he doesn't know the 
project to which that logo refers, your projects does not get advertised! ;)


> So only the drawing part. And there i see the lua logo, which is i think a moon in front of the earth. And those two are 
> orbiting wxWidgets. While i understand the lua logo, meaning lua is meant to orbit applications. This is idea is 
> duplicated in the second circle.
sorry - which second circle?

> "Easy power" i think should be removed, 
why? it's a nice slogan I'd say... Python has the "batteries included" 
slogan. We have "Easy power". We are clearly the winners :D

 >and the "wxLua" in it, is a replication of what is in the drawing.
my teachers were used to say "repetita iuvant" ;)
also, people may not always look at the logos very carefully: some of 
them may not infer from the logo (if there were no text) that it's the 
wxLua logo.
With wxLua written there, there's no problem

> 
> Your turn to critici the old one :-)
well, I think we already strived to put there the most antialiased 
version - and it was not looking so antialiased after all. Plus the new 
one is SVG based and thus can be used at any resolution without loosing 
details.

And yes, the text is for me an advantage over the old one :)
It's a matter of tastes obviously.

Let's see what others vote.

Francesco

Francesco Montorsi wrote:

> Are you sure you are looking at the very latest version (I've posted it 
> 1-2 hours ago) ? I had to hit refresh at least 5-6 times on Firefox 
> before the last version was loaded. I attach a small screenshot which 
> shows how it should look.

Looks much better. I only saw a gray background on the logo, maybe because of old browsers.
But still i think there is to much in it. A logo for me needs to abstract without text.
So only the drawing part. And there i see the lua logo, which is i think a moon in front of the earth. And those two are 
orbiting wxWidgets. While i understand the lua logo, meaning lua is meant to orbit applications. This is idea is 
duplicated in the second circle.
"Easy power" i think should be removed, and the "wxLua" in it, is a replication of what is in the drawing.

Your turn to critici the old one :-)

Klaas



-- 
Unclassified

Klaas Holwerda ha scritto:
> Francesco Montorsi wrote:
>> I almost forgot to inform you: I've updated a bit also the website. In 
>> particular I've "downgraded" the logo to the old wxLua logo.
>>
>> IMHO it looks better than what me and Klaas managed to do ;)
>> Comments welcome.
> 
> Not appealing to me. Gray, big and colors that do not really combine. Also it does not blend with the background nicely.
> The one that was there was not antiliased, but i had versions without that problem, which somehow did not end up there.
> But more think this logo is better, in terms of design (not quality), i am oke with that.
Are you sure you are looking at the very latest version (I've posted it 1-2 
hours ago) ? I had to hit refresh at least 5-6 times on Firefox before the last 
version was loaded. I attach a small screenshot which shows how it should look.

I've also added an SVG version of that logo, which I created (in just a couple 
of minutes thanks to Inkscape and to the SVG blocks at 
http://wx.ibaku.net/logo/) to the "website/images" CVS:

http://wxlua.cvs.sourceforge.net/wxlua/website/images/wxlualogo.svg?view=log

I've done all the logo changes without asking first, please let me know if I 
should revert the changes.
I'm +1 for keeping them.
Klaas -1...

what others say?

Francesco

Francesco Montorsi wrote:
> I almost forgot to inform you: I've updated a bit also the website. In 
> particular I've "downgraded" the logo to the old wxLua logo.
> 
> IMHO it looks better than what me and Klaas managed to do ;)
> Comments welcome.

Not appealing to me. Gray, big and colors that do not really combine. Also it does not blend with the background nicely.
The one that was there was not antiliased, but i had versions without that problem, which somehow did not end up there.
But more think this logo is better, in terms of design (not quality), i am oke with that.

Klaas



-- 
Unclassified

I almost forgot to inform you: I've updated a bit also the website. In 
particular I've "downgraded" the logo to the old wxLua logo.

IMHO it looks better than what me and Klaas managed to do ;)
Comments welcome.

To make the logo appear decently I also had to invert the gradient 
direction and thus change the colours of the wxLua title.

I've also added a few notes on the changelog about the recent build 
system changes.

Francesco



Francesco Montorsi ha scritto:
> Hi all,
>     is it if we try to make wxLua 2.8.0.0 release before 25 december?
> It would be a nice Christmas gift for some of my friends which asked me 
> a nice interpreted language for GUI apps ;)
> 
> Francesco
> 
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

John Labenski ha scritto:
> On 12/18/06, Francesco Montorsi <f18...@ya...> wrote:
>> Hi all,
>>     is it if we try to make wxLua 2.8.0.0 release before 25 december?
>> It would be a nice Christmas gift for some of my friends which asked me
>> a nice interpreted language for GUI apps ;)
> 
> That would be nice. I will test again VC 2005 using dsw files, VC 2003
> using nmake, and configure. My VC 6 machine is not working anymore,
> it's a laptop and the hinge broke...
exactly like my father's super old (i486) laptop... it looks like the 
hinge is one of the most weak parts of laptops...

> There is still one last thing (as of six hours ago or so) for
> modules/build/msw/makefile.vc
> 
> The luamodule wants to compile with lua5.1.lib, see here
> !if "$(SHARED)" == "1" && "$(USE_LUAMODULE)" == "1"
>     ...
> 
> but  has
> 
> !if "$(SHARED)" == "0"
> __verbatimlua_lib___depname = \
>         ..\..\..\lib\vc_lib\wxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_lua.lib
> !endif
> !if "$(SHARED)" == "1"
> __verbatimlua_dll___depname = \
>         ..\..\..\lib\vc_dll\wxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_lua.dll
> 
> If you just copy wxlua_mswXXX_lua.lib to lua5.1.lib the luamodue works.
I was aware - it should be fixed now as our lua library is now named 
lua5.1 and creates an interpreter called exactly "lua".

This is more coherent I think from the previous situation where the lua 
libraries are called lua5.1 (because the lua module _must_ be linked 
against a DSO called exactly lua5.1) but then the interpreter were 
called "wxlua-lua".

Now installing wxLua you get installed also a vanilla lua5.1 using all 
standard names. And since it's now available a USE_SYSTEM_LUA option to 
disable the built-in lua, I think this is the best we can do.


> By the way, is there a way to combine all of wxWidgets and wxLua into
> the wx.dll?
no easy ways I'm aware of. To get a single DLL with all wxWidgets and 
wxLua we'd need a giant library which contains all wx sources and wx lua 
sources.

IIRC there was a system, maybe with borland, to merge different DLLs 
into a single one. I'll have a look at it.

Anyway I don't think it's a problem but rather a (small) advantage: 
instead of a single huge DLL we have a smaller set of DLLs and with a 
bit of luck, when we run a wxLua app, some of them may be already loaded 
in the RAM by other processes, thus allowing for the OS to avoid to load 
all the DLLs from hard disk.

> I had to copy all of the dlls from
> wxWidgets/lib/vc_dll/*.dll and the sample/luamodule.wx.lua into the
> dir that I ran $wxlua-lua.exe from.
I know. that's why I created copy-dlls.bat but now that we use different 
dirs for different builds also for bin\*.exe that script is not so useful...

 > I guess all these dlls could go
> into %WINDIR%/System32 or something?
as Klaas said, it would be better to extend the path, but sometimes I'm 
lazy and yes, I just copy them to windows\system32.

> Anyway the error message you get
> when run from cygwin is "error loading module "wx" from wx.dll." which
> is very cryptic since the real error when run from a DOS prompt is
> that the wxWidgets dlls cannot be found.
yep - error messages from GNU tools in general may be often more helpful 
than they are (just thinking to the "undefined reference to vtable" 
linker error) ;)

Francesco

Francesco Montorsi ha scritto:
> John Labenski ha scritto:
>> Can we test in configure if the lua and lua devel packages are
>> installed and use those sources? Too much work? I guess it would work
>> like wxWidgets use of the jpeg, png, etc libs. I don't know how to do
>> any of this. :(
> It wouldn't be much difficult from the build-system POV.
> The problem may be related to the way we include the lua headers:
> 
> #include "lua/include/lua.h"
> 
> I'll try to implement the check and then set a wxUSE_CUSTOM_LUA 
> preprocessor symbol if a usable lua 5.1 is found. The header inclusion 
> would then be modified:
> 
> #if wxUSE_CUSTOM_LUA
>     #include "lua.h"
> #else
>     #include "lua/include/lua.h"
> #endif
> 
> otherwise we could also simply add the "modules/lua/include" path to the 
> paths given to compiler so that we could just use:
> 
> #include "lua.h"
> 
> all the times.
I've done the change which now allows wxLua to be compiled against a 
system lua.

I've also fixed some other little problems with the build system.

Now everything should be ready (from the build system POV) for the 
release. If everyone could test the build system (in fact, I need to 
test it yet deeply under windows - i'll do that tomorrow), it would be 
great.

Francesco

John Labenski wrote:

> By the way, is there a way to combine all of wxWidgets and wxLua into
> the wx.dll? I had to copy all of the dlls from
> wxWidgets/lib/vc_dll/*.dll and the sample/luamodule.wx.lua into the
> dir that I ran $wxlua-lua.exe from. I guess all these dlls could go
> into %WINDIR%/System32 or something? 

Better extend your path, dll's are searched via the path.
At my work we always use a bat file, in which we extend the path first and next start the tool.
This prevents the polution of windows, at which it is so good.
It also keeps the things portable, like putting it on a network disk.

Klaas



-- 
Unclassified

On 12/18/06, Francesco Montorsi <f18...@ya...> wrote:
> Hi all,
>     is it if we try to make wxLua 2.8.0.0 release before 25 december?
> It would be a nice Christmas gift for some of my friends which asked me
> a nice interpreted language for GUI apps ;)

That would be nice. I will test again VC 2005 using dsw files, VC 2003
using nmake, and configure. My VC 6 machine is not working anymore,
it's a laptop and the hinge broke...

There is still one last thing (as of six hours ago or so) for
modules/build/msw/makefile.vc

The luamodule wants to compile with lua5.1.lib, see here
!if "$(SHARED)" == "1" && "$(USE_LUAMODULE)" == "1"
    ...

but  has

!if "$(SHARED)" == "0"
__verbatimlua_lib___depname = \
        ..\..\..\lib\vc_lib\wxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_lua.lib
!endif
!if "$(SHARED)" == "1"
__verbatimlua_dll___depname = \
        ..\..\..\lib\vc_dll\wxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_lua.dll

If you just copy wxlua_mswXXX_lua.lib to lua5.1.lib the luamodue works.


By the way, is there a way to combine all of wxWidgets and wxLua into
the wx.dll? I had to copy all of the dlls from
wxWidgets/lib/vc_dll/*.dll and the sample/luamodule.wx.lua into the
dir that I ran $wxlua-lua.exe from. I guess all these dlls could go
into %WINDIR%/System32 or something? Anyway the error message you get
when run from cygwin is "error loading module "wx" from wx.dll." which
is very cryptic since the real error when run from a DOS prompt is
that the wxWidgets dlls cannot be found.

Regards,
    John Labenski

Anders F Björklund ha scritto:
> Francesco Montorsi wrote:
> 
>> Hi all|Anders Björklund,
>>
>>     is anyone out there using wxLua on a mac?
>>
>> We would be glad to publish new wxLua screenshots for wxMac, and to fix
>> any problem with mac-bundling, if there's any, before 2.8.0.0
> 
> Not actually using it, but will happy to give building it a try...
Great! Also remember us if you need some other file to generate the 
MacBundle which is not in CVS yet. In fact, if the generation is more 
than 2-3 commands, we may also add a script to do it under 
distrib\macbundle (just like I do for autopackages under 
distrib\autopackage).

Thanks!
Francesco

Hi all,
    is it if we try to make wxLua 2.8.0.0 release before 25 december?
It would be a nice Christmas gift for some of my friends which asked me 
a nice interpreted language for GUI apps ;)

Francesco

John Labenski ha scritto:
> On 12/17/06, Francesco Montorsi <f18...@ya...> wrote:
>>>> Hi all,
>>>>    i've added a file under distrib\announce.txt which lists the places where to
>>>> post the info about the new wxLua release and also the announcement text for it.
>>>>
>>>> Any comments/suggestions gladly accepted,
>>>> Francesco
> 
> Good idea, I added a little more text to make it more "exciting" to
> the uninitiated, a description of what wxWidgets is for the lua
> newsgroup for example.
Good idea!

Francesco

John Labenski ha scritto:
> On 12/17/06, Francesco Montorsi <f18...@ya...> wrote:
>> Francesco Montorsi ha scritto:
>>>   2) renamed lua5.1 library built by wxLua to libwxlua_gtk2d_lua-2.8.a;
>>> that is, to a lib which follows wxLua naming conventions. This is more
>>> coherent with the way we call the (vanilla) lua intepreter which we
>>> build: wxlua-lua. That is, if we care about not replacing the
>>> system-wide "lua" executable, we should care also about not replacing
>>> the system-wide "lua5.1" library.
>>>
>>> I don't remember why we decided to call our verbatim lua library
>>> "lua5.1"... do you see anything wrong with calling it using our naming
>>> convention?
>> Ok, I now remember why we decided to call it lua5.1; the wx.dll module we build
>> from modules\luamodule is coinceived to be used as any other Lua module.  I.e.
>> it must be linked against a DLL/DSO named "lua5.1" not "wxlua_msw28_lua".
>>
>> So, I think we have no other choice that making our "lua" module build a library
>> named lua5.1 and then install it in standard paths, eventually overwriting the
>> preexisting one.
>>
>> This should not be a big problem since the name is versioned and we're using
>> vanilla lua now. It may just be a problem if someone modified lua and thus has
>> in system paths a custom version (but this is a bad practice anyway; that user
>> should consider to name its custom library in some other way).
>>
>> Do you agree with this change?
> 
> Can we test in configure if the lua and lua devel packages are
> installed and use those sources? Too much work? I guess it would work
> like wxWidgets use of the jpeg, png, etc libs. I don't know how to do
> any of this. :(
It wouldn't be much difficult from the build-system POV.
The problem may be related to the way we include the lua headers:

#include "lua/include/lua.h"

I'll try to implement the check and then set a wxUSE_CUSTOM_LUA 
preprocessor symbol if a usable lua 5.1 is found. The header inclusion 
would then be modified:

#if wxUSE_CUSTOM_LUA
    #include "lua.h"
#else
    #include "lua/include/lua.h"
#endif

otherwise we could also simply add the "modules/lua/include" path to the 
paths given to compiler so that we could just use:

#include "lua.h"

all the times.


>> Once we get this up and running I think we should also
>>
>>    1) add our "wx" module to this list:
>>
>>        http://lua-users.org/wiki/LuaBinaryModules (look at the end)
>>
>>    2) publish in the next release a single .ZIP download which contains only the
>> wxLua+wxWidgets DLLs + wx.dll module; so that users could just unzip them and
>> start using wx.dll module as for any other lua module.
> 
> This would be great, I can compile them with MSVC 6 which I think
> should be the best since it generates the smallest binaries. Can mingw
> use dlls use VC dlls?
yes, absolutely.

Generating them with MSVC6 is probably the best choice also because that 
way they probably avoid dependencies on newer MSVC dlls which are 
sometimes missing on old systems (I suspect that the DLL I build using 
MSVC7.1 requires msvc71.dll or something like that).

Francesco