diff --git a/doc/todo/add_remove_to_actionlist.mdwn b/doc/todo/add_remove_to_actionlist.mdwn index 92beabc94..df0f75a59 100644 --- a/doc/todo/add_remove_to_actionlist.mdwn +++ b/doc/todo/add_remove_to_actionlist.mdwn @@ -14,69 +14,3 @@ submission more carefully). I haven't begun on the 'rename' plugin. -- [[Jon]] [[!tag wishlist patch]] - -> This seems like weird overloading of the header parameter - it's -> table data, except when it isn't. - -> > My first cut (now rebased out of existence I think) introduced a -> > new "headerblock" parameter, but trying to clearly document the -> > interaction of data/headerblock/header parameters was too awkward. -- [[Jon]] - -> Perhaps -> something like this would be easier to use in practice? -> (and also more featureful :-) ) -> -> \[[!table header="2 rows 1 column" data=""" -> Name | Platform || -> | Windows | Mac | Linux -> ikiwiki | no | yes | yes -> Starcraft | yes | yes | via Wine -> """]] - -> > Thanks for your prompt feedback! -> > -> > This would probably be good, yes, and having mixed row/column headers is -> > definitely a nice-to-have. I don't relish the prospect of writing the parser -> > but I see you've made a stab already... -> > -> > One thing you'd lose, but it's debatable whether this is valuable, would be -> > to have the header defined in the directive, and the remaining table data -> > declared in an external CSV. -- [[Jon]] - -> intended to be rendered like -> ->
Name | Platform | ->||
---|---|---|---|
Windows | Mac | Linux | |
ikiwiki | no | yes | yes |
Starcraft | yes | yes | via Wine |