This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients belopolsky, eric.araujo, ezio.melotti, lukasz.langa, rhettinger, ron_adam
Date 2010-12-17.11:47:02
SpamBayes Score 8.806787e-07
Marked as misclassified No
Message-id <1292586424.57.0.840815118119.issue10716@psf.upfronthosting.co.za>
In-reply-to
Content
[Raymond]
> I'm looking for a deeper fix, all the in-line styling replaced by a
> stylesheet.  Can you guys work together on bring this to fruition?
When I talked about the CSS reset, I was referring to a precise part of the file proposed by Ron, so we’re already discussing together :-)

I wonder how desirable it is to preserve the look and feel of the pages.  We all agree on externalizing the CSS and add a way for the users to add their own stylesheet; why not take the opportunity to also improve the style?  Huge blocks of colors are not that attractive to me :)

Regarding workflow, I’d find easier to start from bare HTML that works nice (yes, I test with w3m) and then add style.  Technically, I’d like to maintain the HTML as a small set of files (in pydoc_data) containing fragments of HTML with placeholders ({} or $): That’s easy to edit, to validate (a very simple script can put the fragments together) and to use.

I agree that the CSS file should be as short as possible (in content), but not too short (in file size).  For example, trailing commas in properties and brackets on their own line will allow nice diffs, just like Python.

(I won’t have much time for Python in December, but we have a lot of time before 3.3b1 :)
History
Date User Action Args
2010-12-17 11:47:04eric.araujosetrecipients: + eric.araujo, rhettinger, belopolsky, ron_adam, ezio.melotti, lukasz.langa
2010-12-17 11:47:04eric.araujosetmessageid: <1292586424.57.0.840815118119.issue10716@psf.upfronthosting.co.za>
2010-12-17 11:47:02eric.araujolinkissue10716 messages
2010-12-17 11:47:02eric.araujocreate