From: Jason Gibson <jason@infosite.com>
To: sven.luther@wanadoo.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Tcl/Tk and RH 9
Date: Tue, 12 Aug 2003 00:11:44 -0700 [thread overview]
Message-ID: <5.2.1.1.0.20030811224954.01a65b48@infosite.com> (raw)
>What about looking at Cairo (Ex Xr/Xc) and either bind to that, or
>reimplement their protocol in ocaml. Cairo is early enough in its design
>that it can still be influenced enough if someone looks at it, and
>points them problems related to doing ocaml bindings.
>
...
>Basically it is a vector rendering framework, linked to SVG graphics,
>and which should enable to have a vector rendering model (on top of the
>X RENDER extension i think), but which can target various graphic
>systems, including X, local image buffers and Postscript and PDF as
>planned output support. I don't know about windows support, but MacOSX
>support should not be all that difficult to add, and since they also
>have an OpenGL rendering path, it should run on every OpenGL supported
>plateform.
...
>Friendly,
>Sven Luther
I'm glad to see that I wasn't the only one who thought that xr\cairo\svg
would make a
good base for windowing toolkits. I was thinking that having the low level
functionality
vector based would allow you to do lots of interesting things. For
example, you could
do what xml has done, ie allow people to separate out the different classes
of data easily.
Like how html has presentation\data all bunched together, our vector gui
could have the
layout\data\communications\etc all separated out, allowing for better
functionality on
each level. One of the layers of xml-style data could be a communication
path, allowing your
program to be less dependant on the gui model (like an event loop). It
would also let you
expose your gui program to other programs, available for use in a scripted
environment.
One could build a gui application like one draws a picture. Each shape
could be made
separate, so doing things like floating toolbars would be trivial. You
just move that particular
shape, and all its children to a new location. You could group
programs together easier by
joining shapes and doing transformations on them. Maybe you could build
gui components
as little programs that you connect together, like how you use pipes to
link a chain of programs.
JG
-------------------
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
next reply other threads:[~2003-08-12 7:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 7:11 Jason Gibson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-09 2:03 [Caml-list] version 7 beta typing change? skaller
2003-08-09 12:10 ` Jacques Garrigue
2003-08-09 16:33 ` [Caml-list] Tcl/Tk and RH 9 skaller
2003-08-10 1:43 ` [Caml-list] " Jacques Garrigue
2003-08-10 1:53 ` Alexander V. Voinov
2003-08-10 21:26 ` skaller
2003-08-10 23:15 ` Eray Ozkural
2003-08-10 23:24 ` Eray Ozkural
2003-08-11 0:41 ` Matt Gushee
2003-08-11 1:20 ` Eray Ozkural
2003-08-11 2:02 ` skaller
2003-08-11 8:38 ` Sven Luther
2003-08-11 9:41 ` Christoph Bauer
2003-08-10 20:15 ` skaller
2003-08-11 9:17 ` Christoph Bauer
2003-08-12 4:14 ` 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=5.2.1.1.0.20030811224954.01a65b48@infosite.com \
--to=jason@infosite.com \
--cc=caml-list@inria.fr \
--cc=sven.luther@wanadoo.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