the addons wiki page is getting really long, too long.
a victim of its own success!
any objection to splitting it up into individual
Raster-addons
Vector-addons
...
sub-pages, and keeping the front page as table of contents?
wish:
figure a way to create a dynamic table containing the section
headers (ie module names) from the sub-pages on the front page.
(perhaps make the table 5-7 columns wide, sort alphabetically
by row or column?
prerequisite:
figure a way to adjust the {{AddonCmd}} macro to point to the
correct place after the change. if the above wish is filled,
this might be done by linking to the row in the table for the
command on the main page. or maybe adjusting the macro to point
to the sub-page is easier than creating the dynamic table?
Just an short answer - I would vote against splitting add-on page into
smaller ones, as current long list is good for searching for modules
if You have no idea what are You looking for. Current format is a bit
chaotic, still it works.
Maris.
2011/6/18 Hamish <hamish_b@yahoo.com>:
Hi,
the addons wiki page is getting really long, too long.
a victim of its own success!
any objection to splitting it up into individual
Raster-addons
Vector-addons
...
sub-pages, and keeping the front page as table of contents?
wish:
figure a way to create a dynamic table containing the section
headers (ie module names) from the sub-pages on the front page.
(perhaps make the table 5-7 columns wide, sort alphabetically
by row or column?
prerequisite:
figure a way to adjust the {{AddonCmd}} macro to point to the
correct place after the change. if the above wish is filled,
this might be done by linking to the row in the table for the
command on the main page. or maybe adjusting the macro to point
to the sub-page is easier than creating the dynamic table?