On 3 Dec 2008, at 00:07, Hannes Magnusson wrote:
On Mon, Dec 1, 2008 at 20:18, Christian Weiske <[EMAIL PROTECTED]>
wrote:
Hi all,
There are two problems described in the bug:
1. The first section/child of a chunk is no longer put on the
parental
page anymore. This is intentional. The pear themes have a
'phd:chunk="false"' attribute to restore the old behavior, phpdoc
misses that because its DTD doesn't allow it. It can be used, but
configure.php will display errors.
2. The accusation that the TOC on pages with chunked child pages is
displayed randomly. Example was the preface [1,2] which does not
show a
toc, while the exception reference [3,4] does show one.
The TOC on the preface is not displayed because preface is a normal
chunk, while the exception reference is internally a container_chunk.
Only container chunks get their child pages displayed in a TOC. So
this
is intentional, too.
Question is now how to continue with that. Shall every element get a
TOC displayed if it has chunking children?
Apparently noone seems to care, so lets just leave it as is.
People care, but most of us don't know what you guys are talking about
so we (at least I) was hoping you would clear it up in English like
you do best ;) But yes, more people replying to this crucial design
choice is indeed the better option.
As for phd:chunk="false", let's add it and determine if we want it.
For the records:
This means we now how 286 new files.
164 new files due to the setup requirement section being chunked off
and then files like:
http://docs.php.net/manual/en/swf.examples.php (empty container chunk)
Although it looks a little odd, it seems fine because if (when?!) more
examples are added here it'll look better and if we make an arbitrary
rule to include if one widget exists, or separate if more exist, we'd
end up with strange results in the future with content always changing
around.
Example:
- http://docs.php.net/manual/en/sdo.examples.php
- http://us2.php.net/manual/en/sdo.examples.php
http://docs.php.net/manual/en/language.oop5.php (the intro chunked
away)
http://docs.php.net/manual/en/language.control-structures.php (intro)
Regarding intros, I don't mind it either way. I suppose it would be a
lame hack to treat xml:id's ending with .intro differently, or adding
new markup for these circumstances, but I never really liked adding
the first part to the TOC page anyways... although adding the
introduction there did make some sense. However, it's not necessary. I
would say I'm +0 for new TOC behaviour with introductions, and +1 for
new TOC behaviour in other respects.
In that case we'd need official ways to:
- Add a TOC introduction (excerpt of text that goes in the TOC)
- Add an introduction to the part (which would be using foo.intro)
http://docs.php.net/manual/en/preface.php (no way to access
contributors.php)
This is a problem. Let's see if 'phd:chunk="false"' is what we want.
http://docs.php.net/manual/en/language.functions.php (dozens of notes
making no sense)
This seems fine, and I'm sure one of us will move the notes around. As
stated earlier, I prefer language.functions to be generic and not
about some almost random topic (like User-defined functions). And this
thought applies everywhere.
So our content has changed, but since all these pages still contain
TOC information it seems fine and for the best.
Regards,
Philip
