Hello Eric, Saturday, July 21, 2007, 9:29:30 AM, you wrote:

...

can anyone provide wxHaskell already compiled/compilable with ghc 6.6.1 on Windows?

Please try the darcs version darcs get http://darcs.haskell.org/wxhaskell

thanks. should i follow building instructions from homepage/ directory or there are another one? -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com

Hello Eric, I found that wxc Visual Studio Project File for wxWidgets-2.4.2 is broken now. And I think that I forgot to notice some awkward point for Windows.... So I put newer Windows binary on my project's file space. http://sourceforge.net/project/showfiles.php?group_id=168626 On Sun, 22 Jul 2007 23:20:44 +0900, Eric Kow wrote:

...

...

Please try the darcs version darcs get http://darcs.haskell.org/wxhaskell

thanks. should i follow building instructions from homepage/ directory or there are another one?

-- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/

Hellow Bulat, On Sun, 22 Jul 2007 23:20:44 +0900, Eric Kow wrote:

...

...

Please try the darcs version darcs get http://darcs.haskell.org/wxhaskell

thanks. should i follow building instructions from homepage/ directory or there are another one?

I don't remember if this is documented anywhere, sadly:

It's

./configure make make install make wx make wx-install

This instruction isn't perfect when you want to build on Windows with Visual Studio. You must add --with-msc option to ./configure command, if you want to use Visual Studio's dll. http://wxhaskell.sourceforge.net/building-msc.html If you want to use GLCanvas or ODBC support, you must modify wxWidgets' include\wx\msw\setup.h file to enable Option. To use GLCanvas, we must set "#define wxUSE_GLCANVAS 1" ODBC support is simillar, And ODBC support isn't work with Unicode support. wxWidgets 2.4.2 doesn't support ODBC with Unicode. I think 2.6.4 or greater can use ODBC support with Unicode. But I can't where is bug now. wxWidgets 2.4.2's project file is broken. I point out and attched patch for this problem in previous mail, so you can build that with patch. http://www.haskell.org/pipermail/haskell-cafe/2007-July/029438.html I think wxc-2.6.3 project file depends on wxSTC. So you must build wxSTC before building wxc on Windows, if you want to build wxc with wxWidgets 2.6.3, or modifying wxc-2.6.3 to support greater version (e.g. wxWidgets 2.6.4). This problem comes from merging wxStyledTextCntrl support. If we want to avoid it, we must add building option with STC support or not in project file, or add wxc-withSTC-* project file. http://sourceforge.net/mailarchive/forum.php?thread_name=d80c8a540701110913h3e28284aua137ef299f259ff6%40mail.gmail.com&forum_name=wxhaskell-users Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/

Hello Neil, Saturday, July 21, 2007, 11:46:59 PM, you wrote:

...

can anyone provide wxHaskell already compiled/compilable with ghc 6.6.1 on Windows?

This is precisely the reason I switched to Gtk2Hs - Duncan provides Windows installers as each new GHC release comes out. If wxHaskell wants to stand any chance as an alternative GUI framework there really _must_ be Windows binaries released concurrently with GHC versions...

i've taken a look at gtk2hs, but 2 reasons forced me to give wxHaskell a try: - native appearance - current lack of high-level properties machinery in gtk2hs -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com

Hi

...

- native appearance

I think that's pretty good these days, the native theme on Windows has been getting better and better from Gtk+ 2.6 to the current 2.10

wxHaskell used to be 10 times better than Gtk, now its about twice as good. The Gtk developers are seriously addressing some of the mistakes, and the work is going in the direction, so my hope is that it will hit nearly perfect one day. Duncan even volunteered to file the bug report etc. on any bugs I spot and screenshot. Thanks Neil

On Wed, 2007-07-25 at 16:57 +0400, Bulat Ziganshin wrote:

Hello Duncan,

Monday, July 23, 2007, 4:02:42 AM, you wrote:

...

...

i've taken a look at gtk2hs, but 2 reasons forced me to give wxHaskell a try:

- native appearance

...

I think that's pretty good these days, the native theme on Windows has been getting better and better from Gtk+ 2.6 to the current 2.10

it's good and i don't complain about its quality. what i mean here is just what it looks like Unix apps, not like native windows ones. afaiu, GTK paints all controls itself without using native controls and therefore controls look at Windows just the same as in Unix

There's really no such thing as Windows native controls any more, at least not ones that any apps actually use. You'll note that Internet Explorer, MS Office and VisualStudio all paint their own custom control set that are similar but not exactly the same as the native controls (eg those used by NotePad/WordPad). Gtk+ uses themes too, and on Windows it uses a Windows theme. This uses the native WinXP themeing dll. It's possible to use any of the Unix themes on windows, but nobody would ever want to do that. As noted before, the differences between the Gtk+ Windows theme and the common 'native' windows control sets have been getting less and less with each recent release of Gtk+.

...

...

- current lack of high-level properties machinery in gtk2hs

...

Actually Gtk2Hs and wxHaskell have a very similar properties api (they both stole it off of an older Haskell GUI lib) and we're planning to make further improvements to that in the current development cycle.

yes, there is API but as far as i see, it's not yet fully implemented for each type of control. for example, in TreeDemo.hs and DirList.hs examples there are lots of handmade calls - compare them to FileBrowse.hs wxHaskell example (although i may be unfair here, but it seems that wxHaskell example uses properties more extensively)

Yes, that's what we're addressing in the current dev cycle, making more extensive use of properties and removing the duplication between the properties and the direct set/get calls. Duncan

On Wed, 2007-07-25 at 14:58 +0100, Neil Mitchell wrote:

Hi

...

There's really no such thing as Windows native controls any more, at least not ones that any apps actually use. You'll note that Internet Explorer, MS Office and VisualStudio all paint their own custom control set that are similar but not exactly the same as the native controls (eg those used by NotePad/WordPad).

But the native controls are a lot nicer. The fact that MS Office, IE and VS are all annoying doesn't meant that Haskell developers should be excluded from writing non-annoying user interfaces.

Sure :-)

...

Gtk+ uses themes too, and on Windows it uses a Windows theme. This uses the native WinXP themeing dll.

Either 1) it does, but very very badly, or 2) it doesn't. Even the ones that look similar are not quite right. It is getting better though, but I'm not sure they are using the theme DLL (purely from the results, I have no idea what the code says)

I think it uses it mainly when you're using the TellyTubbies WinXP themes. It also uses it for colours etc.

...

Yes, that's what we're addressing in the current dev cycle, making more extensive use of properties and removing the duplication between the properties and the direct set/get calls.

:( - please let the set/get calls remain, since the properties are likely to only be available with non-H98 types. My PropLang wrapper also has to use set/get directly.

The current plan is to mark them as deprecated and remove them from the haddock documentation but not to remove them completely yet. The properties themselves do not have non-H98 types, but the current set function uses existential types. We could provide a simpler version of set that doesn't have the nice syntax and uses H98 types. Duncan

Hi Bulat,

can you please give screenshots? in particular, i see unix-like style in TreeCtrl and scrollbars in examples i've built from gtk2hs.

The scroll bars are OK: http://www-users.cs.york.ac.uk/~ndm/temp/proof.png The appearance is native, but the arrow on the left shouldn't be disabled when scrolled to the full left. They are close, but have got things wrong all over the place. Thanks Neil