Win32-GUI
view release on metacpan or search on metacpan
docs/Documentation.txt view on Meta::CPAN
the Source (XS, CPP and PM files). Depending on the package,
there may be documentation in sub-packages below this one.
(See doPodDocs script, later)
* Win32::GUI::UserGuide docs/GUI/UserGuide/
- Win32::GUI::UserGuide::Readme docs/GUI/UserGuide/Readme.pod
Win32::GUI Readme file. This is used to build Readme and
Readme.html that are put into the distribution files
(see doReadme script, later)
- Win32::GUI::UserGuide::Introduction docs/GUI/UserGuide/Introduction.pod
A brief introduction to Win32::GUI
- Win32::GUI::UserGuide::Concepts docs/GUI/UserGuide/Concepts.pod
A overview of the Win32::GUI concepts
- Win32::GUI::UserGuide::FAQ docs/GUI/UserGuide/FAQ.pod
A (currently outdated) FAQ.
* Win32::GUI::Reference docs/GUI/Reference/
- Win32::GUI::Reference::Packages docs/GUI/Reference/Packages.pod
A list of all the Win32::GUI packages, with links to the
per-package documentation. Package list is built automatically
(See doPodDocs script, later)
- Win32::GUI::Reference::Methods docs/GUI/Reference/Methods.pod
A list of the common methods - actually a list of all the
methods in the Win32::GUI package. Method list is built
automatically.
- Win32::GUI::Reference::Options docs/GUI/Reference/Options.pod
A list of the common options.
- Win32::GUI::Reference::Events docs/GUI/Reference/Events.pod
A list of common events - actually a list of all events found
with "APPLIES_TO:*". Event list is built automatically.
* Win32::GUI::Tutorial docs/GUI/Tutorial.pod
Table of contents for the tutorial
- Win32::GUI::Tutorial::Part1 docs/GUI/Tutorial/Part1.pod
Part 1 of the tutorial
- Win32::GUI::Tutorial::Part2 docs/GUI/Tutorial/Part2.pod
Part 2 of the tutorial
- Win32::GUI::Tutorial::Part3 docs/GUI/Tutorial/Part3.pod
Part 3 of the tutorial
- Win32::GUI::Tutorial::Part4 docs/GUI/Tutorial/Part4.pod
Part 4 of the tutorial
- Win32::GUI::Tutorial::Part5 docs/GUI/Tutorial/Part5.pod
Part 5 of the tutorial
- Win32::GUI::Tutorial::Part9 docs/GUI/Tutorial/Part9.pod
Part 9 of the tutorial
EMBEDED DOCUMENTATION
=====================
The Embedded documentation is turned into POD documentation
by the script 'build_tools/doPodDocs.pl'. This tool is
run by the make target 'all', and puts generated POD documentation
into the correct subdirectory of the blib directory tree, such that
it will be installed in the correct locations by 'make install'.
You may manually invoke this script from the commandline, using the make
target 'poddocs'.
When parsing the documentation, the script uses the package
'build_tools/SrcParser.pm' to parse out the documentation from the
source files.
* Packages
Introduced by a line containing the text:
(@)PACKAGE: Win32::GUI::PackageName
The first comment line, immediately following such a declaration is taken
as the package abstract, and should be a short title for the package
Any other comment lines following the package declaration are taken as
package description text.
* Methods
Introduced by a line containg the text:
(@)METHOD: MethodName(prototype)
This must happen AFTER a (@)PACKAGE declaration. Any comment lines
following such a declaration are taken as a description of the method,
with the exception of addiional (@)METHOD declarations, which are
assumed to be alternate calls for the same method. Alternate calls
my have no package declaration (DoStuff()) in which case they are
assumed to be in the sam epackage as is current, and will get a
'See method()' text, with a link to the current method; or they may
have a package declaration (Win32::GUI::SomePackage::doStuff()) in
which case they will be documented under the alternate package, including
the description, with an addition 'See OriginalPackage::OriginalMethod()'
line.
* Events
Intruduced by a line containg the text:
(@)EVENT: EventName(prototype)
Any following comment lines are assumed to be description, except lines
containing (@)APPLIES_TO: listOfPackages. Where listOfPAckages is either
* (applies to all packages) or non-qualified, comma seperated package names.
There must be at least one (@)APPLIES_TO line.
* DESCRIPTIONS
Decription blocks are continuous block of source comments following one of
the identifier lines described above. The descriptions amy contain POD
formatting commandes (e.g. B<...> C<...> etc.). Any line indented
by more than one space after the comment identifier (#, *) will be treated
as a POD 'verbatim' line. Continuous sets of such indented lines will be
treated as a POD verbatim block. Blank lines will be introduced either
side of verbatim blocks if not provided in the source.
Description blocks are also parsed for text that looks like:
See also method()
See new Win32::GUI:Package()
( run in 1.023 second using v1.01-cache-2.11-cpan-2c0d6866c4f )