From: "Chris King" <colanderman@gmail.com>
To: "Jon Harrop" <jon@ffconsultancy.com>
Cc: "Jacques Garrigue" <garrigue@math.nagoya-u.ac.jp>, caml-list@inria.fr
Subject: Re: [Caml-list] Revolution
Date: Wed, 23 May 2007 23:21:39 -0400 [thread overview]
Message-ID: <875c7e070705232021u2897410cgbcec425e4ef73c97@mail.gmail.com> (raw)
In-Reply-To: <200705240238.37972.jon@ffconsultancy.com>
On 5/23/07, Jon Harrop <jon@ffconsultancy.com> wrote:
> 1. A new GUI library written in a functional style that renders controls as
> vector graphics via Smoke. Everything is rendered using OpenGL but abstracted
> behind Smoke.
I don't know anything about Smoke, but part of my secret plan behind
my O'Caml Reactive Toolkit project is to allow one to develop a pretty
GUI widget set using OpenGL (or Cairo or what-have-you) and have much
of the GUI functionality (such as layout management) already there.
Whether I get as far as implementing an OpenGL-based widget set in the
nine weeks I'm working with Jane St. Capital remains to be seen (I
sort of doubt it, given the amount of other work I'll have), but I'm
keeping that goal in mind as I design it so the infrastructure to
support it will be there.
(Re OpenGL reentrancy, in O'Caml RT multiple OpenGL contexts are
handled in such a way that they are invisible to the user.)
I've also been considering the possibility of writing the library in
such a way that it also compiles under F#, or compiles with a few
changes, but right now I don't know enough about F# to know whether
that's at all possible (especially since I make use of objects,
polymorphic variants, and private types for software engineering
purposes, and would like to avoid giving them up).
- Chris
next prev parent reply other threads:[~2007-05-24 3:21 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 22:10 Teaching bottomline, part 3: what should improve David Teller
2007-05-22 22:22 ` [Caml-list] " William D. Neumann
2007-05-23 13:07 ` David Teller
2007-05-22 22:26 ` Erik de Castro Lopo
2007-05-22 23:16 ` skaller
2007-05-23 2:46 ` David Thomas
2007-05-23 9:19 ` Vincent Hanquez
2007-05-23 12:49 ` Brian Hurt
2007-05-23 13:36 ` Gerd Stolpmann
2007-05-23 14:06 ` skaller
2007-05-23 14:54 ` Florian Hars
2007-05-23 15:11 ` Brian Hurt
2007-05-23 21:48 ` Vincent Hanquez
2007-05-24 8:04 ` Markus E.L.
2007-05-24 8:32 ` Vincent Hanquez
2007-05-24 9:51 ` skaller
2007-05-24 11:22 ` Vincent Hanquez
2007-05-23 13:55 ` David Teller
2007-05-22 23:19 ` skaller
2007-05-23 10:41 ` Richard Jones
2007-05-23 13:04 ` David Teller
2007-05-24 13:51 ` Richard Jones
2007-05-24 14:00 ` Robert Fischer
2007-05-24 14:00 ` Jon Harrop
2007-05-24 14:20 ` Robert Fischer
2007-05-24 14:34 ` David Teller
2007-05-24 14:21 ` skaller
2007-05-22 23:39 ` Jon Harrop
2007-05-23 18:54 ` Richard Jones
2007-05-23 19:27 ` Robert C Fischer
2007-05-23 19:34 ` Brian Hurt
2007-05-23 19:54 ` Robert Fischer
2007-05-23 21:46 ` Jon Harrop
2007-05-23 22:14 ` Jacques Garrigue
2007-05-24 1:38 ` Revolution Jon Harrop
2007-05-24 2:40 ` [Caml-list] Revolution skaller
2007-05-24 3:21 ` Chris King [this message]
2007-05-24 14:24 ` David Teller
2007-05-24 13:40 ` [Caml-list] Teaching bottomline, part 3: what should improve Brian Hurt
2007-05-23 19:29 ` Jon Harrop
2007-05-23 20:20 ` David Teller
2007-05-24 14:18 ` Jon Harrop
2007-05-24 14:23 ` skaller
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=875c7e070705232021u2897410cgbcec425e4ef73c97@mail.gmail.com \
--to=colanderman@gmail.com \
--cc=caml-list@inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
--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