To: patrick at watson.org
Cc: lablgtk at kaba.or.jp
Subject: Re: Improving lablgtk installation
In-Reply-To: <Pine.BSF.3.96.1010220123117.13321C-100000 at fledge.watson.org>
References: <20010220221732D.garrigue at kurims.kyoto-u.ac.jp>
	<Pine.BSF.3.96.1010220123117.13321C-100000@fledge.watson.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010301101751B.garrigue at kurims.kyoto-u.ac.jp>
Date: Thu, 01 Mar 2001 10:17:51 +0900
From: Jacques Garrigue <garrigue at kurims.kyoto-u.ac.jp>
Lines: 32

From: Patrick M Doane <patrick at watson.org>

Sorry for the slow answer,

> > What you need to use threads is gtkThread.cmx, which is installed if
> > your system supports threads in native code (ocaml was compiled with
> > option -with-pthread).  gtkThreadInit is only useful for toplevels.
> 
> Right, but gtkThreadInit is simply a call to GtkThread.start (). Are you
> saying that native code applications should not call GtkThread.start ()?

Yes. Or rather, it they need to call it, they should do it explicitly,
otherwise they will probably exit because they have no main thread.
 
> I don't think there are too many advantages for you since you have a
> permanent connection on the net. But for those of us without such
> resources, or time to setup a large suite of tools, SourceForge offers
> these nice features:
> 
>   * Secure CVS access for project members
>   * Mailing list support through mailman with archiving
>   * Bug/issue tracking
>   * Discussion boards
>   * Ample space for web page
>   * FTP server for file distributions
>   * Compilation Farm for testing with other operating systems

Indeed, nothing we do not have (except discussion board, but the
mailing is not overcrowded anyway). But a bit of publicity is never
bad. I'll look when I have some time...

     Jacques