David,
Could you please look at the 'numbered list' format used for messages in both
search results and user posting history?
At SETI, there is a single visible horizontal rule between the message header
and the text, and no divider at all between the end-of-text and the header for
the next message.
At BOINC, it's slightly better with heavier rules between messages and lighter
rules between header and body - but the distinction is very slight.
On Thursday, 8 December 2016, 8:45, Jord van der Elst
wrote:
This doesn't look good on my mobile browser, Dolphin. The main index is now
all squashed together, with the Threads, Posts and Last Post columns are
super imposed over each other, even when I zoom out.
The individual forum indexes do look good.
But then all text in posts are now squashed into a single one-word column,
that I cannot resize.
(Attached for those that can see them, some images)
Even in Chrome the Threads, Posts and Last Post columns are right up
against each other, and here I can only zoom in, not out.
The same post column is now slightly broader, allowing for as many as four
words in the column.
-- Jord van der Elst.
On Thu, Dec 8, 2016 at 3:58 AM, David Anderson
wrote:
> Thanks; that solved the problem.
> I committed it and deployed on SETI@home.
> I used a slightly wider author column (10em) to accommodate strings like
> "Volunteer moderator".
>
> -- David
>
> On 12/1/2016 1:47 PM, Juha Sointusalo wrote:
>
>>
>> Ok, pre-formatted text stretching table cells and allowing other text to
>> go off-screen.
>>
>> Tables that have pre-formatted text need to be fixed to 100% width:
>>
>> width: 100%;
>> table-layout: fixed;
>>
>> These tables are in Thread view, Post to thread, PM Inbox, Forum search
>> results, Posts by user and Profile: user (the inner table). The theme used
>> in Seti website seems to have tables set to 100% width already but it
>> doesn't hurt to make sure the width stays that even if the theme is changed.
>>
>> When table layout is fixed browser doesn't adjust column widths based on
>> their content any more. Instead the browser divides the available space
>> evenly across the columns unless the browser is told otherwise.
>>
>> Thread view and Post to thread needs width: 8em; set for the author
>> column, PM Inbox needs width: 8em; set for subject and sender columns. The
>> previous style used width: 136px; but that is not exactly responsive to
>> font size changes. I chose 8em because it looks good on my screen.
>>
>> Team search results and Team display are a bit harder. Both could use
>> fixed layout but I'm not sure what to do next. If I limit column widths in
>> Team search results the page looks bad on narrow displays; if I don't it
>> looks bad on wide displays. On Team display page the header that spans the
>> entire table seems to prevent setting width to columns. Anyway, I guess
>> it's rare enough to have very long lines in these two pages so they could
>> probably be left as they are now.
>>
>> The theme used on Seti has black on light grey for blocks which
>> makes large blocks of text to stand out quite a lot on dark theme. I think
>> monospace font would be enough and would use normal text colour for it.
>>
>> You changed [code] BBcode element to render to with white-space:
>> pre-wrap;. For some reason the previous style had made a block level
>> element. Normally it's an inline element, that is, it can be used within
>> text like I have done throughout this message. I would like [code] to be
>> rendered to with slight adjustment. To keep compatibility with
>> existing uses of [code], needs white-space: pre-wrap; set. (There's
>> a small snag with using for multiple lines; the first line is
>> slightly indented.) The colour used for in Seti theme is... eh,
>> eye-catching, so same treatment as with .
>>
>> Putting those two together:
>>
>> code {
>> color: inherit;
>> background-color: inherit;
>> white-space: pre-wrap;
>> }
>>
>> pre {
>> color: inherit;
>> background-color: inherit;
>> white-space: pre;
>> }
>>
>> That leaves borders for theme designers to decide.
>>
>> -Juha
>>
>
> ___
> boinc_projects mailing list
> boinc_proje...@ssl.berkeley.edu
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.