Wow!

[USCode]

Terrific work here Franky!
It's amazing how much work you have gotten done here!
Thanks!

A few questions for you:
- Last version is dated April 2008, is wxJavaScript still being
actively developed?
If so, when do you anticipate being at 1.0?
- Any updates on the status of the OS X version?
- Is there any support for encryption?

Thanks again,
USCode

[Franky Braem]

USCode schreef:

I'm still working on wxJavaScript. I'm currently working on integrating
the POCO api into JavaScript. POCO contains some libraries that are
better then wxWidgets (like sockets, ...). When this is finished, a 1.0
version will be ready.

Jochen Peters was working on a OS X version, but it's about 6 months ago
that I heard anything from him. So I don't think he's working on it.

Encryption is not yet supported. But POCO has some classes for it, so
they can also be ported to wxJavaScript.

I'm considering to rename wxJavaScript into <wx/JavaScript>. wxWidgets
will still be used for the GUI parts, while POCO and other libraries
will be used for utility modules.

Franky.

[USCode]

I'm interested in wxJavaScript for developing client-side applications
only;

Is there a way now, or in the future do you plan to offer a way to run
a wxJavaScript application without the console?
Perhaps by providing a non-console version of wxjs.exe ?

One of the difficulties with distributing scripting-language
applications is all the various files necessary to make the
application run.
Have you considered leveraging the wxZipInputStream to allow
developers to create a single executable that would contain all the
files (except the DLLs) their application needs to run in one neat
package?

The directory information for most executable formats is at the
beginning of the file and the directory information for the ZIP
archive format is at the end of the file. This means that you can
append extra data to an executable and the operating system will not
care and you can prepend information to a ZIP archive and the zip
input stream will not care. So then, there is nothing to prevent you
from appending the ZIP archive to the executable that contains your
JavaScript interpreter and thereby put your entire application into a
single standalone file!

wxjs.exe would of course have to be slightly enhanced to automatically
link in the wx IO module and read the archive appended to itself to
load and execute a predefined startup script. That startup script
would then read into the archive as necessary for any other files
needed by the application.

Something like that would make distributing wxJavaScript applications
much easier, cleaner, hide raw scripts from the user, etc.
What do you think?

[Franky Braem]

USCode schreef:

At the moment there's no way to package scripts an run wxJavaScript from
an archive. Maybe you can enter a feature request on the project page.
That way I can remember to look at the request.

Franky.

[USCode]

Done!

Thanks again