wxlua-users

RE: [Wxlua-users] Can we have standard LUA_PATH for wxLua apps

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

I will upload my stuff as soon as I get the wx interface generator
working and I can tie it altogther.

I say there is a week or two of me fiddling. Maybe longer when baby is
born - second one due this week.

Ray

-----Original Message-----
From: wxl...@li...
[mailto:wxl...@li...] On Behalf Of John
Labenski
Sent: Monday, 20 June 2005 13:43
To: wxl...@li...
Subject: Re: [Wxlua-users] Can we have standard LUA_PATH for wxLua apps

On 6/19/05, Ray Gilbert <ray...@sc...> wrote:
> =20
> Currently we do not set the LUA_PATH when we run scripts.=20
>  =20
> So the require() fn does not correctly find modules.=20
>
> I have added GetLuaPath(), AddLuaPath() to my wxLuaInterpreter object,

> can I add it to wxLua?

Sure! I tried very hard to make it so that wxLua should be as close as I
could make it to your version while keeping any fixes Paul and I made.
Hopefully you can use it out of the box, but probably not, fit it up as
necessary. In the beginning they'll be some growing pains as people
change things to make it work better for them, but so long as it's done
in a way to keep everything else working, nobody should complain.

For example, it looks to me like wxLuaStateVariables should be renamed
to wxLuaState, and it'll encapsulate just the lua_State and manage the
memory. We can put all the tgetxxx and toxxx functions in the wxLuaState
as static functions to make the code a little more readable. The
wxLuaInterpreter will then just be a thin wrapper around the wxLuaState
that provides even simpler methods and the wxLuaEvents.
That way you can use either the simplier wxLuaInterpreter or the lighter
wxLuaState as you see fit.
  =20
Anyway all I'm trying to say is that for a little bit now things may get
ugly, but they'll settle down. The bottom line - I never want to go
though the hassle of merging the different wxLuas again so if you need a
feature, add it here so we can all benefit.

Ray - do you want to put your extra modules up at sourceforge? That way
when people change something they can also compile those and fix them up
if necessary so there won't be too much breakage.

> BTW
>  =20
> I currently only add script path -
> But should we have standard wxLua search path?=20
> Should it search OS PATH?=20
> Are there other paths it should search by default, e.g. =20
> <app>/lua/?.lua; <script>/lua/?.lua;

I thought that require searches typical system places already? I haven't
any thoughts on this.

-John Labenski


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dick
_______________________________________________
Wxlua-users mailing list
Wxl...@li...
https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [Wxlua-users] Can we have standard LUA_PATH for wxLua apps

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

On 6/19/05, Ray Gilbert <ray...@sc...> wrote:
> I will upload my stuff as soon as I get the wx interface generator
> working and I can tie it altogther.
>=20
> I say there is a week or two of me fiddling.=20

Is there a quick hack that could be made to this in the meantime?
http://cvs.sourceforge.net/viewcvs.py/wxlua/wxLua/bindings/genwxbind.lua?vi=
ew=3Dmarkup
Search for the two "FIXME" lines

I've tried quite a few things, but can't figure out why putting this
after the first FIXME doesn't set the DataType
lineState.DataType =3D tag

later on line 1572 we need the DataType for AllocMember
  -- enum parseObject
  if parseState.ObjectStack[1].DefType =3D=3D "enum" then
  ...
  for k, v in lineState do print("lineState", k, v) end
  local member=3D AllocMember(lineState)

The print dump of the lineState shows that lineState.DataType is back to ni=
l.

>Maybe longer when baby is born - second one due this week.

Congrats!

Thanks,
    John

> Ray
>=20
> -----Original Message-----
> From: wxl...@li...
> [mailto:wxl...@li...] On Behalf Of John
> Labenski
> Sent: Monday, 20 June 2005 13:43
> To: wxl...@li...
> Subject: Re: [Wxlua-users] Can we have standard LUA_PATH for wxLua apps
>=20
> On 6/19/05, Ray Gilbert <ray...@sc...> wrote:
> >
> > Currently we do not set the LUA_PATH when we run scripts.
> >
> > So the require() fn does not correctly find modules.
> >
> > I have added GetLuaPath(), AddLuaPath() to my wxLuaInterpreter object,
>=20
> > can I add it to wxLua?
>=20
> Sure! I tried very hard to make it so that wxLua should be as close as I
> could make it to your version while keeping any fixes Paul and I made.
> Hopefully you can use it out of the box, but probably not, fit it up as
> necessary. In the beginning they'll be some growing pains as people
> change things to make it work better for them, but so long as it's done
> in a way to keep everything else working, nobody should complain.
>=20
> For example, it looks to me like wxLuaStateVariables should be renamed
> to wxLuaState, and it'll encapsulate just the lua_State and manage the
> memory. We can put all the tgetxxx and toxxx functions in the wxLuaState
> as static functions to make the code a little more readable. The
> wxLuaInterpreter will then just be a thin wrapper around the wxLuaState
> that provides even simpler methods and the wxLuaEvents.
> That way you can use either the simplier wxLuaInterpreter or the lighter
> wxLuaState as you see fit.
>=20
> Anyway all I'm trying to say is that for a little bit now things may get
> ugly, but they'll settle down. The bottom line - I never want to go
> though the hassle of merging the different wxLuas again so if you need a
> feature, add it here so we can all benefit.
>=20
> Ray - do you want to put your extra modules up at sourceforge? That way
> when people change something they can also compile those and fix them up
> if necessary so there won't be too much breakage.
>=20
> > BTW
> >
> > I currently only add script path -
> > But should we have standard wxLua search path?
> > Should it search OS PATH?
> > Are there other paths it should search by default, e.g.
> > <app>/lua/?.lua; <script>/lua/?.lua;
>=20
> I thought that require searches typical system places already? I haven't
> any thoughts on this.
>=20
> -John Labenski
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dick
> _______________________________________________
> Wxlua-users mailing list
> Wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> Wxlua-users mailing list
> Wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

Re: [Wxlua-users] Can we have standard LUA_PATH for wxLua apps

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

On 6/20/05, John Labenski <jla...@gm...> wrote:
> On 6/19/05, Ray Gilbert <ray...@sc...> wrote:
> > I will upload my stuff as soon as I get the wx interface generator
> > working and I can tie it altogther.
> >
> > I say there is a week or two of me fiddling.
>=20
> Is there a quick hack that could be made to this in the meantime?
> http://cvs.sourceforge.net/viewcvs.py/wxlua/wxLua/bindings/genwxbind.lua?=
view=3Dmarkup
> Search for the two "FIXME" lines

I've committed a simple hack to get the enums to work. However the %if
wxLUA_USE still doesn't work so you have to edit the wx_define.cpp and
add
include "wx/txtstrm.h" and put arbitrary values for CB_XXX (for fl) to
get it compile.

You can run the sample/editor.wx.lua again! The editor.h has to be
regenerated though so you have do do "wxLua.exe editor.wx.lua".
=20
%builtin is still busted so you can't run wxExecute. :(

-John Labenski

> I've tried quite a few things, but can't figure out why putting this
> after the first FIXME doesn't set the DataType
> lineState.DataType =3D tag
>=20
> later on line 1572 we need the DataType for AllocMember
>   -- enum parseObject
>   if parseState.ObjectStack[1].DefType =3D=3D "enum" then
>   ...
>   for k, v in lineState do print("lineState", k, v) end
>   local member=3D AllocMember(lineState)
>=20
> The print dump of the lineState shows that lineState.DataType is back to =
nil.
>=20
> >Maybe longer when baby is born - second one due this week.
>=20
> Congrats!
>=20
> Thanks,
>     John
>=20
> > Ray
> >
> > -----Original Message-----
> > From: wxl...@li...
> > [mailto:wxl...@li...] On Behalf Of John
> > Labenski
> > Sent: Monday, 20 June 2005 13:43
> > To: wxl...@li...
> > Subject: Re: [Wxlua-users] Can we have standard LUA_PATH for wxLua apps
> >
> > On 6/19/05, Ray Gilbert <ray...@sc...> wrote:
> > >
> > > Currently we do not set the LUA_PATH when we run scripts.
> > >
> > > So the require() fn does not correctly find modules.
> > >
> > > I have added GetLuaPath(), AddLuaPath() to my wxLuaInterpreter object=
,
> >
> > > can I add it to wxLua?
> >
> > Sure! I tried very hard to make it so that wxLua should be as close as =
I
> > could make it to your version while keeping any fixes Paul and I made.
> > Hopefully you can use it out of the box, but probably not, fit it up as
> > necessary. In the beginning they'll be some growing pains as people
> > change things to make it work better for them, but so long as it's done
> > in a way to keep everything else working, nobody should complain.
> >
> > For example, it looks to me like wxLuaStateVariables should be renamed
> > to wxLuaState, and it'll encapsulate just the lua_State and manage the
> > memory. We can put all the tgetxxx and toxxx functions in the wxLuaStat=
e
> > as static functions to make the code a little more readable. The
> > wxLuaInterpreter will then just be a thin wrapper around the wxLuaState
> > that provides even simpler methods and the wxLuaEvents.
> > That way you can use either the simplier wxLuaInterpreter or the lighte=
r
> > wxLuaState as you see fit.
> >
> > Anyway all I'm trying to say is that for a little bit now things may ge=
t
> > ugly, but they'll settle down. The bottom line - I never want to go
> > though the hassle of merging the different wxLuas again so if you need =
a
> > feature, add it here so we can all benefit.
> >
> > Ray - do you want to put your extra modules up at sourceforge? That way
> > when people change something they can also compile those and fix them u=
p
> > if necessary so there won't be too much breakage.
> >
> > > BTW
> > >
> > > I currently only add script path -
> > > But should we have standard wxLua search path?
> > > Should it search OS PATH?
> > > Are there other paths it should search by default, e.g.
> > > <app>/lua/?.lua; <script>/lua/?.lua;
> >
> > I thought that require searches typical system places already? I haven'=
t
> > any thoughts on this.
> >
> > -John Labenski
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dick
> > _______________________________________________
> > Wxlua-users mailing list
> > Wxl...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> > _______________________________________________
> > Wxlua-users mailing list
> > Wxl...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
> >
>