update and new manual

update and new manual

[Hans Hagen]

Hi All, 

I uploaded a new version of context, so that i can experiment with the beta
and new features. 

I also uploaded a mathml manual and example doc (follow xml link). I will
distribute the xtag files needed to process mathml later (have to document
'm). 

>From now on, you can directly reach the cod site as: cod.pragma-pod.com ; i
also uploaded a new mathml test page (now you can specify some layout
options). 

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

Re: Still no tooltips (was: Re: update and new manual)

[Hans Hagen]

At 12:52 AM 2/28/01 +0100, Giuseppe Bilotta wrote:
>Hans Hagen wrote:
>> Hi All,
>>
>> I uploaded a new version of context, so that i can experiment with the beta
>> and new features.
>
>Well, I tried my tooltip extension on the new ConTeXt (the file with the
>displayed-math-in-tooltip problem). I still get a "missing $ inserted" error,
>and all the relative problems (see attached file & log). What's wrong?

Formulas assume a \vbox so adding a \vbox around it
(\tooltip{..}{\vbox{....}} helps. Otherwise, use inlinemath. If tooltips
are really used i can consider a \definetooltip so that one can set 'm up
(width setting kind is of needed). 

\definetooltip[bigtip][width=4cm] 

or so. Is there any need for this? 

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

Re: Still no tooltips (was: Re: update and new manual)

[H. Ramm]

Hans Hagen schrieb:
>If tooltips
>are really used i can consider a \definetooltip so that one can set 'm up
>\definetooltip[bigtip][width=4cm] 
>
>or so. Is there any need for this? 

Oh, if I could get mpost to work, I had some ideas, where I would like
to use tooltips (little explanations, where you don' need a whole page).
-- 
Grüßlis vom Hraban!
---
http://angerweit.tikon.ch/    http://www.drucktechniker2001.de/
http://www.planet-interkom.de/fiee.visuelle/formelsammlung.html

Re[2]: Still no tooltips (was: Re: update and new manual)

[Giuseppe Bilotta]

HH> Formulas assume a \vbox so adding a \vbox around it
HH> (\tooltip{..}{\vbox{....}} helps. Otherwise, use inlinemath.

I will get a look at that.

HH>  If tooltips
HH> are really used i can consider a \definetooltip so that one can set 'm up
HH> (width setting kind is of needed).

HH> \definetooltip[bigtip][width=4cm] 

HH> or so. Is there any need for this? 

What do you mean "If tooltips are really used"? You mean you just put
them there for FUN?

The width thing is ok. Maybe a height thing too, don't know. The whole
point of my code was to obtain a box with width more or less double
the height. I don't know how much that was effective (had big problems
with the math).

Giuseppe

Re: Re[2]: Still no tooltips (was: Re: update and new manual)

[Hans Hagen]

At 01:19 AM 3/14/01 +0100, Giuseppe Bilotta wrote:
>
>HH> Formulas assume a \vbox so adding a \vbox around it
>HH> (\tooltip{..}{\vbox{....}} helps. Otherwise, use inlinemath.
>
>I will get a look at that.
>
>HH>  If tooltips
>HH> are really used i can consider a \definetooltip so that one can set 'm up
>HH> (width setting kind is of needed).
>
>HH> \definetooltip[bigtip][width=4cm] 
>
>HH> or so. Is there any need for this? 
>
>What do you mean "If tooltips are really used"? You mean you just put
>them there for FUN?

Most of context is there for fun -) 

When i was making that module, someone asked for them, so i made them. I
will make 'm better soon [auto left,right align] and if i have a bit more
time i can cook up much more functionality (i have many experimental test
files scattered on my machine).  

>The width thing is ok. Maybe a height thing too, don't know. The whole
>point of my code was to obtain a box with width more or less double
>the height. I don't know how much that was effective (had big problems
>with the math).

in tex, a vbox becomes of width hsize, and framed has a feature that
decomposes the whole thing and calculates the width needed, but math is
still a trouble maker in that. If i would add [align=normal] tooltips would
have width, but then, you don't want a tooltip to extend beyond the page.
This is why there is the help system, with stacked stuff to be placed
anywhere, see docu of flow charts, where it is mentioned. 

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

Re: Still no tooltips (was: Re: update and new manual)

[Hans Hagen]

At 12:52 AM 2/28/01 +0100, Giuseppe Bilotta wrote:
>Hans Hagen wrote:
>> Hi All,
>>
>> I uploaded a new version of context, so that i can experiment with the beta
>> and new features.
>
>Well, I tried my tooltip extension on the new ConTeXt (the file with the
>displayed-math-in-tooltip problem). I still get a "missing $ inserted" error,
>and all the relative problems (see attached file & log). What's wrong?

i'll have a look 

>Second though: I strongly believe that the code
>
>  \def\MPOSTbatchswitch {-int=batchmode}
>  \def\MPOSTformatswitch{-progname=mpost -mem=}
>  \def\MPOSTdriver      {dvips}
>
>should be moved from supp-mps to cont-sys, since it's extremely
system-specific.

Yes and no, since i don't want users to take care of such fuzzy code. I'm
thinking of some kind of special like driver modules but it is not so clean
within the concept of specials (actually, i'm awaiting some web2c
extensions concerning running pros, which was discussed some time some
where but never really implemented).  

Actually, the code is fall-back code since texexec generates the miktex
specific code in the runtime setup file and texexec knows what tex is used.

Btw, the dvips is not so specific -) 

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

Re[2]: Still no tooltips (was: Re: update and new manual)

[Giuseppe Bilotta]

>>Second though: I strongly believe that the code
>>
>>  \def\MPOSTbatchswitch {-int=batchmode}
>>  \def\MPOSTformatswitch{-progname=mpost -mem=}
>>  \def\MPOSTdriver      {dvips}
>>
>>should be moved from supp-mps to cont-sys, since it's extremely
>> system-specific.

HH> Actually, the code is fall-back code since texexec generates the miktex
HH> specific code in the runtime setup file and texexec knows what tex is used.

But if I don't fix that manually, it won't work correctly. Hm.

HH> Btw, the dvips is not so specific -) 

Oh, ok, it just fell in ;-)

Giuseppe