| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bit more specific and unobtrusive.
Instead of using a bare except to just silently ignore all encompassed
formatting bugs, invoke .Format() only for items that hasattr
identifies as having the method. For any other items, return the
string representation of the item. This way, python objects that are
mistakenly expected to behave like containers or whatever will be
presented as the python objects they are - making it easier to track
down the error, without crashing the presentation process as a whole.
Moreover, it may be a non-error - any object with a string
representation can be put in an htmlformat container, and show
through.
|
| |
|
|
|
|
| |
(or frames - ptui).
Document.Format() - enclose the title in <head>...</head>.
|
| |
|
|
| |
attributes) on generated documents.
|
| |
|
|
|
|
|
|
|
|
| |
show through, instead of silently failing to show the intended
objects.
Something in between might be better, where the failing rendition is
replaced by a placehold that indicates what failed, but doesn't
disrupt the entire computation. However, until that is resolved, the
bugs will show, instead of hiding in the cupboards...
|
| |
|
|
|
|
| |
it's much clearer which button goes with which label when the buttons
are on the right. If the other cases, where the labels don't wrap to
a second line, it's not so clear, and still a bit ambiguous sometimes.
|
| |
|
|
|
|
|
|
| |
to get the whitespace between entries, instead of the (ugly, in some
cases) kludge i implemented before. Ideally we would group each
name/button pair together in an individual table cell, but i haven't
scoped out the html format mechanism well enough to do that, yet.
(John, are you listening?)
|
| |
|
|
|
| |
put a note in the FontSize class docstring that it is being
deprecated.
|
| | |
|
| |
|
