On Tue, Oct 21, 2008 at 18:16, Anthony Bedford <[EMAIL PROTECTED]> wrote: > Hannes Magnusson wrote: >> This probably works for class variables documented in <refentry>s, >> although I've never tried that. > > What is the recommended markup for class variables? I tried <property> but > that didn't create a link.
I don't think we ever reference class variables anywhere in the current documentations except for on the "class reference pages" (such as http://no2.php.net/manual/en/class.xmlreader.php). If you believe <property> would be the appropriate markup for it then we can implement it in PhD without ASAP. How do you want it to work? To link to class variables: <property>classname->variablename</property> to reference class variable and <property>classname::variablename</property> to reference static variable (::$varname and ::varname would both generate <a href="...">classname::$varname</a> markup)? And then the actual documentation follows the current skeletons (<classsynopsis><classname>classname</classname><fieldsynopsis><type>type</type><varname>variablename</varname></fieldsynopsis></classsynopsis> if decoumented as refentry... any suggestions improved for classname.xml markup with regards to class variables? (currently its just a <section><variableliste>.... which is used for bunch of other things too :( Just tell me how you wanted it to work and we'll implement it. By all means, don't let the current "supported markup" stop you from doing anything. Its PhDs fault if something isn't supported, not yours, so continue as if everything works perfectly and just file bug reports (preferably with suggested rendering specs) :) If you do however commit "unsupported markup", please don't do it on thursday/friday (because every friday we automatically push out new builds, and all "unsupported elements" will get a big fat red <TAGNAME> wrapped around it :)) -Hannes
