ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: U3D (embedded 3D objects)
Date: Mon, 30 Jan 2006 13:02:37 +0100	[thread overview]
Message-ID: <43DE005D.402@wxs.nl> (raw)
In-Reply-To: <FC6DF933-0600-40E3-9243-9AEC8637CD8D@indiana.edu>

Matthias Weber wrote:
> Hello,
>
> is there support for .u3d files in ConTeXt available or planned? This  
> would take advantage of Acrobat 7 support
> for these 3D data  files. There is a LaTeX package (http:// 
> www.tug.org/tex-archive/macros/latex/contrib/movie15/)
> that does that, and it even works on my Mac.
>   
 (mime type controlled i assume that you refer to support for graphic formats that depend on specific plug-ins; contrary to the older support for movies, such features need a bit more, in particular a relationship between the part of the screen where the stuff is shown and the place where the resources are embedded and refered to. the framework for that has been present for a while now (was implemented right after 6 came out) but in practice only a fraction of the plugins / graphic formats work ok (for instance, smill based graphics/sequences are rather plug-in dependent and buggy); the mediashow stuff on the site and in the distributions implements this renderign)

\definerenderingwindow
  [example]
  [width=320pt,height=150pt,frame=off,
   background=color,backgroundcolor=gray,
   openpageaction=StartCurrentRendering,
   closepageaction=NextPage]% StopCurrentRendering]

\useexternalrendering[example-1][audio/mpeg]                   [eldorado.mp3]
\useexternalrendering[example-2][audio/mpeg]                   [myst-12.mp3]
 \useexternalrendering[example-3][application/x-shockwave-flash][http://localhost/mb.swf] [auto]
 \useexternalrendering[example-4][application/x-shockwave-flash][celebration.swf]
 \useexternalrendering[example-5][video/quicktime]              [p1000726.mov]
 \useexternalrendering[example-6][application/smil]             [quadratic_map.smi]

\def\renderingmenu[#1]%
  {\hbox
     {\setupbuttons[width=2.5em]%
      \button{\symbol[StartRendering]} [StartRendering{#1}]\enspace
      \button{\symbol[StopRendering]}  [StopRendering{#1}]\enspace
      \button{\symbol[PauseRendering]} [PauseRendering{#1}]\enspace
      \button{\symbol[ResumeRendering]}[ResumeRendering{#1}]}}

\renderingmenu[example-1]\blank
\renderingmenu[example-2]\blank
\renderingmenu[example-3]\blank
\renderingmenu[example-4] \placefigure{A ShockWave}{\placerenderingwindow[example][example-4]} \page
\renderingmenu[example-5] \placefigure{A Movie}{\placerenderingwindow[example][example-5]} \page
\renderingmenu[example-6] \placefigure{A Smile}{\placerenderingwindow[example][example-6]}

etc etc 

(see x-res-50 for other examples) 

much of the plugin behaviou can be tuned with key/values in pdf, but it is rather messy (kind of: the plugin provides this, so we need these and those keys): no clear consistent model is present); 

in order for me to provide more detailed support, i first need to cook up a more or less consistent control model (not too much pdf dependent) since whenever possible, i keep context's interface independent of the pdf way of doing things

so, if you want more detailed support for this i need (1) proper conforming resources, and (2) a description of what is needed (which is not the same as a cut and paste from the pdf spec with all possible features) and (3) time and (4) motivation (i.e. it should be usable, used, etc etc;)

implementing pdf related features just because it's in pdf is no longer a good motive since pdf specs/functionality keeps changing, esp in those areas it's rather instable 


-----------------------------------------------------------------
                                          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
-----------------------------------------------------------------

  reply	other threads:[~2006-01-30 12:02 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 [this message]
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
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=43DE005D.402@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).