cleanup .info-related docs [#137069]

now that http://drupal.org/node/132018 is committed, themes have .info files in 6.x.
furthermore, the syntax is different, since we can now specify nested data.
and, .info files for install profiles are coming right around the corner.

therefore, i think we need a reorganization of all the .info-related documentation. currently, we've got:
http://drupal.org/node/101009 "Writing .info files (Drupal 5.x)"
http://drupal.org/node/137062 "Writing .info files for themes (Drupal 6.x)" (newly added)
plus, the wisdom sprinkled into the module and theme update docs for 5.x and 6.x...

part of the problem (reflected in trying to submit this issue, in fact) is the rather hard separation of "Developer" and "Themer" docs. :(

i'm not exactly sure what's the best way to restructure everything, but i wanted to move discussion into a more appropriate place than at the bottom of (the already far too long) http://drupal.org/node/132018...

on a related topic, http://api.drupal.org/api/head/function/drupal_parse_info_file looks like crap, since the web version of the doxygen comment is stripping all whitespace. if anyone know how to fix that, i'd love to roll a patch to change the comment so that it's legible both in the code and on api.d.o...

thanks,
-derek

Comments

Comment #1

Steven CreditAttribution: Steven commented 18 April 2007 at 02:55

I updated the doxygen in core with @verbatim tags (as used in theme.inc) however it appears api.module doesn't actually support this. Ack.

I'm thinking a dependency on codefilter.module could solve this with a minimum of custom code. I'll see what I can do about that.

Comment #2

JohnAlbin

he/they/他

English

Taipei, Taiwan

CreditAttribution: JohnAlbin commented 10 October 2007 at 18:52

Since the new Theme developers guide Drupal 6 isn’t linked from the Handbook page, I’ve updated both http://drupal.org/node/137062 and http://drupal.org/node/171205 with tons of .info details for theme developers.

However, since there were several separate theme .info features added, I fear that I’ve missed something.

Also, the info I added about the ini syntax came mostly from the PHPDocs for drupal_parse_info_file(), so that sidesteps the issues with API docs (from a theme developer's perspective.)