Hi,
first of all, some words about wxScript: it's not completed yet -
mainly because:
1) lua was the only real 'interpreter engine' which was easily
embeddable in a C++ project; python gave me ton of memory leaks and I
never got it fixed. Also, since wxLua project resurrected thanks to John
Labenski and other developers, I preferred to give an hand to that
project rather than focusing on wxScript.
2) CINT is old and makes interactions with loaded scripts very very
difficult. OTOH the optimal UnderC project is almost dead - IMHO it
would be a Great Thing to have a C++ interpreter (in general for the
entire FOSS world!!) and AFAIR UnderC only needs some 'final touches'
(E.g. a good build system and a good website) - I always wanted to help
the author with these things but this point is the million-th point of
my TODO list and days are limited to 24 hours unluckily.
3) perl support was contributed by Jerry Fath as I'm quite ignorant in
perl unfortunately and I'm not sure how much it covers.
So, my advise is to currently use wxLua as interpreter to allow the
users of your programs to extend it. Lua is coinceived exactly for that
purpose and thus provide tools to do it.
Other interpreted languages like Perl or Python provide almost no API to
the C++ layers which want to embed them as they are coinceived for
writing entire applications in those languages.
Armel Asselin ha scritto:
> Hello,
>
> i'm evaluating the opportunity of using wxScript from within my app to
> allow my users to easily extend my soft.
> In order to reach maximum power through this integration I'd need two
> big features:
> - multi-threading: two absolutely unrelated scripts should be able to be
> executed in two different threads, is it the case with wxScript?
never tested. Maybe with some hacking you can do it but I have no idea
about where to start with it, sorry.
> - GUI: from the "main thread" i'd like to show dialog boxes from the
> scripts, is it possible to build a wxPython binding in my wx app and let
> wxScript wxPython object show/manipulate them?
wxScript was not intended to expose also the bindings to the wxWidgets
API to the user (the scripter); just to expose the bindings of the
program to extend. To do what you need you'll need to link against the
entire wxPython library, too and obviously find some way to make all
these things work together.
In conclusion my advice is: use wxLua :)
John is very expert in this field and wxLua is now working very well...
HTH,
Francesco
|
