From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [maintainer-tools PATCH 5/5] doc: use Sphinx bizstyle builtin html theme
Date: Thu, 10 Aug 2017 10:22:40 +0300 [thread overview]
Message-ID: <87fuczubsv.fsf@intel.com> (raw)
In-Reply-To: <CABVU7+sjzNGXvAnozgC_8tCKxH9Xd4Mfd6S2Co-o0gP6U3UhpQ@mail.gmail.com>
On Thu, 10 Aug 2017, Rodrigo Vivi <rodrigo.vivi@gmail.com> wrote:
> On Wed, Aug 9, 2017 at 2:08 PM, Jani Nikula <jani.nikula@intel.com> wrote:
>> Matter of taste, but looks better than the default alabaster,
>
> not sure which one I preferred...
> alabaster goes better with 01.org... but it indeed is not very good...
>
>> and is
>> less trouble than requiring some external themes (such as the sphinx rtd
>> theme used in the kernel).
>
> less trouble is good, but since we are already making changes now and
> forcing new packages I believe we could force to use same style as
> kernel so we keep in sync...
Looks like sphinx_rtd_theme is builtin since Sphinx 1.3, and I think we
could easily require that.
The trouble is that the sphinx_rtd_theme forces a fairly narrow layout
horizontally, without horizontal scroll bars, and the wavedrom timeline
overflows the content box and is clipped at the window border. Fail.
I peeked at the Sphinx wavedrom extension, and incorporated their raw
html hack to provide scrollbars for overflowing content. With hack [1],
without hack [2].
What do people think?
(Perhaps the right answer is to use something other than wavedrom
altogether, but I don't have the time and I don't want it to block the
Sphinx conversion.)
BR,
Jani.
[1] https://people.freedesktop.org/~jani/html/drm-intel.html#merge-timeline
[2] https://people.freedesktop.org/~jani/html/drm-misc.html#merge-timeline
>
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> conf.py | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/conf.py b/conf.py
>> index 2e7acb8e76ca..7293d9ddab80 100644
>> --- a/conf.py
>> +++ b/conf.py
>> @@ -119,7 +119,7 @@ todo_include_todos = False
>> # The theme to use for HTML and HTML Help pages. See the documentation for
>> # a list of builtin themes.
>> #
>> -html_theme = 'alabaster'
>> +html_theme = 'bizstyle'
>>
>> # Theme options are theme-specific and customize the look and feel of a theme
>> # further. For a list of options available for each theme, see the
>> --
>> 2.11.0
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-10 7:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 21:08 [maintainer-tools PATCH 0/5] add Sphinx doc build to maintainer tools Jani Nikula
2017-08-09 21:08 ` [maintainer-tools PATCH 1/5] mancheck: run dim.rst through rst2man Jani Nikula
2017-08-09 22:45 ` Rodrigo Vivi
2017-08-09 21:08 ` [maintainer-tools PATCH 2/5] build: add drm-misc-commit-flow.svg to clean target Jani Nikula
2017-08-09 22:45 ` Rodrigo Vivi
2017-08-09 21:08 ` [maintainer-tools PATCH 3/5] doc: use window.onload to call WaveDrom.ProcessAll() Jani Nikula
2017-08-09 22:49 ` Rodrigo Vivi
2017-08-10 8:32 ` Jani Nikula
2017-08-09 21:08 ` [maintainer-tools PATCH 4/5] doc: build documentation using Sphinx Jani Nikula
2017-08-09 22:56 ` Rodrigo Vivi
2017-08-10 6:49 ` Jani Nikula
2017-08-09 21:08 ` [maintainer-tools PATCH 5/5] doc: use Sphinx bizstyle builtin html theme Jani Nikula
2017-08-09 23:09 ` Rodrigo Vivi
2017-08-10 7:22 ` Jani Nikula [this message]
2017-08-10 15:11 ` Rodrigo Vivi
2017-08-09 21:33 ` [maintainer-tools PATCH 6/5] doc: load WaveDrom scripts directly from CDN instead of bundling Jani Nikula
2017-08-09 23:00 ` Rodrigo Vivi
2017-08-10 6:43 ` Jani Nikula
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=87fuczubsv.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox