wxhaskell-users — General mailing list for wxhaskell users

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

[Jeremy O'D. <jer...@gm...>]

Hi Shelarcy,

It's great to see you back...
2012/1/6 shelarcy <she...@gm...>

> 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

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

[Henning T. <le...@he...>]

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 :-)

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

[Peter S. <si...@cr...>]

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

Re: [wxhaskell-users] [wxhaskell-devel] ANN: wxHaskell 0.13.2

[Dave T. <dav...@gm...>]

2012/1/6 shelarcy <she...@gm...>

> 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 <
> jer...@gm...> 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/ <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
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
>
>

Re: [wxhaskell-users] ANN: wxHaskell 0.13.2

[shelarcy <she...@gm...>]

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 <jer...@gm...> 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/

[wxhaskell-users] ANN: wxHaskell 0.13.2

[Jeremy O'D. <jer...@gm...>]

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

Re: [wxhaskell-users] [wxhaskell-devel] Happy New Year, wxHaskellers

[Dave T. <dav...@gm...>]

On 2 January 2012 08:48, Jeremy O'Donoghue <jer...@gm...>wrote:

> Hi lists,
>
> A Happy New Year to all, and with it a chance to talk about some imminent
> changes in wxHaskell. There is nothing new in this mail for those who
> follow the wxhaskell-devel list, but for users who are interested in the
> evolution of the project, I thought this would be a good time to summarise.
>
> First, there will be a new release of wxHaskell in the next few days. This
> is mainly a bugfix edition, but also reinstates some features which were
> lost with Cabalization. Specifically:
>
>    - Styled Text Control support
>    - OpenGL support
>    - Support for building on Haskell Platform 2011.4
>
> This will be the last update of wxHaskell to support the wxWidgets 2.8.x
> releases.
>
Thanks for taking care of this last release Jeremy :)

> Following shortly afterwards, the very exciting news is that a number of
> people (Dave Tapley in particular) have been putting a lot of work over the
> last few months towards support of the wxWidgets 2.9 releases. This does
> introduce a small number of breaking changes as the wxWidgets API has
> changed in places, but brings with it quite a number of improvements:
>
Just to note again, I've been pushing all my 2.9 dev work here:
http://darcsden.com/DukeDave/wxhaskell-dev

That branch's wxC configure will fail if wx-config reports a version other
than 2.9.x, see readWxConfig in:
http://darcsden.com/DukeDave/wxhaskell-dev/browse/wxc/Setup.hs

>
>    - wxC is built as a shared library. This means that wxHaskell works in
>    GHCi again, which has been one of the most requested bugfixes over the past
>    18 months or so.
>    - Support for wxPropertyGrid and associated classes.
>    - Support for the wxWidgets AUI classes.
>    - Support for wxMediaControl.
>    - Removal of legacy use of Eiffel files to generate constant
>    definitions. This is only of interest to developers, but is far cleaner.
>    - Build system improvements to reduce 'unnecessary' rebuilding of
>    source files - again, one for developers.
>    - Support for 64bit OS X platforms.
>
> We will make a release of wxHaskell with all of the new features soon
> after the changes have been merged into the main repository, and have been
> more fully tested on all of our supported platforms.
>
Yes the testing on more platforms is where the emphasis needs to be here.
I'm primarily working in Ubuntu, but I did do a small amount of work trying
to ensure Windows is supported in my branch.
One hurdle I ran in to is that wx-config-win is unmaintained and no longer
works with wxWidgets 2.9.x:
http://code.google.com/p/wx-config-win/

The good news is that I emailed the old maintainer and he both responded
and made me an owner of that project.
I just need to make some small changes there, and then we should be able to
get wxHaskell building in Windows against 2.9.x, see here:
http://code.google.com/p/wx-config-win/issues/detail?id=21

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
> _______________________________________________
> wxhaskell-devel mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
>
>

[wxhaskell-users] Happy New Year, wxHaskellers

[Jeremy O'D. <jer...@gm...>]

Hi lists,

A Happy New Year to all, and with it a chance to talk about some imminent
changes in wxHaskell. There is nothing new in this mail for those who
follow the wxhaskell-devel list, but for users who are interested in the
evolution of the project, I thought this would be a good time to summarise.

First, there will be a new release of wxHaskell in the next few days. This
is mainly a bugfix edition, but also reinstates some features which were
lost with Cabalization. Specifically:

   - Styled Text Control support
   - OpenGL support
   - Support for building on Haskell Platform 2011.4

This will be the last update of wxHaskell to support the wxWidgets 2.8.x
releases.

Following shortly afterwards, the very exciting news is that a number of
people (Dave Tapley in particular) have been putting a lot of work over the
last few months towards support of the wxWidgets 2.9 releases. This does
introduce a small number of breaking changes as the wxWidgets API has
changed in places, but brings with it quite a number of improvements:

   - wxC is built as a shared library. This means that wxHaskell works in
   GHCi again, which has been one of the most requested bugfixes over the past
   18 months or so.
   - Support for wxPropertyGrid and associated classes.
   - Support for the wxWidgets AUI classes.
   - Support for wxMediaControl.
   - Removal of legacy use of Eiffel files to generate constant
   definitions. This is only of interest to developers, but is far cleaner.
   - Build system improvements to reduce 'unnecessary' rebuilding of source
   files - again, one for developers.
   - Support for 64bit OS X platforms.

We will make a release of wxHaskell with all of the new features soon after
the changes have been merged into the main repository, and have been more
fully tested on all of our supported platforms.

Best regards

Jeremy

Re: [wxhaskell-users] adapt layout after changing 'visible' state

[Eric K. <eri...@gm...>]

I'd go ahead and record/send that.

Thanks! This sort of distributed doc effort helps :-)

On 8 Dec 2011, at 18:49, Henning Thielemann wrote:
> Here is my proposed patch:
> 
> wxhaskell/wx$ darcs2 diff --unified src/Graphics/UI/WX/Classes.hs
> --- old-wxhaskell/wx/src/Graphics/UI/WX/Classes.hs      2011-12-08 19:45:56.000000000 +0100
> +++ new-wxhaskell/wx/src/Graphics/UI/WX/Classes.hs      2011-12-08 19:45:56.000000000 +0100
> @@ -173,6 +173,19 @@
>  -- | Visible widgets.
>  class Visible w where
>    -- | Is the widget visible?
> +  --
> +  -- If you hide a widget, its space will not immediately
> +  -- be filled by other widgets.
> +  -- Vice versa if you make a widget visible
> +  -- it will not have space to be rendered into.
> +  -- That is, when changing the visibility state
> +  -- it is advised to update the layout
> +  -- using 'Graphics.UI.WX.Layout.windowReFit'.
> +  --
> +  -- Example:
> +  --
> +  -- > do set w [ visible := False ]
> +  -- >    windowReFit w



-- 
Eric Kow <http://erickow.com>

Re: [wxhaskell-users] adapt layout after changing 'visible' state

[Henning T. <le...@he...>]

On Thu, 8 Dec 2011, Henning Thielemann wrote:

> I think the best place for documenting the solution is not the FAQ but the 
> documentation of the Visible class.

Here is my proposed patch:

wxhaskell/wx$ darcs2 diff --unified src/Graphics/UI/WX/Classes.hs
--- old-wxhaskell/wx/src/Graphics/UI/WX/Classes.hs      2011-12-08 19:45:56.000000000 +0100
+++ new-wxhaskell/wx/src/Graphics/UI/WX/Classes.hs      2011-12-08 19:45:56.000000000 +0100
@@ -173,6 +173,19 @@
  -- | Visible widgets.
  class Visible w where
    -- | Is the widget visible?
+  --
+  -- If you hide a widget, its space will not immediately
+  -- be filled by other widgets.
+  -- Vice versa if you make a widget visible
+  -- it will not have space to be rendered into.
+  -- That is, when changing the visibility state
+  -- it is advised to update the layout
+  -- using 'Graphics.UI.WX.Layout.windowReFit'.
+  --
+  -- Example:
+  --
+  -- > do set w [ visible := False ]
+  -- >    windowReFit w
    visible    :: Attr w Bool
    -- | Refresh the widget explicitly.
    refresh    :: w -> IO ()

Re: [wxhaskell-users] adapt layout after changing 'visible' state

[Henning T. <le...@he...>]

On Wed, 7 Dec 2011, David Virebayre wrote:

> 2011/12/6 Henning Thielemann <le...@he...>
>
>       I have a textCtrl 'editor' and a menu item 'editorVisible' that controls
>       the visibility of the textCtrl.
>
>           set editorVisible
>               [ on command := do
>                    b <- get editorVisible checked
>                    set editor [ visible := b ] ]
> 
> 
> I had the same problem, and I couldn't solve it the way I wanted.
> It's old but I think I read that I shouldn't use visible for this, but remove the
> element from the layout and re-set the modified layout.


  I got it working by adding 'windowReFit editor' or 'windowReLayout frame' 
after 'set editor [ visible := b ]'.

  I do not know, whether this is intended behaviour or an ugly hack. The 
official example controls.cpp uses a BoxSizer object and its Show method. 
I am uncertain how to translate this to wxhaskell. How do I create a 
BoxSizer object? With boxSizerCreate or sizerFromLayout? How do I add the 
BoxSizer object? By converting it to a Layout using 'sizer'?

  I think the best place for documenting the solution is not the FAQ but 
the documentation of the Visible class.

Re: [wxhaskell-users] adapt layout after changing 'visible' state

[David V. <dav...@gm...>]

2011/12/6 Henning Thielemann <le...@he...>

>
> I have a textCtrl 'editor' and a menu item 'editorVisible' that controls
> the visibility of the textCtrl.
>
>     set editorVisible
>         [ on command := do
>              b <- get editorVisible checked
>              set editor [ visible := b ] ]
>

I had the same problem, and I couldn't solve it the way I wanted.
It's old but I think I read that I shouldn't use visible for this, but
remove the element from the layout and re-set the modified layout.

David.

Re: [wxhaskell-users] Please remove me from the wxhaskell list for now.

[Dave T. <duk...@gm...>]

On 6 December 2011 20:02, Jesse Hester <hes...@gm...> wrote:
> Thanks,
>
> Jesse Hester

You'll probably have to do it yourself, here:
https://lists.sourceforge.net/lists/listinfo/wxhaskell-users

See: To unsubscribe from wxhaskell-users, get a password reminder, or
change your subscription options enter your subscription email
address".

>
> ------------------------------------------------------------------------------
> Cloud Services Checklist: Pricing and Packaging Optimization
> This white paper is intended to serve as a reference, checklist and point of
> discussion for anyone considering optimizing the pricing and packaging model
> of a cloud services business. Read Now!
> http://www.accelacomm.com/jaw/sfnl/114/51491232/
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>

[wxhaskell-users] Please remove me from the wxhaskell list for now.

[Jesse H. <hes...@gm...>]

Thanks,

Jesse Hester

Re: [wxhaskell-users] adapt layout after changing 'visible' state

[Eric K. <eri...@gm...>]

Hi,

On 6 Dec 2011, at 19:05, Henning Thielemann wrote:
> How can I achieve immediate relayout of the window when changing the 
> showing or hiding the editor? I tried 'refresh editor' and 'refresh panel' 
> and 'refresh frame' (where panel and frame are the surrounding widgets) 
> but this does not trigger new layout.


I'm sorry I don't have an answer for you, but this appears to be a great candidate for an FAQ, the kind of thing people would run into often.

If you get answer from somebody on the list, would you be willing to add a Howto section to the FAQ of some sort, with your question?
http://www.haskell.org/haskellwiki/WxHaskell/FAQ

FWIW, I have a 'repaint' in my code, but that may not have anything to do with your issue.

-- 
Eric Kow <http://erickow.com>

[wxhaskell-users] adapt layout after changing 'visible' state

[Henning T. <le...@he...>]

I have a textCtrl 'editor' and a menu item 'editorVisible' that controls 
the visibility of the textCtrl.

     set editorVisible
         [ on command := do
              b <- get editorVisible checked
              set editor [ visible := b ] ]

Now when I uncheck the menu item editorVisible, then the editor actually 
disappears, but its space becomes empty and is not occupied by the other 
widgets in the GUI. When I resize the window then all widgets are 
relayouted and the space of the invisible textCtrl is covered by the other 
widgets. That is the result that I want to have, but without resizing the 
window. Vice versa when I make the editor visible via the menu, then it 
cannot be seen immediately but only after window resizing.

How can I achieve immediate relayout of the window when changing the 
showing or hiding the editor? I tried 'refresh editor' and 'refresh panel' 
and 'refresh frame' (where panel and frame are the surrounding widgets) 
but this does not trigger new layout.

I use wxwidgets-2.8 on GTK and Linux.

Re: [wxhaskell-users] Looking for macosx-app? Try cabal-macosx

[Heinrich A. <apf...@qu...>]

Eric Kow wrote:
> The wxHaskell docs mention a shell script called macosx-app, but it
> got lost in our big build system cleanup.
> 
> Now we have a replacement.  Andy Gimblett's cabal-macosx package
> provides - Cabal hooks to build an app bundle - a very thin CLI
> wrapper called 'macosx-app'
> 
> The latter is intended for use with little one-off applications too
> small to merit Cabalisation.  You should be able to use it the same
> way as the old shell script.
> 
> The CLI is currently on GitHub only at the moment, but I think Andy
> is planning to upload it to Hackage :-)
> 
> https://github.com/gimbo/cabal-macosx
> 
> We might want to consider having the wx package depend on
> cabal-macosx, although this isn't strictly speaking necessary 

Awesome! I'm using both already, with a macosx-app script that I had 
pilfered from a StackOverflow thread. Great that it's included in the 
cabal package now.


Best regards,
Heinrich Apfelmus

--
http://apfelmus.nfshost.com

Re: [wxhaskell-users] Looking for macosx-app? Try cabal-macosx

[Eric K. <eri...@gm...>]

On 3 Nov 2011, at 10:49, Eric Kow wrote:
> 
> The CLI is currently on GitHub only at the moment, but I think Andy is planning to upload it to Hackage :-)
> 
> https://github.com/gimbo/cabal-macosx

Now on hackage

cabal update
cabal install macosx-app

-- 
Eric Kow <http://erickow.com>

[wxhaskell-users] Looking for macosx-app? Try cabal-macosx

[Eric K. <eri...@gm...>]

Hi all,

The wxHaskell docs mention a shell script called macosx-app, but it got lost in our big build system cleanup.

Now we have a replacement.  Andy Gimblett's cabal-macosx package provides
- Cabal hooks to build an app bundle
- a very thin CLI wrapper called 'macosx-app'

The latter is intended for use with little one-off applications too small to merit Cabalisation.  You should be able to use it the same way as the old shell script.

The CLI is currently on GitHub only at the moment, but I think Andy is planning to upload it to Hackage :-)

https://github.com/gimbo/cabal-macosx

We might want to consider having the wx package depend on cabal-macosx, although this isn't strictly speaking necessary

-- 
Eric Kow <http://erickow.com>

Re: [wxhaskell-users] Custom events

[Henning T. <le...@he...>]

On Sun, 30 Oct 2011, Henning Thielemann wrote:

> Recently on this list it was suggested to use
>
>   myEventId = wxID_HIGHEST+1
>
> for custom events and register them as menu events.
>
>   http://snipplr.com/view/17538/
>
>
> Now I added menus to my application and I got the strange behaviour that
> selecting a certain menu item (the second one of all items) let my
> application freeze. I found out that this could be solved by choosing a
> different EventId. So is the id wxID_HIGHEST+1 really free for use? How
> can I safely choose an id that is free for custom use? Is it sensible to
> consider custom events as menu events?

I found in Graphics.UI.WXCore.Types:

varTopId :: Var Id
varTopId
   = unsafePerformIO (varCreate (wxID_HIGHEST+1))

It looks like wxID_HIGHEST+1 is alreay used by wxhaskell. How can I make 
sure that I do not clash with id's used by wxhaskell in future?

[wxhaskell-users] Custom events

[Henning T. <le...@he...>]

Recently on this list it was suggested to use

   myEventId = wxID_HIGHEST+1

for custom events and register them as menu events.

   http://snipplr.com/view/17538/


Now I added menus to my application and I got the strange behaviour that 
selecting a certain menu item (the second one of all items) let my 
application freeze. I found out that this could be solved by choosing a 
different EventId. So is the id wxID_HIGHEST+1 really free for use? How 
can I safely choose an id that is free for custom use? Is it sensible to 
consider custom events as menu events?

I don't understand much of these id's. Without these custom events you do 
not have to bother with id's in wxhaskell.

[wxhaskell-users] instance Selection (Notebook a)

[Henning T. <le...@he...>]

How about adding this instance

instance Selection (Notebook a) where
     selection =
         newAttr "selection"
             WXCMZ.notebookGetSelection
             (\nb -> fmap (const ()) . WXCMZ.notebookSetSelection nb)

?

Re: [wxhaskell-users] wxHaskell: Make textCtrl logger scroll one line at a time

[Paulo P. <po...@gm...>]

Hello Bernd

I found a simple way to make textCtrl scroll properly. Just add the
attribute "style := wxTE_MULTILINE" to the textCtrl widget.

Here is an example:
https://code.google.com/p/pmpocinho/source/browse/textCtrl.hs

All the best!
Paulo M. Pocinho

On 17 October 2011 09:47, Bernd Holzmüller <ber...@ic...> wrote:
> Hi Paulo,
>
> I also had this problem some time ago and wasn't able to solve it. Your
> reference to wxWidgets is indeed interesting and seems to be the right
> direction. Unfortunately, many functionality of wxWidgets is not yet mapped
> to wxHaskell or only in a very basic manner.
>
> In case you manage to solve it, please let me know!
>
> Thanks,
> Bernd
>
> Am 16.10.2011 16:04, schrieb Paulo Pocinho:
>
> Hello. I want to know how to make the textCtrl widget scroll only one
> line at a time instead the default one page at a time.
>
> The usage is the same as the one given by the examples. Text is
> appended to a textCtrl that serves as a logging window.
>
> However, once the appended line reaches the bottom of the scrolled
> text, the textCtrl automatically "jumps" one page. There is an
> attribute in wxWidgets called ScrollLine () that makes it only scroll
> the number of lines we want [1] but I can't find it in wxHaskell.
>
> How can I make text scroll one line instead of jumping a screen at a time?
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>
>
> --
> Bernd Holzmüller
> Dipl.-Inform.
>
> Business Unit Methods Processes Tools
>
> Telefon / Phone: +49 (0)711 / 21037 - 41
> Fax: +49 (0)711 / 21037 - 75
> Mobil: +49 (0)172 / 7280 490
> E-Mail: ber...@ic...
> Internet: www.ics-ag.de
>
> Informatik Consulting Systems AG
>
> Postanschrift / Mailing Adress: Postfach 102431, 70220 Stuttgart,
> Deutschland / Germany
> Sitz und Registergericht / Domicile and Court of Registry: Stuttgart /
> HRB-Nr. / Commercial Register No.: 18569
> Vorsitzender des Aufsichtsrat / Chairman: Dr. Jörg Kees
> Vorstand / Management Board: Franz-Josef Winkel, Cid Kiefer
>
> This e-mail message may contain confidential and/or privileged information.
> If you are not an addressee or otherwise authorized to receive this message,
> you should not use, copy, disclose or take any action based on this e-mail
> or any information contained in the message. If you have received this
> material in error, please advise the sender immediately by reply e-mail and
> delete this message.
>
> Thank you.

Re: [wxhaskell-users] Again StyledTextControl

[Jeremy O'D. <jer...@gm...>]

Hi Paulo,

On 21 October 2011 14:22, Paulo Pocinho <po...@gm...> wrote:

> I have spent the last three days figuring how to build wxWidgets.
> After much frustration with GCC, digging information from patches and
> several websites, I can now build the 9,87 MB wxmsw28u_gcc.dll version
> 2.8.12 that works. Yet, I have a new barrier and have to ask for your
> help.
>
> STC was built from contrib. Then I took directions from this thread
>
> http://sourceforge.net/mailarchive/forum.php?thread_name=CDCEC7C4-4463-46FF-BA06-17CC842A05BD%40dc.uba.ar&forum_name=wxhaskell-devel
>
> Did everything like this
>
> http://haskell.org/haskellwiki/WxHaskell/Building_with_styledTextCtrl_support
>

At the moment, STC support is disabled as it is difficult to get contrib
components to build (or not) reliably under the Cabal build system we have.

The error you have is because Cabal is not linking the library containing
STC.

The quickest way to get this to work (it is a bit of a dirty hack) is to
edit wxcore/Setup.hs. In myConfHooks you will find extra_wx_libs. If you add
the name of your stc library correctly in there (and assuming that the
compiler can find the path to it), I believe it should build, compile and
link for you.

The clean way to do this is to come up with a proper solution for
integrating contrib components in wxHaskell, which is mainly held up by the
lack of a working wx-config for Windows which behaves identically to
wx-config for Unix platforms. There has been some good work (not by me, I
hasten to add!) in this direction, but we need to get it properly integrated
and tested on all platforms

Regards
Jeremy

[wxhaskell-users] Again StyledTextControl

[Paulo P. <po...@gm...>]

I have spent the last three days figuring how to build wxWidgets.
After much frustration with GCC, digging information from patches and
several websites, I can now build the 9,87 MB wxmsw28u_gcc.dll version
2.8.12 that works. Yet, I have a new barrier and have to ask for your
help.

STC was built from contrib. Then I took directions from this thread
http://sourceforge.net/mailarchive/forum.php?thread_name=CDCEC7C4-4463-46FF-BA06-17CC842A05BD%40dc.uba.ar&forum_name=wxhaskell-devel

Did everything like this
http://haskell.org/haskellwiki/WxHaskell/Building_with_styledTextCtrl_support

However, this simple program does not work.

module Main where
import Graphics.UI.WX

main = start $ do
    f <- frame [text := "Styled Text Control Widget example"]
    p <- panel f []
    s <- styledTextCtrl p []

    status <- statusField []

    set f [ layout := container p $ margin 5 $ fill $ widget s
          , statusBar := [status]
          , clientSize := sz 800 600
          ]

Using:

ghc --make styledTextCtrl.hs

Linking styledTextCtrl.exe ...
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(eljrc.o):eljrc.cpp:(.text+0x112f):
 undefined reference to
`_imp___ZN16wxStyledTextCtrl6CreateEP8wxWindowiRK7wxPointRK6wxSizelRK8wxString'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(eljrc.o):eljrc.cpp:(.text+0x13f2):
 undefined reference to `_imp___ZTV16wxStyledTextCtrl'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x7):
undefi
ned reference to `_imp___ZN16wxStyledTextCtrl7AddTextERK8wxString'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x17):
undef
ined reference to
`_imp___ZN16wxStyledTextCtrl13AddStyledTextERK14wxMemoryBuffer'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x27):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl10InsertTextEiRK8wxString'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x37):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl8ClearAllEv'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x47):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl18ClearDocumentStyleEv'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x57):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl9GetLengthEv'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x67):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl9GetCharAtEi'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x77):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl13GetCurrentPosEv'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x87):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl9GetAnchorEv'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x97):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl10GetStyleAtEi'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0xa7):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl4RedoEv'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0xbe):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl17SetUndoCollectionEb'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0xcf):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl9SelectAllEv'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0xdf):
undef
ined reference to `_imp___ZN16wxStyledTextCtrl12SetSavePointEv'

(...)

C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x2afc):
und
efined reference to `_imp__wxEVT_STC_START_DRAG'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x2b08):
und
efined reference to `_imp__wxEVT_STC_DRAG_OVER'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x2b14):
und
efined reference to `_imp__wxEVT_STC_DO_DROP'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x2b20):
und
efined reference to `_imp__wxEVT_STC_ZOOM'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x2b2c):
und
efined reference to `_imp__wxEVT_STC_HOTSPOT_CLICK'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x2b38):
und
efined reference to `_imp__wxEVT_STC_HOTSPOT_DCLICK'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x2b44):
und
efined reference to `_imp__wxEVT_STC_CALLTIP_CLICK'
C:\Users\Ulrim\AppData\Roaming\cabal\wxcore-0.12.1.7\ghc-7.2.1/libHSwxcore-0.12.1.7.a(stc.o):stc.cpp:(.text+0x2b50):
und
efined reference to `_imp__wxEVT_STC_AUTOCOMP_SELECTION'
collect2: ld returned 1 exit status


Any help setting up STC is very much appreciated.