wxlua-users — wxLua list for users and developers

[Wxlua-users] Re: LUA_PATH (Ray) Re: require("wx") and build stuff

[Francesco M. <f18...@ya...>]

Hakki Dogusan ha scritto:
> I'm using paths like this (on winxp):
> 
> DSASPATH = "c:/a_C/dsas/server/"
> 
> package.path  = 
> DSASPATH.."?;"..DSASPATH.."?.lua;"..DSASPATH.."/apps/?;"..DSASPATH.."/apps/?.lua" 
> 
> package.cpath = 
> DSASPATH.."?;"..DSASPATH.."?.dll;"..DSASPATH.."/apps/?;"..DSASPATH.."/apps/?.dll" 
> 
> 
> require("testapp")         -- API testing
> ...
> 
Exactly what I was looking for: package.cpath.
Works nicely here, thanks!

Francesco

[Wxlua-users] Re: LUA_PATH (Ray) Re: require("wx") and build stuff

[Francesco M. <f18...@ya...>]

Damien Fagnou ha scritto:
> 
>  I have being using LUA_CPATH
> setenv LUA_CPATH "...../lua/5.1/linux.fedora1/gcc3.3.4/?.so"
> and  doing require "wx" in the scripts 
>  and it works fine 
> 
>  I can`t remember when I found the documentation about it though :)
it works but I was searching a way to set the path from the lua script 
itself...

Thanks anyway,
Francesco

[Wxlua-users] SSH host key changed?

[Francesco M. <f18...@ya...>]

Hi,
   today my SSH client says that the RSA key fingerprint for the CVS 
server is

    13:f1:65:c3:6c:b7:7e:a5:f0:f3:f5:19:f4:42:9c:4a

I had to delete the "offending" line from my 
/home/frm/.ssh/known_hosts... does anyone got the same message ?

Or I've really been subject to a "man-in-the-middle attack" as SSH says ? ;)

Francesco

Re: LUA_PATH (Ray) Re: [Wxlua-users] require("wx") and build stuff

[Hakki D. <dog...@tr...>]

Hi,

John Labenski yazmış:
> On 5/17/06, Francesco Montorsi <f18...@ya...> wrote:
>> Hi,
>>     I'm experimenting with wx module and I've got a few proposals for it:
>>
>> 1) the luamodule.wx.lua files in wxLua/apps/luamodule/src is an example,
>> isn't it ? Shouldn't then go in wxLua/samples ?
>> wrapmodule.wx.lua is an utility so shouldn't it got in wxLua/utils ?
> 
> Eh... I think these are pretty specialized. But, you're probably
> right, once things work they should be moved. I just put them into the
> dir where I generated the shared lib since I was having trouble with
> the paths for require.
> 
>> 2) I'm getting a weird behaviour of lua's require: I'd like to make the
>> "luamodule" app installable in $prefix/lib/lua/5.1; however, while
>> everything works as expected if I put the compiled wx.so in
>> /usr/local/lib/lua/5.1, it doesn't work if I put it in /usr/lib/lua/5.1:
> 
> This is the path stuff I was talking about, it's a nightmare.
> 
>> wxlua-lua: luamodule.wx.lua:17: module 'wx' not found:
>>          no field package.preload['wx']
>>          no file './wx.so'
>>          no file '/usr/local/lib/lua/5.1/wx.so'
>>          no file '/usr/local/lib/lua/5.1/loadall.so'
>> stack traceback:
>>          [C]: in function 'require'
>>          luamodule.wx.lua:17: in main chunk
>>          [C]: ?
>>
>> I tried to set LUA_PATH in luamodule.wx.lua to:
>> LUA_PATH="/usr/lib/lua/5.1/?.so;"
>> *before* the require() call but then I get:
>>
>> wxlua-lua: error loading module 'wx' from file '/usr/lib/lua/5.1/wx.so':
>>          /usr/lib/lua/5.1/wx.so:1: unexpected symbol near 'char(127)'
>> stack traceback:
>>          [C]: ?
>>          [C]: in function 'require'
>>          luamodule.wx.lua:17: in main chunk
>>          [C]: ?
>>
>> that "unexpected symbol near 'char(127)'" is not clear to me !
>>
>> This strange behaviour (lua bug?) is easy to reproduce also putting the
>> wx.so file in /usr/local/lib/lua/5.1 and then setting:
>>
>> LUA_PATH="/usr/local/lib/lua/5.1/?.so"
>>
>> So, it looks that the global variable LUA_PATH, described at
>> http://www.lua.org/pil/8.1.html, does not work... is anyone able to
>> reproduce this "bug" ?
> 
> LUA_PATH, I think, is a 5.0 thing, but recently Ray added some code in
> our version of lua to handle it. Hopefully he (or anyone else)
> understands what this is all about? I've spent far too much time
> trying to understand the PATH thing and got nowhere.
> 
> I was hoping that the people who requested that require work w/ wxLua
> would step forward and finish things. :)
> 
> Regards,
>    John Labenski
> 
[snip]

I'm using paths like this (on winxp):

DSASPATH = "c:/a_C/dsas/server/"

package.path  = 
DSASPATH.."?;"..DSASPATH.."?.lua;"..DSASPATH.."/apps/?;"..DSASPATH.."/apps/?.lua"
package.cpath = 
DSASPATH.."?;"..DSASPATH.."?.dll;"..DSASPATH.."/apps/?;"..DSASPATH.."/apps/?.dll"

require("testapp")         -- API testing
...



--
Regards,
Hakki Dogusan

RE: LUA_PATH (Ray) Re: [Wxlua-users] require("wx") and build stuff

[Ray G. <ray...@sc...>]

Being able to set LUA_PATH from within lua script is does not work with =
5.1

I hacked code to look for LUA_PATH in our version of loadlib.c - but it =
only uses it for pname of "path" i.e. .lua files.

You could change loadlib.c code to

  /* Make 5.0 compatible to allow global LUA_PATH to be set from LUA */
  if (strcmp(pname, "path") =3D=3D 0 || strcmp(pname, "cpath") =3D=3D 0) =
{
						^^^^^^^^^^^^^^^^^^^^^^^^^^^
      lua_getfield(L, LUA_GLOBALSINDEX, LUA_PATH);


so that it will pick up "cpath" libraries=20

Ray


-----Original Message-----
From: wxl...@li... =
[mailto:wxl...@li...] On Behalf Of John =
Labenski
Sent: Thursday, 18 May 2006 03:05
To: wxl...@li...
Subject: LUA_PATH (Ray) Re: [Wxlua-users] require("wx") and build stuff

On 5/17/06, Francesco Montorsi <f18...@ya...> wrote:
> Hi,
>     I'm experimenting with wx module and I've got a few proposals for =
it:
>
> 1) the luamodule.wx.lua files in wxLua/apps/luamodule/src is an =
example,
> isn't it ? Shouldn't then go in wxLua/samples ?
> wrapmodule.wx.lua is an utility so shouldn't it got in wxLua/utils ?

Eh... I think these are pretty specialized. But, you're probably
right, once things work they should be moved. I just put them into the
dir where I generated the shared lib since I was having trouble with
the paths for require.

> 2) I'm getting a weird behaviour of lua's require: I'd like to make =
the
> "luamodule" app installable in $prefix/lib/lua/5.1; however, while
> everything works as expected if I put the compiled wx.so in
> /usr/local/lib/lua/5.1, it doesn't work if I put it in =
/usr/lib/lua/5.1:

This is the path stuff I was talking about, it's a nightmare.

> wxlua-lua: luamodule.wx.lua:17: module 'wx' not found:
>          no field package.preload['wx']
>          no file './wx.so'
>          no file '/usr/local/lib/lua/5.1/wx.so'
>          no file '/usr/local/lib/lua/5.1/loadall.so'
> stack traceback:
>          [C]: in function 'require'
>          luamodule.wx.lua:17: in main chunk
>          [C]: ?
>
> I tried to set LUA_PATH in luamodule.wx.lua to:
> LUA_PATH=3D"/usr/lib/lua/5.1/?.so;"
> *before* the require() call but then I get:
>
> wxlua-lua: error loading module 'wx' from file =
'/usr/lib/lua/5.1/wx.so':
>          /usr/lib/lua/5.1/wx.so:1: unexpected symbol near 'char(127)'
> stack traceback:
>          [C]: ?
>          [C]: in function 'require'
>          luamodule.wx.lua:17: in main chunk
>          [C]: ?
>
> that "unexpected symbol near 'char(127)'" is not clear to me !
>
> This strange behaviour (lua bug?) is easy to reproduce also putting =
the
> wx.so file in /usr/local/lib/lua/5.1 and then setting:
>
> LUA_PATH=3D"/usr/local/lib/lua/5.1/?.so"
>
> So, it looks that the global variable LUA_PATH, described at
> http://www.lua.org/pil/8.1.html, does not work... is anyone able to
> reproduce this "bug" ?

LUA_PATH, I think, is a 5.0 thing, but recently Ray added some code in
our version of lua to handle it. Hopefully he (or anyone else)
understands what this is all about? I've spent far too much time
trying to understand the PATH thing and got nowhere.

I was hoping that the people who requested that require work w/ wxLua
would step forward and finish things. :)

Regards,
    John Labenski

ps. This was a reply I got on the lua-l about dlls and require, it
looks like for gcc in MSW you just link the dlls as you do the .so
files in linux. No news about MSVC.

On 5/13/06, J=E9r=F4me VUARAND <jer...@gm...> wrote:
> With mingw you can do exactly the same to build a wx.dll Lua module :
> wx.dll: luamodule.cpp $(OBJECTS) $(LUA_LIBS) wxLuaLib wxLuaDebugLib
> wxLuaSocketLib wxLuaBindings
>         $(CXX) $(CXXFLAGS) $(APPEXTRADEFS) -g -O -shared -o wx.dll =
-fpic \
>         $(LDLIBS) $(APPEXTRALIBS) \
>         luamodule.cpp
>
> The only extra thing you have to do is to check that all your
> -l$(XXXLIB) point to existing libraries. These libraries can either be
> static libs, or dll import libraries. Static libs are exactly like on
> unix (-lfoo need libfoo.a). Dll import libraries are necessary if you
> want to link dynamically to a dll. You can generate libfoo.a from
> foo.dll with the following commands :
>         impdef foo.dll > foo.def
>         libtool --kill-at --dllname foo.dll --input-def foo.def =
--output-lib libfoo.a
>         rm foo.def
> These import libraries may already exist in the wxWidget build tree if
> you built it with mingw.
>
> Feel free to ask if I'm not clear. I had a hard time finding docs on
> the subject since everything on mingw site is outdated, but now I
> think I know the subject well.


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, =
security?
Get stuff done quickly with pre-integrated technology to make your job =
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache =
Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642
_______________________________________________
Wxlua-users mailing list
Wxl...@li...
https://lists.sourceforge.net/lists/listinfo/wxlua-users

[Wxlua-users] Function naming conventions (follow wxPython or our own way)

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

In going through the the interface files I've noticed that there are a
few naming inconsistencies for C++ overloaded functions and
constructors. Typically they have the names that wxPython uses (where
noted in the docs) and for the most part are fine, but...

Since we can overloaded function in wxLua directly (usually) we don't
actually need to give them unique names, however they need some sort
of name for the C function and might as well be accessible in wxLua
using that name as well as the overloaded way.

Suggested rules for renaming:
1) Most "commonly used" or default function gets actual name
2) Function names use the original name + [With][Data type]
ex. Append(int n), Append(wxString s) -> AppendString(s)
ex. Append(int n), Append(int n, Stuff s) -> AppendWithStuff(n, s)
3) Class constructors start with the ClassName + From[Data type]
Default constructors are always wxClassNameDefault()
Copy constructors are always wxClassNameCopy(const wxClassName& c)

Obviously there will be exceptions or cases where the name may sound
awkward, but the number of these will be small.

Some examples of the inconsistencies I'm talking about:

--------------------------
These member functions will be out of alphabetical order and may be
difficult to directly associate with the original function without
looking through the docs. It is true that the wxPython ones may be
more syntactically "correct", but I think that directly associating
them with the original function is more compelling.

wxListCtrl
wxPython naming (currently wxLua uses this)
  InsertItem(item)   Inserts an item using a wxListItem.
  InsertStringItem(index, label)   Inserts a string item.
  InsertImageItem(index, imageIndex)   Inserts an image item.
  InsertImageStringItem(index, label, imageIndex)   Insert an image/string =
item.

I would prefer
  InsertItem(item)   Inserts an item using a wxListItem.
  InsertItemString(index, label)   Inserts a string item.
  InsertItemImage(index, imageIndex)   Inserts an image item.
  InsertItemImageString(index, label, imageIndex)   Insert an image/string =
item.

---------------------------

Some constructor examples, currently it's this way
  wxColour(const unsigned char red, const unsigned char green, const
unsigned char blue)
  wxNamedColour(const wxString& colourNname) // python compatibility
  wxColourCopy(const wxColour& colour)

I would prefer
  wxColour(const unsigned char red, const unsigned char green, const
unsigned char blue)
  wxColourFromString(const wxString& colourNname) // python compatibility
  wxColourCopy(const wxColour& colour)

other examples
    %constructor wxDefaultBitmap()
    %win wxBitmap(void * data, int type, int width, int height, int depth =
=3D -1)
    %constructor wxBitmapCopy(const wxBitmap& bitmap)
    %constructor wxEmptyBitmap( int width, int height, int depth =3D -1)
    %constructor wxBitmapFromFile( const wxString& name, long type)
    %constructor wxBitmapFromXPMData(const char **data)
    %wxchkver23 %constructor wxBitmapFromImage(const wxImage &image,
int depth =3D -1)
and
    wxImage(const wxImage& image)
    %constructor wxDefaultImage()
    %wxchkver23 %constructor wxImageFromBitmap(const wxBitmap& bitmap)
    %constructor wxEmptyImage(int width, int height, bool clear=3Dtrue)
    %constructor wxImageFromData(int width, int height, unsigned char*
data, bool static_data =3D false)
    %constructor wxImageFromFile(const wxString& name, long type =3D
wxBITMAP_TYPE_ANY)

Hopefully you can see that the naming right now can be fairly
arbitrary, where the default wxImage constructor makes a copy?
wxEmptyImage? wxDefaultImage? The default for wxBitmap takes the
bitmap data itself, but only for MSW, how useful is that?

I would like to normalize all of these, obviously breaking
compatibility, but better sooner than later. :) There's probably about
2 dozen of them to change.

Regards,
    John Labenski

Re: LUA_PATH (Ray) Re: [Wxlua-users] require("wx") and build stuff

[Damien F. <dam...@mo...>]

 I have being using LUA_CPATH
setenv LUA_CPATH "...../lua/5.1/linux.fedora1/gcc3.3.4/?.so"
and  doing require "wx" in the scripts=20
 and it works fine=20

 I can`t remember when I found the documentation about it though :)

damien


> On 5/17/06, Francesco Montorsi <f18...@ya...> wrote:
> > Hi,
> >     I'm experimenting with wx module and I've got a few proposals for i=
t:
> >
> > 1) the luamodule.wx.lua files in wxLua/apps/luamodule/src is an example,
> > isn't it ? Shouldn't then go in wxLua/samples ?
> > wrapmodule.wx.lua is an utility so shouldn't it got in wxLua/utils ?
>=20
> Eh... I think these are pretty specialized. But, you're probably
> right, once things work they should be moved. I just put them into the
> dir where I generated the shared lib since I was having trouble with
> the paths for require.
>=20
> > 2) I'm getting a weird behaviour of lua's require: I'd like to make the
> > "luamodule" app installable in $prefix/lib/lua/5.1; however, while
> > everything works as expected if I put the compiled wx.so in
> > /usr/local/lib/lua/5.1, it doesn't work if I put it in /usr/lib/lua/5.1:
>=20
> This is the path stuff I was talking about, it's a nightmare.
>=20
> > wxlua-lua: luamodule.wx.lua:17: module 'wx' not found:
> >          no field package.preload['wx']
> >          no file './wx.so'
> >          no file '/usr/local/lib/lua/5.1/wx.so'
> >          no file '/usr/local/lib/lua/5.1/loadall.so'
> > stack traceback:
> >          [C]: in function 'require'
> >          luamodule.wx.lua:17: in main chunk
> >          [C]: ?
> >
> > I tried to set LUA_PATH in luamodule.wx.lua to:
> > LUA_PATH=3D"/usr/lib/lua/5.1/?.so;"
> > *before* the require() call but then I get:
> >
> > wxlua-lua: error loading module 'wx' from file '/usr/lib/lua/5.1/wx.so':
> >          /usr/lib/lua/5.1/wx.so:1: unexpected symbol near 'char(127)'
> > stack traceback:
> >          [C]: ?
> >          [C]: in function 'require'
> >          luamodule.wx.lua:17: in main chunk
> >          [C]: ?
> >
> > that "unexpected symbol near 'char(127)'" is not clear to me !
> >
> > This strange behaviour (lua bug?) is easy to reproduce also putting the
> > wx.so file in /usr/local/lib/lua/5.1 and then setting:
> >
> > LUA_PATH=3D"/usr/local/lib/lua/5.1/?.so"
> >
> > So, it looks that the global variable LUA_PATH, described at
> > http://www.lua.org/pil/8.1.html, does not work... is anyone able to
> > reproduce this "bug" ?
>=20
> LUA_PATH, I think, is a 5.0 thing, but recently Ray added some code in
> our version of lua to handle it. Hopefully he (or anyone else)
> understands what this is all about? I've spent far too much time
> trying to understand the PATH thing and got nowhere.
>=20
> I was hoping that the people who requested that require work w/ wxLua
> would step forward and finish things. :)
>=20
> Regards,
>     John Labenski
>=20
> ps. This was a reply I got on the lua-l about dlls and require, it
> looks like for gcc in MSW you just link the dlls as you do the .so
> files in linux. No news about MSVC.
>=20
> On 5/13/06, J=E9r=F4me VUARAND <jer...@gm...> wrote:
> > With mingw you can do exactly the same to build a wx.dll Lua module :
> > wx.dll: luamodule.cpp $(OBJECTS) $(LUA_LIBS) wxLuaLib wxLuaDebugLib
> > wxLuaSocketLib wxLuaBindings
> >         $(CXX) $(CXXFLAGS) $(APPEXTRADEFS) -g -O -shared -o wx.dll -fpi=
c \
> >         $(LDLIBS) $(APPEXTRALIBS) \
> >         luamodule.cpp
> >
> > The only extra thing you have to do is to check that all your
> > -l$(XXXLIB) point to existing libraries. These libraries can either be
> > static libs, or dll import libraries. Static libs are exactly like on
> > unix (-lfoo need libfoo.a). Dll import libraries are necessary if you
> > want to link dynamically to a dll. You can generate libfoo.a from
> > foo.dll with the following commands :
> >         impdef foo.dll > foo.def
> >         libtool --kill-at --dllname foo.dll --input-def foo.def --outpu=
t-lib libfoo.a
> >         rm foo.def
> > These import libraries may already exist in the wxWidget build tree if
> > you built it with mingw.
> >
> > Feel free to ask if I'm not clear. I had a hard time finding docs on
> > the subject since everything on mingw site is outdated, but now I
> > think I know the subject well.
>=20
>=20
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job ea=
sier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=120709&bid&3057&dat=121642
> _______________________________________________
> Wxlua-users mailing list
> Wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

LUA_PATH (Ray) Re: [Wxlua-users] require("wx") and build stuff

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

On 5/17/06, Francesco Montorsi <f18...@ya...> wrote:
> Hi,
>     I'm experimenting with wx module and I've got a few proposals for it:
>
> 1) the luamodule.wx.lua files in wxLua/apps/luamodule/src is an example,
> isn't it ? Shouldn't then go in wxLua/samples ?
> wrapmodule.wx.lua is an utility so shouldn't it got in wxLua/utils ?

Eh... I think these are pretty specialized. But, you're probably
right, once things work they should be moved. I just put them into the
dir where I generated the shared lib since I was having trouble with
the paths for require.

> 2) I'm getting a weird behaviour of lua's require: I'd like to make the
> "luamodule" app installable in $prefix/lib/lua/5.1; however, while
> everything works as expected if I put the compiled wx.so in
> /usr/local/lib/lua/5.1, it doesn't work if I put it in /usr/lib/lua/5.1:

This is the path stuff I was talking about, it's a nightmare.

> wxlua-lua: luamodule.wx.lua:17: module 'wx' not found:
>          no field package.preload['wx']
>          no file './wx.so'
>          no file '/usr/local/lib/lua/5.1/wx.so'
>          no file '/usr/local/lib/lua/5.1/loadall.so'
> stack traceback:
>          [C]: in function 'require'
>          luamodule.wx.lua:17: in main chunk
>          [C]: ?
>
> I tried to set LUA_PATH in luamodule.wx.lua to:
> LUA_PATH=3D"/usr/lib/lua/5.1/?.so;"
> *before* the require() call but then I get:
>
> wxlua-lua: error loading module 'wx' from file '/usr/lib/lua/5.1/wx.so':
>          /usr/lib/lua/5.1/wx.so:1: unexpected symbol near 'char(127)'
> stack traceback:
>          [C]: ?
>          [C]: in function 'require'
>          luamodule.wx.lua:17: in main chunk
>          [C]: ?
>
> that "unexpected symbol near 'char(127)'" is not clear to me !
>
> This strange behaviour (lua bug?) is easy to reproduce also putting the
> wx.so file in /usr/local/lib/lua/5.1 and then setting:
>
> LUA_PATH=3D"/usr/local/lib/lua/5.1/?.so"
>
> So, it looks that the global variable LUA_PATH, described at
> http://www.lua.org/pil/8.1.html, does not work... is anyone able to
> reproduce this "bug" ?

LUA_PATH, I think, is a 5.0 thing, but recently Ray added some code in
our version of lua to handle it. Hopefully he (or anyone else)
understands what this is all about? I've spent far too much time
trying to understand the PATH thing and got nowhere.

I was hoping that the people who requested that require work w/ wxLua
would step forward and finish things. :)

Regards,
    John Labenski

ps. This was a reply I got on the lua-l about dlls and require, it
looks like for gcc in MSW you just link the dlls as you do the .so
files in linux. No news about MSVC.

On 5/13/06, J=E9r=F4me VUARAND <jer...@gm...> wrote:
> With mingw you can do exactly the same to build a wx.dll Lua module :
> wx.dll: luamodule.cpp $(OBJECTS) $(LUA_LIBS) wxLuaLib wxLuaDebugLib
> wxLuaSocketLib wxLuaBindings
>         $(CXX) $(CXXFLAGS) $(APPEXTRADEFS) -g -O -shared -o wx.dll -fpic =
\
>         $(LDLIBS) $(APPEXTRALIBS) \
>         luamodule.cpp
>
> The only extra thing you have to do is to check that all your
> -l$(XXXLIB) point to existing libraries. These libraries can either be
> static libs, or dll import libraries. Static libs are exactly like on
> unix (-lfoo need libfoo.a). Dll import libraries are necessary if you
> want to link dynamically to a dll. You can generate libfoo.a from
> foo.dll with the following commands :
>         impdef foo.dll > foo.def
>         libtool --kill-at --dllname foo.dll --input-def foo.def --output-=
lib libfoo.a
>         rm foo.def
> These import libraries may already exist in the wxWidget build tree if
> you built it with mingw.
>
> Feel free to ask if I'm not clear. I had a hard time finding docs on
> the subject since everything on mingw site is outdated, but now I
> think I know the subject well.

[Wxlua-users] require("wx") and build stuff

[Francesco M. <f18...@ya...>]

Hi,
    I'm experimenting with wx module and I've got a few proposals for it:

1) the luamodule.wx.lua files in wxLua/apps/luamodule/src is an example, 
isn't it ? Shouldn't then go in wxLua/samples ?
wrapmodule.wx.lua is an utility so shouldn't it got in wxLua/utils ?

2) I'm getting a weird behaviour of lua's require: I'd like to make the 
"luamodule" app installable in $prefix/lib/lua/5.1; however, while 
everything works as expected if I put the compiled wx.so in 
/usr/local/lib/lua/5.1, it doesn't work if I put it in /usr/lib/lua/5.1:

wxlua-lua: luamodule.wx.lua:17: module 'wx' not found:
         no field package.preload['wx']
         no file './wx.so'
         no file '/usr/local/lib/lua/5.1/wx.so'
         no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
         [C]: in function 'require'
         luamodule.wx.lua:17: in main chunk
         [C]: ?

I tried to set LUA_PATH in luamodule.wx.lua to:
LUA_PATH="/usr/lib/lua/5.1/?.so;"
*before* the require() call but then I get:

wxlua-lua: error loading module 'wx' from file '/usr/lib/lua/5.1/wx.so':
         /usr/lib/lua/5.1/wx.so:1: unexpected symbol near 'char(127)'
stack traceback:
         [C]: ?
         [C]: in function 'require'
         luamodule.wx.lua:17: in main chunk
         [C]: ?

that "unexpected symbol near 'char(127)'" is not clear to me !

This strange behaviour (lua bug?) is easy to reproduce also putting the 
wx.so file in /usr/local/lib/lua/5.1 and then setting:

LUA_PATH="/usr/local/lib/lua/5.1/?.so"

So, it looks that the global variable LUA_PATH, described at 
http://www.lua.org/pil/8.1.html, does not work... is anyone able to 
reproduce this "bug" ?

Thanks,
Francesco

Re: [Wxlua-users] binary release based on shared libraries?

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

On 5/16/06, Steve Kieu <ha...@ya...> wrote:
>
> shared libraries.  I've tried building it myself but it seems a pretty la=
rge
> undertaking, at least on Windows.
>
> Building wxLua in windows is very easy, I did with VC -2003 even I am so
> awkward in win32 environment and VC ; not require any tricks at all; just
> edit some Makefile.vc in the build directory to agree with wx-2.6.3 confi=
g
> as well and some time to spend, VC compiles fast.

A little tip, you can specify things on the nmake command like like
WX_VERSION=3D27 if you happen to use wxWidgets CVS head. This might save
some editing if you make a little batch file.

These days just go to wxLua/build/msw and you should find a build file
for just about any compiler that wxWidgets can use. Basicly, if you
can compile wxWidgets you should be able to get wxLua going as well.

-John Labenski

Re: [Wxlua-users] binary release based on shared libraries?

[Steve K. <ha...@ya...>]

shared libraries.  I've tried building it myself but it seems a pretty large undertaking, at least on Windows.  

Building wxLua in windows is very easy, I did with VC -2003 even I am so awkward in win32 environment and VC ; not require any tricks at all; just edit some Makefile.vc in the build directory to agree with wx-2.6.3 config as well and some time to spend, VC compiles fast.

Cheers,


   

---------------------------------
New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.


S.KIEU
		
---------------------------------
  The LOST Ninja blog: Exclusive clues, clips and gossip.  

Re: [Wxlua-users] wxLua binding list

[Steve K. <ha...@ya...>]

Heh, how do you like that? :)

Still nice to use wxLua :-)

currently. You'll need to get the CVS version and recompile.
Well for now I must stick with the release version as it is based on lua5.0 and luasql work fine with them. luasql does not work with lua-5.1 in windows (crash) but it is fine in Linux. I probably switch over by the end of the project which I hope luasql will be usesable in win32. (The Kepler team is a bit slow ?)

And I do not like wxWirzard at all :-). It is not flexible enough for  me; and use wxLua, normal dialog and have finished a 10 pages of wirzard just in 3 hours and can set everything I want, can control every flow I wish. So no need for me to use wxWirzard anymore. 


However if you want me to test I will try sometime this evening to play with it and let you know later.

Another thing about wxSocket on another post; I decided to use luasocket with copas instead of using wxSocket as it support more protocol (have UDP, SMTP support as well ; remind me one unpleasant time I had to write a SMTP class for my previous project in wxWidgets c++ because the current wxSMTP in wiki is really messy and unuseable; and write the low level of SMTP protocol like this makes me nut :-), esp. dealing with email server picky like qmail !  ) and proves quite stable, programming interface is simpler.
 
So it might be somtime to test these function in wxLua ; if I have spare in some evenings.

Cheers, thank you very much for your reply.

All the best.




S.KIEU
		
---------------------------------
On Yahoo!7
  Socceroos Central: Latest news, schedule, blogs and videos.  

[Wxlua-users] binary release based on shared libraries?

[Josh T. <zen...@ya...>]

Is it possible that there will be a binary release that uses shared libraries based on the lua binaries project?  I can't use any of my C library bindings with wxLua anymore because everything is statically linked.  I can with the old 2.4 release because it uses shared libraries.  I've tried building it myself but it seems a pretty large undertaking, at least on Windows.  



		
---------------------------------
New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.

Re: [Wxlua-users] wxLua Class Reference is online

[Alec R. <al...@ar...>]

In message 
<a84...@ma...>, John 
Labenski <jla...@gm...> writes
>http://wxlua.sourceforge.net/docs.php
>
>At the top of the page is a link to the reference manual. It's from a
>little hack in lua, see bindings/genidocs.lua, to make a cross
>referenced manual from the interface files.
>
>Regards,
>   John Labenski
>
Many thanks, John.

-- 
Alec Ross

[Wxlua-users] wxLua Class Reference is online

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

http://wxlua.sourceforge.net/docs.php

At the top of the page is a link to the reference manual. It's from a
little hack in lua, see bindings/genidocs.lua, to make a cross
referenced manual from the interface files.

Regards,
    John Labenski

Re: [Wxlua-users] wxLua binding list

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

On 5/15/06, Steve Kieu <ha...@ya...> wrote:
> I just hit a small suprise :-); when I tried to use wxWizard and not
> available in wxLua, then find most of code in dialog.i relating to wxWzar=
d
> is commented out.

Heh, how do you like that? :)

I'm not sure why it is, I probably did it though. There are so many
little bits to wxWidgets that we can't possible use them all, so
classes like that suffer. I've added it back and hopefully you can use
the wxWizardPageSimple... You cannot override the virtual functions
currently. You'll need to get the CVS version and recompile.

> this makes me ask, what more widgets that wxLua has **not** wrap wxWidget=
s?
> anybody has some sort of table or list, etc.. for faster information. I
> think this kind of list is good; just imagine somebody when look at the
> wxluasetup.h and find nearly all there define as 1, he/she is happy to co=
de
> all wizardary thingy,  long long program takes several days and later fou=
nd
> out that his code does not work as actual binding not exists yet.

Well for now every .i file that says "Updated to 2.6.3" has every
function for the classes defined in the .i files available to wxLua,
unless marked. However, as you've found some classes may be missing
altogether, but these are probabgly only ones added in 2.6.x.

I have thought about writing a parser for the .i files to turn them
into HTML, someday...

> (no not for me, I am wise enough to write just 4 lines to test :-) )

You can also just concatenate all the .i files together and use an
editor with a nice find dialog to search.

Regards,
    John Labenski

[Wxlua-users] wxLua binding list

[Steve K. <ha...@ya...>]

Hi everyone,

I just hit a small suprise :-); when I tried to use wxWizard and not available in wxLua, then find most of code in dialog.i relating to wxWzard is commented out.

this makes me ask, what more widgets that wxLua has **not** wrap wxWidgets? anybody has some sort of table or list, etc.. for faster information. I think this kind of list is good; just imagine somebody when look at the wxluasetup.h and find nearly all there define as 1, he/she is happy to code all wizardary thingy,  long long program takes several days and later found out that his code does not work as actual binding not exists yet. 

(no not for me, I am wise enough to write just 4 lines to test :-) )

Cheers,




S.KIEU
		
---------------------------------
  The LOST Ninja blog: Exclusive clues, clips and gossip.  

Re: [Wxlua-users] Re: wxLua works as module, require"wx"

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

On 5/15/06, Damien Fagnou <dam...@mo...> wrote:
>
> I try to send this to the list but it doesn`t go through ..

Humm, that's strange.

> -------------------------------------------------------------------------=
--------------------------
> this is great news !!!!
>
>  our pipeline is strongly based on lua and I can`t wait to put more wxLua=
 in action !!
>
> > A sample program called luamodule.wx.lua in that dir shows it working
> > by simply creating a wxFrame. Test it from the
> > wxLua/apps/luamodule/src dir using
> > $../../../bin/lua luamodule.wx.lua
>
>  this worked great , compile and run .
>
>  but if I try
>         lua luamodule.wx.lua
>
>  I get an error of type :
>         libwx_gtk2_wxlua-2.6.so: undefined symbol: wxLua_lua_getnewthread=
handler
>
>  we have the standard lua 5.1 distribution installed , what is exactly th=
e difference beetwen lua 5.1
>  and lua include the wxLua distribution ?
>
>  is it only the function enable by the  WXLUA_LUA_NEWTHREAD flag ?

We added some functions in lstate.c to track when a coroutine is
created, there's really nothing to them. This is unfortunately tricky
to "fix". In wxLua itself we want to have WXLUA_LUA_NEWTHREAD defined
so that coroutines will work, but for the luamodule we can't have it
defined for people who want to use a stock lua executable which means
that module/wxlua has to be compiled without it.

1) We could add a compiler option or new #define to NOT define
WXLUA_LUA_NEWTHREAD for people who want to use the module. Sounds
strange, but I think it should be on by default, hence the added
define undoes the default define.

2) Use the lua registry? Does it get copied for coroutine created
lua_States? If so then we don't need this hook at all. I had tried to
stick the wxLuaStateData into lua itself as a global variable, but
somehow it wasn't in the coroutine state, though other bits were.

The bottom line is that we need to associate each lua_State with our
wxLuaStateRefData and so things break if lua_States get created behind
our back as they do for coroutines.


For now, just edit the top of wxLua/modules/wxlua/src/wxlstate.cpp and
add this to undef it and that way it won't get compiled in.

#ifdef WXLUA_LUA_NEWTHREAD
#undef WXLUA_LUA_NEWTHREAD
#endif

>  again thank you for your great work on bringing us wxLua !!!!

You're welcome, it's a work in progress...
    John Labenski

Re: [Wxlua-users] Re: wxLua works as module, require"wx"

[Damien F. <dam...@mo...>]

 this is great news !!!!

 our pipeline is strongly based on lua and I can`t wait to put more wxLua in action !!

> A sample program called luamodule.wx.lua in that dir shows it working
> by simply creating a wxFrame. Test it from the
> wxLua/apps/luamodule/src dir using
> $../../../bin/lua luamodule.wx.lua

 this worked great , compile and run .

 but if I try 
	lua luamodule.wx.lua

 I get an error of type :
	libwx_gtk2_wxlua-2.6.so: undefined symbol: wxLua_lua_getnewthreadhandler

 we have the standard lua 5.1 distribution installed , what is exactly the difference beetwen lua 5.1 
 and lua include the wxLua distribution ?

 is it only the function enable by the  WXLUA_LUA_NEWTHREAD flag ?

 again thank you for your great work on bringing us wxLua !!!!

 damien

[Wxlua-users] Re: wxLua works as module, require"wx"

[Francesco M. <f18...@ya...>]

John Labenski ha scritto:
> In the wxLua/apps/luamodule dir is code to make lua require"wx" work in 
> Linux.
> 
> You create the wx.so library by running $make in the
> wxLua/apps/luamodule/src dir and all of wxLua will be created for you.
> The output wx.so lib is just dumped in the src dir for now.  The
> Makefile uses the wx-config script and therefore it MUST be in your
> path. Additionally it puts the resultant wxLua libs it creates in the
> appropriate lib dir of wxWidgets so it must be writeable. As a
> developer I never bother to install wxWidgets, but if you have you'll
> have to hack the Makefiles located in each XXX/src dir to output them
> elsewhere. The Makefiles are fairly straightforward so this shouldn't
> be difficult. Eventually we'll get the bakefile's configure to work
> with this new project.
yes, sure

> 
> A sample program called luamodule.wx.lua in that dir shows it working
> by simply creating a wxFrame. Test it from the
> wxLua/apps/luamodule/src dir using
> $../../../bin/lua luamodule.wx.lua
> 
> ps. Francesco can you rebake the files. I have added back the
> -DWXLUA_CODE define, now called WXLUA_LUA_NEWTHREAD for clarity in
> modules/build/bakefiles/modules.bkl. We had to remove that previously,
> but now I see that it's required for using wxLua as a module.
Done...

> 
> Also, about adding this to bakefile? Note: The output must
> unfortunately be called wx.so since otherwise require"wx" will fail.
I have a little mess currently with wxWidgets as I have various 
installed versions and all patched so it will take me a bit before being 
able to test the bakefiles for luamodule but I've already written the 
necessary stuff ;)

> 
> I don't really understand completely what I've done, but it seems to
> work. See apps/luamodule/src/Makefile and the wx.so: tag. I guess I'm
> compiling the luamodule.cpp file,
yes, sure

> linking it with all the other libs,
yes but this is a dynamic link (wx.so is only 150K on my system)

> and then creating a .so library using -shared. I think also that -fpic
> is needed.
yes, -fpic is for generating code for shared objects (pic = position 
independent code)...

> 
> I haven't the foggiest idea about how to do the same in MSW, I guess
> it should be a DLL? 
yes, I think so.

>But then how do you "link" this DLL to all of the
> wxLua and wxWidgets DLLs 
using the import libraries generated when creating the DLL (i.e. when 
you compile with SHARED=1 both .lib and .dll files are created - the 
.lib are import libraries).

>or can you create the wxLua and wxWidgets
> libs as libs and link them to the DLL?
if I got it right then: no it's not possible.
code compiled in "DLL" mode is different from code compiled for static 
linking.

Francesco

Re: [Wxlua-users] wxLua works as module, require"wx"

[Damien F. <dam...@mo...>]

 this is great news !!!!

 our pipeline is strongly based on lua and I can`t wait to put more wxLua in action !!

> A sample program called luamodule.wx.lua in that dir shows it working
> by simply creating a wxFrame. Test it from the
> wxLua/apps/luamodule/src dir using
> $../../../bin/lua luamodule.wx.lua

 this worked great , compile and run .

 but is I try 
	lua luamodule.wx.lua

 I get an error of type :
	libwx_gtk2_wxlua-2.6.so: undefined symbol: wxLua_lua_getnewthreadhandler

 we have the standard lua 5.1 distribution installed , what is exactly the difference beetwen lua 5.1 
 and lua include the wxLua distribution ?

 is it only the function enable by the  WXLUA_LUA_NEWTHREAD flag ?

 again thank you for your great work on bringing us wxLua !!!!

 damien

 

Re: [Wxlua-users] wxSocket sample code ?

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

On 5/14/06, Steve Kieu <ha...@ya...> wrote:
> http://wxlua.sourceforge.net/wxLua/bindings/wxwidgets/socket.i
> Hi there, just started to port a sample server from wxWidgets c++ to wxLu=
a
> but it seems that the support for wxSocket  in wxLua is not quite useable
> yet. please correct if I am wrong.
>
> First I did not see any wxSocketEventFlags exported to lua; the  socket.i
> has only one comment line
>
> // %enum wxSocketEventFlags %endenum

These are actually not enums at all, they're actually typedefs in C++.
We just treat them as enums. They're added as of this afternoon.

> And the method. SetEventHandler  of wxSocket  is not exported yet so I ha=
ve
> no way to set a SOCKET_ID  for a socket created in wxLua .
>
> Any idea to work around it?

Get the current CVS HEAD, I had just updated all of socket.i earlier
today. Let me know if anything is still missing or doesn't work since
I just used the docs and the headers to do it.

Regards,
    John Labenski

Re: [Wxlua-users] wxSocket sample code ?

[Steve K. <ha...@ya...>]

Here's the interface file for the socket classes of wxWidgets that
wxLua wraps. You use them in wxLua as you would in C++, but I have to
admit that I've never tried them. See the wxWidgets documentation.

http://wxlua.sourceforge.net/wxLua/bindings/wxwidgets/socket.i
Hi there, just started to port a sample server from wxWidgets c++ to wxLua but it seems that the support for wxSocket  in wxLua is not quite useable yet. please correct if I am wrong.

First I did not see any wxSocketEventFlags exported to lua; the  socket.i has only one comment line 

// %enum wxSocketEventFlags %endenum


And the method. SetEventHandler  of wxSocket  is not exported yet so I have no way to set a SOCKET_ID  for a socket created in wxLua .

Any idea to work around it? 



S.KIEU
		
---------------------------------
Do you Yahoo!?
  Yahoo! Personals: It's free to check out our great singles!  

Re: [Wxlua-users] wxSocket sample code ?

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

On 5/13/06, Steve Kieu <ha...@ya...> wrote:
> > thinking about using luasocket (kepler project) as well but their uses =
of
> > coroutine (copas) make me a bit uncomfortable :-). And me think wxLua
>
> Sorry never tried this either.
> couroutine in lua IMHO is not really a replacement for thread. But I thin=
k
> using it in wxLua is convinient enough to overcome the limitation; as if =
I
> have a
> lua_interp =3D new wxLuaState(NULL, wxID_ANY);
> and whenever I do  a
>
> int retval=3Dlua_interp->RunFile(lua_file);
>
> wxApp will spawn a new thread (?)  to run the lua file and control return
> immediately. If this is correct then I can spawn several lua_file in
> OnInit() without blocking the GUI; and the lua_file might be for the serv=
er
> process, the GUI.
>
> Correct me if I am wrong please.

The wxApp will not spawn a new thread. wxLua runs the lua code in the
main thread since it may create GUI elements and therefore *has* to be
in the main thread. However the wxWidgets sockets use events so that
you can make them non blocking. In this way you can create as many
wxLuaStates creating as many wxSockets as you like with each
wxLuaState's lua program handling the wxSocketEvents appropriately.

> > already provide wxLuaSocket why not using it (even it is not easy to no=
t
> > link with it anyway)
>
> I don't know know what you mean by this?
> :-).  If you enable wxLuaDebug then you need to enable wxLuaSocket and ha=
ve
> to link your application with it even not using it, that is what I mean. =
But
> I can build the library only without debug and socket and wxlua, which is
> fine, just save about 400Kb of size though.

Ok, yes this is probably not clear, I will try to write a little about
it in the docs. But to be sure, wxLuaDebug is just some simple
debugging code for wxLua and wxLuaSocket is socket code for wxLua to
communicate with another wxLua program for debugging.

To turn them off set in modules/wxbind/setup/wxluasetup.h
#define wxLUA_USE_wxLuaDebugServer              0
otherwise the bindings will have the wxLuaDebugServer which the wxlua
app uses to debug programs and therefore you have to link to the
wxLuaSocket module.


Regards,
    John Labenski

[Wxlua-users] Re: wxLua works as module, require"wx"

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

ps. I've also posted this on <lu...@ba...> to see if
anyone there can clarify how to deal with this in MSW.

On 5/13/06, John Labenski <jla...@gm...> wrote:
> In the wxLua/apps/luamodule dir is code to make lua require"wx" work in L=
inux.
>
> You create the wx.so library by running $make in the
> wxLua/apps/luamodule/src dir and all of wxLua will be created for you.
> The output wx.so lib is just dumped in the src dir for now.  The
> Makefile uses the wx-config script and therefore it MUST be in your
> path. Additionally it puts the resultant wxLua libs it creates in the
> appropriate lib dir of wxWidgets so it must be writeable. As a
> developer I never bother to install wxWidgets, but if you have you'll
> have to hack the Makefiles located in each XXX/src dir to output them
> elsewhere. The Makefiles are fairly straightforward so this shouldn't
> be difficult. Eventually we'll get the bakefile's configure to work
> with this new project.
>
> A sample program called luamodule.wx.lua in that dir shows it working
> by simply creating a wxFrame. Test it from the
> wxLua/apps/luamodule/src dir using
> $../../../bin/lua luamodule.wx.lua
>
> ps. Francesco can you rebake the files. I have added back the
> -DWXLUA_CODE define, now called WXLUA_LUA_NEWTHREAD for clarity in
> modules/build/bakefiles/modules.bkl. We had to remove that previously,
> but now I see that it's required for using wxLua as a module.
>
> Also, about adding this to bakefile? Note: The output must
> unfortunately be called wx.so since otherwise require"wx" will fail.
>
> I don't really understand completely what I've done, but it seems to
> work. See apps/luamodule/src/Makefile and the wx.so: tag. I guess I'm
> compiling the luamodule.cpp file, linking it with all the other libs,
> and then creating a .so library using -shared. I think also that -fpic
> is needed.
>
> I haven't the foggiest idea about how to do the same in MSW, I guess
> it should be a DLL? But then how do you "link" this DLL to all of the
> wxLua and wxWidgets DLLs or can you create the wxLua and wxWidgets
> libs as libs and link them to the DLL?
>
> Maybe someone who uses lua's require more regularly can shed some light o=
n this?
>
> Regards,
>     John Labenski
>