Re: [clisp-list] Re: Lisp and Win32 GUIs ( wxWidgets)

[Scott W. <or...@gm...>]

You can use the C ffi if you happen to know the mangled name of the
symbol, assuming you could figure out how C++ lets a function know about
<this> (is it a hidden first argument on the stack?).

About how many classes and methods are there in wxWindows? Does it
require multithreading? I'd be interested in helping out with this
project, perhaps we could split the encapsulation (which I assume would
be the bulk of the programming).

Surendra Singhi wrote:

>André Vargas Abs da Cruz <an...@el...> writes:
>
>  
>
>>Changing the subject a bit, does anyone know if is there any work
>>going on towards writing a kind of wrapper to the wxWidgets library ?! 
>>I can think of a few good reasons to write a 'wxClisp wrapper'
>>(similar to wxPython):
>>
>>- wxWidgets is open-source;
>>- It's a cross-platform GUI;
>>- Provides a relative easy way to write a graphical application
>>
>>    
>>
>It seems wxWidgets doesn't have any C API library, and most of the features are
>provided by means of a C++ class library.  So, until clisp provides ffi support
>for C++, writing ffi wrappers is ruled out. 
>
>I think the way to incorporate wxWidgets would be by means of modules. 
>
>--But, how hard is it? 
>--Does it requires knowledge of substantial clisp internals? Will it be easy
>to look at the other existing modules, and follow them as an example to
>provide wxWidgets as a module?
>--Approximately how long will it take?
>
>Currently, I am pondering on these questions, any suggestions are welcome.
>
>
>  
>