Hi Andries,
Andries Seutens wrote:
> I'm not sure if it's possible to add a tab to the wiki space. I'll have
> to check with Gavin or Darby for this. Gavin, Darby?
Honestly, I'm not sure how this would be done the way I think you mean,
though perhaps it is possible. Maybe the {deck} and {card} wiki tags, as
seen on:
http://framework.zend.com/wiki/renderer/notationhelp.action?section=advanced
would meet the end goals you had in mind?
> I have a few more notes/questions:
>
> - Leave the sidebar on the left of the page or put it on the right side
> of the page?
I would like to see it on the right side of the page, since expanding
long class names results in the left-most side of the main manual
content being pushed to the right. I think it would be better if
expansion of sidebar content would only result text wrapping changes to
the main manual content. I hope that makes sense, though I also think
that the converse could be said for right-to-left languages. :-/
> - Is it possible to hide the navigation bar when printing/exporting to pdf?
Maybe try the {hide-if} tag? (also on advanced editing help page)
> - Some of our component names are so long that they don't fit in the
> sidebar, what should we do with that? (less padding would be one)
I see the component names wrapping at the edge of the sidebar (maybe
we're talking about the same thing). Just guessing, but maybe using CSS
"white-space:nowrap" (or something similar) would work?
> - I couldn't keep the links from the docbook alive, as the page
> structure is a lot different (more content on one page, less clicking,
> more scrolling) do you guys mind?
I see that even links to outside resources have been lost, such as the
include() and include_once() links to php.net on
http://framework.zend.com/manual/en/zend.loadfile.html. I think at least
these are important to have propagated, since they generally link to
information only available outside the scope of our manual. What is the
technical limitation encountered here, so that we all could understand
how it might be solved?
> - The {toc} macro seems to have problems with heading with the same name
> (wrong anchor links)
I believe that the {toc-zone} lets you get around this problem by
specifying to which content the macro applies.
> For those of you that don't know yet, the wiki import test can be found
> here:
>
> http://framework.zend.com/wiki/display/ZFDOCDEV/Home
Overall, this is great work, Andries, and I'm sure I speak not only for
myself when I say *thank you!*
Best regards,
Darby
