Interactive documents

Interactive documents

[MANUEL GONZALEZ SUAREZ]

[-- Attachment #1: Type: text/html, Size: 6089 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: Interactive documents

[Hans Hagen]

On 11-7-2012 09:35, MANUEL GONZALEZ SUAREZ wrote:
>
> Hi
> My name is Manuel Gonzalez and I am a teacher of Classical Greek at the
> University of Oviedo(Spain). So far I've been using LaTeX but recently I have
> discovered the extraordinary possibilities of ConTeXt. However, I have
> continuously problems which I solved as I can (I'm a complete newbie and I do
> not know the details of programming languages​​). Well, theproblem is the
> following: I want to make an interactive document and I copy the code that
> appears in "Context an excursion", page 65, but did not appear in the final
> document navigation tools, such as EXIT, STOP, etc.. What could be the cause?

it helps if you post a small example of your test source here

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------


___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: Interactive documents

[Wolfgang Schuster]

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


Am 11.07.2012 um 09:35 schrieb MANUEL GONZALEZ SUAREZ:

> 
> Hi
> My name is Manuel Gonzalez and I am a teacher of Classical Greek at the University of Oviedo (Spain). So far I've been using LaTeX but recently I have discovered the extraordinary possibilities of ConTeXt. However, I have continuously problems which I solved as I can (I'm a complete newbie and I do not know the details of programming languages​​). Well, theproblem is the following: I want to make an interactive document and I copy the code that appears in "Context an excursion", page 65, but did not appear in the final document navigation tools, such as EXIT, STOP, etc.. What could be the cause?
> 


\setuplayout
  [width=12cm,
   rightedge=2cm]

\setupinteraction
  [state=start,
   menu=on]

\setupinteractionmenu
  [right]
  [state=start,
   align=middle,
   background=screen,
   frame=on,
   width=broad,
   style=smallbold,
   color=]

\startinteractionmenu[right]
  \startbut [content]    Content \stopbut
  \startbut [index]      Index   \stopbut
  \vfill
  \startbut [ExitViewer] Stop    \stopbut
\stopinteractionmenu

\starttext

\completecontent %\showframe

\dorecurse{4}
  {\chapter{Chapter #1}\index{chapter #1}
   \input knuth\page}

\completeindex

\stoptext

Wolfgang

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

[-- Attachment #2: Type: text/plain, Size: 485 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: Interactive documents

[Wolfgang Schuster]

Am 11.07.2012 um 10:12 schrieb Hans Hagen:

> On 11-7-2012 09:35, MANUEL GONZALEZ SUAREZ wrote:
>> 
>> Hi
>> My name is Manuel Gonzalez and I am a teacher of Classical Greek at the
>> University of Oviedo(Spain). So far I've been using LaTeX but recently I have
>> discovered the extraordinary possibilities of ConTeXt. However, I have
>> continuously problems which I solved as I can (I'm a complete newbie and I do
>> not know the details of programming languages​​). Well, theproblem is the
>> following: I want to make an interactive document and I copy the code that
>> appears in "Context an excursion", page 65, but did not appear in the final
>> document navigation tools, such as EXIT, STOP, etc.. What could be the cause?
> 
> it helps if you post a small example of your test source here

The manuals uses

  \setupinteractionmenu
    [mymenu]
    [{Content[content]},
     {Index[index]},
     {\vfill},
     {Stop[ExitViewer]}]

to set the content for the menu and not

  \startinteractionmenu[mymenu]
    \startbut [content] Content \stopbut
    …
  \stopinteractionmenu


What’s also missing is a note that you have to adjust the layout (decrease
the text width and set rightwidth) to let the menu appear on the page.


@Hans: Can you take a look at the output from my example in the other mail
because the first button of the menu appears in the header of the document.

Wolfgang
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: Interactive documents

[Hans Hagen]

At 07:59 PM 2/10/01 +0100, Giuseppe Bilotta wrote:
>Hello,
>a couple of question on interactive documents.
>
>Since I use interaction also on "printable" documents,
>I find a feature to be a nuisance: when I click on a link,
>Acrobat sets the veiw to "fit in window", which I don't like.
>I assume the problem being using page destinations instead of
>named ones ... is there and advantage in this? is it possible
>to turn it off (so that the proper destination is reached,
>preserving the zoom factor)?

Page destinations are more save, especially in the past viewers have been
buggy with respect to named destination [some funny sort / search
optimization bugs in acroread 2 and 3] so this is why i always use page
destinations when possible; right from the start context supported the dual
scheme (although acro v 1 only had page dest while for instance dviwindo
only had neamed ones]. Page dest are more efficient too, but they need more
housekeeping in the macro package.

Concerning your problem: in spec-fdf you wile find something \setuppageview
which you can change into: 

\definespecial\dosetuppageview#1%
  {\processaction
     [#1]
     [\v!passend=>\def\PDFpageviewkey{   fit}%
                  \def\PDFpageviewwrd{  /Fit},
      \v!breedte=>\def\PDFpageviewkey{  fith}%   % watch the v-h
                  \def\PDFpageviewwrd{ /FitH},   % swapping here
       \v!hoogte=>\def\PDFpageviewkey{  fitv}%   % and here and
                  \def\PDFpageviewwrd{ /FitV},   % here too
%   \v!standaard=>\def\PDFpageviewkey{  xyz 0 0 0}%
%                 \def\PDFpageviewwrd{ /XYZ 0 0 0},
      \s!unknown=>\def\PDFpageviewkey{   fit}%
                  \def\PDFpageviewwrd{  /Fit}]%
   \edef\PDFpageview{/View [\PDFpageviewwrd]}}

with a aslightly adapted \dodosetupinteraction: 

\def\dodosetupinteraction[#1]% % \dosetupinteraction == special
  {\getparameters[\??ia][#1]%
   \doifelse{\@@iastatus}{\v!start}
     {\iflocation\else
        \showmessage{\m!interactions}{2}
          {\ifusepagedestinations\space(PAGE)\fi}%
        \global\locationtrue
      \fi}
     {\iflocation
        \showmessage{\m!interactions}{3}
          {\ifusepagedestinations\space(PAGE)\fi}%
        \global\locationfalse
      \fi}%
   \iflocation
     \enablemode [\systemmodeprefix\v!interactie]%
   \else
     \disablemode[\systemmodeprefix\v!interactie]%
   \fi
   \dosetuppageview{\@@iafocus}%
   \doifsomething{\@@iabereken}
     {\doregistercalculationset\@@iabereken}%
   \doifelse{\@@iastrut}{\v!ja}
     {\locationstruttrue}
     {\locationstrutfalse}%
   \doifelse{\@@iaklik}{\v!ja}
     {\highlighthyperlinkstrue}
     {\highlighthyperlinksfalse}%
   \doifelse{\@@iasplitsen}{\v!ja}
     {\locationsplittrue}
     {\locationsplitfalse}%
   \doifelse{\v!nieuw}{\@@iascherm}
     {\gotonewwindowtrue}
     {\gotonewwindowfalse}%
   \doifelse{\@@iapagina}{\v!ja}
     {\global\usepagedestinationstrue}
     {\global\usepagedestinationsfalse}}

and a setup like this: 

\setupinteraction[focus=width,state=start]

you have more control (width, height, fit). 

There is no way to preserve the current zoom, although the pdf spec
suggests it. If you find the right way ... 

Zooming and alike has always been buggy / fuzzy in pdf. This is why i never
finished proper thread support (and probably will remove it). It has to do
with the fact that annotations have a separate layer in pdf.  

>Second question: I have a document to be produced in both
>electronic and printable version. I use the \coupledocument
>feature (but it seems not to work).

It's a two stage def: 

\coupledocument
  [alternative] % symbolic name 
  [docu-p] % name of paper version 
  [chapter,section,subsection]
  [the printable version]

\setuphead
  [chapter,section,subsection]
  [file=alternative]

and the same for the screen doc. 

>I produce the two documents this way:
>
>texexec --pdf --mode=screen --result=usatex1-e usatex1
>
>texexec --pdf usatex1
>
>I have to use this order because creating the screen version
>deletes the print version (--result renames the file after
>completion). Two questions:

tex has fixed output names, so there is no other decent way; this is why i
use two times a suffix in that case (-s and -p). 

>1) MiKTeX 2.0 allows to specify the resulting filename;
>shouldn't texexec take advantage of this when --result is
>specified?

dunno, since i don't run miktex i cannot test it, also, the main name is to
be the original in order not to get problems with all kind of internal refs
and names and so; at most you would save a couple of renames which does not
take that much time 

>2) Is it possible to obtain both documents with a single run?

Eh, i don't think so, since I suppose that you use different layouts. 

Hans
-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------

Interactive documents

[Giuseppe Bilotta]

Hello,
a couple of question on interactive documents.

Since I use interaction also on "printable" documents,
I find a feature to be a nuisance: when I click on a link,
Acrobat sets the veiw to "fit in window", which I don't like.
I assume the problem being using page destinations instead of
named ones ... is there and advantage in this? is it possible
to turn it off (so that the proper destination is reached,
preserving the zoom factor)?

Second question: I have a document to be produced in both
electronic and printable version. I use the \coupledocument
feature (but it seems not to work).

I produce the two documents this way:

texexec --pdf --mode=screen --result=usatex1-e usatex1

texexec --pdf usatex1

I have to use this order because creating the screen version
deletes the print version (--result renames the file after
completion). Two questions:

1) MiKTeX 2.0 allows to specify the resulting filename;
shouldn't texexec take advantage of this when --result is
specified?

2) Is it possible to obtain both documents with a single run?

Thanks for your attention,

Giuseppe Bilotta

Using Microsoft products is like
having sex without condoms---but
much less pleasurable