From: "Walter B. Rader" <wrader@OCF.Berkeley.EDU>
To: caml-list@inria.fr
Subject: [Caml-list] Skinnable windowing system in OCaml
Date: Wed, 9 Jan 2002 17:41:21 -0800 (PST) [thread overview]
Message-ID: <Pine.SOL.4.44.0201091729100.18807-100000@apocalypse.OCF.Berkeley.EDU> (raw)
I'm developing a windowing system (a la X Windows) in OCaml using SDL
(Simple DirectMedia Library) which is a cross-playform graphics library
written in C.
I want the end user to be able to configure the "look-and-feel" of the
windowing system at runtime, and I'm not sure the best way to go about
doing this. Currently, the window manager calls upon a class called
"decorator" that performs the window decorations (title bar, frame, etc.)
The decorator class could be sub-classed (or perhasp redefined?) to
change the behavior.
Any thoughts on the "best way"? Is it possible to compile several
different modules that contain a decorator class (with, say, a Windows 95
theme, a MacOS theme, etc.) and dynamically load one? Would loading one
redefine the "decorator" class that was defined prior to the loading?
If I understand correctly, the dynamic loading works with byte-code
compiled modules? If the main program were compiled to native code, would
they work together seamlessly?
Are there any resources (books, papers, how-to's about "this kind of
thing" (e.g. loading modules at run-time to redefine default behavior)? I
know of plenty books about designing OSs but haven't found any about
writing windowing systems.
Any suggestions about anything even remotely related to the above
subject/questions would be more than welcome!
Thanks,
Walter Rader
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2002-01-10 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 1:41 Walter B. Rader [this message]
2002-01-10 23:14 ` John Prevost
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=Pine.SOL.4.44.0201091729100.18807-100000@apocalypse.OCF.Berkeley.EDU \
--to=wrader@ocf.berkeley.edu \
--cc=caml-list@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