caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: malc <malc@pulsesoft.com>
Cc: Eric Mangold <ericmangold@myrealbox.com>, caml-list@inria.fr
Subject: Re: [Caml-list] OCaml on Windows please advise
Date: Sat, 9 Nov 2002 08:13:45 +0100	[thread overview]
Message-ID: <20021109071345.GA757@iliana> (raw)
In-Reply-To: <Pine.LNX.4.44.0211090413210.4538-100000@home.oyster.ru>

On Sat, Nov 09, 2002 at 04:21:32AM +0300, malc wrote:
> On Fri, 8 Nov 2002, Eric Mangold wrote:
> 
> > malc wrote:
> > 
> > >Btw. i advice everyone to stay as far away of GTK+ as possible.
> > >  
> > >
> > Why?
> 
> My personal hatered aside, its slow(sluggish if you wish), has terrible 
> keyboad/focus problems. And on Windows all the problems feel ten times
> worse (Modal dialogs anyone? Underlining? Etc etc) Another point is that
> under Windows you have to either live with multimegabyte executables or 
> redistribute gtk dlls, cause virtually no one has them installed. 
> Certainly not my idea of fun.

I think it is ok to redistribute the gtk dlls, but then i suppose you
use lablgtk, and it would be the responsaibility of the lablgtk dlls to
also include the gtk dlls.

All the more reason to have propper binary only windows packaging system
for ocaml.

> Perhaps some of the shortcomings are fixed with 2.x, but i doubt it,
> after poking at the sorces a while back it felt horribly misdesigned, 
> but i wont elaborate on this.

What about using ocamlsdl for interface ?

> P.S. But it has all those themes and looks so lovely at times, well duh
> id rather live without them.

:)))

Friendly,

Sven Luther
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2002-11-09  7:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 21:23 isaac gouy
2002-11-04 23:46 ` SooHyoung Oh
2002-11-05 18:21 ` Nicolas Cannasse
2002-11-05 18:12   ` achrist
2002-11-06  5:53     ` Eric Mangold
2002-11-06 19:54     ` Nicolas Cannasse
2002-11-06 19:58       ` achrist
2002-11-06 20:31         ` jeanmarc.eber
2002-11-07  8:30         ` Xavier Leroy
2002-11-08  0:20           ` achrist
2002-11-08 18:41             ` Nicolas Cannasse
2002-11-08 18:14               ` Sven Luther
2002-11-08 20:20                 ` jeanmarc.eber
2002-11-08 20:47                   ` Sven Luther
2002-11-08 22:43                     ` malc
2002-11-08 23:02                       ` Sven Luther
2002-11-08 23:47                         ` malc
2002-11-09  1:00                           ` Eric Mangold
2002-11-09  1:21                             ` malc
2002-11-09  7:13                               ` Sven Luther [this message]
2002-11-09  9:17                                 ` Olivier Andrieu
2002-11-09 10:08                                   ` Sven Luther
2002-11-12 13:28                                     ` Olivier Andrieu
2002-11-09 17:20                     ` Warp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021109071345.GA757@iliana \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=caml-list@inria.fr \
    --cc=ericmangold@myrealbox.com \
    --cc=malc@pulsesoft.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).