Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Smoke on 3.09.2
Date: Sun, 25 Nov 2007 20:48:30 +0000	[thread overview]
Message-ID: <200711252048.31111.jon@ffconsultancy.com> (raw)
In-Reply-To: <200711252112.52259.san.vu-ngoc@univ-rennes1.fr>

On Sunday 25 November 2007 20:12, Vu Ngoc San wrote:
> Thanks, now it builds fine. And I really thought the problem was gone;
> After resizing the window madly, I was just trying to anwser that
> everything was ok when it suddenly froze exactly as before. :-(
>
> It's maybe a bug of my video driver (xorg-intel). However, I tried to
> reproduce it with glxgears and I couldn't.

Ok. That was a common problem cited by our users before, particularly with 
regard to ATi cards rather than Intel. Perhaps nVidia cards should be a 
requirement under Linux. Hopefully Mac OS X can handle all of the cards that 
it supports.

Have you tried using software rendering via Mesa rather than xorg-intel?

Do you use any other OpenGL software on a regular basis?

> Btw: I don't know if it is useful or not, but your 'clicking and zooming'
> in the tiger demo is quite nice

Yes. Smoke is based upon the hierarchical decomposition of vector scenes into 
non-overlapping tesselations that can be cached on the graphics card. This 
underpins its performance, which is typically an order of magnitude faster 
than Cairo, Adobe Flash or Microsoft Silverlight. Consequently, Smoke is 
ideal for building responsive vector GUIs and OCaml makes it a dream to work 
with.

We've been sitting on the OCaml implementation of Smoke for several years and 
problems like these are preventing us from commercializing it successfully. 
This is a great shame because OCaml is an excellent language for graphics 
programming. I believe the best solution would be an OpenGL-enabled OCaml VM.

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e


  reply	other threads:[~2007-11-25 20:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23 18:08 Floating exception Sebastien Ferre
2007-11-23 22:36 ` [Caml-list] " Jon Harrop
2007-11-24  8:23   ` Vu Ngoc San
     [not found]     ` <200711242236.24433.jon@ffconsultancy.com>
2007-11-25  8:26       ` Vu Ngoc San
2007-11-25 15:35         ` [Caml-list] Smoke on 3.09.2 Jon Harrop
2007-11-25 18:26           ` Jon Harrop
2007-11-25 20:12             ` Vu Ngoc San
2007-11-25 20:48               ` Jon Harrop [this message]
2007-11-25 21:20                 ` Vu Ngoc San
2007-11-25 21:22                   ` Jon Harrop
2007-11-27 10:24   ` [Caml-list] Floating exception Jean-Marc EBER
2007-11-27 11:19     ` Jon Harrop
2007-11-27 13:53       ` Jean-Marc EBER
2007-11-27 15:35       ` Richard Jones
2007-11-27 18:13         ` Jon Harrop
2007-11-28 10:47       ` Vu Ngoc San
2007-11-28 14:48         ` Jon Harrop
2007-11-29 14:39         ` Vu Ngoc San
     [not found] ` <1195900308.7242.19.camel@localhost>
2007-11-26 17:25   ` Sebastien Ferre
2007-11-26 17:56     ` Dmitry Bely
2007-11-27  0:01     ` Richard Jones
2007-11-27  6:56       ` Sebastien Ferre

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=200711252048.31111.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@yquem.inria.fr \
    /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