From: Hans Hagen <pragma@wxs.nl>
Subject: Re: 3D Artwork with ConTeXt
Date: Fri, 29 Sep 2006 00:01:55 +0200 [thread overview]
Message-ID: <451C4653.3090302@wxs.nl> (raw)
In-Reply-To: <451C0FCE.7090201@nibua-r.org>
Renaud AUBIN wrote:
>
> Hi all,
>
> I'm now playing with u3d and since I'm at rookie level in ConTeXt dev,
> I have (a lot?) of questions for you.
> First, download http://www.nibua-r.org/ConTeXt/devel/3dartwork.tgz and
> "texexec test-3dartwork". Since I use \externalfigure and u3d mean
> nothing to ConTeXt, I obtain
>
> TeXUtil | running texmfstart rlxtools --identify ./context.u3d
> identify: no decode delegate for this image format `./context.u3d'.
> RlxTools | unable to identify ./context.u3d
>
> Ok, this is normal... I used \placefigure and \externalfigure for
> convenience for the moment since I found natural to use them... How to
> bypass RlxTools ?
hm, maybe we need a feature to mark a category as non-rlx-able
for the moment use \chardef\figurerlxmode\zerocount
it's comparable to movies and so, as long as some kind of dimensions are
known ... i'll look into that later
>
> Now, see t-3dartwork. There is a lot of work. The main idea is to
> split \doPDFinsertiiidartwork into several macros ;) . I need help on:
> 1. What's the best way to define the following macro
>
> \defineiiidartworkprojection[name][type=perspective|orthographic ,
> nf=automatic|explicit , near=number, far=number, fov=number.....]
try to use existing ones: auto instead of automatic
>
> You're welcome to give your opinion on naming convention ;)
>
> 2. Same question for
> \defineiiidartworkview[name][bgr=number, bgg=number, bgb=number (or 3
> floats for bgcol), projection=name, camera= 3 floats (but how?),
> target= idem, up=idem]
>
> I'll use ruby and a magic | (see [NTG-context] run a ruby script and
> use the standard output ???) to calculate C2W and CO...
best is to make that pluggable, so that we can optimize such computations
>
> 3. ... I need to define a macro to setup the 3D annot before to use it
> by \externalfigure or with another brand new macro...
just collect whatever we need to do that and i'll integrate it in such a way that multiple backend are supported as well as mkii and mkiv code
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-09-28 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 18:09 Renaud AUBIN
2006-09-28 22:01 ` Hans Hagen [this message]
2006-09-29 7:53 ` Renaud AUBIN
2006-09-29 14:06 ` Hans Hagen
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=451C4653.3090302@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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;
as well as URLs for NNTP newsgroup(s).