Simon Ruderich wrote:
> Hi Rainer,
>
> sorry for the late reply.
>
> I'm glad you like it. I just [1] committed the change and now the guide makes
> it easy to link to subsections. Thanks for the suggestion.
Thanks for the implementation :)
I really like it.
Rainer
_
On Thu, Mar 06, 2008 at 02:04:48PM +0100, Rainer Müller wrote:
> [EMAIL PROTECTED] wrote:
>>> I just tried this using DocBook but it didn't work for me. So I used a
>>> simple
>>> sed replacement to get this working. I created two examples:
>>> http://ruderich.com/macports/guide-link.html
>
> I lik
Done.
-Bill
On Mar 8, 2008, at 1:59 PM, Simon Ruderich wrote:
On Wed, Mar 05, 2008 at 12:53:40PM -0800, William Siegrist wrote:
Its handled via the Makefile. The post-commit job performs 1 copy
when make
is done:
cp doc-new/guide/html/*
So if you make subdirectories, I'll add a -R, othe
On Wed, Mar 05, 2008 at 12:53:40PM -0800, William Siegrist wrote:
> Its handled via the Makefile. The post-commit job performs 1 copy when make
> is done:
>
> cp doc-new/guide/html/*
>
> So if you make subdirectories, I'll add a -R, otherwise it should work.
>
> -Bill
Hi Bill,
thanks for your
[EMAIL PROTECTED] wrote:
>> I just tried this using DocBook but it didn't work for me. So I used a
>> simple
>> sed replacement to get this working. I created two examples:
>> http://ruderich.com/macports/guide-link.html
I like this one with the links. It makes it easy to get the URL which
links
>> But as we are talking about the guide, I might also bring up another
>> issue with the current presentation. I find it difficult to link to
>> specific headlines. Could the headlines made clickable with a link
>> target on themself? Or maybe some marker item on mouse-move like trac
>> does? At t
On Wed, Mar 05, 2008 at 09:49:37AM +0100, Lutz Horn wrote:
> Hi Simon,
>
> Nice! Could you add Up links at the top and the bottom of the page? This
> would allow the user not only to navigate to the next and previous page
> but also back to the TOC.
>
> Lutz
There is a "Home" link at the bottom
On Wed, Mar 05, 2008 at 12:52:46PM -0430, Juan Manuel Palacios wrote:
>
> [snip]
>
> Simon, I like it and I still think the entire thing in a single page is
> a
> bit too much, but I would like to go over what Mark originally replied
> 'cause he did raise some valid points there (and it's
On Sun, Feb 17, 2008 at 01:32:09AM +0100, Rainer Müller wrote:
>
> But as we are talking about the guide, I might also bring up another
> issue with the current presentation. I find it difficult to link to
> specific headlines. Could the headlines made clickable with a link
> target on themself
> Simon, I like it and I still think the entire thing in a single
>page
>is a bit too much, but I would like to go over what Mark originally
>replied 'cause he did raise some valid points there (and it's been a
>while and I don't remember them at the moment ;-). One thing I would
>comment abo
On Wed, Mar 05, 2008 at 06:14:46PM +0100, Rainer Müller wrote:
> Hi Simon,
>
> Simon Ruderich wrote:
>> I just created a chunked version of the guide and uploaded it on my homepage:
>> http://ruderich.com/macports/chunked/
>
> Looks good so far. But I would like the TOC to be on each page for easie
Its handled via the Makefile. The post-commit job performs 1 copy
when make is done:
cp doc-new/guide/html/*
So if you make subdirectories, I'll add a -R, otherwise it should work.
-Bill
On Mar 5, 2008, at 9:42 AM, Rainer Müller wrote:
Simon Ruderich wrote:
This shouldn't be a problem.
Simon Ruderich wrote:
> This shouldn't be a problem. I already modified my local Makefile for the
> documentation generation. The question is how we should provide these two
> versions (maybe also a third: a downloadable version of the guide). Maybe
> http://guide.macports.org/ should display a sel
On Wed, Mar 05, 2008 at 08:15:52AM +0100, Thomas Reifferscheid wrote:
> Hi, great work Simon!
Hi,
I'm glad you like it.
> For doing this automatically (e.g. every night),
> we could need some kind of shell (bash) script doing this. Do you think
> thats possible for fully automation?
This should
On Mar 5, 2008, at 2:45 AM, Thomas Reifferscheid wrote:
> Hi, great work Simon!
>
> For doing this automatically (e.g. every night),
> we could need some kind of shell (bash) script doing this. Do you
> think
> thats possible for fully automation?
>
> Kind regards
> Thomas
Guide regen
Thomas Reifferscheid wrote:
> For doing this automatically (e.g. every night),
> we could need some kind of shell (bash) script doing this. Do you think
> thats possible for fully automation?
I think finally this should go on guide.macports.org, there the guide is
already built automatically. We
Hi Simon,
Simon Ruderich wrote:
> I just created a chunked version of the guide and uploaded it on my homepage:
> http://ruderich.com/macports/chunked/
Looks good so far. But I would like the TOC to be on each page for
easier switching of chapters. Could the current chapter be marked inside
the
Hi Simon,
On Wed, 5 Mar 2008 00:20:07 +0100, "Simon Ruderich"
<[EMAIL PROTECTED]> said:
> I just created a chunked version of the guide and uploaded it on my
> homepage: http://ruderich.com/macports/chunked/
>
> Please tell me what you think and if I should change anything.
Nice! Could you add Up
Hi, great work Simon!
For doing this automatically (e.g. every night),
we could need some kind of shell (bash) script doing this. Do you think
thats possible for fully automation?
Kind regards
Thomas
Simon Ruderich wrote:
[...]
> Hi all,
> sorry for the late reply.
>
> I just created a chunked
On Sat, Feb 16, 2008 at 02:46:33PM -0800, [EMAIL PROTECTED] wrote:
>>Hey guys!
>>
>>The guide is advancing so nicely that I'm afraid we've hit the
>> point when it's maybe becoming a tad too large for a single page, wouldn't
>> y'all think?
>>
>>Every time I have to load a s
[EMAIL PROTECTED] wrote:
> Well I agree it is really too big, but on the other hand we hated to split
> it and have cumbersome "forward" and "back" buttons. Also it makes
> searching easier in one page, but then I suppose indexing might solve
> that. But then maybe a page for each chapter wouldn'
>Hey guys!
>
>The guide is advancing so nicely that I'm afraid we've hit the
>point
>when it's maybe becoming a tad too large for a single page, wouldn't
>y'all think?
>
>Every time I have to load a section of the guide a have a moment
>of
>hesitation in fear of loading such
Hey guys!
The guide is advancing so nicely that I'm afraid we've hit the point
when it's maybe becoming a tad too large for a single page, wouldn't
y'all think?
Every time I have to load a section of the guide a have a moment of
hesitation in fear of loading such a
23 matches
Mail list logo