From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v1] doc: autogenerate nic overview table from ini files
Date: Thu, 30 Jun 2016 20:25:14 +0200 [thread overview]
Message-ID: <1604656.XReoQ6n0NJ@xps13> (raw)
In-Reply-To: <1467309817-11739-1-git-send-email-john.mcnamara@intel.com>
2016-06-30 19:03, John McNamara:
> This patch converts the NIC feature table in the overview doc into a set of
> ini files and adds some functions into the Sphinx conf.py file to convert them
> back into an RST table.
>
> The reason for doing this is to make it easier for PMD maintainers to update
> the feature matrix that makes up the table and to avoid frequent and hard to
> resolve conflicts in doc/guides/nics/overview.rst.
Great idea!
Would it be possible to make it a bit more generic and reusable to
generate other tables of this kind?
> * In order to avoid the merge conflict issue noted above the RST table is now
> in an external RST include file and excluded from the repo via .gitignore.
It would be better to generate the rst file in the build directory.
But I guess it makes sphinx build more difficult.
> * Blank entries in the PMD ini files are optional. They will get a default
> blank entry in the RST table based on the entries in the default.ini file.
> The ini files in this patch were generated programmatically from the
> original RST table.
I don't think there is a benefit to have blank entries in the .ini file.
And there would be less conflicts if the guideline was to avoid blank entries
when adding a new feature.
>
> * I would like to extend this to produce a pure Html table with rotated column
> headers like this: https://css-tricks.com/rotated-table-column-headers/
> I tried to get this to work within the current RST + CSS preamble but
> failed.
Nice
> * I would also like to extend this to produce a table, or more likely a number
> of tables, that would display the same information in the PDF document
> without going off the page.
PDF output is restrictive :)
next prev parent reply other threads:[~2016-06-30 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 18:03 [PATCH v1] doc: autogenerate nic overview table from ini files John McNamara
2016-06-30 18:03 ` John McNamara
2016-06-30 18:25 ` Thomas Monjalon [this message]
2016-07-01 1:40 ` Yuanhan Liu
2016-07-08 19:52 ` Mcnamara, John
2016-07-17 12:59 ` [PATCH v2] " John McNamara
2016-07-19 13:08 ` Ferruh Yigit
2016-07-29 11:59 ` [PATCH v3] " John McNamara
2016-07-29 12:02 ` Mcnamara, John
2016-08-01 21:37 ` Thomas Monjalon
2016-08-03 14:32 ` Bruce Richardson
2016-08-03 16:44 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1604656.XReoQ6n0NJ@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.