[wxhaskell-devel] Source code?

2011-03-09 Thread maciek . makowski
Where is the official source code repository for wxHaskell? The details in http://www.haskell.org/haskellwiki/WxHaskell/Development are incorrect. Thanks, Maciek -- Colocation vs. Managed Hosting A question and answer gui

Re: [wxhaskell-devel] [wxhaskell-users] Haskell Platform roadmap?

2011-06-16 Thread Maciek Makowski
Getting wxHaskell into HP would be great and I'd be happy to commit a couple of hours each week for a year to help make it happen. That said, I'm relatively new to Haskell and have very little experience with linking with native libraries (my day job is Java programming) so I might need quite a lot

[wxhaskell-devel] Building wxcore on Windows: problem with wx-config

2011-06-19 Thread maciek . makowski
wx-config-win (from https://sites.google.com/site/wxconfig/) does not support --version flag used by latest wxcore/Setup.hs. How should I go about building on Windows? Regards, Maciek -- EditLive Enterprise is the world's

Re: [wxhaskell-devel] Building wxcore on Windows: problem with wx-config

2011-06-19 Thread Maciek Makowski
This is darcs tip, hackage version built fine for me a couple of weeks ago. Do we want the ability to build given version of wxHaskell against different versions of wxWidgets? If so, wouldn't patching wx-config-win be the simplest solution? Maciek On 20 Jun 2011 00:28, "Jeremy O'Donoghue" wrote

[wxhaskell-devel] Conflicting exports in wxcore

2011-07-17 Thread maciek . makowski
I get the following during "cabal install" in wxcore (darcs tip): -- src\haskell\Graphics\UI\WXCore.hs:25:11: Conflicting exports for `wxEVT_FIRST': `module Graphics.UI.WXCore.WxcClasses' exports `Graphics.UI.WXCore.WxcClasses.wxEVT_FIRST' imported fro

Re: [wxhaskell-devel] Conflicting exports in wxcore

2011-07-29 Thread maciek . makowski
Thanks, that sorted this one out. In summary, to build darcs tip on Windows against wxWidgets 2.8 I needed: 1. a patch that removes wx-config --version call and hard-codes 2.8 libraries (attached) 2. Dave's patch from the previous e-mail in this thread 1. is obviously not ideal given that the go

Re: [wxhaskell-devel] [wxhaskell-users] Haskell Platform roadmap?

2011-08-07 Thread maciek . makowski
I set up a BuildBot instance for wxHaskell darcs tip: http://build.bimbr.com/wxhaskell/waterfall. At the moment it is configured to run nightly, at 1 AM CET (numerous builds at other times are a result of me testing the setup). The only slave I configured so far is Windows with wxWidgets 2.8, but i

[wxhaskell-devel] Fix for Windows build

2011-08-12 Thread maciek . makowski
Attached is my attempt to fix the Windows build. It should not have any impact on the builds on other platforms. The patch contains: - Dave's fix to conflicting wxEVT definitions - Eric's wx-config replacement - my changes to WxConfig and wxcore Setup.hs Any chance this can be applied to the offi

[wxhaskell-devel] Fix for 3019730

2011-08-13 Thread maciek . makowski
Attached is a patch for the colorDialog return value bug: https://sourceforge.net/tracker/?func=detail&aid=3019730&group_id=73133&atid=536845. Can someone please review it and, if there are no issues with it, apply? Thanks, Maciek fix_for_3019730 Description: Binary data ---

Re: [wxhaskell-devel] liberal commit access?

2011-11-28 Thread Maciek Makowski
I don't have a strong opinion on which version of wx should be supported by wxHaskell, as long as there is at least one that works on Windows without the need to compile wxWidgets from source. Until there is a wxPack available for 2.9 I fear that the majority of Windows users will be stuck with wxH

Re: [wxhaskell-devel] liberal commit access?

2011-11-28 Thread maciek . makowski
with 2.8. > Well, you can always bundle the wx libraries with your application in that > case and create your own wxPack. :-) > > - Alessandro > On 28 nov. 2011, at 19:09, Maciek Makowski wrote: > >> I don't have a strong opinion on which version of wx should be >>

[wxhaskell-devel] UI updates from non-UI threads: an addition to wx?

2012-08-24 Thread maciek . makowski
Getting wxHaskell to handle UI updates from non-UI threads was a frustrating experience; it's embarassing how long it took me to realise that the solution presented in this StackOverflow answer: http://stackoverflow.com/a/3182588/424978 is probably the only viable one. I've packaged it into a tiny