|
Subject: Re: Overcoming limitations of reST tables Newsgroups: gmane.text.docutils.devel Date: 2005-08-25 21:59:37 GMT (2 years, 37 weeks, 18 hours and 49 minutes ago)
> David Goodger wrote:
>> Perhaps we need a "container-class" directive: like "class", but
>> applies to the container/parent. This would also be useful for list
>> items.
[Mark Nodine]
> This proposal might be useful in some contexts, but it wouldn't
> allow, for example, to apply a class to a <row> since it's
> a level above the <entry> container.
It would if defined flexibly enough:
.. container-class:: classname
:levels: 2
The existing class directive could simply be extended instead:
.. class:: classname
:parent: 2
The parent option's default could be 1 if used without an argument,
meaning "immediate parent". 2 means parent's parent, etc. Of course,
not including the parent option at all would leave the behavior as it
is now.
Alternatively or additionally, the parent option could take the name
of the element as argument:
.. class:: classname
:parent: row
Admittedly, this would be an ¸ber-power-user feature.
>> Why bother? Why not go whole-hog instead, and make a directive
>> that parses an established table standard, like the OASIS XML
>> Exchange Table Model (a.k.a. CALS tables)?
...
> Yes. Something like this would be a reasonable compromise and would
> be eminently generatable. Observations:
>
> 1. It's not quite "whole hog" since the contents of <entry> would
> still need to be parsed in your example to produce the
> bullet_list.
Call it half-hog then
|
|
|