Enhancement request : publish page limits

Enhancement request : publish page limits

[Richard Riley]

I didn't spot anything in the manual, but it would be nice if publish
automatically split large published org files into multiple html files
based on a "num entries per page" setting. This would then effectively
work as a handy  blogging client IMO (ok no replies etc). Clearly it
would need to render a navigation widget too. (page 1,2,4,5 .. next 5 )
etc. Does anyone have something like this or suggestions along the same
path?

-- 
The saddest aspect of life right now is that science gathers knowledge faster than society gathers wisdom.  ~Isaac Asimov, Isaac Asimov's Book of Science and Nature Quotations, 1988

Re: Enhancement request : publish page limits

[Sebastian Rose]

org-info.js ;-)

???

Make the de facto standard for viewing text in the internet !!!

:-D


Richard Riley <rileyrgdev@googlemail.com> writes:
> I didn't spot anything in the manual, but it would be nice if publish
> automatically split large published org files into multiple html files
> based on a "num entries per page" setting. This would then effectively
> work as a handy  blogging client IMO (ok no replies etc). Clearly it
> would need to render a navigation widget too. (page 1,2,4,5 .. next 5 )
> etc. Does anyone have something like this or suggestions along the same
> path?

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover

Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http:  www.emma-stil.de

Re: Enhancement request : publish page limits

[Sebastian Rose]

Richard Riley <rileyrgdev@googlemail.com> writes:

> Hi,
>
> Do you have an example?
>
> The link
>
> http://orgmode.org/worg/code/org-info-js/org-info.js.html
>
> mentioned in the info file is dead.


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

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover

Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http:  www.emma-stil.de

Re: Enhancement request : publish page limits

[Sebastian Rose]

Patch to fix this in doc/org.texi (pulled an hour ago).


diff --git a/doc/org.texi b/doc/org.texi
index 0ae852e..b2ce486 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -7688,7 +7688,7 @@ as well, press @kbd{?} for an overview of the available keys).  The second
 view type is a @emph{folding} view much like Org provides it inside Emacs.
 The script is available at @url{http://orgmode.org/org-info.js} and you can
 find the documentation for it at
-@url{http://orgmode.org/worg/code/org-info-js/org-info.js.html}.  We are
+@url{http://orgmode.org/worg/code/org-info-js/index.html}.  We are
 serving the script from our site, but if you use it a lot, you might not want
 to be dependent on @url{orgmode.org} and prefer to install a local copy on
 your own web server.


Richard Riley <rileyrgdev@googlemail.com> writes:
> Hi,
>
> Do you have an example?
>
> The link
>
> http://orgmode.org/worg/code/org-info-js/org-info.js.html
>
> mentioned in the info file is dead.
>
> r.
>
>
> Sebastian Rose <sebastian_rose@gmx.de> writes:
>
>> org-info.js ;-)
>>
>> ???
>>
>> Make the de facto standard for viewing text in the internet !!!
>>
>> :-D
>>
>>
>> Richard Riley <rileyrgdev@googlemail.com> writes:
>>> I didn't spot anything in the manual, but it would be nice if publish
>>> automatically split large published org files into multiple html files
>>> based on a "num entries per page" setting. This would then effectively
>>> work as a handy  blogging client IMO (ok no replies etc). Clearly it
>>> would need to render a navigation widget too. (page 1,2,4,5 .. next 5 )
>>> etc. Does anyone have something like this or suggestions along the same
>>> path?

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover

Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http:  www.emma-stil.de

Re: Re: Enhancement request : publish page limits

[Sebastian Rose]

Richard,

there is a tutorial at org/worg:
http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.php

which shows how I handle the HTML export here. It's shorter to read,
than the old org-info documentation, and covers a nice way to handle
recursive exporting of entire directory trees and glue them together
by org-info.js.


I like this example most, currently, since it shows how `i TAB' is
handled with fixed-toc:

http://orgmode.org/worg/org-faq.php


Regards,

   Sebastian


> Sebastian Rose <sebastian_rose@gmx.de> writes:
>> Patch to fix this in doc/org.texi (pulled an hour ago).
>>
>>
>> diff --git a/doc/org.texi b/doc/org.texi
>> index 0ae852e..b2ce486 100644
>> --- a/doc/org.texi
>> +++ b/doc/org.texi
>> @@ -7688,7 +7688,7 @@ as well, press @kbd{?} for an overview of the available keys).  The second
>>  view type is a @emph{folding} view much like Org provides it inside Emacs.
>>  The script is available at @url{http://orgmode.org/org-info.js} and you can
>>  find the documentation for it at
>> -@url{http://orgmode.org/worg/code/org-info-js/org-info.js.html}.  We are
>> +@url{http://orgmode.org/worg/code/org-info-js/index.html}.  We are
>>  serving the script from our site, but if you use it a lot, you might not want
>>  to be dependent on @url{orgmode.org} and prefer to install a local copy on
>>  your own web server.
>>
>>
>> Richard Riley <rileyrgdev@googlemail.com> writes:
>>> Hi,
>>>
>>> Do you have an example?
>>>
>>> The link
>>>
>>> http://orgmode.org/worg/code/org-info-js/org-info.js.html
>>>
>>> mentioned in the info file is dead.
>>>
>>> r.
>>>
>>>
>>> Sebastian Rose <sebastian_rose@gmx.de> writes:
>>>
>>>> org-info.js ;-)
>>>>
>>>> ???
>>>>
>>>> Make the de facto standard for viewing text in the internet !!!
>>>>
>>>> :-D
>>>>
>>>>
>>>> Richard Riley <rileyrgdev@googlemail.com> writes:
>>>>> I didn't spot anything in the manual, but it would be nice if publish
>>>>> automatically split large published org files into multiple html files
>>>>> based on a "num entries per page" setting. This would then effectively
>>>>> work as a handy  blogging client IMO (ok no replies etc). Clearly it
>>>>> would need to render a navigation widget too. (page 1,2,4,5 .. next 5 )
>>>>> etc. Does anyone have something like this or suggestions along the same
>>>>> path?

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover

Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http:  www.emma-stil.de