<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE message PUBLIC
  "-//MLarc//DTD MLarc output files//EN"
  "../../mlarc.dtd"[
  <!ATTLIST message
    listname CDATA #REQUIRED
    title CDATA #REQUIRED
  >
]>

  <?xml-stylesheet href="../../mlarc.xsl" type="text/xsl"?>


<message 
  url="2003/01/4c25a38b0b4a29a0e077f61edf9843aa"
  from="Jacques Garrigue &lt;garrigue@k...&gt;"
  author="Jacques Garrigue"
  date="2003-01-09T09:12:30"
  subject="Re: [Caml-list] Native labltk for Mac OS X"
  prev="2003/01/148644b11cb880a744ab0d853a427c98"
  next="2003/01/ef04a27385c591a8234c591df26a7c87"
  prev-in-thread="2003/01/3f2bfcf520c7508366615239172e76c7"
  next-in-thread="2003/01/55e0693ccdecf869674f92896e045239"
  prev-thread="2003/01/ffa553f7b474e1e0d8832df3cc727cf6"
  next-thread="2003/01/3e3525568cadacef5d886bb7c9a1f04f"
  root="../../"
  period="month"
  listname="caml-list"
  title="Archives of the Caml mailing list">

<thread subject="[Caml-list] Native labltk for Mac OS X">
<msg 
  url="2003/01/8fb51787be19c5a51bde1b15e3640728"
  from="Ken Wakita &lt;wakita@i...&gt;"
  author="Ken Wakita"
  date="2003-01-07T11:27:04"
  subject="[Caml-list] Native labltk for Mac OS X">
<msg 
  url="2003/01/2438719bf3e7b1a34847e33eda7cd713"
  from="Ken Wakita &lt;wakita@i...&gt;"
  author="Ken Wakita"
  date="2003-01-08T08:33:44"
  subject="Re: [Caml-list] Native labltk for Mac OS X">
<msg 
  url="2003/01/eeeaaab137be48beacb56e0a8c60e774"
  from="Sven Luther &lt;luther@d...&gt;"
  author="Sven Luther"
  date="2003-01-08T09:13:13"
  subject="Re: [Caml-list] Native labltk for Mac OS X">
<msg 
  url="2003/01/fa46d32f8dfd212b909a860c3d817be8"
  from="Ken Wakita &lt;wakita@i...&gt;"
  author="Ken Wakita"
  date="2003-01-08T11:17:59"
  subject="Re: [Caml-list] Native labltk for Mac OS X">
<msg 
  url="2003/01/3f2bfcf520c7508366615239172e76c7"
  from="Sven Luther &lt;luther@d...&gt;"
  author="Sven Luther"
  date="2003-01-08T11:23:24"
  subject="Re: [Caml-list] Native labltk for Mac OS X">
<msg 
  url="2003/01/4c25a38b0b4a29a0e077f61edf9843aa"
  from="Jacques Garrigue &lt;garrigue@k...&gt;"
  author="Jacques Garrigue"
  date="2003-01-09T09:12:30"
  subject="Re: [Caml-list] Native labltk for Mac OS X">
<msg 
  url="2003/01/55e0693ccdecf869674f92896e045239"
  from="Ken Wakita &lt;wakita@i...&gt;"
  author="Ken Wakita"
  date="2003-01-09T12:01:02"
  subject="Re: [Caml-list] Native labltk for Mac OS X">
</msg>
<msg 
  url="2003/01/052677e729ac5d19e4510cbd9c516a35"
  from="Sven Luther &lt;luther@d...&gt;"
  author="Sven Luther"
  date="2003-01-09T12:46:08"
  subject="Re: [Caml-list] Native labltk for Mac OS X">
</msg>
</msg>
</msg>
</msg>
</msg>
</msg>
</msg>
</thread>

<contents>
From: Sven Luther &lt;luther@dpt-info.u-strasbg.fr&gt;
&gt; On Wed, Jan 08, 2003 at 08:17:54PM +0900, Ken Wakita wrote:
&gt; &gt; Thanks for the information about gtk-osx.  I will try it.
&gt; &gt; 
&gt; &gt; I continue my effort as I want native ocamlbrowser to browse lablgtk
&gt; &gt; documents.
&gt; 
&gt; Mmm, i think there is also a lablgtk based ocamlbrowser, ..., yes there
&gt; is, altough it is not build per default, needs the ocaml sources, and
&gt; failed to build, altough i did not take time to check the error (it
&gt; speaks about not finding the Parser module).

I indeed tried once to port ocamlbrowser to lablgtk, but quickly
realized that the text widget was much too weak for that.
That attempt is applications/browser, and is only updated once in a
while.

But with GTK2 this shall become possible.
I must just find some time to do that, knowing that ocamlbrowser is
rather dirty code, with lots of dependencies on Tk.

By the way, gtk-osx is 1.2-based, not 2.2.  And it is carbonized
rather cocoated.  Doesn't seem so attractive, but I definitely hope we
get a nice aqua gtk at some point.

Cheers,

Jacques Garrigue
-------------------
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

</contents>

</message>

