ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "luigi scarso" <luigi.scarso@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: embedding 3d pdf
Date: Wed, 26 Nov 2008 10:57:45 +0100	[thread overview]
Message-ID: <fe8d59da0811260157o5469be22w2bd8779ca1c6bc80@mail.gmail.com> (raw)
In-Reply-To: <1214.212.192.224.123.1227687404.squirrel@squirrelmail.iaas.msu.ru>


[-- Attachment #1.1: Type: text/plain, Size: 943 bytes --]

On Wed, Nov 26, 2008 at 9:16 AM, Michail Vidiassov <master@iaas.msu.ru>wrote:

> Dear All,
>
> Renaud Aubin wrote:
> > See http://www.nibua-r.org/ConTeXt/devel/
>
> while the macros there are a great improvement from
> what was posted on the list and look extandable for my purposes
> (thanks, Renaud),
> the other question remains - does it make sense to try to implement
> 3d model embedding in proper way for public use now or the underlying
> luatex/context part has not been developed/updated yet?
>
> LuaTeX roadmap promised that
> "Think of annotations and object management. The first code will show up
> later in 2008."
> Did it?
> Is there a ConTeXt API to it?
> Is it planned to come in some future?
> Or  spec-pdf dated 1997.09.20 is what we are to live with?
>
>              Sincerely, Michail
>
>
BTW, If you are able to make some samples with context mkiv, please do them
and then wikifi it.
Something is better than nothing .

[-- Attachment #1.2: Type: text/html, Size: 1466 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2008-11-26  9:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22 15:55 Michail Vidiassov
2008-11-22 17:23 ` Renaud Aubin
2008-11-22 17:33   ` luigi scarso
2008-11-22 17:53     ` Renaud Aubin
2008-11-22 17:50       ` luigi scarso
2008-11-22 17:54         ` luigi scarso
2008-11-22 18:07         ` Renaud Aubin
2008-11-22 18:15           ` Renaud Aubin
2008-11-22 17:51       ` Idris Samawi Hamid ادريس سماوي حامد
2008-11-22 17:53         ` luigi scarso
2008-11-22 17:57         ` Matija Šuklje
2008-11-22 18:16           ` Idris Samawi Hamid ادريس سماوي حامد
2008-11-22 18:03         ` Renaud Aubin
2008-11-22 18:10         ` Renaud Aubin
2008-11-22 17:57       ` Renaud Aubin
2008-11-22 17:46   ` Renaud Aubin
2008-11-26  8:16   ` Michail Vidiassov
2008-11-26  9:48     ` Hans Hagen
2008-11-26  9:57     ` luigi scarso [this message]
2008-11-28  8:27       ` Michail Vidiassov
2008-11-28  9:05         ` luigi scarso
2009-01-01 10:55           ` Michail Vidiassov

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=fe8d59da0811260157o5469be22w2bd8779ca1c6bc80@mail.gmail.com \
    --to=luigi.scarso@gmail.com \
    --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).