Re: [wxhaskell-devel] [wxhaskell-users] [Haskell] ANN: wxHaskell 0.92

[Conal Elliott]

Sounds consistent. I'd expect that the compiled BouncingBalls.exe can be
run twice because you get two separate processes, each opening a top-level
window only once. Sadly, this limitation stops wxHaskell from being useful
for exploratory programming, which is why I stopped using it several years
ago.

On Sat, Sep 5, 2015 at 6:07 AM, Henk-Jan van Tuyl <hjgt...@chello.nl> wrote:

>
> I tried running BouncingBalls.hs in the samples\wxcore directory; inside
> GHCi, it runs the second time only for a short while, then crashes. The
> Windows application log shows exception code 0xc005, which means
> "Access violation". The standalone BouncingBalls.exe can be run multiple
> times without a problem.
>
> Henk-Jan
>
>
>
> On Fri, 04 Sep 2015 23:56:47 +0200, Conal Elliott <co...@conal.net> wrote:
>
> The original bug report (perhaps 7 years ago) was at
>> http://sourceforge.net/p/wxhaskell/bugs/84/ . Seems to be gone now. The
>> symptom was a reliable crash whenever a second top-level window was
>> displayed from a given process, whether in ghci or standalone compiled.
>> Especially inconvenient with ghci, as I typically wanted to open more than
>> one top-level window in that context (exploratory programming).
>>
>> -- Conal
>>
>> On Fri, Sep 4, 2015 at 1:13 AM, Henk-Jan van Tuyl <hjgt...@chello.nl>
>> wrote:
>>
>> On Thu, 03 Sep 2015 16:57:13 +0200, Henk-Jan van Tuyl <hjgt...@chello.nl>
>>> wrote:
>>>
>>> :
>>> > Currently, I am not able to run wxHaskell inside GHCi (on Windows).
>>> :
>>>
>>> I discovered that wxHaskell runs inside GHCi, when I install it locally,
>>> i.o. in a sandbox.
>>>
>>> Regards,
>>> Henk-Jan van Tuyl
>>>
>>>
>>> --
>>> Folding@home
>>> What if you could share your unused computer power to help find a cure?
>>> In
>>> just 5 minutes you can join the world's biggest networked computer and
>>> get
>>> us closer sooner. Watch the video.
>>> http://folding.stanford.edu/
>>>
>>>
>>> http://Van.Tuyl.eu/
>>> http://members.chello.nl/hjgtuyl/tourdemonad.html
>>> Haskell programming
>>> --
>>>
>>>
>>>
>>> --
>>> ___
>>> wxhaskell-devel mailing list
>>> wxhaskell-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
>>>
>>>
>
>
>
>
> --
> Folding@home
> What if you could share your unused computer power to help find a cure? In
> just 5 minutes you can join the world's biggest networked computer and get
> us closer sooner. Watch the video.
> http://folding.stanford.edu/
>
>
> http://Van.Tuyl.eu/
> http://members.chello.nl/hjgtuyl/tourdemonad.html
> Haskell programming
> --
>
--
___
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel

Re: [wxhaskell-devel] [wxhaskell-users] [Haskell] ANN: wxHaskell 0.92

[Conal Elliott]

The original bug report (perhaps 7 years ago) was at
http://sourceforge.net/p/wxhaskell/bugs/84/ . Seems to be gone now. The
symptom was a reliable crash whenever a second top-level window was
displayed from a given process, whether in ghci or standalone compiled.
Especially inconvenient with ghci, as I typically wanted to open more than
one top-level window in that context (exploratory programming).

-- Conal

On Fri, Sep 4, 2015 at 1:13 AM, Henk-Jan van Tuyl  wrote:

> On Thu, 03 Sep 2015 16:57:13 +0200, Henk-Jan van Tuyl 
> wrote:
>
> :
> > Currently, I am not able to run wxHaskell inside GHCi (on Windows).
> :
>
> I discovered that wxHaskell runs inside GHCi, when I install it locally,
> i.o. in a sandbox.
>
> Regards,
> Henk-Jan van Tuyl
>
>
> --
> Folding@home
> What if you could share your unused computer power to help find a cure? In
> just 5 minutes you can join the world's biggest networked computer and get
> us closer sooner. Watch the video.
> http://folding.stanford.edu/
>
>
> http://Van.Tuyl.eu/
> http://members.chello.nl/hjgtuyl/tourdemonad.html
> Haskell programming
> --
>
>
> --
> ___
> wxhaskell-devel mailing list
> wxhaskell-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
>
--
___
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel

Re: [wxhaskell-devel] [Haskell] ANN: wxHaskell 0.92

[Conal Elliott]

Thanks for the update. What's the status of the old problem of crashing the
host process if one opens more than one top-level window (as typical in
GHCi)?  - Conal

On Fri, Aug 28, 2015 at 1:16 AM, Henk-Jan van Tuyl 
wrote:

>
> L.S.,
>
> I am happy to announce a new version of wxHaskell (0.92).
>
> What is it?
> ---
> wxHaskell[1] is a portable and native GUI library for Haskell. The goal of
> the project is to provide an industrial strength GUI library for Haskell,
> but without the burden of developing (and maintaining) one ourselves.
>
> wxHaskell is therefore built on top of wxWidgets – a comprehensive C++
> library that is portable across all major GUI platforms; including GTK,
> Windows, X11, and MacOS X. Furthermore, it is a mature library (in
> development since 1992) that supports a wide range of widgets with the
> native look-and-feel.
>
>
> What's new?
> ---
>- wxc/setup.hs now stops searching for wxWidgets when a
>  compatible version is found (this solves bug ticket 96)
>- Support for simple Wizards added
>- Calendar support added
>- GCC > 4.5 can now be used on Windows, which is a big
>  improvement, as wxWidgets and wxHaskell must use the
>  exact same GCC, to prevent compatibility problems
>- wxAui is added to wxc, wxAuiNotebook events are added
>  to wxcore and wx
>- Missing GLAttributes added
>- Packet version limits adapted to the newest Haskell
>  Platform
>- Bitness check on Windows no longer uses an external
>  executable
>- wxHaskell can now be installed with MSYS2
>- wxc/Setup.hs is modified to also link to the wx OpenGL
>  libraries for wxGLCanvas
>- The "warning: Adding duplicate image handler for
>  '... file'" messages are removed
>- Created a new class Updating with corresponding event
>  "update". Provided instances for TextCtrl and ComboBox:
>  update gets called when the text changes.
>- Support for wxSplashScreen in wxc and wxcore is added
>- Many warnings are solved
>
> Links
> -
> See the homepage of wxHaskell for more information:
> https://wiki.haskell.org/WxHaskell
>
> The packages are:
>- wxc   https://hackage.haskell.org/package/wxc
>- wxdirect  https://hackage.haskell.org/package/wxdirect
>- wxcorehttps://hackage.haskell.org/package/wxcore
>- wxhttps://hackage.haskell.org/package/wx
>
> Regards,
> Henk-Jan van Tuyl
>
>
> [0] https://www.wxwidgets.org
> [1] https://wiki.haskell.org/WxHaskell
>
>
>
> --
> Folding@home
> What if you could share your unused computer power to help find a cure? In
> just 5 minutes you can join the world's biggest networked computer and get
> us closer sooner. Watch the video.
> http://folding.stanford.edu/
>
>
> http://Van.Tuyl.eu/
> http://members.chello.nl/hjgtuyl/tourdemonad.html
> Haskell programming
> --
> ___
> Haskell mailing list
> hask...@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell
>
--
___
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel

Re: [wxhaskell-devel] Let's release the current wxHaskell

[Conal Elliott]

I'm always glad to hear of wxHaskell activity. Has there been any progress
on the wxHaskell-vs-ghci issue http://sourceforge.net/p/wxhaskell/bugs/84/?
-- Conal


On Fri, Feb 21, 2014 at 3:54 PM, Henk-Jan van Tuyl hjgt...@chello.nlwrote:


 L.S.,

 I think we can release the current wxHaskell on Hackage and go on with
 wxWidgets 3.0.0 without branching on GitHub. If someone adds me to the
 list of maintainers (for the packages wxdirect, wxc, wxcore and wx) on
 Hackage, I will do this myself. My account on Hackage is HenkJanVanTuyl.

 The main advantage of this release is that this version installs properly
 on Windows.

 Regards,
 Henk-Jan van Tuyl


 --
 Folding@home
 What if you could share your unused computer power to help find a cure? In
 just 5 minutes you can join the world's biggest networked computer and get
 us closer sooner. Watch the video.
 http://folding.stanford.edu/


 http://Van.Tuyl.eu/
 http://members.chello.nl/hjgtuyl/tourdemonad.html
 Haskell programming
 --


 --
 Managing the Performance of Cloud-Based Applications
 Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
 Read the Whitepaper.

 http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk
 ___
 wxhaskell-devel mailing list
 wxhaskell-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel

--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel

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

[Conal Elliott]

 Wow! If this works, Conal might be pleased.


Yes, indeed! I've been blocked in my high-level GUIs  graphics work for a
few years, while waiting for a low-level (imperative) Haskell library to
show up that combines GUIs  graphics, works cross-platform (including
native graphics on Mac), and supports incremental development. gtk2hs
almost got there recently, but not quite, and I've always preferred
wxHaskell's API.

  - Conal

On Thu, Jan 5, 2012 at 7:36 AM, Dave Tapley dave.a.tap...@gmail.com wrote:

 On 4 January 2012 18:23, Eric Kow eric@gmail.com wrote:


 On 4 Jan 2012, at 16:59, Dave Tapley wrote:
  Also, I imagine that while this brings us closer to wxHaskell in GHCi,
 we would still need to solve the second start crash?
 
 
 https://sourceforge.net/tracker/?func=detailaid=1610984group_id=7the3133atid=536845
 
  Well, I just had a look, and that issue seems to have gone away in my
 darcsden branch!
  I've added a comment to the tracker.
 

 Wow! If this works, Conal might be pleased.


 It certainly seems to, insomuch as the given test code no longer causes a
 crash :)



 By the way, you mentioned wx-config (I get the feeling you'd asked me a
 direct question and I forgot to answer).  Did you have a look at the
 Haskell code in our repo which provides a wx-config replacement?  The
 replacement is very very stupid and needs generalising, but it might be
 easier to bring it closer to the kind of completeness we need than to
 maintain the C++ one.


 Ah, yes, I suspected this would need some debate.
 I was on the cusp of merging in your wx-config implementation, namely:
 http://darcsden.com/kowey/wxhaskell/browse/wx-config/

 But then I got a reply from the previous project leader wx-config-win:
 http://code.google.com/p/wx-config-win/

 He had hoped that one day wx-config-win might be merged in to wxWidgets,
 but noted that it had fallen behind the project and had several known
 issues:
 http://code.google.com/p/wx-config-win/issues/list

 Personally I feel that (for similar arguments to those for maintaining wxC
 as a language-agnostic project) we should pursue wx-config-win. Thoughts?




 --
 Eric Kow http://erickow.com


 -BEGIN PGP SIGNATURE-

 iEYEARECAAYFAk8EmT4ACgkQBUrOwgisBPnz/wCdEapNshQh+ZqEh2SyyXi/uXO9
 5lcAnRymzM7qQnzru6cdKpoTqZZ3kQM4
 =hcbP
 -END PGP SIGNATURE-



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