From: "alphablock" <alphablock@wanadoo.fr>
To: "caml-list" <caml-list@yquem.inria.fr>
Subject: [Caml-list] ANN: OCaml meets lego bricks
Date: Sun, 31 Jul 2005 19:34:17 +0200 [thread overview]
Message-ID: <004e01c595f6$14623100$92e7f8c1@oemcomputer> (raw)
Can the rather formal and academic world of OCaml meet the rather artistic
and fairy world of lego toys? I think yes and i wrote Peeroml to prove it.
As far as i know it's a première, functionnal technologies have never been
used in a Lego-CAD context.
The Peeroml package allows one to construct lego parts inventories or
deconstruct them from a lego set catalog.
Download here: http://perso.wanadoo.fr/alphablock/downloads/Peeroml.zip
Here are to some links to popular Lego-CAD tools:
LDRAW:
http://www.ldraw.org/modules.php?op=modload&name=News&file=article&sid=90
MLCAD:
http://www.lm-software.com/mlcad/
LDVIEW:
http://ldview.sourceforge.net/Downloads.html
PEERON inventories:
http://www.peeron.com/
Considerations,
- damien
my lego page: http://perso.wanadoo.fr/alphablock/
next reply other threads:[~2005-07-31 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 17:34 alphablock [this message]
2005-07-31 23:38 ` 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='004e01c595f6$14623100$92e7f8c1@oemcomputer' \
--to=alphablock@wanadoo.fr \
--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