rest2web-develop — A discussion list for rest2web development.

Re: [Rest2web-develop] Feature request - 'ignore' a source directory

[Chris G <cl...@is...>]

On Fri, Mar 30, 2007 at 07:34:49PM -0300, Marcelo Huerta wrote:
> Chris G escribió:
> 
> > I want to be able to use 'r2w.py -f' but specifically ignore a
> > directory called 'config' (or something similar).  Then I can put all
> > the customisation for a particular rest2web hierarchy in that config
> > directory.
> 
> *Cough*
> 
> http://www.voidspace.org.uk/python/rest2web/special_files.html#prune
> 
> *Cough*
> 
I *almost* asked if I was missing something obvious!  :-)

However it's not documented for the purpose for which I want it which
is probably why I missed it.  (That's my excuse anyway)

Thanks!

-- 
Chris Green

Re: [Rest2web-develop] Feature request - 'ignore' a source directory

[Marcelo H. <mar...@gm...>]

Chris G escribi=F3:

> I want to be able to use 'r2w.py -f' but specifically ignore a
> directory called 'config' (or something similar).  Then I can put all
> the customisation for a particular rest2web hierarchy in that config
> directory.

*Cough*

http://www.voidspace.org.uk/python/rest2web/special_files.html#prune

*Cough*


--=20

     o-=3D< Marcelo >=3D-o

[Rest2web-develop] What's available when using <* .... *> for inserting values?

[Chris G <cl...@is...>]

When using the <* .... *> syntax to insert something into a rst page
what variables are available?

I tried 'title' and was told that wasn't defined and I suppose that's
not unreasonable.  Then I tried 'pagename' and that was undefined too
which doesn't seem right to me, surely the filename should be known.

-- 
Chris Green

Re: [Rest2web-develop] Doesn't r2w create destination directories?

[Chris G <cl...@is...>]

On Fri, Mar 30, 2007 at 02:29:21PM +0100, Chris G wrote:
> This may seem to be a rather basic question!
> 
> I've been using r2w for a while but I've only just tried to create a
> new destination hierarchy.  Previously I'd been regenerating existing
> hierarchies (e.g. the r2w 'docs_html' one) or I was working with r2w's
> destination set the same as the source so the .html files were put in
> the same directories as the .txt files.
> 
> Now I've changed the destination so that it's a new directory in
> /var/www/htdocs and r2w.py fails with a "No such file or directory"
> for the first level of subdirectory under /var/www/htdocs.
> 
> Have I really got to create the destination hierarchy manually (or at
> least write a script to do it)?
> 
A little further checking and I think I see what's happening.

I'm using "r2w.py -f".  If a source directory contains no *.txt files
then I get the "No such file or directory" for the corresponding
destination directory.  Presumably it doesn't create the destination
because there are no files to put there, and then it tries to create
the default index.html file and there's no directory.  At least that's
what it looks like.

-- 
Chris Green

[Rest2web-develop] Doesn't r2w create destination directories?

[Chris G <cl...@is...>]

This may seem to be a rather basic question!

I've been using r2w for a while but I've only just tried to create a
new destination hierarchy.  Previously I'd been regenerating existing
hierarchies (e.g. the r2w 'docs_html' one) or I was working with r2w's
destination set the same as the source so the .html files were put in
the same directories as the .txt files.

Now I've changed the destination so that it's a new directory in
/var/www/htdocs and r2w.py fails with a "No such file or directory"
for the first level of subdirectory under /var/www/htdocs.

Have I really got to create the destination hierarchy manually (or at
least write a script to do it)?

-- 
Chris Green

[Rest2web-develop] Feature request - 'ignore' a source directory

[Chris G <cl...@is...>]

Partially as a consequence of my 'thoughts' about how to organise a
rest2web installation, is there any chance of adding some sort of
'ignore' directive either in the .ini file or in the restindex part of
an index.txt file?

I want to be able to use 'r2w.py -f' but specifically ignore a
directory called 'config' (or something similar).  Then I can put all
the customisation for a particular rest2web hierarchy in that config
directory.

Yes, I could use a hidden file like '.config', but it feels a bit
clumsy.

-- 
Chris Green

[Rest2web-develop] How to arrange multiple rest2web trees?

[Chris G <cl...@is...>]

Maybe it's just me and wanting a tidy way to do things but I just
can't come up with a 'tidy' way of arranging a rest2web installation
so it appears logical and reasonably easy to maintain.

How do others handle this?

As I see it (and this will probably ramble a bit as I explain as I'm
talking to myself to some extent):-

    When you install rest2web you (very reasonably) get a
    rest2web-0.5.1 directory where everything you need is installed.
    I have copied the rest2web subdirectory to my python site-packages
    directory and I have put a copy of r2w.py on my path.  So far so
    good.

    Now I want to create a new 'source' tree for creating a web site.
    In my case it's called 'info'.  One of the major advantages of
    rest2web is that the source is readable in its own right, this is
    why I chose it.  So I create a sub-directory 'info' in my home
    directory and create text files there which I can (and will) view
    directly for local use.

    So where do I put the r2w files associated with my 'info' tree?
    By default r2w expects them to be in /home/chris/info but, to my
    mind anyway, that clutters the nice clean information resource I'm
    creating with things like templates, css files, etc.

    My solution at present is to create an 'info' directory in the
    rest2web-0.5.1 directory and put an r2w.ini, template file, css,
    etc. there but it's not ideal because that's the r2w software
    installation directory and having other (configuration related)
    stuff there makes upgrades awkward.  It also doesn't really work
    with the r2w examples and documentation there which are partly but
    not totally done the same way.

Maybe I'm being too complicated/demanding but ideally how I'd like it
to work is:-

    The rest2web installation itself goes into /usr/local or somewhere
    like that and, once installed, you never touch it except to
    upgrade it.  (Automation of the copying to site-packages would be
    nice but I'm quite happy with doing it manually)

    There's a configuration directory, probably somewhere in the
    user's home directory, where the .ini file for each 'tree' is kept
    and also any custom template and css files.   (I'm not sure about
    css, since they're used at run time)

    The 'source' and 'destination' directories (i.e. where the .txt
    files and .html files are respectively) have *only* the .txt and
    .html files in them.

I think there's probably a 'grey area' around the css files and maybe
template.txt.  Having 'images' and 'stylesheets' directories in the
destination directory is not too unreasonable as these don't visibly
clutter places that one sees normally.  On the other hand they're not
really in an easy to find place while building a site.


Just some ideas for kicking around, if I'm the only person thinking
this way then never mind, I'll live with it as it is because it does
so much in the sort of way I want.

-- 
Chris Green

Re: [Rest2web-develop] Where does 'page-description:' go?

[Michael F. <fuz...@vo...>]

Eur Ing Chris Green wrote:
> If I create a 'page description:' in a restindex for a file what does
> rest2web do with it?  I.e. where does it (usefully) appear?
>   

The idea is that you can use it in indexes for the directory that pages 
appear in.

You can access this information via the 'sections' data-structure.

Each directory is divided into sections. 'sections' is a dictioanry 
keyed by section. If you don't use sections then all the pages will be 
in the default section (keyed by None.)

pages = sections[None]['pages']
for page in pages:
    description = page['page-description']
    link_title = page['link-title']

Below is some example code I use in an index page to *auto-generate* 
indexes. It includes a link to every page, with a description of that 
page. (It also uses the link-title.)


<#

indexblock = '''
    <a name="%s" id="%s"></a>
    <div class="indexblock">
    <h2>%s</h2>
    %s
   
    <ul>
    %s
    </ul>
    </div>
'''

pageblock = '''
        <li><a href="%s">%s</a>
            %s
        </li>   
'''

for section in sectionlist:
    thepages = []
    for page in sections[section]['pages']:
        thispage = pageblock % (page['target'], page['link-title'], 
page['page-description'])
        if type(thispage) is unicode:
            thispage = thispage.encode('utf8')
        thepages.append(thispage)  

    thepages = '\n'.join(thepages)
    id = urllib.quote(str(section))
    sect_title = sections[section]['title']
    desc = sections[section]['description']
   
    this_sect = indexblock % ( id, id, sect_title, desc, thepages)
    print this_sect

#>

All the best,

Fuzzyman
http://www.voidspace.org.uk/python/index.shtml
> Similarly, where does 'link title:' end up?
>
> Are there some macros or functions that allow one to use 'page
> description:' and 'link title:'?
>
>   

Re: [Rest2web-develop] target: cannot take external values

[Michael F. <fuz...@vo...>]

martin f krafft wrote:
> also sprach Eur Ing Chris Green <cl...@is...> [2007.03.23.1139 +0100]:
>   
>>>     restindex
>>>         target: abcd.html
>>>     /restindex
>>>     restindex
>>>         target: defg.html
>>>     /restindex
>>>     restindex
>>>         target: hijk.html
>>>     /restindex
>>>
>>>       
>> Well I tried it and it works!  :-)
>>
>> I think a little expnasion of the documentation might help here, it's
>> note clear (hence my original question) that the above is how to do
>> it.  It needs a little more of course, e.g. some 'crumb:' entries at
>> least.
>>     
>
> On a related note, I cannot do something like
>
>   target: http://external.server.org/path/to/file
>
> rest2web will replace http:// with http:/ and thus make the browser
> treat the link as a relative link.
>   

Sorry for the delayed reply.  That sounds like a bad bug. I'll track it
down and fix it soon.

Fuzzyman
http://www.voidspace.org.uk/python/index.shtml

>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Rest2web-develop mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/rest2web-develop
>   

Re: [Rest2web-develop] Question about 'build' in restindex

[Michael F. <fuz...@vo...>]

Eur Ing Chris Green wrote:
> On Fri, Mar 23, 2007 at 10:17:20AM +0000, Eur Ing Chris Green wrote:
> [snip]
>   
>> Going on from this I'm trying to understand what restindex.txt does
>> for me.  I can see that it would be useful to combine (say) the
>> abcd.txt, defg.txt and hijk.txt files that I would otherwise need to
>> create to add pre-existing abcd.html, defg.html and hijk.html files to
>> a rest2web index, is this what restindex.txt is for?  If so how can it
>> refer to multiple targets?  Does one do it as follows:-
>>
>>     restindex
>>         target: abcd.html
>>     /restindex
>>     restindex
>>         target: defg.html
>>     /restindex
>>     restindex
>>         target: hijk.html
>>     /restindex
>>
>>     
> Well I tried it and it works!  :-)
>
> I think a little expnasion of the documentation might help here, it's
> note clear (hence my original question) that the above is how to do
> it.  It needs a little more of course, e.g. some 'crumb:' entries at
> least.
>
> Thinking onwards, what's to prevent allowing the same multiple
> restindex entries in the index.txt file?  This would mean that all you
> need in directories where all the HTML (and maybe other) files already
> exist would be an index.txt file.
>   

Ok - it sounds like their is a need for better documentation here.

I note the request for multiple restindexes in the index page. This is 
not immediately straightforward - but should be possible.

Fuzzyman
http://www.voidspace.org.uk/python/index.shtml

Re: [Rest2web-develop] target: cannot take external values

[Michael F. <ar...@vo...>]

martin f krafft wrote:
> also sprach Eur Ing Chris Green <cl...@is...> [2007.03.23.1139 +0100]:
>   
>>>     restindex
>>>         target: abcd.html
>>>     /restindex
>>>     restindex
>>>         target: defg.html
>>>     /restindex
>>>     restindex
>>>         target: hijk.html
>>>     /restindex
>>>
>>>       
>> Well I tried it and it works!  :-)
>>
>> I think a little expnasion of the documentation might help here, it's
>> note clear (hence my original question) that the above is how to do
>> it.  It needs a little more of course, e.g. some 'crumb:' entries at
>> least.
>>     
>
> On a related note, I cannot do something like
>
>   target: http://external.server.org/path/to/file
>
> rest2web will replace http:// with http:/ and thus make the browser
> treat the link as a relative link.
>   

Sorry for the delayed reply.  That sounds like a bad bug. I'll track it 
down and fix it soon.

Fuzzyman
http://www.voidspace.org.uk/python/index.shtml

>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Rest2web-develop mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/rest2web-develop
>   

[Rest2web-develop] target: cannot take external values

[martin f k. <ma...@ma...>]

also sprach Eur Ing Chris Green <cl...@is...> [2007.03.23.1139 +0100]:
> >     restindex
> >         target: abcd.html
> >     /restindex
> >     restindex
> >         target: defg.html
> >     /restindex
> >     restindex
> >         target: hijk.html
> >     /restindex
> >=20
> Well I tried it and it works!  :-)
>=20
> I think a little expnasion of the documentation might help here, it's
> note clear (hence my original question) that the above is how to do
> it.  It needs a little more of course, e.g. some 'crumb:' entries at
> least.

On a related note, I cannot do something like

  target: http://external.server.org/path/to/file

rest2web will replace http:// with http:/ and thus make the browser
treat the link as a relative link.

--=20
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
=20
spamtraps: mad...@ma...
=20
stupidity management for the superuser
is a user space issue in unix systems.
                                                           -- alan cox

[Rest2web-develop] Where does 'page-description:' go?

[Eur I. C. G. <cl...@is...>]

If I create a 'page description:' in a restindex for a file what does
rest2web do with it?  I.e. where does it (usefully) appear?

Similarly, where does 'link title:' end up?

Are there some macros or functions that allow one to use 'page
description:' and 'link title:'?

-- 
Chris Green

Re: [Rest2web-develop] Question about 'build' in restindex

[Eur I. C. G. <cl...@is...>]

On Fri, Mar 23, 2007 at 10:17:20AM +0000, Eur Ing Chris Green wrote:
[snip]
> Going on from this I'm trying to understand what restindex.txt does
> for me.  I can see that it would be useful to combine (say) the
> abcd.txt, defg.txt and hijk.txt files that I would otherwise need to
> create to add pre-existing abcd.html, defg.html and hijk.html files to
> a rest2web index, is this what restindex.txt is for?  If so how can it
> refer to multiple targets?  Does one do it as follows:-
> 
>     restindex
>         target: abcd.html
>     /restindex
>     restindex
>         target: defg.html
>     /restindex
>     restindex
>         target: hijk.html
>     /restindex
> 
Well I tried it and it works!  :-)

I think a little expnasion of the documentation might help here, it's
note clear (hence my original question) that the above is how to do
it.  It needs a little more of course, e.g. some 'crumb:' entries at
least.

Thinking onwards, what's to prevent allowing the same multiple
restindex entries in the index.txt file?  This would mean that all you
need in directories where all the HTML (and maybe other) files already
exist would be an index.txt file.

-- 
Chris Green

[Rest2web-develop] Question about 'build' in restindex

[Eur I. C. G. <cl...@is...>]

I need some clarification of what 'build:' in the restindex does.

I can understand that when it's set to 'yes' then the file in which
the 'build: yes' is will be processed (using docutils) to create an
HTML version.  By default, thus, a file abcd.txt will be processed to
create a file abcd.html.

However I'm not clear what happens with 'build: no'.  If the file
abcd.txt has a restindex with 'build: no' does anything happen at all?
In the documentation it says "allows you to specify that a file is not
to be built, but should be included in the index."  So, this
apparently means that the index for the directory where the file
abcd.txt is will have a reference to 'abcd', but we haven't built
abcd.  Is this just so that if I want to include a pre-existing
abcd.html file I can create a corresponding abcd.txt with 'build: no'?

Going on from this I'm trying to understand what restindex.txt does
for me.  I can see that it would be useful to combine (say) the
abcd.txt, defg.txt and hijk.txt files that I would otherwise need to
create to add pre-existing abcd.html, defg.html and hijk.html files to
a rest2web index, is this what restindex.txt is for?  If so how can it
refer to multiple targets?  Does one do it as follows:-

    restindex
        target: abcd.html
    /restindex
    restindex
        target: defg.html
    /restindex
    restindex
        target: hijk.html
    /restindex

-- 
Chris Green

[Rest2web-develop] Caching Branch in Sunbversion

[Michael F. <fuz...@vo...>]

Hello all,

For your information, I've just created a branch in subversion for the 
caching. This is 'caching-spike' :

    http://svn.rest2web.python-hosting.com/branches/caching-spike/

Hopefully in a few days this will have a usable caching implementation 
that you can test. It will require a command line / config file option 
switching on, and then rebuilding large websites should be massively 
quicker.

I'll give you a heads-up when it is ready to test.

All the best,


Michael Foord

Re: [Rest2web-develop] caching?

[Michael F. <fuz...@vo...>]

Thomas Koch wrote:
> Hallo,
>
> I'm evaluating r2w to be used for documenting development and collaborating on 
> design documents. (See http://www.egroupware2.de)
>
> How can quickly rebuild the pages after every change? Is there any caching 
> inside r2w or could I tell r2w to create only one page? But where should it 
> get the sitetree from?
>   

By coincidence today I have been working on the first steps needed to 
add caching.

It isn't easy, rest2web actually uses several data structures to 
represent the current directory whilst also building up a big data 
structure that represents the site.

Once I am done, rest2web will skip attempting to build pages that 
haven't changed - so it will be much faster.

Currently it attempts to build each page, but it doesn't write out pages 
that haven't changed.

Michael
http://www.voidspace.org.uk/python/rest2web/

> Thanks,
>
> Thomas Koch
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Rest2web-develop mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/rest2web-develop
>
>   

Re: [Rest2web-develop] caching?

[martin f k. <ma...@ma...>]

also sprach Thomas Koch <th...@ru...> [2007.03.13.1959 +0100]:
> How can quickly rebuild the pages after every change? Is there any
> caching inside r2w or could I tell r2w to create only one page?
> But where should it get the sitetree from?

r2w will only rebuild pages whose source has changed. You cannot
rebuild single pages, AFAIK.

--=20
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
=20
spamtraps: mad...@ma...
=20
military intelligence is a contradiction in terms.
                                                       -- groucho marx

[Rest2web-develop] caching?

[Thomas K. <th...@ru...>]

Hallo,

I'm evaluating r2w to be used for documenting development and collaborating on 
design documents. (See http://www.egroupware2.de)

How can quickly rebuild the pages after every change? Is there any caching 
inside r2w or could I tell r2w to create only one page? But where should it 
get the sitetree from?

Thanks,

Thomas Koch

Re: [Rest2web-develop] Force Mode Fixes

[Eur I. C. G. <cl...@is...>]

On Tue, Mar 13, 2007 at 01:07:00PM +0000, Fuzzyman wrote:
> Hello all,
> 
> I've made a few minor fixes to rest2web. I can't commit from where I am,
> and I know that at least Chris will be pleased with some of the fixes,
> so I've attached an updated 'restprocessor.py' to this email.
> 
> The fixes are :
> 
> * Fixed bug where 'force' in the config file was required to be spelt
> 'Force' by mistake
> * 'template.txt' files (without a restindex) will not be processed in
> force mode
> * In force mode, directories *will* use the templates of their parent
> directories
> 
Excellent, thanks very much, I won't be able to use it today as I have
a very tight timetable for going out to the theatre but I will install
and use it tomorrow.

-- 
Chris Green

[Rest2web-develop] Force Mode Fixes

[Fuzzyman <fuz...@vo...>]

Hello all,

I've made a few minor fixes to rest2web. I can't commit from where I am,
and I know that at least Chris will be pleased with some of the fixes,
so I've attached an updated 'restprocessor.py' to this email.

The fixes are :

* Fixed bug where 'force' in the config file was required to be spelt
'Force' by mistake
* 'template.txt' files (without a restindex) will not be processed in
force mode
* In force mode, directories *will* use the templates of their parent
directories

All the best,

Fuzzyman
http://www.voidspace.org.uk/python/articles.shtml

Re: [Rest2web-develop] How template is chosen in force mode

[Michael F. <fuz...@vo...>]

Eur Ing Chris Green wrote:
> In the section on 'restindex' where it talks about the template entry
> the documentation says:-
>
>     In an 'index.txt' this can specify the template file for the whole
>     directory (and directories below it as well).
>
> ... and in the 'force mode' section it says:-
>
>     When force is on and no template is specified, then the default
>     one (restweb/defaults/template.txt) is used.
>
>     If a template is specified in the restindex of any index page,
>     then that will be used for that directory (and all subdirectories)
>     in the usual way.
>
>     Every directory that has no index.txt will use the default one.
>     (restweb/defaults/index.txt)
>
>
> This doesn't seem to be working as specified.  In my top level
> index.txt file I have:-
>
>     restindex
>         crumb: Home
>         template: /home/chris/www/r2w/info/template.tpl
>         link-title: HomeTitle
>     /restindex
>
> It's using the specified template file for the top level HTML creation
> but for all the sub-directories it's using the default template file
> /usr/lib/python2.4/site-packages/rest2web/defaults/template.txt.
>
> I have some subdirectories which have explicit index.txt files and
> some which don't but *none* of the subdirectories are using the
> template.tpl file specified in the top level index.txt. The only HTML
> that's formatted with the top-level template.tpl is the top level
> directory.
>
>   
Ok. I need to confirm this, but that certainly sounds like a bug.

Thanks

Fuzzyman
http://www.voidspace.org.uk/python/articles.shtml

[Rest2web-develop] How template is chosen in force mode

[Eur I. C. G. <cl...@is...>]

In the section on 'restindex' where it talks about the template entry
the documentation says:-

    In an 'index.txt' this can specify the template file for the whole
    directory (and directories below it as well).

... and in the 'force mode' section it says:-

    When force is on and no template is specified, then the default
    one (restweb/defaults/template.txt) is used.

    If a template is specified in the restindex of any index page,
    then that will be used for that directory (and all subdirectories)
    in the usual way.

    Every directory that has no index.txt will use the default one.
    (restweb/defaults/index.txt)


This doesn't seem to be working as specified.  In my top level
index.txt file I have:-

    restindex
        crumb: Home
        template: /home/chris/www/r2w/info/template.tpl
        link-title: HomeTitle
    /restindex

It's using the specified template file for the top level HTML creation
but for all the sub-directories it's using the default template file
/usr/lib/python2.4/site-packages/rest2web/defaults/template.txt.

I have some subdirectories which have explicit index.txt files and
some which don't but *none* of the subdirectories are using the
template.tpl file specified in the top level index.txt. The only HTML
that's formatted with the top-level template.tpl is the top level
directory.

-- 
Chris Green

Re: [Rest2web-develop] Another wish/request

[Michael F. <fuz...@vo...>]

Eur Ing Chris Green wrote:
> On Fri, Mar 09, 2007 at 02:48:38PM +0000, Michael Foord wrote:
>   
>> Eur Ing Chris Green wrote:
>>     
>>> A request 'for the next release' maybe.
>>>
>>> Can the configuration/layout be changed so that the templates and
>>> stylesheets are in the same place?  It makes sense because they are
>>> closely related and one nearly always wants to edit them both, or at
>>> least refer to one while you're editing the other.
>>>
>>> Simply making the default directory for the template.txt file being
>>> the stylesheets directory would be OK.  It might be even better to
>>> make this directory configurable in the .ini file.
>>>   
>>>       
>> Except rest2web itself has no knowledge of CSS - you can store your CSS 
>> files wherever you want.
>>
>>     
> Yes, I'd not thought far enough. The stylesheets are, of course,
> referenced from the template. It is quite a common convention now
> though, to have all templates and stylesheets gathered together in one
> place.  It can be done with rest2web but it's not that way 'out of the
> box'.
>  
>   

I think what is more relevant is that you are doing something slightly 
unusual in having the same directory for the source and target 
directory. Many users won't have a CSS directory in their source directory.

The -t command line option ought to work fine with force mode by the way.

Fuzzyman
http://www.voidspace.org.uk/python/articles.shtml

Re: [Rest2web-develop] Another wish/request

[Eur I. C. G. <cl...@is...>]

On Fri, Mar 09, 2007 at 02:48:38PM +0000, Michael Foord wrote:
> Eur Ing Chris Green wrote:
> > A request 'for the next release' maybe.
> >
> > Can the configuration/layout be changed so that the templates and
> > stylesheets are in the same place?  It makes sense because they are
> > closely related and one nearly always wants to edit them both, or at
> > least refer to one while you're editing the other.
> >
> > Simply making the default directory for the template.txt file being
> > the stylesheets directory would be OK.  It might be even better to
> > make this directory configurable in the .ini file.
> >   
> 
> Except rest2web itself has no knowledge of CSS - you can store your CSS 
> files wherever you want.
> 
Yes, I'd not thought far enough. The stylesheets are, of course,
referenced from the template. It is quite a common convention now
though, to have all templates and stylesheets gathered together in one
place.  It can be done with rest2web but it's not that way 'out of the
box'.
 

> If you are using force mode there is no way of specifying where your 
> template file is other than the command line. To make this more 
> convenient you could create a batch file which runs rest2web with  the 
> correct command line options set to keep your template file there.
> 
I'm actually specifying where the template file is using the restindex
section of the top level index.txt file now.  Force mode doesn't
override this does it?  (I'm using force mode because there are places
lower down that don't have an index.txt file)

-- 
Chris Green