wxlua-users — wxLua list for users and developers

Re: [wxlua-users] building 2.8.0.0 with wxstedit-1.2.4

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

John Labenski ha scritto:
> On 12/26/06, Doug Currie <dou...@gm...> wrote:
>> On Tuesday, December 26, 2006 Francesco Montorsi wrote:
>>
>>> I don't remember right now if wxCode bakefiles/autoconf stuff fully support the
>>>     mkdir mybuild && cd mybuild && ../configure
>>> trick.
>> It seems to work well for wxWidgets and wxLua except for this one
>> file.
>>
>>> Calling configure in the root dir (./configure) doesn't solve the problem?
>> I don't think it would; in that case pencil.ico would be in ./art/pencil.ico
> 
> Can we not just have no path for pencil.ico and add an -I include
> directive for it? I can't test in MSW right now, but IIRC the include
> paths work in RC files, but maybe not for icons? Dunno.
> 
> wxstedit.rc
> pencil16 ICON "pencil.ico"
I don't know if this will work... probably it does only if a copy of 
pencil.ico is in the same folder of wxstedit.rc; so I'd suggest to  move 
wxstedit.rc in art\ (if the -I trick fails).


>>> and then define SRCDIR to be $(srcdir) for MSYS but I don't really know if other
>>> win32 compilers would like it.
>> Maybe the Makefile should cd into the $(srcdir)/./samples/stedit
>> directory and execute $(WINDRES) there. This might make it more
>> compatible with the "other" IDE.
>>
>> Is the sample even needed for wxLua? The only reason I'm making it is
>> for the stedit prerequisite for wxLua. Maybe the sample should not be
>> in the 'all:' target of wxstedit's Makefile to avoid the problem for
>> those, like me, who are only trying to get the wxstedit library?
if you're trying to get only the wxstedit library, then even if the 
sample fails to compile, you should already have the library correctly 
placed in lib\...


> It really should be built for people who just want to use wxStEdit
> since it's a test to see that things work. Hopefully we can fix this
> since the sample program is very small and should compile quickly.
> 
> =====================
> 
> Franscesco, what is the status of the wxCode bakefiles? What bakefile
> should I use to regenerate  wxCode projects in the future?
wxCode bakefiles are ok. The problem is that the WINDRES-hack has been 
added to wxpresets "recently" (I'd say 5-6 months ago) and maybe the 
change didn't go in wx 2.6.3 and maybe you used those wxpresets together 
with the wxCode bakefiles to regen wxstedit makefiles....

to see if your wx presets are recent enough look at wx_unix.bkl; they 
should contain a line like:

<set var="WINDRES">$(WX_RESCOMP)</set>


Francesco

Re: [wxlua-users] wxLua 2.8.0.0 build failure on Mac OS X 10.4 Intel

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

On 12/26/06, Francesco Montorsi <f18...@ya...> wrote:
> > Just tried building wxLua and have run into a couple problems... I'm not
> > that much of a make guru, but it looks like it could be a relatively
> > minor path issue (or not :).
> >
> > Here are some pasted error messages.  Anyone have any idea?

Here's what I get with the current CVS, where I have run $../configure
from the dir wxLua/config_osxu_mono

g++ -o ../bin/wxlua app_wxlua_wxlua.o app_wxlua_lconsole.o   -L../lib
-L/Users/emac/wx/wxLua/wxLua/config_osxu_mono/../modules/lua/lib
-lwxlua_macu_wxlua-2.8 -lwxlua_macu_wxbindstc-2.8
-lwxlua_macu_wxbind-2.8 -lwxlua_macu_wxluasocket-2.8
-lwxlua_macu_wxluadebug-2.8 -llua5.1
-L/Users/emac/wx/wxWidgets/wxWidgets_a/wxWidgets/config_osxu_mono/lib
 -framework QuickTime -framework IOKit -framework Carbon -framework
Cocoa -framework System
/Users/emac/wx/wxWidgets/wxWidgets_a/wxWidgets/config_osxu_mono/lib/libwx_macu_stc-2.8.a
/Users/emac/wx/wxWidgets/wxWidgets_a/wxWidgets/config_osxu_mono/lib/libwx_macu-2.8.a
-framework WebKit -lwxregexu-2.8 -lwxexpat-2.8 -lwxtiff-2.8
-lwxjpeg-2.8 -lwxpng-2.8 -lz -lpthread -liconv
/usr/bin/ld: warning -L: directory name
(/Users/emac/wx/wxLua/wxLua/config_osxu_mono/../modules/lua/lib) does
not exist
/Developer/Tools/Rez -d __DARWIN__ -t APPL -i ../../modules -i ./../..
-i /Users/emac/wx/wxLua/wxLua/config_osxu_mono/../modules/lua/include
-o ../bin/wxlua ../../art/wxlua.r
/Developer/Tools/SetFile -a C wxlua
ERROR: File Not Found. (-43)  on file: wxlua
make[1]: *** [../bin/wxlua] Error 2
make: *** [apps] Error 2
[emac@eMac config_osxu_mono]$ dir bin
total 26816
drwxr-xr-x    4 emac  emac       136 Dec 26 19:11 .
drwxr-xr-x   16 emac  emac       544 Dec 26 18:54 ..
-rwxr-xr-x    1 emac  emac    167884 Dec 26 19:10 lua
-rwxr-xr-x    1 emac  emac  13526188 Dec 26 19:11 wxlua

The problem is that SetField has the wrong path to wxlua, it's correct
for lua itself.

__app_lua___mac_setfilecmd = \
        $(SETFILE) -t APPL $(top_builddir)/bin/lua$(EXEEXT)
...

Added "$(top_builddir)/lib/"

__app_wxlua___mac_setfilecmd = \
        $(SETFILE) -a C $(top_builddir)/lib/wxlua$(EXEEXT)

Added "$(top_builddir)/lib/"

__app_wxluaedit___mac_setfilecmd \
        = $(SETFILE) -a C $(top_builddir)/lib/wxluaedit$(EXEEXT)

Will do some more testing in a bit.

Regards,
    John Labenski

Re: [wxlua-users] wxLua 2.8.0.0 build failure on Mac OS X

[Ryan R. <rya...@gm...>]

> Hi,
>
>     mac build support is still not 100% perfect; the problem is that I
> don't have a mac and thus I cannot test the build system on a mac
directly.
>
> With the help of Anders we did a lot of progresses in this direction
> however.
>
>
> Ryan Raaum ha scritto:
> > Hi all,
> >
> > Just tried building wxLua and have run into a couple problems... I'm not
> > that much of a make guru, but it looks like it could be a relatively
> > minor path issue (or not :).
> >
> > Here are some pasted error messages.  Anyone have any idea?
> >
> > http://pastebin.com/844893
> I've got an idea of why that happens. However I'd like first to know why
> the line
>
> ln -f ../bin/wxlua wxLua.app/Contents/MacOS/app_wxlua
>
> succeeds while the line
>
> ln: ../bin/wxlua: No such file or directory
>
> complains about missing ../bin/wxlua; what I mean is: why does ln -f
> ../bin/wxlua succeeds if ../bin/wxlua does not exist?
>
> My suspect however is that "wxlua" has not been built as the configure
> script has not found the wxSTC wrappers but nonetheless make tries to
> build the "wxLua.app/Contents/PkgInfo" target.
>
> I've fixed it in CVS.

Great.  I tried the latest cvs checkout and it builds without error.  (Now I
just have to figure out the next step :)

Thanks Francesco!

-r

>
> Thanks,
> Francesco

-- 
Ryan Raaum
http://raaum.org
http://rails.raaum.org -- Rails docs
http://locomotive.raaum.org -- Self contained Rails for Mac OS X

Re: [wxlua-users] building 2.8.0.0 with wxstedit-1.2.4

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

On 12/26/06, Doug Currie <dou...@gm...> wrote:
> On Tuesday, December 26, 2006 Francesco Montorsi wrote:
>
> > I don't remember right now if wxCode bakefiles/autoconf stuff fully support the
>
> >     mkdir mybuild && cd mybuild && ../configure
>
> > trick.
>
> It seems to work well for wxWidgets and wxLua except for this one
> file.
>
> > Calling configure in the root dir (./configure) doesn't solve the problem?
>
> I don't think it would; in that case pencil.ico would be in ./art/pencil.ico

Can we not just have no path for pencil.ico and add an -I include
directive for it? I can't test in MSW right now, but IIRC the include
paths work in RC files, but maybe not for icons? Dunno.

wxstedit.rc
pencil16 ICON "pencil.ico"


> > and then define SRCDIR to be $(srcdir) for MSYS but I don't really know if other
> > win32 compilers would like it.
>
> Maybe the Makefile should cd into the $(srcdir)/./samples/stedit
> directory and execute $(WINDRES) there. This might make it more
> compatible with the "other" IDE.
>
> Is the sample even needed for wxLua? The only reason I'm making it is
> for the stedit prerequisite for wxLua. Maybe the sample should not be
> in the 'all:' target of wxstedit's Makefile to avoid the problem for
> those, like me, who are only trying to get the wxstedit library?

It really should be built for people who just want to use wxStEdit
since it's a test to see that things work. Hopefully we can fix this
since the sample program is very small and should compile quickly.

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

Franscesco, what is the status of the wxCode bakefiles? What bakefile
should I use to regenerate  wxCode projects in the future?

Thanks,
    John Labenski

Re: [wxlua-users] building 2.8.0.0 with wxstedit-1.2.4

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

On 12/25/06, Doug Currie <dou...@gm...> wrote:
> In the midst of building 2.8.0.0 with wxstedit-1.2.4 with mingw and
> msys on WinXP using configure...
>
> Also, in setup.h if I use:
>
> #define STE_USE_LANG_VB          0 // 8
>
> I get:
>
> ./bk-deps g++ -c -o stedit_lib_stelangs.o  -I../include -I/contrib/include -I/usr/local/lib/wx/include/msw-unicode-release-static-2.8 -I/usr/local/include/wx-2.8 -D__WXMSW__ -mthreads  -g0 -O2 .././src/stelangs.cpp
> .././src/stelangs.cpp:4475: error: `STE_WordList1_STE_LANG_VB' was not declared in this scope
> make: *** [stedit_lib_stelangs.o] Error 1

Fixed in CVS now, the HTML lexer uses VB words as a keyword list as
well so the VB keyword list is #ifed for either VB or HTML.

see http://wxcode.cvs.sourceforge.net/wxcode/wxCode/components/wxstedit/src/stelangs.cpp


Thanks,
    John Labenski

Re: [wxlua-users] building 2.8.0.0 with wxstedit-1.2.4

[Doug C. <dou...@gm...>]

On Tuesday, December 26, 2006 Francesco Montorsi wrote: 

> I don't remember right now if wxCode bakefiles/autoconf stuff fully support the

>     mkdir mybuild && cd mybuild && ../configure

> trick.

It seems to work well for wxWidgets and wxLua except for this one
file.

> Calling configure in the root dir (./configure) doesn't solve the problem?

I don't think it would; in that case pencil.ico would be in ./art/pencil.ico

> and then define SRCDIR to be $(srcdir) for MSYS but I don't really know if other
> win32 compilers would like it.

Maybe the Makefile should cd into the $(srcdir)/./samples/stedit
directory and execute $(WINDRES) there. This might make it more
compatible with the "other" IDE.

Is the sample even needed for wxLua? The only reason I'm making it is
for the stedit prerequisite for wxLua. Maybe the sample should not be
in the 'all:' target of wxstedit's Makefile to avoid the problem for
those, like me, who are only trying to get the wxstedit library?

Regards,

e

--
Doug Currie
Londonderry, NH, USA

Re: [wxlua-users] building 2.8.0.0 with wxstedit-1.2.4

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

Doug Currie ha scritto:
> On Tuesday, December 26, 2006 Francesco Montorsi wrote: 
> 
>> Doug Currie ha scritto:
>>> In the midst of building 2.8.0.0 with wxstedit-1.2.4 with mingw and
>>> msys on WinXP using configure...
>>>
>>> When making wxstedit-1.2.4 I ran into the old problem of
>>> wxstedit-1.2.4\samples\stedit\wxstedit.rc  having paths such as
>>> "../../art/pencil.ico" that I must modify to "../art/pencil.ico" to
>>> make the build proceed.
>> I don't understand why that's required: wxstedit.rc indeed needs to use
>> ../.. to reference to the "art" directory... I don't understand why with
>> msys you'd need to use only a single ".."
> 
> The makefile is in a directory at the top level of the distribution;
> i.e., ../configure produces the Makefile line
I don't remember right now if wxCode bakefiles/autoconf stuff fully support the

    mkdir mybuild && cd mybuild && ../configure

trick. Calling configure in the root dir (./configure) doesn't solve the problem?


> srcdir = ..
> 
> and the make target is:
> 
> wxstedit_wxstedit_rc.o: $(srcdir)/./samples/stedit/wxstedit.rc
> 
> So, we are compiling
> 
> ..././samples/stedit/wxstedit.rc
I'd guess you meant .././samples/stedit/wxstedit.rc here

> 
> Now, pencil.ico is in
> 
> ..././art/pencil.ico
> 
> which is
> 
> .../art/pencil.ico
ok, thanks for the explanation.
To fix your problem we'd need to have something like

aaaaaaaa ICON "$(srcdir)/art/pencil.ico"

which is not allowed by other win32 compilers (and wouldn't work even with 
MSYS). We could complicate the build system adding a

#ifndef SRCDIR
     #define SRCDIR ../..
#endif

aaaaaaaa ICON SRCDIR/art/pencil.ico

and then define SRCDIR to be $(srcdir) for MSYS but I don't really know if other 
win32 compilers would like it.


Francesco

Re: [wxlua-users] building 2.8.0.0 with wxstedit-1.2.4

[Doug C. <dou...@gm...>]

On Tuesday, December 26, 2006 Francesco Montorsi wrote: 

> Doug Currie ha scritto:
>> In the midst of building 2.8.0.0 with wxstedit-1.2.4 with mingw and
>> msys on WinXP using configure...
>> 
>> When making wxstedit-1.2.4 I ran into the old problem of
>> wxstedit-1.2.4\samples\stedit\wxstedit.rc  having paths such as
>> "../../art/pencil.ico" that I must modify to "../art/pencil.ico" to
>> make the build proceed.
> I don't understand why that's required: wxstedit.rc indeed needs to use
> ../.. to reference to the "art" directory... I don't understand why with
> msys you'd need to use only a single ".."

The makefile is in a directory at the top level of the distribution;
i.e., ../configure produces the Makefile line

srcdir = ..

and the make target is:

wxstedit_wxstedit_rc.o: $(srcdir)/./samples/stedit/wxstedit.rc

So, we are compiling

.././samples/stedit/wxstedit.rc

Now, pencil.ico is in

.././art/pencil.ico

which is

../art/pencil.ico

e

-- 
Doug Currie
Londonderry, NH, USA

Re: [wxlua-users] wxLua 2.8.0.0 build failure on Mac OS X 10.4 Intel

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

Hi,

     mac build support is still not 100% perfect; the problem is that I 
don't have a mac and thus I cannot test the build system on a mac directly.

With the help of Anders we did a lot of progresses in this direction 
however.


Ryan Raaum ha scritto:
> Hi all,
> 
> Just tried building wxLua and have run into a couple problems... I'm not 
> that much of a make guru, but it looks like it could be a relatively 
> minor path issue (or not :).
> 
> Here are some pasted error messages.  Anyone have any idea?
> 
> http://pastebin.com/844893
I've got an idea of why that happens. However I'd like first to know why 
the line

ln -f ../bin/wxlua wxLua.app/Contents/MacOS/app_wxlua

succeeds while the line

ln: ../bin/wxlua: No such file or directory

complains about missing ../bin/wxlua; what I mean is: why does ln -f 
../bin/wxlua succeeds if ../bin/wxlua does not exist?

My suspect however is that "wxlua" has not been built as the configure 
script has not found the wxSTC wrappers but nonetheless make tries to 
build the "wxLua.app/Contents/PkgInfo" target.

I've fixed it in CVS.

Thanks,
Francesco

Re: [wxlua-users] Announcing wxLua 2.8.0.0: lua bindings to wxWidgets

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

Doug Currie ha scritto:
> I note that in:
> 
> C:\Dev\wxLua-2.8.0.0\modules\wxlua\include\wxldefs.h
> 
> the version number is not updated...
> 
> #define WXLUA_MAJOR_VERSION      2
> #define WXLUA_MINOR_VERSION      6
> #define WXLUA_RELEASE_VERSION    3
> #define WXLUA_SUBRELEASE_VERSION 0
> #define WXLUA_VERSION_STRING    wxT("wxLua 2.6.3")
> 
Fixed, thanks!

Francesco

Re: [wxlua-users] building 2.8.0.0 with wxstedit-1.2.4

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

Doug Currie ha scritto:
> In the midst of building 2.8.0.0 with wxstedit-1.2.4 with mingw and
> msys on WinXP using configure...
> 
> When making wxstedit-1.2.4 I ran into the old problem of
> wxstedit-1.2.4\samples\stedit\wxstedit.rc  having paths such as
> "../../art/pencil.ico" that I must modify to "../art/pencil.ico" to
> make the build proceed.
I don't understand why that's required: wxstedit.rc indeed needs to use 
../.. to reference to the "art" directory... I don't understand why with 
msys you'd need to use only a single ".."


> Also, in setup.h if I use:
> 
> #define STE_USE_LANG_VB          0 // 8
> 
> I get:
> 
> ./bk-deps g++ -c -o stedit_lib_stelangs.o  -I../include -I/contrib/include -I/usr/local/lib/wx/include/msw-unicode-release-static-2.8 -I/usr/local/include/wx-2.8 -D__WXMSW__ -mthreads  -g0 -O2 .././src/stelangs.cpp
> .././src/stelangs.cpp:4475: error: `STE_WordList1_STE_LANG_VB' was not declared in this scope
> make: *** [stedit_lib_stelangs.o] Error 1
I'm not sure that those STE_USE_LANG* settings are meant to be changed 
by the user to customize the build; John surely knows it better.


> Also, the Makefile built by configure doesn't have any include path
> for windres for wx, so I had to add:
> 
> --include-dir /usr/local/include/wx-2.8
> 
> at the end of the WINDRES line in the wxstedit_wxstedit_rc.o target
that's a known "bug" of wxWidgets 2.6.x wxpresets - it has been fixed in 
wxCVS and the fix should be in wxWidgets 2.8.x wxpresets.

Thus, just rebaking with newer presets will erase this bug ;)

Thanks for your report,
Francesco

[wxlua-users] wxLua 2.8.0.0 build failure on Mac OS X 10.4 Intel

[Ryan R. <rya...@gm...>]

Hi all,

Just tried building wxLua and have run into a couple problems... I'm not
that much of a make guru, but it looks like it could be a relatively minor
path issue (or not :).

Here are some pasted error messages.  Anyone have any idea?

http://pastebin.com/844893

Best,

-r

-- 
Ryan Raaum
http://raaum.org
http://rails.raaum.org -- Rails docs
http://locomotive.raaum.org -- Self contained Rails for Mac OS X

Re: [wxlua-users] Announcing wxLua 2.8.0.0: lua bindings to wxWidgets

[Doug C. <dou...@gm...>]

I note that in:

C:\Dev\wxLua-2.8.0.0\modules\wxlua\include\wxldefs.h

the version number is not updated...

#define WXLUA_MAJOR_VERSION      2
#define WXLUA_MINOR_VERSION      6
#define WXLUA_RELEASE_VERSION    3
#define WXLUA_SUBRELEASE_VERSION 0
#define WXLUA_VERSION_STRING    wxT("wxLua 2.6.3")

Regards,

e

-- 
Doug Currie
Londonderry, NH, USA

[wxlua-users] building 2.8.0.0 with wxstedit-1.2.4

[Doug C. <dou...@gm...>]

In the midst of building 2.8.0.0 with wxstedit-1.2.4 with mingw and
msys on WinXP using configure...

When making wxstedit-1.2.4 I ran into the old problem of
wxstedit-1.2.4\samples\stedit\wxstedit.rc  having paths such as
"../../art/pencil.ico" that I must modify to "../art/pencil.ico" to
make the build proceed.

Also, in setup.h if I use:

#define STE_USE_LANG_VB          0 // 8

I get:

./bk-deps g++ -c -o stedit_lib_stelangs.o  -I../include -I/contrib/include -I/usr/local/lib/wx/include/msw-unicode-release-static-2.8 -I/usr/local/include/wx-2.8 -D__WXMSW__ -mthreads  -g0 -O2 .././src/stelangs.cpp
.././src/stelangs.cpp:4475: error: `STE_WordList1_STE_LANG_VB' was not declared in this scope
make: *** [stedit_lib_stelangs.o] Error 1

Also, the Makefile built by configure doesn't have any include path
for windres for wx, so I had to add:

--include-dir /usr/local/include/wx-2.8

at the end of the WINDRES line in the wxstedit_wxstedit_rc.o target

Regards,

e

-- 
Doug Currie
Londonderry, NH, USA

[wxlua-users] [ wxlua-Patches-1622013 ] editor

[SourceForge.net <no...@so...>]

Patches item #1622013, was opened at 2006-12-25 10:17
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745326&aid=1622013&group_id=140042

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andre Arpin (andrearpin)
Assigned to: Nobody/Anonymous (nobody)
Summary: editor

Initial Comment:
These changes are to make the editor easier to use to improve it. This should make the editor friendlier. 

Fix a numbers of minor problems.
Added comment toggling
Added sort
Added a more complete find/replace
Added some folding

There is a number of issues that still have to addressed.

Andre

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745326&aid=1622013&group_id=140042

Re: [wxlua-users] wxlua-2.8.0.0-dlls, windows pop and depop immediatly

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

On 12/24/06, J=E9r=F4me VUARAND <jer...@gm...> wrote:
> 2006/12/24, John Labenski <jla...@gm...>:
> > On 12/24/06, J=E9r=F4me VUARAND <jer...@gm...> wrote:
> > > 2006/12/24, John Labenski <jla...@gm...>:
> > > > What you're suggesting is not normal, it's better to have the syste=
m's
> > > > native mainloop control program flow rather than implementing your =
own
> > > > which will most likely be far less efficient. In any case you shoul=
d
> > > > be able to do it using wxApp::Pending and wxApp::Dispatch.
> > >
> > > wxApp::Pending+wxApp::Dispatch seems to be exactly what I need.
> >
> > You may still want to consider using wxEVT_IDLE though since I think
> > that's what is typically suggested on the C++ wxusers mailing list for
> > doing pseudo-threading like this.
>
> I've tried Pending+Dispatch but that don't seems to work.
> wx.wxGetApp():Pending() never returns true.
>
> The code is :
> wx =3D require("wx")
> dofile(...)
> local use_custom_loop =3D true
> if use_custom_loop then
>     while true do
          while wx.wxGetApp():Pending() do
>             wx.wxGetApp():Dispatch()
>         end

           wx.wxMilliSleep(10) -- adjust as necessary
           wx.wxGetApp():ProcessIdle()

>     end
> else
>     wx.wxGetApp():MainLoop()
> end
>
> The command line is :
> lua bootstrap.lua minimal.wx.lua
>
> Everything works ok if I set my use_custom_loop to false. I'll have a
> look at the internals of MainLoop to see what may be missing. And I
> still need to try the idle event model, though I don't think that will
> match my timing requirement.

I can't test the changes above right now, but take a look at
wxPython's samples/mainloop/mainloop.py program and it's wxApp's
MainLoop function. Hopefully the only problem is that you need to
completely flush the events with the "while wx.wxGetApp():Pending()"
loop and give the event handler a little kick with
wx.wxGetApp():ProcessIdle() every once in a while.

see here and the posts before and after it.
http://lists.wxwidgets.org/archive/wxPython-users/msg07355.html

Regards,
    John Labenski

Re: [wxlua-users] wxlua-2.8.0.0-dlls, windows pop and depop immediatly

[<jer...@gm...>]

MjAwNi8xMi8yNCwgSm9obiBMYWJlbnNraSA8amxhYmVuc2tpQGdtYWlsLmNvbT46Cj4gT24gMTIv
MjQvMDYsIErDqXLDtG1lIFZVQVJBTkQgPGplcm9tZS52dWFyYW5kQGdtYWlsLmNvbT4gd3JvdGU6
Cj4gPiAyMDA2LzEyLzI0LCBKb2huIExhYmVuc2tpIDxqbGFiZW5za2lAZ21haWwuY29tPjoKPiA+
ID4gV2hhdCB5b3UncmUgc3VnZ2VzdGluZyBpcyBub3Qgbm9ybWFsLCBpdCdzIGJldHRlciB0byBo
YXZlIHRoZSBzeXN0ZW0ncwo+ID4gPiBuYXRpdmUgbWFpbmxvb3AgY29udHJvbCBwcm9ncmFtIGZs
b3cgcmF0aGVyIHRoYW4gaW1wbGVtZW50aW5nIHlvdXIgb3duCj4gPiA+IHdoaWNoIHdpbGwgbW9z
dCBsaWtlbHkgYmUgZmFyIGxlc3MgZWZmaWNpZW50LiBJbiBhbnkgY2FzZSB5b3Ugc2hvdWxkCj4g
PiA+IGJlIGFibGUgdG8gZG8gaXQgdXNpbmcgd3hBcHA6OlBlbmRpbmcgYW5kIHd4QXBwOjpEaXNw
YXRjaC4KPiA+Cj4gPiB3eEFwcDo6UGVuZGluZyt3eEFwcDo6RGlzcGF0Y2ggc2VlbXMgdG8gYmUg
ZXhhY3RseSB3aGF0IEkgbmVlZC4KPgo+IFlvdSBtYXkgc3RpbGwgd2FudCB0byBjb25zaWRlciB1
c2luZyB3eEVWVF9JRExFIHRob3VnaCBzaW5jZSBJIHRoaW5rCj4gdGhhdCdzIHdoYXQgaXMgdHlw
aWNhbGx5IHN1Z2dlc3RlZCBvbiB0aGUgQysrIHd4dXNlcnMgbWFpbGluZyBsaXN0IGZvcgo+IGRv
aW5nIHBzZXVkby10aHJlYWRpbmcgbGlrZSB0aGlzLgoKSSd2ZSB0cmllZCBQZW5kaW5nK0Rpc3Bh
dGNoIGJ1dCB0aGF0IGRvbid0IHNlZW1zIHRvIHdvcmsuCnd4Lnd4R2V0QXBwKCk6UGVuZGluZygp
IG5ldmVyIHJldHVybnMgdHJ1ZS4KClRoZSBjb2RlIGlzIDoKd3ggPSByZXF1aXJlKCJ3eCIpCmRv
ZmlsZSguLi4pCmxvY2FsIHVzZV9jdXN0b21fbG9vcCA9IHRydWUKaWYgdXNlX2N1c3RvbV9sb29w
IHRoZW4KICAgIHdoaWxlIHRydWUgZG8KICAgICAgICBpZiB3eC53eEdldEFwcCgpOlBlbmRpbmco
KSB0aGVuCiAgICAgICAgICAgIHd4Lnd4R2V0QXBwKCk6RGlzcGF0Y2goKQogICAgICAgIGVuZAog
ICAgZW5kCmVsc2UKICAgIHd4Lnd4R2V0QXBwKCk6TWFpbkxvb3AoKQplbmQKClRoZSBjb21tYW5k
IGxpbmUgaXMgOgpsdWEgYm9vdHN0cmFwLmx1YSBtaW5pbWFsLnd4Lmx1YQoKRXZlcnl0aGluZyB3
b3JrcyBvayBpZiBJIHNldCBteSB1c2VfY3VzdG9tX2xvb3AgdG8gZmFsc2UuIEknbGwgaGF2ZSBh
Cmxvb2sgYXQgdGhlIGludGVybmFscyBvZiBNYWluTG9vcCB0byBzZWUgd2hhdCBtYXkgYmUgbWlz
c2luZy4gQW5kIEkKc3RpbGwgbmVlZCB0byB0cnkgdGhlIGlkbGUgZXZlbnQgbW9kZWwsIHRob3Vn
aCBJIGRvbid0IHRoaW5rIHRoYXQgd2lsbAptYXRjaCBteSB0aW1pbmcgcmVxdWlyZW1lbnQuCg==

Re: [wxlua-users] wxlua-2.8.0.0-dlls, windows pop and depop immediatly

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

On 12/24/06, J=E9r=F4me VUARAND <jer...@gm...> wrote:
> 2006/12/24, John Labenski <jla...@gm...>:
> > What you're suggesting is not normal, it's better to have the system's
> > native mainloop control program flow rather than implementing your own
> > which will most likely be far less efficient. In any case you should
> > be able to do it using wxApp::Pending and wxApp::Dispatch.
>
> wxApp::Pending+wxApp::Dispatch seems to be exactly what I need.
>
> I don't know what your definition of normal is, but my question seems
> perfectly normal to me. What I want to achieve is to have several Lua
> frameworks working together in a single thread (because Lua is not
> thread safe). Each of my frameworks need to be updated several times a
> second, but I can't give application main loop control to any of
> these, so I need to make them cooperate.

Sounds good, I was just using "normal" in the sense that having lua
run the mainloop is a little like having the tail wag the dog. It
sounds like you're doing something a little more advanced though, good
luck.

You may still want to consider using wxEVT_IDLE though since I think
that's what is typically suggested on the C++ wxusers mailing list for
doing pseudo-threading like this.

Regards,
    John Labenski

Re: [wxlua-users] wxlua-2.8.0.0-dlls, windows pop and depop immediatly

[<jer...@gm...>]

2006/12/24, John Labenski <jla...@gm...>:
> What you're suggesting is not normal, it's better to have the system's
> native mainloop control program flow rather than implementing your own
> which will most likely be far less efficient. In any case you should
> be able to do it using wxApp::Pending and wxApp::Dispatch.

wxApp::Pending+wxApp::Dispatch seems to be exactly what I need.

I don't know what your definition of normal is, but my question seems
perfectly normal to me. What I want to achieve is to have several Lua
frameworks working together in a single thread (because Lua is not
thread safe). Each of my frameworks need to be updated several times a
second, but I can't give application main loop control to any of
these, so I need to make them cooperate.

Example :

void F1::MainLoop()
{
    bool quit;
    Message message;
    while (message = F1::GetMessage_Blocking())
    {
        F1::ProcessMessage(message);
    }
}

void F2::MainLoop()
{
    bool quit;
    do
    {
        F2::Render();
        quit = F2::ProcessInput();
    } while (!quit);
}

void F3::MainLoop()
{
    bool quit;
    do
    {
        F3::Update();
        if (F3::LastError())
            quit = true;
    } while (!quit);
}

void InterleavedMainLoop()
{
    bool quit = false;
    Message message;
    while (true)
    {
        // Update framework F1
        while (F1::IsMessagePresent())
        {
            message = F1::GetMessage_NonBlocking();
            if (message)
                F1::ProcessMessage();
            else
                quit = true;
        }
        if (quit) break;

        // Update framework F2
        F2::Render();
        quit = F2::ProcessInput();
        if (quit) break;

        // Update framework F3
        F3::Update();
        if (F3::LastError())
            quit = true;
        if (quit) break;

        // Main application control refresh rate
        usleep(10000);
    }
}

Replace F1 with wxLua, F2 with my OpenGL renderer and F3 with john
doe's network framework if that makes things clearer. The basic idea
is that an extension module should not take control of the
application. There are a lot of multi-threaded solution to this kind
of problem, but in some context a full thread control is a big
requirement for an extension module.

Re: [wxlua-users] wxlua-2.8.0.0-dlls, windows pop and depop immediatly

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

On 12/24/06, J=E9r=F4me VUARAND <jer...@gm...> wrote:
> 2006/12/24, Hakki Dogusan <dog...@tr...>:
> > Most of the samples designed for wxLua.exe.
> >
> > You may write a simple bootstrap file, ie:
> >
> >
> > wx =3D require("wx")
> > dofile("wxluasudoku.wx.lua")
> > wx.wxGetApp():MainLoop()
>
> Is there an equivalent of wx.wxGetApp():MainLoop() that is not
> blocking ? It would process all pending messages, and then give back
> control to application. I would then call it from my own frame-based
> main loop.

You have to do all initialization or whatever you need to do before
running the GUI main loop which is always blocking since thats what
the underlying framework does. You can use the wxEVT_IDLE events to do
things continuously by calling event.RequestMore(true), but note that
continuously doing this will use 100% of your processor.

What you're suggesting is not normal, it's better to have the system's
native mainloop control program flow rather than implementing your own
which will most likely be far less efficient. In any case you should
be able to do it using wxApp::Pending and wxApp::Dispatch.

Hope this helps,
    John Labenski

Re: [wxlua-users] wxlua-2.8.0.0-dlls, windows pop and depop immediatly

[<jer...@gm...>]

2006/12/24, Hakki Dogusan <dog...@tr...>:
> Most of the samples designed for wxLua.exe.
>
> You may write a simple bootstrap file, ie:
>
>
> wx = require("wx")
> dofile("wxluasudoku.wx.lua")
> wx.wxGetApp():MainLoop()

Is there an equivalent of wx.wxGetApp():MainLoop() that is not
blocking ? It would process all pending messages, and then give back
control to application. I would then call it from my own frame-based
main loop.

Re: [wxlua-users] wxlua-2.8.0.0-dlls, windows pop and depop immediatly

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

Hi Jérôme,

Jérôme VUARAND ha scritto:
> I just downloaded the new module release wxlua-2.8.0.0-dlls.zip. Since
> there are no samples with it
yes, it's supposed to be a very very minimal download, with just all DLLs
required by wxLua. If you're interested in using wxLua you should get either the
installer or the source archives and then build them.

> I downloaded those from the wxLua source
> packages. I then tried to run them with that command line :
> $ lua -lwx minimal.wx.lua
> 
> But the application are not running properly. Consistently with all
> samples,
the luamodule.wx.lua sample works fine with me....

> the application window pops for a fraction of a second and
> then depops. I tried adding an infinite loop at the end of the sample
> or a blocking read on stdin, but then the window don't receive any
> event.
yes, I do see it (except in the luamodule.wx.lua sample). It's because they miss 
the

  require("wx")

call...

HTH,
Francesco

Re: [wxlua-users] wxlua-2.8.0.0-dlls, windows pop and depop immediatly

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

Hi,


Jérôme VUARAND wrote:
> Hi list,
> 
> I just downloaded the new module release wxlua-2.8.0.0-dlls.zip. Since
> there are no samples with it I downloaded those from the wxLua source
> packages. I then tried to run them with that command line :
> $ lua -lwx minimal.wx.lua
> 
> But the application are not running properly. Consistently with all
> samples, the application window pops for a fraction of a second and
> then depops. I tried adding an infinite loop at the end of the sample
> or a blocking read on stdin, but then the window don't receive any
> event.
> 
> I looked at the list archive but didn't found anything. Is there a
> known problem with this release of the module version or does I have
> to adapt the samples to a different paradigm/api ?
> 
> Jérôme.

Most of the samples designed for wxLua.exe.

You may write a simple bootstrap file, ie:


wx = require("wx")
dofile("wxluasudoku.wx.lua")
wx.wxGetApp():MainLoop()




--
Regards,
Hakki Dogusan

[wxlua-users] wxlua-2.8.0.0-dlls, windows pop and depop immediatly

[<jer...@gm...>]

SGkgbGlzdCwKCkkganVzdCBkb3dubG9hZGVkIHRoZSBuZXcgbW9kdWxlIHJlbGVhc2Ugd3hsdWEt
Mi44LjAuMC1kbGxzLnppcC4gU2luY2UKdGhlcmUgYXJlIG5vIHNhbXBsZXMgd2l0aCBpdCBJIGRv
d25sb2FkZWQgdGhvc2UgZnJvbSB0aGUgd3hMdWEgc291cmNlCnBhY2thZ2VzLiBJIHRoZW4gdHJp
ZWQgdG8gcnVuIHRoZW0gd2l0aCB0aGF0IGNvbW1hbmQgbGluZSA6CiQgbHVhIC1sd3ggbWluaW1h
bC53eC5sdWEKCkJ1dCB0aGUgYXBwbGljYXRpb24gYXJlIG5vdCBydW5uaW5nIHByb3Blcmx5LiBD
b25zaXN0ZW50bHkgd2l0aCBhbGwKc2FtcGxlcywgdGhlIGFwcGxpY2F0aW9uIHdpbmRvdyBwb3Bz
IGZvciBhIGZyYWN0aW9uIG9mIGEgc2Vjb25kIGFuZAp0aGVuIGRlcG9wcy4gSSB0cmllZCBhZGRp
bmcgYW4gaW5maW5pdGUgbG9vcCBhdCB0aGUgZW5kIG9mIHRoZSBzYW1wbGUKb3IgYSBibG9ja2lu
ZyByZWFkIG9uIHN0ZGluLCBidXQgdGhlbiB0aGUgd2luZG93IGRvbid0IHJlY2VpdmUgYW55CmV2
ZW50LgoKSSBsb29rZWQgYXQgdGhlIGxpc3QgYXJjaGl2ZSBidXQgZGlkbid0IGZvdW5kIGFueXRo
aW5nLiBJcyB0aGVyZSBhCmtub3duIHByb2JsZW0gd2l0aCB0aGlzIHJlbGVhc2Ugb2YgdGhlIG1v
ZHVsZSB2ZXJzaW9uIG9yIGRvZXMgSSBoYXZlCnRvIGFkYXB0IHRoZSBzYW1wbGVzIHRvIGEgZGlm
ZmVyZW50IHBhcmFkaWdtL2FwaSA/CgpKw6lyw7RtZS4K

Re: [wxlua-users] release now

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

On 12/24/06, Francesco Montorsi <f18...@ya...> wrote:
> Hi,
>     I finally managed to get the release done. Tagged, built binary
> releases, uploaded, updated website and posted announcements.

Great! Thanks very much for all your work on wxLua.

> Hopefully we will be able to add a mac bundle soon.

That would be nice.

> Thanks to everyone and happy christmas and happy new year!
> Francesco

Happy Christmas and new year as well!


Thanks,
    John Labenski