org-info.js

org-info.js

[Pete Phillips]

Morning all

I'm trying to use org-info.js.

I am using the git repository, and have placed the stylesheet.css and
the org-info.js into the same directory that my org file is in.

The top of my org-file is as follows:

#+TITLE:     ubuntu-general.org
#+AUTHOR:    Pete Phillips
#+EMAIL:     pete@smtl.co.uk
#+DATE:      <2008-03-25 Tue>
#+LANGUAGE:  en
#+TEXT:      Some descriptive text to be emitted.  Several lines OK.
#+OPTIONS:   H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:nil skip:t d:nil tags:not-in-toc
#+STYLE:     <script type=\"text/javascript\" language=\"JavaScript\" src="org-info.js\" /> <script type="text/javascript" language="JavaScript">/* <![CDATA[ */ org_html_manager.setup ();/* ]]> */</script>

When I use ^C^Eh (to export as html), the resulting html file does not
have any of the <script> stuff in there. browsing with firefox does not
give me the interface that the org-info.js.html does.

Can anyone explain what I'm doing wrong ?

Cheers,
Pete

--
Pete Phillips, Acting Director,     |   http://www.smtl.co.uk/
Surgical Materials Testing Lab,     |   http://www.worldwidewounds.com/
Princess of Wales Hospital, S Wales |   http://www.dressings.org/
Tel/Fax: +44 1656-752820/30         |   pete@smtl.co.uk

Re: org-info.js

[Sebastian Rose]

Pete Phillips <pete@smtl.co.uk> writes:
> I'm trying to use org-info.js.
>
> I am using the git repository, and have placed the stylesheet.css and
> the org-info.js into the same directory that my org file is in.
>
> The top of my org-file is as follows:
>
> #+TITLE:     ubuntu-general.org
> #+AUTHOR:    Pete Phillips
> #+EMAIL:     pete@smtl.co.uk
> #+DATE:      <2008-03-25 Tue>
> #+LANGUAGE:  en
> #+TEXT:      Some descriptive text to be emitted.  Several lines OK.
> #+OPTIONS:   H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:nil skip:t d:nil tags:not-in-toc
> #+STYLE:     <script type=\"text/javascript\" language=\"JavaScript\" src="org-info.js\" /> <script type="text/javascript" language="JavaScript">/* <![CDATA[ */ org_html_manager.setup ();/* ]]> */</script>
>
> When I use ^C^Eh (to export as html), the resulting html file does not
> have any of the <script> stuff in there. browsing with firefox does not
> give me the interface that the org-info.js.html does.
>
> Can anyone explain what I'm doing wrong ?

Hello Pete,

unfortunately I can not tell what's wrong. I tried some of the
configuration alternatives I mentioned in the documentation of
org-info.js and found that none of them works anymore. Exept the one in
section 4.2.3. So I'm afraid it's the only way that works at the moment.

Or just put the code in the header of the generated XHTML by hand. I
suspect something is broken in the export. Well, I'm quite shure it
worked that way here. But I can't find the keyword #+STYLE: in the docs
and `M-x org-insert-export-options-templat´ does not insert the STYLE
option, so maybe I'm wrong here.

I'll have investigate this tonight at home and rework the documentation
accordingly.

Sorry for this late answer, but I just got home from searching easter
eggs with my kids ;-)


Regards,

    Sebastian



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sebastian Rose             Fachinformatiker/Anwendendungsentwickler
Viktoriastaße 22
30451 Hannover             Entwicklung  von Internetanwendungen und
                           Programmen  mit  freien  Werkzeugen  und
sebastian_rose at gmx de   Bibliotheken.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

org-info.js

[Dan Davison]

If I'm viewing the manual with Sebastian's org-info javascript info
emulation, and I'm on node 13 of the manual, what key do I press to get
to 13.1?

I wish I were better with info. My understanding is that I would use
space or ] in emacs.

Thanks,

Dan

Re: org-info.js

[Nick Dokos]

Dan Davison <davison@stats.ox.ac.uk> wrote:

> If I'm viewing the manual with Sebastian's org-info javascript info
> emulation, and I'm on node 13 of the manual, what key do I press to get
> to 13.1?
> 
> I wish I were better with info. My understanding is that I would use
> space or ] in emacs.
> 

In emacs info, <SPACE> advances down the imaginary scroll, so it may or
may not get you to the next (sub)section, depending on the length of the
current section and the size of your screen. ']' will go to the next
node in a depth-first traversal, 'n' will get you to the next node in a
level-traversal (always assuming that the relevant nodes exist).
Numeric arguments will get you to the relevant subsection (i.e. if you
are in sec. 13 and press 6, you'll end up in subsection 13.6 - assuming
that it exists), whereas 'n' and 'p' will get you to the next/previous
heading at the same level and 'u' will go up a level.

Now I'm on much shakier ground (iow, I don't necessarily know what I'm
talking about), but I think `n' does a depth-first traversal, so it will
go from 13 to 13.1 - the question is how to go from 13 to 14 without
visiting all the 13.x... in-between: I thought I would go UP to the TOC
and then TAB to or click on the next section, but the UP link does not
seem to do what I think it should do (go up one level in the hierarchy -
at least that seems to be the case in the org-info pages:
http://orgmode.org/worg/code/org-info-js). I'm not saying there is no
way: I just didn't find one after a few minutes of fooling around.

HTH,
Nick

Re: org-info.js

[Dan Davison]

Nick Dokos <nicholas.dokos@hp.com> writes:

> Dan Davison <davison@stats.ox.ac.uk> wrote:
>
>> If I'm viewing the manual with Sebastian's org-info javascript info
>> emulation, and I'm on node 13 of the manual, what key do I press to get
>> to 13.1?
>> 
>> I wish I were better with info. My understanding is that I would use
>> space or ] in emacs.
>> 
>
> In emacs info, <SPACE> advances down the imaginary scroll, so it may or
> may not get you to the next (sub)section, depending on the length of the
> current section and the size of your screen. ']' will go to the next
> node in a depth-first traversal, 'n' will get you to the next node in a
> level-traversal (always assuming that the relevant nodes exist).
> Numeric arguments will get you to the relevant subsection (i.e. if you
> are in sec. 13 and press 6, you'll end up in subsection 13.6 - assuming
> that it exists), whereas 'n' and 'p' will get you to the next/previous
> heading at the same level and 'u' will go up a level.
>
> Now I'm on much shakier ground (iow, I don't necessarily know what I'm
> talking about), but I think `n' does a depth-first traversal, so it will
> go from 13 to 13.1 - the question is how to go from 13 to 14 without
> visiting all the 13.x... in-between:

Actually, no, n goes from 13 to 14 (at least in google-chrome). But I'm
with you -- it seems to behave differently in

http://orgmode.org/worg/code/org-info-js

There n does the depth-first traversal you describe (and that is the
behaviour I'm looking for).

So
- how to get the full traversal in the org manual?
- why is there different behaviour between the manual and the worg page?

Dan


> I thought I would go UP to the TOC
> and then TAB to or click on the next section, but the UP link does not
> seem to do what I think it should do (go up one level in the hierarchy -
> at least that seems to be the case in the org-info pages:
> http://orgmode.org/worg/code/org-info-js). I'm not saying there is no
> way: I just didn't find one after a few minutes of fooling around.
>
> HTH,
> Nick
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: org-info.js

[Carsten Dominik]

On May 19, 2010, at 4:34 PM, Dan Davison wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
>
>> Dan Davison <davison@stats.ox.ac.uk> wrote:
>>
>>> If I'm viewing the manual with Sebastian's org-info javascript info
>>> emulation, and I'm on node 13 of the manual, what key do I press  
>>> to get
>>> to 13.1?
>>>
>>> I wish I were better with info. My understanding is that I would use
>>> space or ] in emacs.
>>>
>>
>> In emacs info, <SPACE> advances down the imaginary scroll, so it  
>> may or
>> may not get you to the next (sub)section, depending on the length  
>> of the
>> current section and the size of your screen. ']' will go to the next
>> node in a depth-first traversal, 'n' will get you to the next node  
>> in a
>> level-traversal (always assuming that the relevant nodes exist).
>> Numeric arguments will get you to the relevant subsection (i.e. if  
>> you
>> are in sec. 13 and press 6, you'll end up in subsection 13.6 -  
>> assuming
>> that it exists), whereas 'n' and 'p' will get you to the next/ 
>> previous
>> heading at the same level and 'u' will go up a level.
>>
>> Now I'm on much shakier ground (iow, I don't necessarily know what  
>> I'm
>> talking about), but I think `n' does a depth-first traversal, so it  
>> will
>> go from 13 to 13.1 - the question is how to go from 13 to 14 without
>> visiting all the 13.x... in-between:
>
> Actually, no, n goes from 13 to 14 (at least in google-chrome). But  
> I'm
> with you -- it seems to behave differently in
>
> http://orgmode.org/worg/code/org-info-js
>
> There n does the depth-first traversal you describe (and that is the
> behaviour I'm looking for).
>
> So
> - how to get the full traversal in the org manual?

> - why is there different behaviour between the manual and the worg  
> page?


Because the manual is created by texinfo, Worg is published by Org-mode.
I also would love to have a depth-first way to travel in the manual -  
but I don't know how.

I *am* hacking the html manual pages already (UTILITIES/mansplit.pl)  
to get the sidebar toc in there - the same program could maybe also  
hack some of those keys, I guess.  But I don't know how.  And there  
are issues of what people expect.  I love it that Sebastian has made a  
way to travel depth-first, but I also think that people who are used  
to read texinfo manpages like to have consistent keys....

- Carsten

>
> Dan
>
>
>> I thought I would go UP to the TOC
>> and then TAB to or click on the next section, but the UP link does  
>> not
>> seem to do what I think it should do (go up one level in the  
>> hierarchy -
>> at least that seems to be the case in the org-info pages:
>> http://orgmode.org/worg/code/org-info-js). I'm not saying there is no
>> way: I just didn't find one after a few minutes of fooling around.
>>
>> HTH,
>> Nick
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

org-info.js

[Phillip Lord]

Can anyone tell me where the source code for org-info at

http://orgmode.org/org-info.js

is? This verison if minified.

There are these:

https://github.com/SebastianRose/org-info-js/
https://github.com/RickMoynihan/org-info-js

Some of the web pages aabout org-info aren't working.

http://orgmode.org/worg/code/org-info-js/index.html

Unfortunately, it is only output to documents including it in minified
forms and as a link.

Phil

Re: org-info.js

[Achim Gratz]

Phillip Lord writes:
> Can anyone tell me where the source code for org-info at
>
> http://orgmode.org/org-info.js
>
> is? This verison if minified.
>
> There are these:
>
> https://github.com/SebastianRose/org-info-js/

A copy of this version is on Worg under code/org-info-js, the plain
source is org-info-src.js.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

Re: org-info.js

[Phillip Lord]

Achim Gratz <Stromeko@nexgo.de> writes:

> Phillip Lord writes:
>> Can anyone tell me where the source code for org-info at
>>
>> http://orgmode.org/org-info.js
>>
>> is? This verison if minified.
>>
>> There are these:
>>
>> https://github.com/SebastianRose/org-info-js/
>
> A copy of this version is on Worg under code/org-info-js, the plain
> source is org-info-src.js.


Thanks!

Phil