Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: jon@ffconsultancy.com
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Native-code ocamlbrowser
Date: Tue, 08 Jan 2008 11:46:23 +0900 (JST)	[thread overview]
Message-ID: <20080108.114623.191488419.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <200801071246.48230.jon@ffconsultancy.com>

From: Jon Harrop <jon@ffconsultancy.com>

> May I put in a request for a native-code implementation of the ocamlbrowser 
> tool. It is a great tool for browsing OCaml's many APIs but it gets very slow 
> on big ones, like GLCaml.

Actually, the problem is not the speed of ocaml code, but of Tk's text
widget. Ocamlbrowser uses lots of tags for text coloring, and this
slows the text widget. If somebody knows of a more efficient way to do
it...
Another approach would be to port ocamlbrowser to GTK, but I never
found the time to finish it.

Jacques Garrigue


      reply	other threads:[~2008-01-08  2:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 12:46 Jon Harrop
2008-01-08  2:46 ` Jacques Garrigue [this message]

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=20080108.114623.191488419.garrigue@math.nagoya-u.ac.jp \
    --to=garrigue@math.nagoya-u.ac.jp \
    --cc=caml-list@yquem.inria.fr \
    --cc=jon@ffconsultancy.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