wxhaskell-users — General mailing list for wxhaskell users

RE: [wxhaskell-users] Menues problem

[Daan L. <daa...@xs...>]

Hi Gaby,

> The compiler prompts this error
> menuprincipal.hs:23: The last statement in a 'do' construct must be an
expression

This is due to Haskell syntax. You probably have an error in
the layout of the do-statement. Check your code for "tab" characters
and replace them with wi

Thanks,
Gaby


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.545 / Virus Database: 339 - Release Date: 27/11/2003

[wxhaskell-users] Menues problem

[Gaby <ga...@ad...>]

Hi,
I need to create a frame with 3 menus.
I have the following code, but it doesn=92t work. Could you help me?
=20
import Graphics.UI.WX
=20
main :: IO ()
main
  =3D start menuPpal
=20
menuPpal :: IO ()
menuPpal
  =3D do -- the application frame
       f      <- frame         [text :=3D "MAC", clientSize :=3D sz 640 =
480]
=20
       -- Menu Archivo
       archivo   <- menuPane      [text :=3D "&Archivo"]
       cargar <- menuItem archivo [text :=3D "&Cargar", help:=3D "Limpia =
y
carga definiciones desde un archivo"]
       agregar <- menuItem archivo [text :=3D "&Agregar", help:=3D =
"Agrega
definiciones desde un archivo"]
       quit   <- menuQuit archivo [text:=3D"&Salir", help :=3D "Terminar
sesi=F3n MAC", on command :=3D close f]
=20
       -- Menu Definir
       definir   <- menu  [text :=3D "&Definir"]
       entero <- menuItem definir [text :=3D "&Entero"]
       -- Menu Ayuda
       hlp    <- menuHelp      [text :=3D "&Ayuda"]
       about  <- menuAbout hlp [text :=3D "&Acerca de...", help :=3D =
"Acerca
de MAC"]
=20
       -- create statusbar field
       status <- statusField   [text :=3D "Bienvenidos a MAC"]
=20
       -- Setea los men=FAes
       set f [ statusBar :=3D [status]
             , menuBar   :=3D [archivo,definir,hlp]
             ,on (menu about) :=3D infoDialog f "Acerca de MAC" "WinMAC =
v
0.0.0.1"
             ]
=20
The compiler prompts this error
menuprincipal.hs:23: The last statement in a 'do' construct must be an
expression
=20
Thanks,
Gaby

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.545 / Virus Database: 339 - Release Date: 27/11/2003
=20

Re: [wxhaskell-users] problem with scrolledWindow

[David R. <dr...@jd...>]

On Mon, Dec 01, 2003 at 03:28:44PM +0100, Daan Leijen wrote:
> >>Use "virtualSize" to set the scrolling area. Use "scrollRate" to set the
> >>speed of the scrollbars.
> >
> >In the example program below, I can't resize the window smaller than the
> >size required to fit all the labels, and thus no scrollbars show up.  Is
> >there any way to use layout to arrange widgets in a scrolled window and
> >still get scrollbars? Or is there some other method that I should be using
> >to arrange the widgets in a scrolled window?
> 
> Honestly, I have no idea :-) Maybe you can find some info in the
> wxWindows documentation? Furthermore, it is rather strange for a UI
> to put widgets inside a scrollable window -- normally all widgets
> are either visible, or in a notebook or something, but not dynamically
> placed.

I don't think putting widgets in scrolled windows is that uncommon.  The
only reason I can see to avoid it would be if you were afraid the memory
overhead of using a large number of widgets would be prohibitive.  It is
pretty standard that tree widgets exist inside scrollable
windows--otherwise they won't typically fit on your screen.  In fact, any
time you have a non-fixed number of widgets they should be in a scrollable
window--e.g. an image browser that displays thumbnails might want to have
each thumbnail be a widget, and they'd obviously need to be in a scrolled
window.

> So, 1) it might be that this is just not something that is properly
> supported on wxWindows, or 2) you need to call specific wxWindows
> functions to get the sizers running correctly within scrollable windows,
> or 3) you shouldn't use sizers here but place all widgets yourself at
> specific spots (and install a repaint handler).

The impression I get from the wxwin docs is that 4) it should work
automatically.  Quoting the section on wxScrolledWindow:

"The most automatic and newest way is to simply let sizers determine the
scrolling area. This is now the default when you set an interior sizer into
a wxScrolledWindow with wxWindow::SetSizer. The scrolling area will be set
to the size requested by the sizer and the scrollbars will be assigned for
each orientation according to the need for them and the scrolling increment
set by wxScrolledWindow::SetScrollRate."

My only guess is that someone is calling wxWindow::SetSizeHints and setting
the minimum size to be equal to the size of the scrolledWindow's contents.
At least with wxHaskell 0.3 I used to be able to make the scrolledWindow
work right by calling SetSizeHints to reset the size hints to their default
values (all arguments being -1).
-- 
David Roundy
http://civet.berkeley.edu/droundy/

Re: [wxhaskell-users] problem with scrolledWindow

[Daan L. <daa...@xs...>]

Hi David,

>> Use "virtualSize" to set the scrolling area. Use "scrollRate" to set the
>> speed of the scrollbars.
>
> In the example program below, I can't resize the window smaller than the
> size required to fit all the labels, and thus no scrollbars show up.  Is
> there any way to use layout to arrange widgets in a scrolled window and
> still get scrollbars? Or is there some other method that I should be using
> to arrange the widgets in a scrolled window?

Honestly, I have no idea :-) Maybe you can find some info in the
wxWindows documentation? Furthermore, it is rather strange for a UI
to put widgets inside a scrollable window -- normally all widgets
are either visible, or in a notebook or something, but not dynamically
placed. So, 1) it might be that this is just not something that is
properly supported on wxWindows, or 2) you need to call specific
wxWindows functions to get the sizers running correctly within scrollable
windows, or 3) you shouldn't use sizers here but place all widgets yourself
at specific spots (and install a repaint handler).

If the case is 1) or 2), we/I might be able to solve it using some
abstractions in Haskell. If it is 1) or 3), we should probably report
it as a bug to the wxWindows dev's. Thanks for the example program
though, it makes a good test case.

> I've basically just been trying random permutations,

Good luck ;-)
  Daan



> but haven't been able to guess how to get
> scrollbars.
>
> import Graphics.UI.WX
>
> main = start test
>
> test = do
>     f <- frame [text := "Testing wxHaskell"]
>     quit <- button f [text := "Cancel", on command := close f]
>     scrolled <- scrolledWindow f [virtualSize := size 500 500,
>                                   scrollRate := size 20 20]
>     set scrolled [layout := margin 5 $ column 5 labels]
>     set f [layout := column 0 [fill $ widget scrolled,
>                                margin 5 $ row 5 [hglue, widget quit, hspace 20]],
>            clientSize := size 100 100 -- this doesn't seem to have any effect at all.
>           ]
>     return ()
>
> labels = l 30 where l 0 = []
>                     l n = label ("Label "++show n) : l (n-1)

Re: [wxhaskell-users] problem with scrolledWindow

[David R. <dr...@jd...>]

On Mon, Dec 01, 2003 at 09:10:02AM -0500, David Roundy wrote:
> I've basically just been trying random permutations, but haven't been
> able to guess how to get scrollbars.

I've gotten scrollbars by setting virtualSize *after* setting the layout,
but this still doesn't allow me to resize the window such that the
scrollbars do any good.  It just adds a lot of blank space that I can
scroll around.  And the scrollbars disappear when I resize the window...
-- 
David Roundy
http://www.abridgegame.org

Re: [wxhaskell-users] problem with scrolledWindow

[David R. <dr...@jd...>]

On Mon, Dec 01, 2003 at 01:49:16PM +0100, Daan Leijen wrote:
> >Is there some trick I need to know in order to get a scrolledWindow with
> >scrollbars?
> 
> Use "virtualSize" to set the scrolling area. Use "scrollRate" to set the
> speed of the scrollbars.

In the example program below, I can't resize the window smaller than the
size required to fit all the labels, and thus no scrollbars show up.  Is
there any way to use layout to arrange widgets in a scrolled window and
still get scrollbars? Or is there some other method that I should be using
to arrange the widgets in a scrolled window? I've basically just been
trying random permutations, but haven't been able to guess how to get
scrollbars.

import Graphics.UI.WX

main = start test

test = do
    f <- frame [text := "Testing wxHaskell"]
    quit <- button f [text := "Cancel", on command := close f]
    scrolled <- scrolledWindow f [virtualSize := size 500 500,
                                  scrollRate := size 20 20]
    set scrolled [layout := margin 5 $ column 5 labels]
    set f [layout := column 0 [fill $ widget scrolled,
                               margin 5 $ row 5 [hglue, widget quit, hspace 20]],
           clientSize := size 100 100 -- this doesn't seem to have any effect at all.
          ]
    return ()

labels = l 30 where l 0 = []
                    l n = label ("Label "++show n) : l (n-1)
-- 
David Roundy
http://www.abridgegame.org

Re: [wxhaskell-users] Re: wxHaskell on win32 without the DOS-box

[David R. <dr...@jd...>]

On Mon, Dec 01, 2003 at 01:32:39PM +0100, Daan Leijen wrote:
> Another solution that I am contemplating is the use of reflective
> attributes where the constructor would look in the list of attributes to
> see if an initial size is specified. This would solve your troubles but
> it is kind of unsatifying that this would create a distinction between:
> 
> >f <- frame [attr := expr]
> 
> and
> 
> >f <- frame []
> >set f [attr := expr]
> 
> 
> Anyhow, I think that I will implement the latter solution anyway,
> so your program will work as expected in the next release.

This does make the WX layer a bit confusing, but it would bring it closer
to the way wxWindows works, which would make things a bit easier for people
moving to wxHaskell from wxWindows, so I'm all for it.
-- 
David Roundy
http://www.abridgegame.org

Re: [wxhaskell-users] problem with scrolledWindow

[Daan L. <daa...@xs...>]

Hi David,

> The refit function is definitely a nice addition, but I've run into
> difficulties again in not been able to figure out how to get my scrolled
> window working when it contains widgets (in a layout) that resize
> themselves and then call refit.  When they do this, the scrolled window
> gets resized to be big enough to contain the widgets, and won't let the
> user make it any smaller.  I'm not sure what the problem here is.  The
> layout should be determining the virtualSize of the scrolled window, not
> its actual size as it seems to be doing.

It is the correct behaviour for "refit" -- just not the behaviour that
you want :-) I think we need a special refit operation that does re-layout
the child widgets, but increases/decreases the "virtualSize" of a scrolled
window instead of its clientSize.

I am kind of busy with other things but I hope to look into it
somewhere this week, but if you feel like hacking, I have
added some implementation hints to the end of this mail.

> Is there some trick I need to know in order to get a scrolledWindow with
> scrollbars?

Use "virtualSize" to set the scrolling area. Use "scrollRate" to set the
speed of the scrollbars.

> Totally unrelated:
>
> It seems that wxhaskell doesn't compile with ghc 6.2 because parsec has
> moved into its own package.

I heard about that, however, I have decided not to support 'unreleased' ghc
versions actively. For now, you can probably just add

> HCFLAGS += -package parsec

to the makefile to get things working.

All the best,
  Daan.


---------------------------------
hints for implementing refitVirtual
---------------------------------

In WXCore/Layout.hs are the following functions:

windowRefitMinimal and windowReLayoutMinimal:

windowRefitMinimal just gets the parent window and calls relayout:

  windowReFitMinimal :: Window a -> IO ()
  windowReFitMinimal w
    = do p <- windowGetFrameParent w
         windowReLayout p

windowRelayout gets the sizer of a window and calls "windowFit"
to re-layout the child widgets.

  windowReLayoutMinimal w
    = do windowLayout w
         szr <- windowGetSizer w
         when (not (objectIsNull szr)) (sizerSetSizeHints szr w)
         windowFit w

At the end, the new clientSize of a window is set.
For a "windowReLayoutVirtual", one probably doesn't want
to call "windowFit" but set the virtual size of a window
instead??

Re: [wxhaskell-users] Re: wxHaskell on win32 without the DOS-box

[Daan L. <daa...@xs...>]

Hi Martin,

> Both tricks works perfectly, however the program launch still looks a bit
> nasty because the main window always starts up with a default width/height
> and the resizes to whatever I specified. This happens even though I use:
>
>         f <- frameFixed [text := "Hello", clientSize := size 100 100]
>
> Is there a known work-around for this problem?

This behaviour is a somewhat intertwined with wxWindows itself.
The "WX" layer tries to abstract from the basic wxWindows calls (in WXCore)
and is very dynamic: that is, a frame is first created with some
unspecified width and height, and later it is changed to the "clientSize"
specified in the attribute list. One would expect that the window
would only be shown once the layout is set, but unfortunately, that is
not how wxWindows works.

I could solve this by requiring an initial widht and height as a
parameter to "frame" (or "frameFixed") but I feel that is somewhat
against the spirit of the WX design.

Another solution that I am contemplating is the use of reflective
attributes where the constructor would look in the list of attributes
to see if an initial size is specified. This would solve your troubles
but it is kind of unsatifying that this would create a distinction
between:

> f <- frame [attr := expr]

and

> f <- frame []
> set f [attr := expr]


Anyhow, I think that I will implement the latter solution anyway,
so your program will work as expected in the next release.


All the best,
  Daan.

Re: [wxhaskell-users] Re: wxHaskell on win32 without the DOS-box

[Arjan v. I. <af...@cs...>]

Hi Martin,

> [..] the main window always starts up with a default width/height
> and the resizes to whatever I specified. This happens even though I 
> use:
>
>        f <- frameFixed [text := "Hello", clientSize := size 100 100]
>
> Is there a known work-around for this problem?

Maybe creating it invisible and then setting visible to True after 
adding all your components...? Or you could buy a really fast computer 
:-)

> Also, there is another issue which I'm abit worried about, the 
> executable
> generated by GHC is 6.42 megs.

You can "strip" the executable. This gets rid of everything that is 
linked to it but unnecessary.
And then you can internally compress it using UPX ( 
http://upx.sourceforge.net/ )
The latter saves a lot. The Helium compiler goes from 6 megabytes to 
less than one.

Regards, Arjan

Re: [wxhaskell-users] Re: wxHaskell on win32 without the DOS-box

[Martin O. <re...@mn...>]

Okay, I've tried both your trick and the other which was posted by Arjan.
Thanks for the help, I really appreciate it! :-)

Both tricks works perfectly, however the program launch still looks a bit
nasty because the main window always starts up with a default width/height
and the resizes to whatever I specified. This happens even though I use:

        f <- frameFixed [text := "Hello", clientSize := size 100 100]

Is there a known work-around for this problem?

Also, there is another issue which I'm abit worried about, the executable
generated by GHC is 6.42 megs. Perhaps it's just me, but it's that alot
for a program which just creates a window with title "hello" ?!
Can I fix this without having to force the end-user to install some DLLs etc?


Regards,
/m

At 12:24 2003-11-30, 72...@in... wrote:
>Hi Martin. This is a more general GHC's issue you can fix linking with the
>-optl-mwindows flag. (ref. chapter 11.2 in the GHC User's guide).

[wxhaskell-users] Re: wxHaskell on win32 without the DOS-box

[<72...@in...>]

Hi Martin. This is a more general GHC's issue you can fix linking with the
-optl-mwindows flag. (ref. chapter 11.2 in the GHC User's guide).

Regards.

Jose David.




---------------------------------------------
Este mensaje lo ha enviado un Alumno de la Universidad de Malaga.
http://www.alumnos.uma.es/

[wxhaskell-users] problem with scrolledWindow

[David R. <dr...@jd...>]

I've gotten around to running my code using wxhaskell 0.4 on the mac.

The refit function is definitely a nice addition, but I've run into
difficulties again in not been able to figure out how to get my scrolled
window working when it contains widgets (in a layout) that resize
themselves and then call refit.  When they do this, the scrolled window
gets resized to be big enough to contain the widgets, and won't let the
user make it any smaller.  I'm not sure what the problem here is.  The
layout should be determining the virtualSize of the scrolled window, not
its actual size as it seems to be doing.

Is there some trick I need to know in order to get a scrolledWindow with
scrollbars? With wxhaskell 0.3 I had a trick using windowSetSizeHints to
set the size hints for the scrolledWindow to their defaults, but this
doesn't seem to work if the children of the scrolled window call refit.
:(

Totally unrelated:

It seems that wxhaskell doesn't compile with ghc 6.2 because parsec has
moved into its own package.
-- 
David Roundy
http://www.abridgegame.org

[wxhaskell-users] wxHaskell on win32 without the DOS-box

[Martin O. <re...@mn...>]

Hi,

Is it possible to compile a wxHaskell GUI program and not get a DOS-box 
appearing behind the GUI?


Regards,
/m

Re: [wxhaskell-users] A couple problems with wxhaskell-0.4 on Mac

[Jeffrey S. <je...@ma...>]

Daan:

> This problem was fixed last Monday, so I guess that you have
> either an older binary installer -- or getting an older one
> from a mirror. Just try to get a version from a big mirror.

Yes, I downloaded a new version and everything works really well
now.  It solves my resizing problems also.  I just have to call
refit.

Thanks very much!

Regards,

Jeff Scofield
Seattle

Re: [wxhaskell-users] linker error

[Brandon M. M. <br...@it...>]

There is no need to modify wxWindows. The problem seems to be that
libwx_gtk_gl-2.4.so is not included when linking a wxHaskell proram.
Adding wx_gtk_gl-2.4 to the extra_libraries entry in the package
description fixed this for me. Your version numbers might be different and
there is probably a better way to do this. I don't know much about
building libraries, but it seems like there should be a way to record in
libwxcore.a that you need to link with this code.

Brandon

Re: [wxhaskell-users] Problem with wxHaskell

[Arjan v. I. <af...@cs...>]

Hi Wojtek,

> But actually, the speed is very slow. When I drew the rectangle just by
> calling putPixel on appropriate points, on 2.5 GHz machine, even after
> compilation with -O2 switch it worked slowly.

Haskell is fast enough and wxWindows itself, too. I think that calling
wxWindows from Haskell takes a little time, though. And that adds up if you
try to draw hundreds of pixels. I believe there is a faster way by drawing
pixels to a buffer and then displaying that buffer. Anyway, drawing the
rectangles works fine, I think.

Arjan

Re: [wxhaskell-users] A couple problems with wxhaskell-0.4 on Mac

[Daan L. <daa...@xs...>]

Hi Jeff,


This problem was fixed last Monday, so I guess that you have
either an older binary installer -- or getting an older one
 from a mirror. Just try to get a version from a big mirror.


Let me know if that works for you,
All the best,

  Daan.



On Wed, 12 Nov 2003 11:47:39 -0800, Jeffrey A. Scofield <je...@ma...> wrote:On Thu, 13 Nov 2003 13:00:15 +0100, Daan Leijen <daa...@xs...> wrote:

> Hi Jeff,
>
> This problem was fixed last Monday, so I guess that you have
> either an older binary installer -- or getting an older one
>  from a mirror. Just try to get a version from a big mirror.
>
> Let me know if that works for you,
> All the best,
>   Daan.
>
> On Wed, 12 Nov 2003 11:47:39 -0800, Jeffrey A. Scofield <je...@ma...> wrote:
>
>> Greetings wxHaskell users,
>>
>> Here are some problems I have with the wxhaskell-0.4 binary release for
>> Mac OS X.
>>
>> 1.  The installer fails.  This seems to be due to some erroneous file
>>     names in the post-install (and post-upgrade) scripts.
>>
>> 2.  If I do the post-install step manually (i.e., add the wx packages to
>>     ghc's package database), there is an error at link time.  The linker
>>     claims to be looking for a file that doesn't even exist in the
>>     wxhaskell-0.4 installation.  However, the file *did* exist under
>>     wxhaskell-0.3.  (I wiped my wxhaskell-0.3 installation completely
>>     before running the 0.4 installer.)
>>
>> I've submitted two bug reports with more details on these problems.
>> Let me know if I should repeat the details on this mailing list.
>>
>> wxHaskell is very cool.  That's why I want to get it working on my Mac!
>> (I'd also love to see a binary rpm of 0.4 for Linux, by the way.)
>>
>> Regards,
>> Jeff Scofield (PhD)
>> Seattle
>>
>>
>> -------------------------------------------------------
>> This SF.Net email sponsored by: ApacheCon 2003,
>> 16-19 November in Las Vegas. Learn firsthand the latest
>> developments in Apache, PHP, Perl, XML, Java, MySQL,
>> WebDAV, and more! http://www.apachecon.com/
>> _______________________________________________
>> wxhaskell-users mailing list
>> wxh...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>>
>

Re: [wxhaskell-users] linker error

[Daan L. <daa...@xs...>]

Hi Johannes,

I have only tested OpenGL on windows, and there it works fine. When
I build on freeBSD, I get exactly the same kind of errors....

I don't have much time now to look into this problem, but when I look
into the Makefile of wxWindows (wxGTK-2.4.2/build/Makefile) I see that
there are separate rules for libwx_gtk_gl.xxx that include "glcanvas.o".

So, it seems that you probably need to make wxWindows with a special argument
to get it to use the gtk_gl version. Maybe you could fix it manually by
adding the rule: OBJECTS += glcanvas.o
This is of course a terrible hack, but maybe you can find on the wxWindows
site more information about openGL on unixes.

Sorry for not being able to fix this for you anytime soon, but hopefully
you can find a solution for yourself (and us),
All the best,
  Daan.

On Wed, 12 Nov 2003 20:51:31 +0100, Johannes Goetz <jg...@jg...> wrote:

> Hi there!
>
> I know that some people on this list have encountered the same problem like I did (do). It seems to be impossible to link ANY sample distributed with wxhaskell. Everything compiles fine but the linker complains about some missing symbols that are obviously needed when writing opengl-programs...
> After some reading about wxwindows-installation and glcanvas-stuff I managed to install the latest wxwindows (Linux GTK version) on my debian system. I compile wxwindows like this:
> ./configure --with-gtk --with-opengl --enable-glcanvas
> make
> make install
> All libraries (even *gtk_gl*) were built correctly... I AM ABLE TO COMPILE the wxwindows samples. Everything works as expected. glcanvas-opengl-examples are doing just fine. No problem here.
> I then recompiled / installed wxhaskell using the following commands:
> ./configure
> make
> make install
> (ups, dont know if I deleted configure cache... could it be the problem???)
> There were no errors. Everything in the right place.
> Please help me with this. I REALLY would LIKE to use wxhaskell for my project. Thank you very much in advance for your answers.
>
> Johannes
>
>
> PS: Linker output:
>
>> $ ghc Paint.hs -package wx -package wxcore -package wx
>> /usr/local/lib/libwxc-0.4.so: undefined reference to `wxGLCanvas::SwapBuffers()'
>> /usr/local/lib/libwxc-0.4.so: undefined reference to `wxGLCanvas::SetColour(char const*)'
>> /usr/local/lib/libwxc-0.4.so: undefined reference to `wxGLCanvas::wxGLCanvas[in-charge](wxWindow*, wxGLCanvas const*, int, wxPoint const&, wxSize const&, long, wxString const&, int*, wxPalette const&)'
>> /usr/local/lib/libwxc-0.4.so: undefined reference to `wxGLCanvas::SetCurrent()'
>> /usr/local/lib/libwxc-0.4.so: undefined reference to `wxGLCanvas::wxGLCanvas[in-charge](wxWindow*, int, wxPoint const&, wxSize const&, long, wxString const&, int*, wxPalette const&)'
>> collect2: ld returned 1 exit status
>
>
>
> PS: Do you really need to --enable-glcanvas?
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>

Re: [wxhaskell-users] A couple problems with wxhaskell-0.4 on Mac

[Daan L. <daa...@xs...>]

Hi Jeff,

This problem was fixed last Monday, so I guess that you have
either an older binary installer -- or getting an older one
 from a mirror. Just try to get a version from a big mirror.

Let me know if that works for you,
All the best,
  Daan.

On Wed, 12 Nov 2003 11:47:39 -0800, Jeffrey A. Scofield <je...@ma...> wrote:

> Greetings wxHaskell users,
>
> Here are some problems I have with the wxhaskell-0.4 binary release for
> Mac OS X.
>
> 1.  The installer fails.  This seems to be due to some erroneous file
>     names in the post-install (and post-upgrade) scripts.
>
> 2.  If I do the post-install step manually (i.e., add the wx packages to
>     ghc's package database), there is an error at link time.  The linker
>     claims to be looking for a file that doesn't even exist in the
>     wxhaskell-0.4 installation.  However, the file *did* exist under
>     wxhaskell-0.3.  (I wiped my wxhaskell-0.3 installation completely
>     before running the 0.4 installer.)
>
> I've submitted two bug reports with more details on these problems.
> Let me know if I should repeat the details on this mailing list.
>
> wxHaskell is very cool.  That's why I want to get it working on my Mac!
> (I'd also love to see a binary rpm of 0.4 for Linux, by the way.)
>
> Regards,
> Jeff Scofield (PhD)
> Seattle
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>

Re: [wxhaskell-users] build problems on SuSE Linux 8.2

[Daan L. <daa...@xs...>]

Hi David,

> Hello there,
>   I tried a build of wxHaskell, following the instructions as published.

Markus was right, you are following build instructions
for "wxWindows" instead of wxHaskell.

Just type "./configure" without making a build directory etc.

All the best,
  Daan.

> Here's what
> happened. Regards,
>
> David
> ----------------------------------------------------------------------------
>
> Script started on Sun 09 Nov 2003 08:11:41 GMT
> dw@shinjuku:~/Documents/wxhaskell-0.4> uname -a
> Linux shinjuku 2.4.20-4GB #1 Mon Mar 17 17:54:44 UTC 2003 i686 unknown unknown
> GNU/Linux
> dw@shinjuku:~/Documents/wxhaskell-0.4> mkdir build
> dw@shinjuku:~/Documents/wxhaskell-0.4> cd build
> dw@shinjuku:~/Documents/wxhaskell-0.4/build> ../configure
>
> ./config.search: ./config.search: No such file or directory
> ./config.search: ./config.search: No such file or directory
>  ./config.search:
> ./config.search: No such file or directory
> ./config.search: ./config.search: No such file or directory
>  install libraries at :
> /usr/local/lib                                           ./config.search:
> ./config.search: No such file or
> directory
> error:
>   Unable to find the 'wx-config' program:
> wx-config
>  Maybe you forgot to run 'make install' on wxWindows?
>   Otherwise, add the
> install directory of wx-config to your path.
> dw@shinjuku:~/Documents/wxhaskell-0.4/build>
> Script done on Sun 09 Nov 2003 08:12:30 GMT
>
>
>
> Ok, let's try some other things...
>
>
> Script started on Sun 09 Nov 2003 08:15:29 GMT
> dw@shinjuku:~/Documents/wxhaskell-0.4> ./configure --with  -odbc
> error: Unknown option "--with-odbc". Use "--help" to show valid options.
>
> dw@shinjuku:~/Documents/wxhaskell-0.4> ./configure --with-glcanvas
> error: Unknown option "--with-glcanvas". Use "--help" to show valid options.
>
> dw@shinjuku:~/Documents/wxhaskell-0.4> ./configure --enable-wave
> error: Unknown option "--enable-wave". Use "--help" to show valid options.
> Script done on Sun 09 Nov 2003 08:16:58 GMT
>
>
>
>
> ---------------------------------
> http://www.dcs.ex.ac.uk/~dwakelin
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>

[wxhaskell-users] re: linker error

[Johannes G. <jg...@jg...>]

Don't know if it helps, but thats the output if ldd -r -d libwxc-0.4.so:


# ldd -d -r libwxc-0.4.so
        libwx_gtk-2.4.so => /usr/local/lib/libwx_gtk-2.4.so (0x400b4000)
        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40566000)
        libm.so.6 => /lib/libm.so.6 (0x4061e000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40640000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x40648000)
        libc.so.6 => /lib/libc.so.6 (0x4069b000)
        libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x407ce000)
        libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x408ec000)
        libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x40920000)
        libgthread-1.2.so.0 => /usr/lib/libgthread-1.2.so.0 (0x40923000)
        libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x40926000)
        libdl.so.2 => /lib/libdl.so.2 (0x40947000)
        libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x4094a000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40952000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40960000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0x40a1c000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40a3d000)
        libtiff.so.3 => /usr/lib/libtiff.so.3 (0x40a5b000)
        libz.so.1 => /usr/lib/libz.so.1 (0x40a9e000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
undefined symbol: 
_ZN10wxGLCanvasC1EP8wxWindowiRK7wxPointRK6wxSizelRK8wxStringPiRK9wxPalette    
(./libwxc-0.4.so)
undefined symbol: 
_ZN10wxGLCanvasC1EP8wxWindowPKS_iRK7wxPointRK6wxSizelRK8wxStringPiRK9wxPalette        
(./libwxc-0.4.so)
undefined symbol: _ZN10wxGLCanvas10SetCurrentEv (./libwxc-0.4.so)
undefined symbol: _ZN10wxGLCanvas9SetColourEPKc (./libwxc-0.4.so)




Thanks,
Johannes

[wxhaskell-users] linker error

[Johannes G. <jg...@jg...>]

Hi there!

I know that some people on this list have encountered the same problem 
like I did (do). It seems to be impossible to link ANY sample 
distributed with wxhaskell. Everything compiles fine but the linker 
complains about some missing symbols that are obviously needed when 
writing opengl-programs...
After some reading about wxwindows-installation and glcanvas-stuff I 
managed to install the latest wxwindows (Linux GTK version) on my debian 
system. I compile wxwindows like this:
./configure --with-gtk --with-opengl --enable-glcanvas
make
make install
All libraries (even *gtk_gl*) were built correctly... I AM ABLE TO 
COMPILE the wxwindows samples. Everything works as expected. 
glcanvas-opengl-examples are doing just fine. No problem here.
I then recompiled / installed wxhaskell using the following commands:
./configure
make
make install
(ups, dont know if I deleted configure cache... could it be the problem???)
There were no errors. Everything in the right place.
Please help me with this. I REALLY would LIKE to use wxhaskell for my 
project. Thank you very much in advance for your answers.

Johannes


PS: Linker output:

> $ ghc Paint.hs -package wx -package wxcore -package wx
> /usr/local/lib/libwxc-0.4.so: undefined reference to 
> `wxGLCanvas::SwapBuffers()'
> /usr/local/lib/libwxc-0.4.so: undefined reference to 
> `wxGLCanvas::SetColour(char const*)'
> /usr/local/lib/libwxc-0.4.so: undefined reference to 
> `wxGLCanvas::wxGLCanvas[in-charge](wxWindow*, wxGLCanvas const*, int, 
> wxPoint const&, wxSize const&, long, wxString const&, int*, wxPalette 
> const&)'
> /usr/local/lib/libwxc-0.4.so: undefined reference to 
> `wxGLCanvas::SetCurrent()'
> /usr/local/lib/libwxc-0.4.so: undefined reference to 
> `wxGLCanvas::wxGLCanvas[in-charge](wxWindow*, int, wxPoint const&, 
> wxSize const&, long, wxString const&, int*, wxPalette const&)'
> collect2: ld returned 1 exit status



PS: Do you really need to --enable-glcanvas?

[wxhaskell-users] A couple problems with wxhaskell-0.4 on Mac

[Jeffrey A. S. <je...@ma...>]

Greetings wxHaskell users,

Here are some problems I have with the wxhaskell-0.4 binary release for
Mac OS X.

1.  The installer fails.  This seems to be due to some erroneous file
    names in the post-install (and post-upgrade) scripts.

2.  If I do the post-install step manually (i.e., add the wx packages to
    ghc's package database), there is an error at link time.  The linker
    claims to be looking for a file that doesn't even exist in the
    wxhaskell-0.4 installation.  However, the file *did* exist under
    wxhaskell-0.3.  (I wiped my wxhaskell-0.3 installation completely
    before running the 0.4 installer.)

I've submitted two bug reports with more details on these problems.
Let me know if I should repeat the details on this mailing list.

wxHaskell is very cool.  That's why I want to get it working on my Mac!
(I'd also love to see a binary rpm of 0.4 for Linux, by the way.)

Regards,
Jeff Scofield (PhD)
Seattle

AW: [wxhaskell-users] build problems on SuSE Linux 8.2

[<Mar...@in...>]

Sorry, forget it. I'm already tired.
Cheers,
Markus

--
Markus Schnell

> -----Urspr=FCngliche Nachricht-----
> Von: wxh...@li...=20
> [mailto:wxh...@li...] Im=20
> Auftrag von Schnell Markus (CPR ET)
> Gesendet: Mittwoch, 12. November 2003 17:57
> An: D.W...@ex...; wxh...@li...
> Betreff: AW: [wxhaskell-users] build problems on SuSE Linux 8.2
>=20
>=20
> try ./configure instead of ../configure
>=20
> --
> Markus Schnell
> Infineon Technologies AG, CPR ET
> Tel +49 (89) 234-20875
>=20
>=20
> > -----Urspr=FCngliche Nachricht-----
> > Von: wxh...@li...=20
> > [mailto:wxh...@li...] Im=20
> > Auftrag von dwakelin
> > Gesendet: Sonntag, 9. November 2003 09:38
> > An: wxh...@li...
> > Betreff: [wxhaskell-users] build problems on SuSE Linux 8.2
> >=20
> >=20
> > Hello there,
> >   I tried a build of wxHaskell, following the instructions as=20
> > published.=20
> > Here's what=20
> > happened. Regards,
> >   =20
> > David=20
> > --------------------------------------------------------------
> > --------------
> > =20
> > Script started on Sun 09 Nov 2003 08:11:41 GMT=20
> > dw@shinjuku:~/Documents/wxhaskell-0.4> uname -a=20
> > Linux shinjuku 2.4.20-4GB #1 Mon Mar 17 17:54:44 UTC 2003=20
> > i686 unknown unknown=20
> > GNU/Linux=20
> > dw@shinjuku:~/Documents/wxhaskell-0.4> mkdir build=20
> > dw@shinjuku:~/Documents/wxhaskell-0.4> cd build=20
> > dw@shinjuku:~/Documents/wxhaskell-0.4/build> ../configure
> >                                     =20
> > ./config.search: ./config.search: No such file or directory=20
> > ./config.search: ./config.search: No such file or directory
> >  ./config.search:=20
> > ./config.search: No such file or directory=20
> > ./config.search: ./config.search: No such file or directory
> >  install libraries at :=20
> > /usr/local/lib                                          =20
> > ./config.search:=20
> > ./config.search: No such file or=20
> > directory=20
> > error:
> >   Unable to find the 'wx-config' program:=20
> > wx-config
> >  Maybe you forgot to run 'make install' on wxWindows?
> >   Otherwise, add the=20
> > install directory of wx-config to your path.=20
> > dw@shinjuku:~/Documents/wxhaskell-0.4/build>=20
> > Script done on Sun 09 Nov 2003 08:12:30 GMT
> >=20
> >=20
> > =20
> > Ok, let's try some other things...
> >=20
> > =20
> > Script started on Sun 09 Nov 2003 08:15:29 GMT=20
> > dw@shinjuku:~/Documents/wxhaskell-0.4> ./configure --with  -odbc=20
> > error: Unknown option "--with-odbc". Use "--help" to show=20
> > valid options.
> > =20
> > dw@shinjuku:~/Documents/wxhaskell-0.4> ./configure --with-glcanvas=20
> > error: Unknown option "--with-glcanvas". Use "--help" to show=20
> > valid options.
> > =20
> > dw@shinjuku:~/Documents/wxhaskell-0.4> ./configure --enable-wave=20
> > error: Unknown option "--enable-wave". Use "--help" to show=20
> > valid options.=20
> > Script done on Sun 09 Nov 2003 08:16:58 GMT
> >=20
> >=20
> >=20
> >=20
> > ---------------------------------
> > http://www.dcs.ex.ac.uk/~dwakelin
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.Net email sponsored by: ApacheCon 2003,
> > 16-19 November in Las Vegas. Learn firsthand the latest
> > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > WebDAV, and more! http://www.apachecon.com/
> > _______________________________________________
> > wxhaskell-users mailing list
> > wxh...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
> >=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>=20