Re: PhD generated Indexes
| From: | Hannes Magnusson | Date: | Thu, 07 Jul 2011 07:23:20 +0000 |
| Subject: | Re: PhD generated Indexes | ||
| References: | 1 2 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969382889@lists.php.net to get a copy of this message | ||
On Wed, Jul 6, 2011 at 13:20, Hannes Magnusson
<hannes.magnusson@gmail.com> wrote:
> On Wed, Jul 6, 2011 at 12:20, Hannes Magnusson
> <hannes.magnusson@gmail.com> wrote:
>> Hi all
>>
>>
>> Currently our php.net/indexes is "manually generated" with the
>> genfuncindex.php script..
>>
>> I'd like to propose to use an PI for this, and generate the list in PhD...
>> You could print out indexes for pretty much anything PhD indexes.. so
>> the following patch prints out the list of all refentries and
>> examples.
>
>
> There is a slight problem with that.
> There doesn't seem to be any correct way of differentiating
> refentries.. so if its a refentry for function, method, variable, url
> wrapper, context option.. PhD has no idea.
> I played around a little trying to teach the indexer the difference
> (depending on the refnames, and the rest of the structure of the
> file), but it becomes very messy and not 100% accurate.
>
> I can't think of any other way then to modify the markup to explicitly
> mention what kind of refentry it is.. thoughts?
> Maybe its not important for the indexes page, just list all refentries
> alphabetically?
So.. Whats the next step here then?
Adding explicit markup for this would also simplify the way PhD_IDE
works. The funcgen.txt file for example only has refentries below
xml:id="funcref" and therefore misses the classes and stuff in
language/
In our newest skeletons we have a role="oop" and role="procedural" for
methodsynopsis to identify the OO and functional interface for aliased
method/functions.
role="noversion" is already reserved for refentries we absolutely do
not want to print out versioninformation for..
What other options do we have?
-Hannes