Hi all,
Sorry I've been a little quiet the last week or two, rest assured I have
lurking all along.
On 22 January 2012 00:37, Jeremy O'Donoghue wrote:
> I now have wxC building on Windows. Details below and patches attached.
>
Excellent!
I'll take a look.
>
> Jeremy
>
> On 18 January 2012 23
On 16 January 2012 00:46, Eric Kow wrote:
>
> I was going to post on your blog, but you beat me to mentioning it. So
> better hear it from me, you should totally use GitHub for wxC. Plus it
> would be a chance to work with darcs-bridge maybe.
>
>
>1. Eric will probably kill me for saying this
On 15 January 2012 22:38, Jeremy O'Donoghue wrote:
> Hi developers,
>
> Think the subject says it all :-)
Bwahahahaa.
So, this is code.haskell.org?
How does one go about obtaining access?
>
> Jeremy
>
> --
> RSA(R) Conf
On 14 January 2012 23:02, Eric Kow wrote:
>
> On 14 Jan 2012, at 23:01, Eric Kow wrote:
>> I think our haddocks should include pictures. If not possible due to
>> technical constraints, they should include links to pictures hosted on the
>> wiki or perhaps somewhere more stable like a darcs rep
On 13 January 2012 16:28, Frodo Kenny wrote:
>
> On Thu, Jan 12, 2012 at 5:19 PM, Dave Tapley wrote:
>>
>> On 12 January 2012 15:09, Jeremy O'Donoghue
>> wrote:
>> > Thank you Kenneth,
>> >
>> > That's an extremely detailed and compl
On 12 January 2012 15:09, Jeremy O'Donoghue wrote:
> Thank you Kenneth,
>
> That's an extremely detailed and complete set of notes. It is very much
> appreciated.
I'd also like to offer my thanks, this is extremely useful to us.
>
> Best regards
> Jeremy
>
> On 12 January 2012 14:52, Frodo Kenny
On 11 January 2012 00:56, Dave Tapley wrote:
> Does anyone know why wxTreeCtrl_GetBoundingRect is implemented [1] such that:
> 1. It returns a null pointer on non-Windows platforms.
> 2. It disregards the returned value and returns GetRect().
>
> It came in with: "wxhaskell-f
Does anyone know why wxTreeCtrl_GetBoundingRect is implemented [1] such that:
1. It returns a null pointer on non-Windows platforms.
2. It disregards the returned value and returns GetRect().
It came in with: "wxhaskell-from-cvs @ 2004-09-14 10:27:48 by dleijen".
Dave,
[1] http://darcsden.com/Du
On 9 January 2012 22:19, Jeremy O'Donoghue wrote:
> On 9 January 2012 18:09, Dave Tapley wrote:
>
>> On 9 January 2012 17:04, Jeremy O'Donoghue wrote:
>>
>>> On 6 January 2012 16:02, Dave Tapley wrote:
>>>
>>>> 2012/1/6 shelarcy
&
On 9 January 2012 17:04, Jeremy O'Donoghue wrote:
> Hi Dave, all
> On 6 January 2012 16:02, Dave Tapley wrote:
>
>> 2012/1/6 shelarcy
>>
>>> 2. It seems that wxcore depends on Eric's wx-config implicitly at least
>>> Windows environmen
2012/1/8 shelarcy
> 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 wxhas
2012/1/6 shelarcy
> 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 cat
On 4 January 2012 18:23, Eric Kow 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/?fu
On 2 January 2012 09:22, Eric Kow wrote:
>
> On 2 Jan 2012, at 08:48, Jeremy O'Donoghue wrote:
>
> > • 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.
>
> Sweet!
>
> I've ma
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
> ch
On 19 December 2011 22:02, Dave Tapley wrote:
> On 14 December 2011 07:16, Dave Tapley wrote:
> > The only major problem remaining (aside from the woeful lack of
> > testing, and support for non-Linux platforms) is you have to pass an
> > rpath to the linker when compiling;
On 14 December 2011 07:16, Dave Tapley wrote:
> Well, after a couple of days' frantic hacking I've made more progress,
> and I'd invite anyone to comment on my decisions:
>
> The compilation of the C++ 'wrapper' code has now been moved to a
> separate pr
Well, after a couple of days' frantic hacking I've made more progress,
and I'd invite anyone to comment on my decisions:
The compilation of the C++ 'wrapper' code has now been moved to a
separate project which I've called wxc.
This will now do the compilation and linking as per Jeremy's gist, and
xc.dll or
> libwxc.dylib or whatever) was in a 'normal' place before wxcore gets built.
>
> On 9 December 2011 14:13, Dave Tapley wrote:
>>
>> On 8 December 2011 22:34, Dave Tapley wrote:
>> > Hello everyone,
>> >
>> > I wrote a story, and I in
On 8 December 2011 22:34, Dave Tapley wrote:
> Hello everyone,
>
> I wrote a story, and I invite you all to comment and help me make it better.
> As an experiment I've decided to put it on hpaste instead of having
> the mail thread get out of hand (I'm also cross posti
Hello everyone,
I wrote a story, and I invite you all to comment and help me make it better.
As an experiment I've decided to put it on hpaste instead of having
the mail thread get out of hand (I'm also cross posting it to the
cabal list and have mentioned it in #haskell, and I want to keep all
co
On 28 November 2011 11:37, Jeremy O'Donoghue wrote:
> On 21 November 2011 18:31, Dave Tapley wrote:
>>
>> Not surprisingly, I am in favour of this :)
>
> I have spent a while thinking about this, as it has considerable
> ramifications.
>
> I don
Not surprisingly, I am in favour of this :)
Given that there aren't going to be any more 2.8.x releases of
wxWidgets, I'm happy to say:
If you want a stable(ish) wxHaskell, then use the current hackage
release along with the last stable wxWidgets release (2.8.12).
If you want bleeding edge wxHaske
This concerns Eric's patch, but may be of interest to the list as a whole..
I'm just merging in your "wxcore: No more Eiffel" patch (thanks
again!) and I've spotted an anomaly.
I see that you:
addfile ./wxcore/src/haskell/Graphics/UI/WXCore/WxcDefs.hs
Which makes perfect sense as this file w
On 16 November 2011 16:42, Jeremy O'Donoghue wrote:
> Hi Dave,
>
> On 21 October 2011 18:43, Dave Tapley wrote:
>>
>> On 21 October 2011 11:28, Jeremy O'Donoghue
>> wrote:
>>
>> >> Did the work on OpenGL, or the branch you mention on da
I just found this which may be of interest to those of you who (like
me) have been hacking with the call to wx-config in wxcore's Setup.hs,
specifically to get the correct libraries returned for your platform:
"wx-config --libs now only gives the standard libs. For e.g. aui you
need to do: wx-conf
Thanks for the responses guys, just to let you know I'm currently
going through the backlog here and merging relevant patches in to my
wx-2.9-only-wxhaskell-devel branch[1].
I'll send further periodic updates to the list when I reach milestones
/ get stuck.
It's worth noting that the wxWidgets pe
Firstly I'd like to say thanks to Eric for offering up these patches,
I've only been working with wxHaskell for a few months, but I must say
I wholeheartedly welcome the work; I for one don't want to see
wxHaskell go the same way as ewxw!
I just have a few requests/questions for you Eric:
1. Could
Interesting, it looks like this was fixed at some point, but the fix
never made it in to a release on hackage.
You'll need to either remove, or more correctly #if out this line:
#include "wx/tabctrl.h"
As shown in here:
http://code.haskell.org/wxhaskell/wxcore/src/include/wrapper.h
Perhaps someo
On 21 October 2011 11:28, Jeremy O'Donoghue wrote:
> Hi Dave
>
> Sorry for taking so long to respond.
That's okay, long is a relative term!
(Off-topic: Reminded me of this: http://www.schuhmacher.at/weblog/52cards.html)
>
> On 5 October 2011 00:13, Dave Tapley wro
Hi again Jeremy,
Did the work on OpenGL, or the branch you mention on darcsden[1] ever
get anywhere?
I'd like to nominate myself to work on it :)
I've created my own wxhaskell branch on darcsden[2], to which I'm
committing all the "wx-2.9 dev build / GTK2 / I don't care about
supporting wx < 2.9"
Hi all, would someone like to add me (davetapley) to the
SourceForge.net project.
It doesn't look like there has been much activity on it, I assume this
is just through lack of interest/development, and not because we've
moved somewhere else?
I'd like to start looking at getting OpenGL support bac
Hi all, I'm still struggling along with this.
I've summarised my current problem here: http://hpaste.org/51854
If any of you would be kind enough to take a look.
Dave,
On 27 September 2011 21:05, Dave Tapley wrote:
> Hi all, I've spent a few hours now trying to wrap the wxA
Hi all, I've spent a few hours now trying to wrap the wxAny class, I
just wondered if anyone had given any thought to this (or it's 2.8
predecessor: wxVariant) already?
It's needed because I'm wrapping this functionality:
http://docs.wxwidgets.org/2.9.2/classwx_property_grid_event.html#577d7fb277b
On 20 September 2011 20:57, Dave Tapley wrote:
> Hi Eric,
>
> Am I correct in recalling that you did some of the work to get wxHaskell
> supporting unicode?
>
> I've using wxHaskell with wxWidgets 2.9.2 (the latest development release)
> and it seems that any attempt
On 21 September 2011 21:02, Dave Tapley wrote:
> On 21 September 2011 17:33, Jeremy O'Donoghue
> wrote:
>> Hi Dave,
>>
>> On 20 September 2011 17:58, Dave Tapley wrote:
>>>
>>> On 16 September 2011 23:30, Dave Tapley wrote:
>>>>
On 22 September 2011 09:54, Jeremy O'Donoghue
wrote:
> Hi list,
>
> On 21 September 2011 21:58, Dave Tapley wrote:
>>
>> Hi -devel,
>>
>> As I've alluded to before I have a fairly large number of local
>> patches (mostly gtk/2.9 fixes) in my l
Hi -devel,
As I've alluded to before I have a fairly large number of local
patches (mostly gtk/2.9 fixes) in my local darcs repo.
I think it makes sense to get these on to code.haskell.org at some point.
The good news is I've been fairly meticulous in ensuring each patch is
encapsulated and has a
On 21 September 2011 17:33, Jeremy O'Donoghue
wrote:
> Hi Dave,
>
> On 20 September 2011 17:58, Dave Tapley wrote:
>>
>> On 16 September 2011 23:30, Dave Tapley wrote:
>>>
>>> I presume everyone has a very long compile time when building wxcore?
>
On 21 September 2011 15:29, eric.kow wrote:
>
> On Tue, Sep 20, 2011 at 20:57:37 +0100, Dave Tapley wrote:
> > Am I correct in recalling that you did some of the work to get wxHaskell
> > supporting unicode?
>
> That's right. Mostly swapping char with w_char
>
&g
On 21 September 2011 16:30, David Virebayre wrote:
> Bonjour,
>
> > Ah! Yes! I had error too, but I can't remember how I resolved it, which
> > makes me think I might have just cleaned everything up and started afresh
> > (just with the modified library list); have you tried that?
>
> I'm not sur
On 20 September 2011 18:45, David Virebayre wrote:
> 2011/9/18 D.V. :
> > 2011/9/17 Dave Tapley :
>
> Bonjour Dave, bonjour list !
>
> >> You'll need to edit wxcore/Setup.hs thus:
> > [...]
> >> Hopefully you can adjust this for your needs, and it wo
Hi Eric,
Am I correct in recalling that you did some of the work to get wxHaskell
supporting unicode?
I've using wxHaskell with wxWidgets 2.9.2 (the latest development release)
and it seems that any attempt to get back a wxString in Haskell code will
result in a "Prelude.chr: bad argument:" crash
Hi all, here's a curious problem:
I've found that if I already have issued (from a fresh darcs pull):
$ cabal-dev install ./wx ./wxcore ./wxdirect
I can compile (with "ghc -package-conf ..") and run some test code
successfully.
But then, if I do:
$ cabal-dev install ./wxcore
When I try to compile
On 16 September 2011 23:30, Dave Tapley wrote:
> I presume everyone has a very long compile time when building wxcore?
> Specifically rebuilding everything under src/cpp/ every time..
>
> Has anyone ever looked into avoiding this complete rebuild?
>
I've just spent a few hou
On 15 September 2011 01:40, Dave Tapley wrote:
> Hi all,
>
> Having been hacking around with wrapping new functionality in wxHaskell I
> decided to write a wiki page detailing my findings:
> http://haskell.org/haskellwiki/WxHaskell/Development/Environment
>
> Please feel
On 16 September 2011 22:40, D.V. wrote:
> Bonsoir List,
>
> I'm trying to follow the instructions from
> http://www.haskell.org/haskellwiki/WxHaskell/Development/Environment
> however it's not working.
>
> - cabal-dev add-source wxdirect works fine
> - cabal-dev add-source wxcorehas an error
I presume everyone has a very long compile time when building wxcore?
Specifically rebuilding everything under src/cpp/ every time..
Has anyone ever looked into avoiding this complete rebuild?
Dave,
--
BlackBerry® DevCon
Hi all,
Having been hacking around with wrapping new functionality in wxHaskell I
decided to write a wiki page detailing my findings:
http://haskell.org/haskellwiki/WxHaskell/Development/Environment
Please feel free to edit/comment.
Dave,
-
On 1 September 2011 21:18, Dave Tapley wrote:
> I don't know if this is a known issue which I've stumbled across using the
> Debug.Trace library:
> If you run this sample code¹ you'll see that six lines of output are
> generated.
> Now uncomment the WX import and
I don't know if this is a known issue which I've stumbled across using the
Debug.Trace library:
If you run this sample code¹ you'll see that six lines of output are
generated.
Now uncomment the WX import and try again, you should see only four lines of
output.
It appears anything written to stderr
Hi all,
First of all I'm using wxHaskell from hackage:
$ ghc-pkg list wx*
wx-0.12.1.6
wxcore-0.12.1.7
wxdirect-0.12.1.4
I also so happen to be using a wxWidget-2.8 I compiled locally with debug
on:
$ wx-config --list
Default config is gtk2-unicode-debug-2.8
I've noticed when running
On 29 July 2011 21:49, Dave Tapley wrote:
> Hi Jeremy,
>
> Did you ever make a start wrapping wxPropertyGrid?
> http://permalink.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/1016
>
> I'm going to have a go now.
>
> Dave,
>
In my quest to understand how a c
On 29 July 2011 21:40, Dave Tapley wrote:
> Hi all,
>
> So I can now build the latest from the wxHaskell darcs repo, but only after
> applying the attached patches.
> Quite a lot of them are very "hack it to make it work" patches, but I
> thought I'd offer t
The attached patch resolves this issue for me.
Let me know how you get on.
Dave,
On 28 July 2011 23:08, Dave Tapley wrote:
> Yep, I see this¹ as well, I'll take a look now.
>
> Dave,
>
>
> ¹ http://sourceforge.net/mailarchive/mess
Hi all,
So I can now build the latest from the wxHaskell darcs repo, but only after
applying the attached patches.
Quite a lot of them are very "hack it to make it work" patches, but I
thought I'd offer them to the list for review before cleaning them up.
Comments are welcome.
Dave,
On 29 July 2011 08:54, Heinrich Apfelmus wrote:
> Dave Tapley wrote:
> > Hmm, further to this:
> >
> > $ darcs pull
> > Pulling from "http://code.haskell.org/wxhaskell";...
> > Official wxHaskell darcs repository
> > ***
Yep, I see this¹ as well, I'll take a look now.
Dave,
¹ http://sourceforge.net/mailarchive/message.php?msg_id=27810904
--
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help oft
On 28 July 2011 02:45, Dave Tapley wrote:
> Please find attached a darcs patch file with the changes I had to make to
> build wxcore.
> Feel free to have a look and comment, they are all very much "make it
> compile" changes and I suspect I may have introduced badness (retu
Please find attached a darcs patch file with the changes I had to make to
build wxcore.
Feel free to have a look and comment, they are all very much "make it
compile" changes and I suspect I may have introduced badness (returning a
null pointer).
Unfortunately having made these changes and followi
On 26 July 2011 00:41, Dave Tapley wrote:
> On 25 July 2011 15:49, Jeremy O'Donoghue wrote:
>
>> Hi all,
>>
>> On 25 July 2011 07:45, Eric Y. Kow wrote:
>>
>>> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote:
>>> > A very good s
On 26 July 2011 09:15, Jeremy O'Donoghue wrote:
> On 26 July 2011 06:59, Eric Y. Kow wrote:
>
>> On Tue, Jul 26, 2011 at 00:28:01 +0100, Dave Tapley wrote:
>> > I'm getting the impression that most people are using wxWidgets 2.9 with
>> > wxHaskell
On 26 July 2011 06:59, Eric Y. Kow wrote:
> On Tue, Jul 26, 2011 at 00:28:01 +0100, Dave Tapley wrote:
> > I'm getting the impression that most people are using wxWidgets 2.9 with
> > wxHaskell, is that a fair assumption?
>
> I was surprised by your impression, but
On 25 July 2011 15:49, Jeremy O'Donoghue wrote:
> Hi all,
>
> On 25 July 2011 07:45, Eric Y. Kow wrote:
>
>> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote:
>> > A very good suggestion.
>> > I cabal unpacked wxcore-0.12.1.7 and it appears t
I'm getting the impression that most people are using wxWidgets 2.9 with
wxHaskell, is that a fair assumption?
I've just grabbed the latest dev release (2.9.2) of wxWidgets because I'm
still getting errors trying to compile against the 2.8.10 version I got from
the Ubuntu repositories (I'm going t
On 25 July 2011 15:49, Jeremy O'Donoghue wrote:
> Hi all,
>
> On 25 July 2011 07:45, Eric Y. Kow wrote:
>
>> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote:
>> > A very good suggestion.
>> > I cabal unpacked wxcore-0.12.1.7 and it appears t
On 25 July 2011 07:45, Eric Y. Kow wrote:
> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote:
> > A very good suggestion.
> > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹.
> >
> > Do we know why this fix is in the release, but not
On 24 July 2011 22:57, Eric Y. Kow wrote:
> On Sat, Jul 23, 2011 at 21:26:12 +0100, Dave Tapley wrote:
> > Well I have a response¹ from someone in the wx-dev group saying that the
> > missing GTK constructor "is
> > available in 2.9.2 but chances of this being
or 2.8 with GTK?
Dave,
¹
-- Forwarded message --
From: Vadim Zeitlin
Date: 23 July 2011 12:52
Subject: Re: [wx-dev] [2.8.12] Missing constructor definition in gtk
cursor.h
To: wx-...@googlegroups.com
On Sat, 23 Jul 2011 02:32:12 +0100 Dave Tapley wrote:
DT> It seems that in (at
ell/wxcore/wxcore.cabal
On 22 July 2011 20:06, Dave Tapley wrote:
> Hmm, unfortunately whilst cabal configure now completes successfully, I am
> having a problem when doing cabal build, see output below. Could it be
> related to this:
> http://comments.gmane.org/gmane.comp.lang.haskell
or.h:23:0:
note: wxCursor::wxCursor(const wxCursor&)
On 21 July 2011 23:00, Dave Tapley wrote:
> That was exactly the problem!
>
> Thank you very much Eric :)
>
> Dave,
>
>
>
>
> On 21 July 2011 22:44, Eric Y. Kow wrote:
>
>> Hi Dave,
>>
&g
That was exactly the problem!
Thank you very much Eric :)
Dave,
On 21 July 2011 22:44, Eric Y. Kow wrote:
> Hi Dave,
>
> On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote:
> > I am having trouble compiling wxcore on Ubuntu 10.04.
> > The source I am using I pul
Hi all,
I am having trouble compiling wxcore on Ubuntu 10.04.
The source I am using I pulled with a "darcs get" from hackage, I then
descended into the wxcore directory and did a "cabal configure".
It gives me a "* Missing C libraries: wx_baseu-2.8, wx_baseu_net-2.8,
wx_baseu_xml-2.8..." error,
I
Hi all,
I am having trouble compiling wxcore on Ubuntu 10.04.
The source I am using I pulled with a "darcs get" from hackage, I then
descended into the wxcore directory and did a "cabal configure".
It gives me a "* Missing C libraries: wx_baseu-2.8, wx_baseu_net-2.8,
wx_baseu_xml-2.8..." error,
I
74 matches
Mail list logo
