Re: Re: New skeletons
| From: | Hannes Magnusson | Date: | Wed, 31 Oct 2007 18:20:36 +0000 |
| Subject: | Re: Re: New skeletons | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969378267@lists.php.net to get a copy of this message | ||
On Oct 31, 2007 6:11 PM, Edward Z. Yang <edwardzyang@thewritingpot.com> wrote:
> Hannes Magnusson wrote:
> > Do we really want that?
> > I suppose we can create a page for class overview and print all the
> > classes on one page in the same way as the class reference does...
>
> One of the great things about XSLT is that it makes things like this
> specifically possible. I don't see why not.
The problem isn't implementing it, the problem is the duplicated
function/method listing that I fear may confuse people.
> > If we don't have the classname there we cannot link to the method
> > since we don't know to which class it belongs to (may be inherited..).
>
> I understand XSLT has somewhat deficient string comparison facilities,
> but what if the class name was omitted if it was equal to the current
> class definition?
We are ditching xslt in favor of the new PHP based rendering system
(see the top news entry on php.net :)), called PhD, which uses 3% of
the time the xslt rendering takes...
But I really don't like these kind of rendering hacks, we should
rather fix it at the markup level if at all possible (which I don't
think it is :().
I also think it may be confusing for people needing to check if there
is a comment above the method to know if its an inherited one (and
from which class) or not.
-Hannes