[Wxlua-users] Re: Printing and derived functions fixed & wxLuaFreeze

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

John Labenski ha scritto:
> Francesco, can you rebake the build files? I've added wxluafreeze by
> copying every instance where I saw wxluacan. I hope I got it right.
yes, everything was perfect in bakefiles.
I just added a new option to configure.ac.

A minor thing: wxLuaFreeze had a dependency from wxSTC because of an 
unnecessary call to wxLuaBinding_wxstc_init();... I've removed it...

>> I have fixed the printing and in general calling derived functions
>> like the ones in wxLuaPrintout.
Very good !


>>
>> I think that after I add the wxLuaFreeze program that works in Linux
>> using gcc (at least) I think we can make the 2.6.3.1 release!
Sure. Can we fix a date for it ?
Until 19 April I'll be in (semi) holidays... ;)


>> The wxLuaFreeze I wrote consists of a lua script that appends a wxLua
>> program to the wxLuaFreeze.exe executable which when started looks at
>> the end of itself for a special tag that tells it how big the script
>> at the end is and then loads and runs it.
I looked how it's implemented and it looks a short & elegant solution ;)

>>
>> I still don't have a good idea how to really get freeze to work for
>> multiple files and modules, but it's a start and at least it shows how
>> to make a very minimal wxLua program that simply runs a script. I
>> think we'd have to rewrite the lua module loading to use some sort of
>> fake file system, for example reading from a wxZipFilestream. However
>> we can't just replace the io.open functions since the wxLua program
>> may want to actually use them to read/write files that are really on
>> the disk.
I think you're right: an additional abstraction level is necessary to 
hide to the scripts the facts that the scripts themselves have been 
embedded in a single exe... but as you say that's a good start.

An important thing before making 2.6.3.1 is also to update the ChangeLog...

Francesco