Re: [wxhaskell-devel] Happy New Year, wxHaskellers
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
Re: [wxhaskell-devel] Happy New Year, wxHaskellers
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
Re: [wxhaskell-devel] Happy New Year, wxHaskellers
On 2 January 2012 08:48, Jeremy O'Donoghue jeremy.odonog...@gmail.comwrote: 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 wxhaskell-devel@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___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Happy New Year, wxHaskellers
Jeremy O'Donoghue wrote: 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. Hurray, that promises to be a really happy new year! The bananas will *dance*! Best regards, Heinrich Apfelmus -- http://apfelmus.nfshost.com -- 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
