Jeremy O'Donoghue | 5 Jan 18:44 2012
Picon

ANN: wxHaskell 0.13.2

Hi Lists,
 
I am please to announce that wxHaskell 0.13.2 has just been uploaded to Hackage.
 
This is mainly a bugfix release, although it brings a few useful changes:
  • Changes to support build under Haskell Platform 2011.4.0.0
  • OpenGL support if your wxWidgets build is configured with it (reinstated functionality)
  • StyledTextControl support if your wxWidgets build is configured with it (reinstated functionality)
This is intended to be the final wxHaskell release supporting wxWidgets 2.8.x.
 
Provided that you have a suitable Unicode wxWidgets 2.8 install configured on your machine, you should be able to install with. cabal install wx
 
In the near future, we will be committing an updated wxHaskell release supporting wxWidgets 2.9, but this implies a number of breaking API changes, and the size of team supporting wxHaskell is not large enough to cover both. As such, this release is recommended to those who will not be able to move to wxWidgets 2.9 and later.
 
The next release has more significant improvements planned, including wrapping several additional wxWIdgets libraries and restoring correct operation in GHCi. We do not have a formal timeline as yet, but the code is working in test repositories, and mainly needs work to make it cross-platform clean.
 
This release has been tested on the following platforms:
  • Windows 7 / Haskell Platform 2011.4.0.0 / wxPack 2.8.12 (Unicode, Release)
    • OpenGL is not enabled on the test platform, so OpenGL samples do not work.
    • StyledTextControl is not enabled on the test platform, so STC samples do not work.
    • All other sample code compiles, links and runs, but has only been tested for Unicode wxWidgets builds.
  • Ubuntu 10.0.4 LTS (32 bit) / GHC 6.12 / wxWidgets 2.8.10
    • Repo packages: wx2.8-headers, libwxgtk2.8-0, libwxgtk2.8-dev, libglitz1, libglitz-gl1, libgl1-mesa-dri, libglu1-mesa, libglu1-mesa-dev, mesa-common-dev, libgl1-mesa-dev, libgl1-mesa-glx, ghc6
    • Cabal packages: strict, stm, OpenGL, cabal-install
    • OpenGL is enabled on the test platform, and the samples compile and run.
    • StyledTextControl is not enabled on the test platform, so STC samples do not work.
    • All other sample code compiles, links and runs, but has only been tested for Unicode wxWidgets.
I do not have access to an OS X platform for test, so would appreciate feedback on any issues found by OS X users. There are known to be issues on 64 bit OS X builds, which will be addressed in the next release.
 
The source repository at code.haskell.org has not yet been updated with the patches. This will happen in the next day or so.
 
Best regards
Jeremy
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
Peter Simons | 7 Jan 22:39 2012
Picon

Re: ANN: wxHaskell 0.13.2

Hi guys,

 > I am please to announce that wxHaskell 0.13.2 has just been uploaded
 > to Hackage.

when I try to build the latest version on Linux/x86_64 running NixOS, I
get the following error at configure time:

    Setup: Missing dependency on a foreign library:
    * Missing C library: wx_gtk2u_media-2.8

I searched my hard disk for that library, and apparently my installed
copy of wxGTK-2.8.12 doesn't have it. There are plenty of libwx_gtk2u_*
libraries, but none of them is called "media".

Does anyone know how wxGtk must be built in order to make sure that
library exists? Is there some special configure flag, maybe?

Take care,
Peter
Henning Thielemann | 8 Jan 12:39 2012
Picon

Re: ANN: wxHaskell 0.13.2


On Sat, 7 Jan 2012, Peter Simons wrote:

> Hi guys,
>
> > I am please to announce that wxHaskell 0.13.2 has just been uploaded
> > to Hackage.
>
> when I try to build the latest version on Linux/x86_64 running NixOS, I
> get the following error at configure time:
>
>    Setup: Missing dependency on a foreign library:
>    * Missing C library: wx_gtk2u_media-2.8
>
> I searched my hard disk for that library, and apparently my installed
> copy of wxGTK-2.8.12 doesn't have it. There are plenty of libwx_gtk2u_*
> libraries, but none of them is called "media".

Is it the only missing header? Once when I tried to install wxhaskell I 
got a lot of missing header errors although all dev packages were 
installed. They went away when I installed 'g++'. It was a plain Haskell 
development machine before :-)

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
Jeremy O'Donoghue | 9 Jan 10:52 2012
Picon

Re: ANN: wxHaskell 0.13.2

Hi Peter,

On 8 January 2012 11:39, Henning Thielemann <lemming-ITu1Rrsodqc+tg1Y5gVVPFBS56g+DFv5@public.gmane.org> wrote:

On Sat, 7 Jan 2012, Peter Simons wrote:

> Hi guys,
>
> > I am please to announce that wxHaskell 0.13.2 has just been uploaded
> > to Hackage.
>
> when I try to build the latest version on Linux/x86_64 running NixOS, I
> get the following error at configure time:
>
>    Setup: Missing dependency on a foreign library:
>    * Missing C library: wx_gtk2u_media-2.8
>
> I searched my hard disk for that library, and apparently my installed
> copy of wxGTK-2.8.12 doesn't have it. There are plenty of libwx_gtk2u_*
> libraries, but none of them is called "media".

Is it the only missing header? Once when I tried to install wxhaskell I
got a lot of missing header errors although all dev packages were
installed. They went away when I installed 'g++'. It was a plain Haskell
development machine before :-
 
I'm not so familiar with NixOS - I did my testing on an Ubuntu 10.4 VMWare image. However, I have built wxWidgets more often than I care to think about.
 
To solve the particular issue you have, you need '--enable-mediactrl' in your configure script for wxWidgets.
 
I think you probably want something like the following if you want all of the wxHaskell features:
 
./configure --enable-unicode --enable-html --enable-xrc --enable-aui --enable-stc --enable-mediactrl --enable-richtext --with-gtk=2 --with-opengl
 
Hope this helps.
 
Best regards
Jeremy
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
Peter Simons | 13 Jan 18:33 2012
Picon

Re: ANN: wxHaskell 0.13.2

Hi Jeremy,

 > To solve the particular issue you have, you need '--enable-mediactrl'
 > in your configure script for wxWidgets.

you were right, that did the trick. I also had to add 'gstreamer' as a
build input. Without that package the build wxGTK failed to produce the
media sublibrary -- but it failed silently and kept on building
regardless. Duh!

Anyway, NixOS now has the latest version of wxHaskell. Thank you for
your efforts.

I noticed, by the way, that wxHaskell doesn't compile with GHC 7.2.2:

 | Building wx-0.13.2...
 | Preprocessing library wx-0.13.2...
 | [ 1 of 16] Compiling Graphics.UI.WX.Types ( src/Graphics/UI/WX/Types.hs,
dist/build/Graphics/UI/WX/Types.o )
 | [ 2 of 16] Compiling Graphics.UI.WX.Attributes ( src/Graphics/UI/WX/Attributes.hs,
dist/build/Graphics/UI/WX/Attributes.o )
 | [ 3 of 16] Compiling Graphics.UI.WX.Layout ( src/Graphics/UI/WX/Layout.hs,
dist/build/Graphics/UI/WX/Layout.o )
 | [ 4 of 16] Compiling Graphics.UI.WX.Classes ( src/Graphics/UI/WX/Classes.hs,
dist/build/Graphics/UI/WX/Classes.o )
 | [ 5 of 16] Compiling Graphics.UI.WX.Media ( src/Graphics/UI/WX/Media.hs,
dist/build/Graphics/UI/WX/Media.o )
 |
 | src/Graphics/UI/WX/Media.hs:48:10:
 |     Illegal instance declaration for `Sized (Bitmap a)'
 |       (All instance types must be of the form (T a1 ... an)
 |        where a1 ... an are *distinct type variables*,
 |        and each type variable appears at most once in the instance head.
 |        Use -XFlexibleInstances if you want to disable this.)
 |     In the instance declaration for `Sized (Bitmap a)'
 |
 | src/Graphics/UI/WX/Media.hs:69:10:
 |     Illegal instance declaration for `Sized (Image a)'
 |       (All instance types must be of the form (T a1 ... an)
 |        where a1 ... an are *distinct type variables*,
 |        and each type variable appears at most once in the instance head.
 |        Use -XFlexibleInstances if you want to disable this.)
 |     In the instance declaration for `Sized (Image a)'
 |
 | src/Graphics/UI/WX/Media.hs:93:10:
 |     Illegal instance declaration for `Media (Sound a)'
 |       (All instance types must be of the form (T a1 ... an)
 |        where a1 ... an are *distinct type variables*,
 |        and each type variable appears at most once in the instance head.
 |        Use -XFlexibleInstances if you want to disable this.)
 |     In the instance declaration for `Media (Sound a)'
 | builder for `/nix/store/r486ymv1ci2zdlfh282a7x4fk4cnffb7-haskell-wx-ghc7.2.2-0.13.2.drv'
failed with exit code 1

Take care,
Peter

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
Dave Tapley | 16 Jan 17:21 2012
Picon

Re: ANN: wxHaskell 0.13.2

On 13 January 2012 17:33, Peter Simons <simons@...> wrote:
> Hi Jeremy,
>
>  > To solve the particular issue you have, you need '--enable-mediactrl'
>  > in your configure script for wxWidgets.
>
> you were right, that did the trick. I also had to add 'gstreamer' as a
> build input. Without that package the build wxGTK failed to produce the
> media sublibrary -- but it failed silently and kept on building
> regardless. Duh!
>
> Anyway, NixOS now has the latest version of wxHaskell. Thank you for
> your efforts.
>
> I noticed, by the way, that wxHaskell doesn't compile with GHC 7.2.2:
>
>  | Building wx-0.13.2...
>  | Preprocessing library wx-0.13.2...
>  | [ 1 of 16] Compiling Graphics.UI.WX.Types ( src/Graphics/UI/WX/Types.hs,
dist/build/Graphics/UI/WX/Types.o )
>  | [ 2 of 16] Compiling Graphics.UI.WX.Attributes ( src/Graphics/UI/WX/Attributes.hs,
dist/build/Graphics/UI/WX/Attributes.o )
>  | [ 3 of 16] Compiling Graphics.UI.WX.Layout ( src/Graphics/UI/WX/Layout.hs,
dist/build/Graphics/UI/WX/Layout.o )
>  | [ 4 of 16] Compiling Graphics.UI.WX.Classes ( src/Graphics/UI/WX/Classes.hs,
dist/build/Graphics/UI/WX/Classes.o )
>  | [ 5 of 16] Compiling Graphics.UI.WX.Media ( src/Graphics/UI/WX/Media.hs,
dist/build/Graphics/UI/WX/Media.o )
>  |
>  | src/Graphics/UI/WX/Media.hs:48:10:
>  |     Illegal instance declaration for `Sized (Bitmap a)'
>  |       (All instance types must be of the form (T a1 ... an)
>  |        where a1 ... an are *distinct type variables*,
>  |        and each type variable appears at most once in the instance head.
>  |        Use -XFlexibleInstances if you want to disable this.)
>  |     In the instance declaration for `Sized (Bitmap a)'
>  |
>  | src/Graphics/UI/WX/Media.hs:69:10:
>  |     Illegal instance declaration for `Sized (Image a)'
>  |       (All instance types must be of the form (T a1 ... an)
>  |        where a1 ... an are *distinct type variables*,
>  |        and each type variable appears at most once in the instance head.
>  |        Use -XFlexibleInstances if you want to disable this.)
>  |     In the instance declaration for `Sized (Image a)'
>  |
>  | src/Graphics/UI/WX/Media.hs:93:10:
>  |     Illegal instance declaration for `Media (Sound a)'
>  |       (All instance types must be of the form (T a1 ... an)
>  |        where a1 ... an are *distinct type variables*,
>  |        and each type variable appears at most once in the instance head.
>  |        Use -XFlexibleInstances if you want to disable this.)
>  |     In the instance declaration for `Media (Sound a)'
>  | builder for `/nix/store/r486ymv1ci2zdlfh282a7x4fk4cnffb7-haskell-wx-ghc7.2.2-0.13.2.drv'
failed with exit code 1

Could this be as simple as using FlexibleInstances?
Perhaps someone else has a better grasp of the implications of
FlexibleInstances?

>
> Take care,
> Peter
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Mar 27 - Feb 2
> Save $400 by Jan. 27
> Register now!
> http://p.sf.net/sfu/rsa-sfdev2dev2
> _______________________________________________
> wxhaskell-users mailing list
> wxhaskell-users@...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
Jeremy O'Donoghue | 9 Jan 00:47 2012
Picon

Re: ANN: wxHaskell 0.13.2

On 5 January 2012 17:44, Jeremy O'Donoghue <jeremy.odonoghue-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
 
The source repository at code.haskell.org has not yet been updated with the patches. This will happen in the next day or so.
 
 
The source repository at code.haskell.org has now been updated with wxHaskell 0.13.2 plus the two patches (add IOExtra to wxdirect and remove old-time from wxcore) from Shelarcy.
 
I suggest a period of one more week (i.e. until 15th Jan 2012) for any further issues or fixes on the 0.13.2 series. After that, Dave, Eric and others will start to upload the changes needed to support wxWidgets 2.9.x.
 
These changes will not work against wxWidgets 2.8.x installations, and are pretty significant in places. Please expect the main repo to unstable for a while after next Sunday.
 
Best regards
Jeremy
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
shelarcy | 6 Jan 16:13 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

Hello,

This version has two installing problem.

1. wxdirect's sdist dropped IOExtra module, so I can't install this version.
I uploaded newer version for fixing this problem, and attached a patch
for fixing same problem in Dave's wxhaskell-dev branch.

2. It seems that wxcore depends on Eric's wx-config implicitly at least
Windows environment. "cabal install" fail with wx-config-win binary,
and "cabal install" success with Eric's one. If wxcore depends on
wx-config package in only Windows environment, I think we should upload
Eric's wx-config package, and modify wxcore to denped on wx-config package
on  Windows environment for workaround.

if os(windows)
    Build-Depends: wx-config

wx-config package isn't uploaded yet. So, I don't upload newer version,
nor attach patch for fixing this problem.

Best Regards,

On Fri, 06 Jan 2012 02:44:24 +0900, Jeremy O'Donoghue
<jeremy.odonoghue@...> wrote:
> Hi Lists,
>
> I am please to announce that wxHaskell 0.13.2 has just been uploaded to
> Hackage.
>
> This is mainly a bugfix release, although it brings a few useful changes:
>
>    - Changes to support build under Haskell Platform 2011.4.0.0
>    - OpenGL support if your wxWidgets build is configured with it
>    (reinstated functionality)
>    - StyledTextControl support if your wxWidgets build is configured with
>    it (reinstated functionality)
>
> This is intended to be the final wxHaskell release supporting wxWidgets
> 2.8.x.
>
> Provided that you have a suitable Unicode wxWidgets 2.8 install configured
> on your machine, you should be able to install with. cabal install wx
>
> In the near future, we will be committing an updated wxHaskell release
> supporting wxWidgets 2.9, but this implies a number of breaking API
> changes, and the size of team supporting wxHaskell is not large enough to
> cover both. As such, this release is recommended to those who will not be
> able to move to wxWidgets 2.9 and later.
>
> The next release has more significant improvements planned, including
> wrapping several additional wxWIdgets libraries and restoring correct
> operation in GHCi. We do not have a formal timeline as yet, but the code is
> working in test repositories, and mainly needs work to make it
> cross-platform clean.
>
> This release has been tested on the following platforms:
>
>    - Windows 7 / Haskell Platform 2011.4.0.0 / wxPack 2.8.12 (Unicode,
>    Release)
>       - OpenGL is not enabled on the test platform, so OpenGL samples do
>       not work.
>       - StyledTextControl is not enabled on the test platform, so STC
>       samples do not work.
>       - All other sample code compiles, links and runs, but has only been
>       tested for Unicode wxWidgets builds.
>    - Ubuntu 10.0.4 LTS (32 bit) / GHC 6.12 / wxWidgets 2.8.10
>       - Repo packages: wx2.8-headers, libwxgtk2.8-0, libwxgtk2.8-dev,
>       libglitz1, libglitz-gl1, libgl1-mesa-dri, libglu1-mesa, libglu1-mesa-dev,
>       mesa-common-dev, libgl1-mesa-dev, libgl1-mesa-glx, ghc6
>       - Cabal packages: strict, stm, OpenGL, cabal-install
>       - OpenGL is enabled on the test platform, and the samples compile and
>       run.
>       - StyledTextControl is not enabled on the test platform, so STC
>       samples do not work.
>       - All other sample code compiles, links and runs, but has only been
>       tested for Unicode wxWidgets.
>
> I do not have access to an OS X platform for test, so would appreciate
> feedback on any issues found by OS X users. There are known to be issues on
> 64 bit OS X builds, which will be addressed in the next release.
>
> The source repository at code.haskell.org has not yet been updated with the
> patches. This will happen in the next day or so.

--

-- 
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/
Attachment (missing.dpatch): application/octet-stream, 26 KiB
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
Dave Tapley | 6 Jan 17:02 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

2012/1/6 shelarcy <shelarcy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hello,

This version has two installing problem.

1. wxdirect's sdist dropped IOExtra module, so I can't install this version.
I uploaded newer version for fixing this problem, and attached a patch
for fixing same problem in Dave's wxhaskell-dev branch.

Good catch, thanks, I've pushed to the -dev branch.
 

2. It seems that wxcore depends on Eric's wx-config implicitly at least
Windows environment. "cabal install" fail with wx-config-win binary,

Can you remember how this failed, or send some output from the failure, and also let us know what version of wxWidgets you have?
I'm hoping you say you have wx-2.9.x, in which case it could be this issue:
http://code.google.com/p/wx-config-win/issues/detail?id=21

and "cabal install" success with Eric's one. If wxcore depends on
wx-config package in only Windows environment, I think we should upload
Eric's wx-config package, and modify wxcore to denped on wx-config package
on  Windows environment for workaround.

if os(windows)
  Build-Depends: wx-config

wx-config package isn't uploaded yet. So, I don't upload newer version,
nor attach patch for fixing this problem.

We're still making a decision on whether to continue using wx-config(-win), or to adopt Eric's one.
I'm going to see if I can get a conversation going with the wxWidgets people and then I'll send out another mail.

Cheers,
 


Best Regards,



On Fri, 06 Jan 2012 02:44:24 +0900, Jeremy O'Donoghue <jeremy.odonoghue <at> gmail.com> wrote:
Hi Lists,

I am please to announce that wxHaskell 0.13.2 has just been uploaded to
Hackage.

This is mainly a bugfix release, although it brings a few useful changes:

  - Changes to support build under Haskell Platform 2011.4.0.0
  - OpenGL support if your wxWidgets build is configured with it
  (reinstated functionality)
  - StyledTextControl support if your wxWidgets build is configured with

  it (reinstated functionality)

This is intended to be the final wxHaskell release supporting wxWidgets
2.8.x.

Provided that you have a suitable Unicode wxWidgets 2.8 install configured
on your machine, you should be able to install with. cabal install wx

In the near future, we will be committing an updated wxHaskell release
supporting wxWidgets 2.9, but this implies a number of breaking API
changes, and the size of team supporting wxHaskell is not large enough to
cover both. As such, this release is recommended to those who will not be
able to move to wxWidgets 2.9 and later.

The next release has more significant improvements planned, including
wrapping several additional wxWIdgets libraries and restoring correct
operation in GHCi. We do not have a formal timeline as yet, but the code is
working in test repositories, and mainly needs work to make it
cross-platform clean.

This release has been tested on the following platforms:

  - Windows 7 / Haskell Platform 2011.4.0.0 / wxPack 2.8.12 (Unicode,
  Release)
     - OpenGL is not enabled on the test platform, so OpenGL samples do
     not work.
     - StyledTextControl is not enabled on the test platform, so STC
     samples do not work.
     - All other sample code compiles, links and runs, but has only been

     tested for Unicode wxWidgets builds.
  - Ubuntu 10.0.4 LTS (32 bit) / GHC 6.12 / wxWidgets 2.8.10
     - Repo packages: wx2.8-headers, libwxgtk2.8-0, libwxgtk2.8-dev,

     libglitz1, libglitz-gl1, libgl1-mesa-dri, libglu1-mesa, libglu1-mesa-dev,
     mesa-common-dev, libgl1-mesa-dev, libgl1-mesa-glx, ghc6
     - Cabal packages: strict, stm, OpenGL, cabal-install
     - OpenGL is enabled on the test platform, and the samples compile and
     run.
     - StyledTextControl is not enabled on the test platform, so STC
     samples do not work.
     - All other sample code compiles, links and runs, but has only been

     tested for Unicode wxWidgets.

I do not have access to an OS X platform for test, so would appreciate
feedback on any issues found by OS X users. There are known to be issues on
64 bit OS X builds, which will be addressed in the next release.

The source repository at code.haskell.org has not yet been updated with the
patches. This will happen in the next day or so.

--
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
wxhaskell-devel mailing list
wxhaskell-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel


------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
Jeremy O'Donoghue | 9 Jan 18:04 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

Hi Dave, all

On 6 January 2012 16:02, Dave Tapley <dave.a.tapley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
2012/1/6 shelarcy <shelarcy <at> gmail.com>
2. It seems that wxcore depends on Eric's wx-config implicitly at least
Windows environment. "cabal install" fail with wx-config-win binary,

Can you remember how this failed, or send some output from the failure, and also let us know what version of wxWidgets you have?
I'm hoping you say you have wx-2.9.x, in which case it could be this issue:
http://code.google.com/p/wx-config-win/issues/detail?id=21

and "cabal install" success with Eric's one. If wxcore depends on
wx-config package in only Windows environment, I think we should upload
Eric's wx-config package, and modify wxcore to denped on wx-config package
on  Windows environment for workaround.

if os(windows)
  Build-Depends: wx-config

wx-config package isn't uploaded yet. So, I don't upload newer version,
nor attach patch for fixing this problem.

We're still making a decision on whether to continue using wx-config(-win), or to adopt Eric's one.
I'm going to see if I can get a conversation going with the wxWidgets people and then I'll send out another mail.
 
Now that the 0.13 branch looks like it is finished, I have pulled your development repo (so as to be up to date), and started to look at Windows support.
 
Needless to say, I have immediately hit the wx-config roadblock, since I have compiled a release build of wxWidgets 2.9.3, and wx-config-win only knows about debug builds.
 
I am leaning towards doing something with Eric's wx-config. There are a couple of reasons for this:
  • It keeps us in control of our own destiny;
  • Haskell is a *much* more pleasant implementation language for a utility which mainly does text processing than C++.

Does the group have an opinion on this? My feeling is that since the last commit to wx-config-win was in 2006, it may be a while before fixes come along, and even then, we will probably need to write the patches.

Regards
Jeremy
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
Dave Tapley | 9 Jan 19:09 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

On 9 January 2012 17:04, Jeremy O'Donoghue <jeremy.odonoghue-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
Hi Dave, all
On 6 January 2012 16:02, Dave Tapley <dave.a.tapley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
2012/1/6 shelarcy <shelarcy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2. It seems that wxcore depends on Eric's wx-config implicitly at least
Windows environment. "cabal install" fail with wx-config-win binary,

Can you remember how this failed, or send some output from the failure, and also let us know what version of wxWidgets you have?
I'm hoping you say you have wx-2.9.x, in which case it could be this issue:
http://code.google.com/p/wx-config-win/issues/detail?id=21

and "cabal install" success with Eric's one. If wxcore depends on
wx-config package in only Windows environment, I think we should upload
Eric's wx-config package, and modify wxcore to denped on wx-config package
on  Windows environment for workaround.

if os(windows)
  Build-Depends: wx-config

wx-config package isn't uploaded yet. So, I don't upload newer version,
nor attach patch for fixing this problem.

We're still making a decision on whether to continue using wx-config(-win), or to adopt Eric's one.
I'm going to see if I can get a conversation going with the wxWidgets people and then I'll send out another mail.
 
Now that the 0.13 branch looks like it is finished, I have pulled your development repo (so as to be up to date), and started to look at Windows support.

Excellent, I hope it's not too much of a nightmare, I played around a little with my branch in Windows, but I'm primarily in Ubuntu.
 
 
Needless to say, I have immediately hit the wx-config roadblock, since I have compiled a release build of wxWidgets 2.9.3, and wx-config-win only knows about debug builds.

Welcome to the party :)
Just for the sake of clarity, I feel obliged to question your use of the words "release" and "debug"; are you aware of the "Debug Build Changes in wx3"?
Here's the news: http://wxwidgets.blogspot.com/2009/09/debug-build-changes-in-wx3.html
(seeing the date of the post made me realise just how far behind we are, and also how slow the wxWidgets release cycles are!)

That has manifested itself in this known issue with wx-config-win:
http://code.google.com/p/wx-config-win/issues/detail?id=21

Finally, just out of curiosity: Did you build wxWidgets with VC++ or gcc?
I dutifully downloaded the free version of Visual C++ 2010 express, loaded the wxWidgets 2.9.3 project, built, and ran some sample code. However when I tried to use wx-config-win I realised that it required a "build.cfg" file, which isn't generated when you build with VC++ (I suppose because VC++ manages all the build settings itself, and so doesn't need to export anything). Without this one is unable to install wxHaskell.

I turned to the wiki and discovered this:
http://www.scribd.com/doc/38034374/20100923-WxHaskell-Setup)

Using it as a guide (note that one can't use wxPack because there are no wxPack releases for the development (2.9.x) releases of wxWidgets) I was (almost) able to cabal install wxHaskell from my darcsden branch (it failed because I didn't --with-OpenGL the wxWidgets configure, and then I ran out of time).

 
I am leaning towards doing something with Eric's wx-config. There are a couple of reasons for this:
  • It keeps us in control of our own destiny;
  • Haskell is a *much* more pleasant implementation language for a utility which mainly does text processing than C++.

Does the group have an opinion on this? My feeling is that since the last commit to wx-config-win was in 2006, it may be a while before fixes come along, and even then, we will probably need to write the patches.

Ah, well, yes..
Firstly the pro-(wx-config-win) items:
* I contacted the owner of wx-config-win and he made me an owner of the Google code project, so we're 'in charge' now.
* I got a small discussion going on its existence in #wxwidgets on freenode. The consensus is that, because /most/ people use Visual Studio (in some flavour) to develop with wxWidgets in Windows, there simply wasn't the need to maintain wx-config-win. As a result it was never stable enough to merit merging in to the wxWidgets code base. By comparison the wx-config we know and love on Linux systems (and, I presume, OS X?) is essential and so well maintained:

http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/wx-config.in
(I didn't realise until recently that it is just a shell script, copied in to your install dir and symlinked into your PATH).

And now the cons:
* It is woefully out of date. There are 18 open issues (http://code.google.com/p/wx-config-win/issues/list) and who knows how many undiscovered bugs.
* As mentioned, the wxWidgets community doesn't seem desperately fussed about its existence, so long as Visual Studio is around
* It's implementation is in need of an overhaul, as identified by the previous owner (http://code.google.com/p/wx-config-win/issues/detail?id=6)

So, in summary, I'm not sure.
My optimist, open-source heart says we should resurrect the wx-win-config project.
My do-it-the-right-way heart says we ditch the existing C++ source and replicate the shell script (Windows PowerShell anyone?)
My everything-is-wonderful-with-Haskell heart says let's just roll our own, no one uses wx-config-win anyway, and all it does it find a few headers and libs.

 
Regards
Jeremy

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
Jeremy O'Donoghue | 9 Jan 23:19 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

On 9 January 2012 18:09, Dave Tapley <dave.a.tapley <at> gmail.com> wrote:
On 9 January 2012 17:04, Jeremy O'Donoghue <jeremy.odonoghue-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On 6 January 2012 16:02, Dave Tapley <dave.a.tapley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
 
Needless to say, I have immediately hit the wx-config roadblock, since I have compiled a release build of wxWidgets 2.9.3, and wx-config-win only knows about debug builds.

Welcome to the party :)
Just for the sake of clarity, I feel obliged to question your use of the words "release" and "debug"; are you aware of the "Debug Build Changes in wx3"?
Here's the news: http://wxwidgets.blogspot.com/2009/09/debug-build-changes-in-wx3.html
(seeing the date of the post made me realise just how far behind we are, and also how slow the wxWidgets release cycles are!)
 
I wasn't aware of the blog posting, but I did realise that there were changes in this area - some of this is covered in the install instructions. Strictly I built with:
 
BUILD=release
DEBUG_INFO=default
DEBUG_FLAG=1
 
This means I keep the asserts, which seemed like an appropriate configuration for wxHaskell development.
 

That has manifested itself in this known issue with wx-config-win:
http://code.google.com/p/wx-config-win/issues/detail?id=21

Finally, just out of curiosity: Did you build wxWidgets with VC++ or gcc?
I dutifully downloaded the free version of Visual C++ 2010 express, loaded the wxWidgets 2.9.3 project, built, and ran some sample code. However when I tried to use wx-config-win I realised that it required a "build.cfg" file, which isn't generated when you build with VC++ (I suppose because VC++ manages all the build settings itself, and so doesn't need to export anything). Without this one is unable to install wxHaskell.
 
I built with gcc. I have played with VC++ in the past, because the build 'just works' but it was really too painful to sort out the configuration.

I turned to the wiki and discovered this:
http://www.scribd.com/doc/38034374/20100923-WxHaskell-Setup)

Using it as a guide (note that one can't use wxPack because there are no wxPack releases for the development (2.9.x) releases of wxWidgets) I was (almost) able to cabal install wxHaskell from my darcsden branch (it failed because I didn't --with-OpenGL the wxWidgets configure, and then I ran out of time).

 
I am leaning towards doing something with Eric's wx-config. There are a couple of reasons for this:
  • It keeps us in control of our own destiny;
  • Haskell is a *much* more pleasant implementation language for a utility which mainly does text processing than C++.

Does the group have an opinion on this? My feeling is that since the last commit to wx-config-win was in 2006, it may be a while before fixes come along, and even then, we will probably need to write the patches.

Ah, well, yes..
Firstly the pro-(wx-config-win) items:
* I contacted the owner of wx-config-win and he made me an owner of the Google code project, so we're 'in charge' now.
* I got a small discussion going on its existence in #wxwidgets on freenode. The consensus is that, because /most/ people use Visual Studio (in some flavour) to develop with wxWidgets in Windows, there simply wasn't the need to maintain wx-config-win. As a result it was never stable enough to merit merging in to the wxWidgets code base. By comparison the wx-config we know and love on Linux systems (and, I presume, OS X?) is essential and so well maintained:

http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/wx-config.in
(I didn't realise until recently that it is just a shell script, copied in to your install dir and symlinked into your PATH).
 
I did know that wx-config is just a shell script. I'm not so surprised that most wxWidgets developers on Windows use VS. It's a really nce development environment. I actually think they advertise support for too many build options when in reality only a few of them get any serious use.
 
I was actually planning on looking carefully at wx-config while updating Eric's Haskell wx-config :-)
 

And now the cons:
* It is woefully out of date. There are 18 open issues (http://code.google.com/p/wx-config-win/issues/list) and who knows how many undiscovered bugs.
* As mentioned, the wxWidgets community doesn't seem desperately fussed about its existence, so long as Visual Studio is around
* It's implementation is in need of an overhaul, as identified by the previous owner (http://code.google.com/p/wx-config-win/issues/detail?id=6)
 
I tend to think that you've hit on the problem with this approach. The wxWidgets community doesn't really care. Therefore we would be left maintaining a piece of C++ to support what is basically our own need.

So, in summary, I'm not sure.
My optimist, open-source heart says we should resurrect the wx-win-config project.
My do-it-the-right-way heart says we ditch the existing C++ source and replicate the shell script (Windows PowerShell anyone?)
My everything-is-wonderful-with-Haskell heart says let's just roll our own, no one uses wx-config-win anyway, and all it does it find a few headers and libs.
 
 
I think a port of wx-config (shell) to Haskell is probably easier than doing a port into PowerShell (which I've never touched...), but I take your point about the 'right way'.
 
I'll nail my colours to the mast and leave things open for debate after that.
  • My day job is C++. Thus I tend to tolerate doing it for my 'fun' projects where it is needed (e.g. wrapping a C++ library), but I kind-of prefer to spend my spare time writing Haskell rather than C++ ;-)
  • While the 'community' aspect of having a wxC is superficially attractive, I think history is against the idea that it is something the world really needs:
    • wxC has been moribund for years. I don't think it's been touched for over 5 years. This suggests that there is not so much demand out there.
    • wxHaskell has struggled for contributons for as long as I remember. I basically became involved because I didn't want to see it bit-rot.
 
What I *do* believe is that there is a real demand in the Haskell community for a GUI with native look and feel, commercial-friendly licensing and ease of installation. My preference, therefore, is to move wxHaskell in that direction as far as possible, and to make the bar for becoming a developer as low as possible for Haskell developers. Basically, I want to enable the Haskell ecosystem, and that's why I'm a big fan of cabal install, despite its limitations as a generalised build system.
 
Having said my piece, I fully understand why others may have a different view, and I think if there was I strong indication that other language communities had a serious interest in using and helping to maintain wxC, I would be easily persuaded in that direction. What I don't really believe is in 'if you build it, they will come'.
 
I'll leave things for a couple of days to let others have their say, and then follow the community preference.
 
Best regards
Jeremy
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
Dave Tapley | 10 Jan 18:01 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

On 9 January 2012 22:19, Jeremy O'Donoghue <jeremy.odonoghue-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On 9 January 2012 18:09, Dave Tapley <dave.a.tapley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On 9 January 2012 17:04, Jeremy O'Donoghue <jeremy.odonoghue-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On 6 January 2012 16:02, Dave Tapley <dave.a.tapley-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
 
Needless to say, I have immediately hit the wx-config roadblock, since I have compiled a release build of wxWidgets 2.9.3, and wx-config-win only knows about debug builds.

Welcome to the party :)
Just for the sake of clarity, I feel obliged to question your use of the words "release" and "debug"; are you aware of the "Debug Build Changes in wx3"?
Here's the news: http://wxwidgets.blogspot.com/2009/09/debug-build-changes-in-wx3.html
(seeing the date of the post made me realise just how far behind we are, and also how slow the wxWidgets release cycles are!)
 
I wasn't aware of the blog posting, but I did realise that there were changes in this area - some of this is covered in the install instructions. Strictly I built with:
 
BUILD=release
DEBUG_INFO=default
DEBUG_FLAG=1

Yikes, these flags are very (imho) counter-intuitive.

Referencing a thread I have going: https://groups.google.com/d/msg/wx-dev/4PuKS-xQX3k/JYd4ydh6v-IJ
Vadim states that: "DEBUG_FLAG is correctly set to 1 indicating that debug code is not disabled (which is the default)".
So I'm substituting  "not disable" with "enabled" and reading it as: a release build with debugging enabled, or as you put it:

This means I keep the asserts, which seemed like an appropriate configuration for wxHaskell development.

What I'm not sure about here is whether the "BUILD" flag is superfluous under any GCC build, or just non-Windows GCC builds. A question which I'm asking about here: https://groups.google.com/d/msg/wx-dev/4PuKS-xQX3k/nfUuz_cg-HUJ

If the answer to my question there is "under Windows using MSVC", and if we accept that wxHaskell isn't going to support an MSVC build of wxWidgets (which I get the impression is the case); then I suppose that wxC can be completely agnostic to all the (non-libs) wxWidgets build type information (namely: release/debug, debugging flag on/off).

Thoughts?

 

That has manifested itself in this known issue with wx-config-win:
http://code.google.com/p/wx-config-win/issues/detail?id=21

Finally, just out of curiosity: Did you build wxWidgets with VC++ or gcc?
I dutifully downloaded the free version of Visual C++ 2010 express, loaded the wxWidgets 2.9.3 project, built, and ran some sample code. However when I tried to use wx-config-win I realised that it required a "build.cfg" file, which isn't generated when you build with VC++ (I suppose because VC++ manages all the build settings itself, and so doesn't need to export anything). Without this one is unable to install wxHaskell.
 
I built with gcc. I have played with VC++ in the past, because the build 'just works' but it was really too painful to sort out the configuration.

Hazaa, I'm going to say it again:
*wxHaskell doesn't support an MSVC build of wxWidgets*

Is that the sort of message we can put out?
 

I turned to the wiki and discovered this:
http://www.scribd.com/doc/38034374/20100923-WxHaskell-Setup)

Using it as a guide (note that one can't use wxPack because there are no wxPack releases for the development (2.9.x) releases of wxWidgets) I was (almost) able to cabal install wxHaskell from my darcsden branch (it failed because I didn't --with-OpenGL the wxWidgets configure, and then I ran out of time).

 
I am leaning towards doing something with Eric's wx-config. There are a couple of reasons for this:
  • It keeps us in control of our own destiny;
  • Haskell is a *much* more pleasant implementation language for a utility which mainly does text processing than C++.

Does the group have an opinion on this? My feeling is that since the last commit to wx-config-win was in 2006, it may be a while before fixes come along, and even then, we will probably need to write the patches.

Ah, well, yes..
Firstly the pro-(wx-config-win) items:
* I contacted the owner of wx-config-win and he made me an owner of the Google code project, so we're 'in charge' now.
* I got a small discussion going on its existence in #wxwidgets on freenode. The consensus is that, because /most/ people use Visual Studio (in some flavour) to develop with wxWidgets in Windows, there simply wasn't the need to maintain wx-config-win. As a result it was never stable enough to merit merging in to the wxWidgets code base. By comparison the wx-config we know and love on Linux systems (and, I presume, OS X?) is essential and so well maintained:

http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/wx-config.in
(I didn't realise until recently that it is just a shell script, copied in to your install dir and symlinked into your PATH).
 
I did know that wx-config is just a shell script. I'm not so surprised that most wxWidgets developers on Windows use VS. It's a really nce development environment. I actually think they advertise support for too many build options when in reality only a few of them get any serious use.
 
I was actually planning on looking carefully at wx-config while updating Eric's Haskell wx-config :-)

I did actually miss another 'pro' here:
I think it's fair to say that wx-config-win is more 'complete' than Eric's Haskell implementation, insomuch as all that's required to fix the "wx-config roadblock" is (I think) changing this line as per Vadim's suggestion :
http://code.google.com/p/wx-config-win/source/browse/trunk/wx-config-win.cpp#952
 
 

And now the cons:
* It is woefully out of date. There are 18 open issues (http://code.google.com/p/wx-config-win/issues/list) and who knows how many undiscovered bugs.
* As mentioned, the wxWidgets community doesn't seem desperately fussed about its existence, so long as Visual Studio is around
* It's implementation is in need of an overhaul, as identified by the previous owner (http://code.google.com/p/wx-config-win/issues/detail?id=6)
 
I tend to think that you've hit on the problem with this approach. The wxWidgets community doesn't really care. Therefore we would be left maintaining a piece of C++ to support what is basically our own need.

So, in summary, I'm not sure.
My optimist, open-source heart says we should resurrect the wx-win-config project.
My do-it-the-right-way heart says we ditch the existing C++ source and replicate the shell script (Windows PowerShell anyone?)
My everything-is-wonderful-with-Haskell heart says let's just roll our own, no one uses wx-config-win anyway, and all it does it find a few headers and libs.
 
 
I think a port of wx-config (shell) to Haskell is probably easier than doing a port into PowerShell (which I've never touched...), but I take your point about the 'right way'.
 
I'll nail my colours to the mast and leave things open for debate after that.
  • My day job is C++. Thus I tend to tolerate doing it for my 'fun' projects where it is needed (e.g. wrapping a C++ library), but I kind-of prefer to spend my spare time writing Haskell rather than C++ ;-)
  • While the 'community' aspect of having a wxC is superficially attractive, I think history is against the idea that it is something the world really needs:
    • wxC has been moribund for years. I don't think it's been touched for over 5 years. This suggests that there is not so much demand out there.
    • wxHaskell has struggled for contributons for as long as I remember. I basically became involved because I didn't want to see it bit-rot.
 
What I *do* believe is that there is a real demand in the Haskell community for a GUI with native look and feel, commercial-friendly licensing and ease of installation. My preference, therefore, is to move wxHaskell in that direction as far as possible, and to make the bar for becoming a developer as low as possible for Haskell developers. Basically, I want to enable the Haskell ecosystem, and that's why I'm a big fan of cabal install, despite its limitations as a generalised build system.
 
Having said my piece, I fully understand why others may have a different view, and I think if there was I strong indication that other language communities had a serious interest in using and helping to maintain wxC, I would be easily persuaded in that direction. What I don't really believe is in 'if you build it, they will come'.
 
I'll leave things for a couple of days to let others have their say, and then follow the community preference.

I don't know either, needs more input I think :(
 
 
Best regards
Jeremy

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
shelarcy | 6 Jan 17:54 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

On Sat, 07 Jan 2012 01:02:44 +0900, Dave Tapley
<dave.a.tapley@...> wrote:
>
>> This version has two installing problem.
>>
>> 2. It seems that wxcore depends on Eric's wx-config implicitly at least
>> Windows environment. "cabal install" fail with wx-config-win binary,
>>
>
> Can you remember how this failed, or send some output from the failure, and
> also let us know what version of wxWidgets you have?
> I'm hoping you say you have wx-2.9.x, in which case it could be this issue:
> http://code.google.com/p/wx-config-win/issues/detail?id=21

I used wxWidgets 2.8.12 (wxPack v2.8.12.01) to install wxcore. I can install
previous version with wx-config(-win).

C:\home\working> cabal install wx-0.12.1.6 wxcore-0.12.1.7
(snip)
Registering wxcore-0.12.1.7...
Installing library in
C:\Users\shelarcy\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.0.4
Registering wxcore-0.12.1.7...
Configuring wx-0.12.1.6...
Preprocessing library wx-0.12.1.6...
Building wx-0.12.1.6...
(snip)
Registering wx-0.12.1.6...
Installing library in
C:\Users\shelarcy\AppData\Roaming\cabal\wx-0.12.1.6\ghc-7.0.4
Registering wx-0.12.1.6...

But ... I can't install current version with wx-config(-win).

Here's the output.

C:\home\working>wx-config -v
wx-config revision 21 2006-10-19

C:\home\working>cabal install wxcore
Resolving dependencies...
[1 of 1] Compiling Main             ( C:\Users\shelarcy\AppData\Local\Temp\wxcor
e-0.13.27884\wxcore-0.13.2\Setup.hs, C:\Users\shelarcy\AppData\Local\Temp\wxcore
-0.13.27884\wxcore-0.13.2\dist\setup\Main.o )
Linking C:\Users\shelarcy\AppData\Local\Temp\wxcore-0.13.27884\wxcore-0.13.2\dis
t\setup\setup.exe ...
generating: src/haskell/Graphics/UI/WXCore/WxcClassTypes.hs
reading class definitions:
parsing: src/include/wxc.h
parsing: src/include/wxc_types.h
parsing: src/include/wxc_glue.h
parsing: src/include/dragimage.h
parsing: src/include/graphicscontext.h
parsing: src/include/glcanvas.h
parsing: src/include/sound.h
parsing: src/include/managed.h
parsing: src/include/mediactrl.h
parsing: src/include/previewframe.h
parsing: src/include/printout.h
parsing: src/include/textstream.h
parsing: src/include/stc.h
parsing: src/include/stc_gen.h
generated 535 class definitions.
ok.
generating: src/haskell/Graphics/UI/WXCore/WxcClassInfo.hs
reading class definitions:
parsing: src/include/wxc.h
parsing: src/include/wxc_types.h
parsing: src/include/wxc_glue.h
parsing: src/include/dragimage.h
parsing: src/include/graphicscontext.h
parsing: src/include/glcanvas.h
parsing: src/include/sound.h
parsing: src/include/managed.h
parsing: src/include/mediactrl.h
parsing: src/include/previewframe.h
parsing: src/include/printout.h
parsing: src/include/textstream.h
parsing: src/include/stc.h
parsing: src/include/stc_gen.h
generated 382 class info definitions
ok.
parsing: src/include/wxc.h
parsing: src/include/wxc_types.h
parsing: src/include/wxc_glue.h
parsing: src/include/dragimage.h
parsing: src/include/graphicscontext.h
parsing: src/include/glcanvas.h
parsing: src/include/sound.h
parsing: src/include/managed.h
parsing: src/include/mediactrl.h
parsing: src/include/previewframe.h
parsing: src/include/printout.h
parsing: src/include/textstream.h
parsing: src/include/stc.h
parsing: src/include/stc_gen.h
generating: src/haskell/Graphics/UI/WXCore/WxcClassesAL.hs
reading class definitions:
parsing: src/include/wxc.h
parsing: src/include/wxc_types.h
parsing: src/include/wxc_glue.h
parsing: src/include/dragimage.h
parsing: src/include/graphicscontext.h
parsing: src/include/glcanvas.h
parsing: src/include/sound.h
parsing: src/include/managed.h
parsing: src/include/mediactrl.h
parsing: src/include/previewframe.h
parsing: src/include/printout.h
parsing: src/include/textstream.h
parsing: src/include/stc.h
parsing: src/include/stc_gen.h
generated 1468 methods for 116 classes.
generating: src/haskell/Graphics/UI/WXCore/WxcClassesMZ.hs
generated 2320 methods for 123 classes.
generating: src/haskell/Graphics/UI/WXCore/WxcClasses.hs
generated 3788 total methods for 239 total classes.
ok.
parsing: src/eiffel/wxc_defs.e
parsing: src/eiffel/wx_defs.e
parsing: src/eiffel/stc.e
generating: src/haskell/Graphics/UI/WXCore/WxcDefs.hs
generated 2454 constant definitions
ok.
Usage: wx-config [options]
Options:
   --prefix[=DIR]              Path of the wxWidgets installation (ie. C:\wxWidge
ts2.6.3)
   --wxcfg[=DIR]               Relative path of the build.cfg file (ie. gcc_dll\m
swud)
   --cflags                    Outputs all pre-processor and compiler flags.
   --cxxflags                  Same as --cflags but for C++.
   --rcflags                   Outputs all resource compiler flags. [UNTESTED]
   --libs                      Outputs all linker flags.

   --debug[=yes|no]            Uses a debug configuration if found.
   --unicode[=yes|no]          Uses an unicode configuration if found.
   --static[=yes|no]           Uses a static configuration if found.
   --universal[=yes|no]        Uses an universal configuration if found.
   --easymode[=yes|no]         Outputs warnings, and optimize flags.
   --compiler[=gcc,dmc,vc]     Selects the compiler.
   --release                   Outputs the wxWidgets release number.
   --cc                        Outputs the name of the C compiler.
   --cxx                       Outputs the name of the C++ compiler.
   --ld                        Outputs the linker command.
   -v                          Outputs the revision of wx-config.

   Note that using --prefix is not needed if you have defined the
   environmental variable WXWIN.

   Also note that using --wxcfg is not needed if you have defined the
   environmental variable WXCFG.

setup.exe: failed
cabal: Error: some packages failed to install:
wxcore-0.13.2 failed during the configure step. The exception was:
ExitFailure 1

Best Regards,

>  and "cabal install" success with Eric's one. If wxcore depends on
>> wx-config package in only Windows environment, I think we should upload
>> Eric's wx-config package, and modify wxcore to denped on wx-config package
>> on  Windows environment for workaround.
>>
>> if os(windows)
>>   Build-Depends: wx-config
>>
>> wx-config package isn't uploaded yet. So, I don't upload newer version,
>> nor attach patch for fixing this problem.
>>
>
> We're still making a decision on whether to continue using wx-config(-win),
> or to adopt Eric's one.
> I'm going to see if I can get a conversation going with the wxWidgets
> people and then I'll send out another mail.

--

-- 
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
Jeremy O'Donoghue | 8 Jan 23:54 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

Hi Shelarcy,
 
It's great to see you back...
2012/1/6 shelarcy <shelarcy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
This version has two installing problem.

1. wxdirect's sdist dropped IOExtra module, so I can't install this version.
I uploaded newer version for fixing this problem, and attached a patch
for fixing same problem in Dave's wxhaskell-dev branch.
 
I have just applied this to my local repo, and it will be uploaded tonight. Thanks.
 

2. It seems that wxcore depends on Eric's wx-config implicitly at least
Windows environment. "cabal install" fail with wx-config-win binary,
and "cabal install" success with Eric's one. If wxcore depends on
wx-config package in only Windows environment, I think we should upload
Eric's wx-config package, and modify wxcore to denped on wx-config package
on  Windows environment for workaround.

if os(windows)
  Build-Depends: wx-config
 
This is surprising. I am using wx-config-win on my Windows environment (when I run wx-config -v, I get "wx-config revision 26 2006-12-21"). I deliberately did not choose to use Eric's version as he had noted some issues with it.
 
We should investigate your problem further (I am also using wPack 2.8.12)
 
Best regards
Jeremy
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
shelarcy | 9 Jan 17:32 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

Hi Jeremy,

I found where causes installation problem. My wx-config-win can't recognise
--version option.

$ wx-config --version
wx-config Error: Unrecognised option: '--version'

Usage: wx-config [options]
Options:
(snip)
   -v                          Outputs the revision of wx-config.

   Note that using --prefix is not needed if you have defined the
   environmental variable WXWIN.

   Also note that using --wxcfg is not needed if you have defined the
   environmental variable WXCFG.

So, wxcore/Setup.hs' below line causes problem.

>    ver <- fmap (head . drop 1 . splitBy (== '.')) (readProcess "wx-config" ["--version"] "")

I can install wxcore with wx-config-win when commenting out that line, or
using -v option instead of --version option .

Best Regards,

On Mon, 09 Jan 2012 07:54:28 +0900, Jeremy O'Donoghue
<jeremy.odonoghue@...> wrote:
>> 2. It seems that wxcore depends on Eric's wx-config implicitly at least
>> Windows environment. "cabal install" fail with wx-config-win binary,
>> and "cabal install" success with Eric's one. If wxcore depends on
>> wx-config package in only Windows environment, I think we should upload
>> Eric's wx-config package, and modify wxcore to denped on wx-config package
>> on  Windows environment for workaround.
>>
>> if os(windows)
>>   Build-Depends: wx-config
>
>
> This is surprising. I am using wx-config-win on my Windows environment
> (when I run wx-config -v, I get "wx-config revision 26 2006-12-21"). I
> deliberately did not choose to use Eric's version as he had noted some
> issues with it.
>
> We should investigate your problem further (I am also using wPack 2.8.12)

--

-- 
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
shelarcy | 8 Jan 15:34 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

Hi,

I think that we can remove old-time dependency from wxcore now. Because
wxcore uses old-time's System.Time modules in only Graphics.UI.WXCore.Db
module, and that module is removed this version.

I attached a patch for removing old-time dependency in Dave's wxhaskell-dev
branch. (This patch also includes one more change that removing unused
wxhaskell/src/eiffel directory.)

Best Regards,

On Fri, 06 Jan 2012 02:44:24 +0900, Jeremy O'Donoghue
<jeremy.odonoghue@...> wrote:

> Hi Lists,
>
> I am please to announce that wxHaskell 0.13.2 has just been uploaded to
> Hackage.
>
> This is mainly a bugfix release, although it brings a few useful changes:
>
>    - Changes to support build under Haskell Platform 2011.4.0.0
>    - OpenGL support if your wxWidgets build is configured with it
>    (reinstated functionality)
>    - StyledTextControl support if your wxWidgets build is configured with
>    it (reinstated functionality)
>
> This is intended to be the final wxHaskell release supporting wxWidgets
> 2.8.x.
>
> (snip)
>
> The source repository at code.haskell.org has not yet been updated with the
> patches. This will happen in the next day or so.

--

-- 
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/
Attachment (unnecessary.dpatch): application/octet-stream, 28 KiB
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
Dave Tapley | 9 Jan 18:27 2012
Picon

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

2012/1/8 shelarcy <shelarcy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi,

I think that we can remove old-time dependency from wxcore now. Because
wxcore uses old-time's System.Time modules in only Graphics.UI.WXCore.Db
module, and that module is removed this version.

I attached a patch for removing old-time dependency in Dave's wxhaskell-dev
branch. (This patch also includes one more change that removing unused
wxhaskell/src/eiffel directory.)

Thanks again, I've applied these to my branch also.
It's funny you should spot that unnecessary old-time dependency now, because I spotted and removed the .Db sample code at at almost exactly the same time (I was trying to build all the samples..):
http://darcsden.com/DukeDave/wxhaskell-dev/patch/20120107182358-a1f0b
 

Best Regards,



On Fri, 06 Jan 2012 02:44:24 +0900, Jeremy O'Donoghue <jeremy.odonoghue <at> gmail.com> wrote:

Hi Lists,

I am please to announce that wxHaskell 0.13.2 has just been uploaded to
Hackage.

This is mainly a bugfix release, although it brings a few useful changes:

  - Changes to support build under Haskell Platform 2011.4.0.0
  - OpenGL support if your wxWidgets build is configured with it
  (reinstated functionality)
  - StyledTextControl support if your wxWidgets build is configured with

  it (reinstated functionality)

This is intended to be the final wxHaskell release supporting wxWidgets
2.8.x.

(snip)


The source repository at code.haskell.org has not yet been updated with the
patches. This will happen in the next day or so.

--
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox

Gmane