From: Renaud AUBIN <aubin@nibua-r.org>
Subject: Re: U3D (embedded 3D objects)
Date: Wed, 26 Jul 2006 01:30:01 +0200 [thread overview]
Message-ID: <44C6A979.4060701@nibua-r.org> (raw)
In-Reply-To: <44C4C6F9.6060505@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1994 bytes --]
Hans Hagen a écrit :
>
>indeed pdfannot is what we need; however, the first thing is to figure out what kind of control we want (probably best from within javascript); in your sampe i see pretty raw pdf code in the key/val pairs, which is something alien to context
>
>- what features make sense
>- what features do we expect to be stable
>
>Hans
>
>
How to do that in the ConTeXt way ? ;) I have read spec-tpd.tex but
didn't know much...
Take care of the heart attack.... (I've done it the rookie way, reversed
from movie15)
\starttext
\xdef\uthreedfilename{pa10}
\pdfobj {<</Subtype/P/FOV 30/PS/Min>>}%
\pdfrefobj\pdflastobj%
%
\pdfobj {<<%
/MS/M% define the view as C2W matrix
/CO 1200% orbital radius
/P \the\pdflastobj\space 0 R%
/C2W [-1.0 0.0 0.0 0.0 -1.0 0.0 0.0 0.0 1.0 0.000000000000000000
-600.000000000000000000 -3200.000000000000000000]%
/XN(Default)% name of the view appearing in the drop down list
/BG<</CS/DeviceRGB/C[1 1 1]>>%
>>}\pdfrefobj\pdflastobj%
\xdef\defaultview{/3DV << /N \the\pdflastobj\space 0 R >>}
\pdfobj stream %
attr {%
/Subtype/U3D/VA [\the\pdflastobj\space0 R] /DV/F%
}%
file {\uthreedfilename.u3d}%
\pdfrefobj\pdflastobj%
\xdef\iiidstream{\the\pdflastobj}
\pdfobj stream {}\pdfrefobj\pdflastobj%
\xdef\apdict{/AP << /N \the\pdflastobj\space 0 R >>}
\pdfannot width 200pt height 200pt depth 200pt {% don't know how to deal
with w,h and d !!!
/Subtype/3D%
/F 4% we cannot put F 5 here; bug in Reader; 3D annot would be
/T (\uthreedfilename.u3d)% disabled even if plugin were
available
/Contents (3D Object (model/u3d))% mime type
/NM (pa10)% label
/P 0 0 R%
\apdict%
\defaultview%
/3DI true%
/3DD \iiidstream\space 0 R% 3D stream object
/3DA << /A/PV/AIS/I/D/PI/DIS/I >>%
}%
\stoptext
[-- Attachment #1.2: Type: text/html, Size: 2757 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-07-25 23:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 14:41 Matthias Weber
2006-01-30 12:02 ` Hans Hagen
2006-01-30 20:36 ` Matthias Weber
2006-01-30 22:22 ` Hans Hagen
2006-01-31 1:24 ` Matthias Weber
2006-01-31 10:27 ` Hans Hagen
2006-01-31 15:30 ` Matthias Weber
2006-01-31 16:37 ` Hans Hagen
2006-01-31 16:46 ` Matthias Weber
2006-01-31 22:45 ` Hans Hagen
2006-02-01 15:51 ` Henning Hraban Ramm
2006-02-01 11:07 ` Hans Hagen
2006-07-22 1:18 ` Renaud AUBIN
2006-07-22 15:44 ` Hans Hagen
2006-07-22 17:18 ` aubin
2006-07-24 9:48 ` Hans Hagen
2006-07-24 9:55 ` Renaud AUBIN
2006-07-23 0:27 ` Renaud AUBIN
2006-07-24 9:46 ` Hans Hagen
2006-07-24 10:15 ` Renaud AUBIN
2006-07-24 13:11 ` Hans Hagen
2006-07-25 18:36 ` Renaud AUBIN
2006-07-25 23:30 ` Renaud AUBIN [this message]
2006-07-25 23:37 ` Renaud AUBIN
2006-01-31 14:42 ` Renaud AUBIN
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=44C6A979.4060701@nibua-r.org \
--to=aubin@nibua-r.org \
--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).