RFC: Skeleton for php-doc-function.xml
 Version: 0.2
 State: Alpha
 Author: Philip Olson
 - Think other parts like class, method, predefined variables, constants, etc.
 - Discuss with multiple IDE developers, and ensure we include all desired information
 - Discuss handling of extensions with both OO and Procedural (ex: mysqli)
 - Discuss removing or adding elements, ex: add 'description' which might be the first paragraph of role=description?
 - Create a theme/format for PhD to generate this
 - Think about ways this could help find inconsistencies in the manual
 - Have methods for conversion into other forms like a sqlite db, funcindex.xml, quickref, ...
 - Discuss license issues for various uses like IDE integration
 - This deals with:
 - The current version (0.2) should not be taken too seriously -- it's a proof of concept
   Its intention is to maximize the available information by adding options for users. For
   example, it's likely an IDE developer will not want all of this information so they'll
   pull (and format) their desired elements accordingly.
  <version>PHP 3, 4, 5</version>
  <purpose>Checks the foo of a bar</purpose>
  <!-- Before going live, let's evaluate our current manual IDs and realize:
       - They should work forever 
       - They are consistent
       - We like them
       - Note: some are not lowercase, problem?
      Typically the following url works: so
  <!-- This information comes from both the methodsynopsis and parameters role -->
      <description>Used for this and that</description>
      <description>Used for this and that</description>
  <!-- Type from methodsynopsis, description from return role -->
    <description>This and that</description>
      <change>this and that changed</change>
      <change>another change</change>
  <!-- Discuss: we may or may not want to add examples.
       We don't always have a return, but sometimes via screen.
    <title>foo() example</title>
    <code>Not sure if we want this
<!-- Most documents do not have this, but some do -->
  <description>Other error conditions</description>
<!-- There are several different types of notes, discuss -->
    <description>This is needed</description>
    <description>be careful about</description>
    <description>watch out!</description>
<!-- Determine the handling of our different type of see also links.
     - Typically contain a link and descriptive text
     - Typically are a single element, ex: <function>foo</function> 
     - Sometimes include descriptive text, ex: the <link linkend="bar">bar chapter</link>
     - The 'purpose' of these are available in phd
    <description>purpose of baz</description>
    <name>stuff within first link</name>
    <description>the entire text</description>

</function> </code>

doc/skeletons/ide-function.txt · Last modified: 2011/04/06 12:59 (external edit)