Re: [wxhaskell-users] General questions

[Daniel C. <dan...@th...>]

Jeremy O'Donoghue wrote:
> Depending on how you build wxWidgets / wxHaskell, you can have just a
> single DLL to distribute along with your application (the default
> build creates about 10 DLLs and uses dynamically linked C library, but
> Microsoft has recently invented a whole new version of 'DLL hell' with
> the use of Manifest library descriptions. I find it much simpler (i.e.
> more or less guaranteed to work on any client machine) to build a
> single DLL containing wxWidgets, C runtime and the wxC bindings (to
> which wxHaskell talks via FFI).

Btw, can you compile and deploy a wxHaskell program using only FOSS? For 
example, can you use mingw an still get the one DLL? Is it hard to get 
the one DLL?

> Depends on how critical your users are. Qt and wx are probably fine
> for all but the most demanding UI zealots. I think Qt has its own
> (non-native) implementations of a few widgets on Mac, but they are
> probably avoidable if you really must look native.

In all honesty, I'm not willing to put the effort in being 100% native, 
and I don't think my users would care either.

Oh, I just thought of a new question: WebKit. I know that there is a 
project to port WebKit to wxWidgets. Can wxHaskell use wxWebKit? That 
would be uber-cool? (I don't know if I can use it for anything, but I 
can say it would be cool).

Daniel.