Ihor Radchenko <yantar92@posteo.net> writes:
> The "All" tab in the report list shows all the report types mixed> together.
Yes. That's because once you have distinct URLs for patches, bugs,
etc., then you need the home (aka "/") URL to list all reports.
> I find the previous version with reports grouped by type more> readable.
Are other tabs not useful enough?
While providing several tables in the "All" tab is possible in theory,
I find it would break the "one tab = one table" UI expectations.
Perhaps sorting by subject could group report by types and then sort
subjects by alphabetical order? (Only sorting by alphabetical order
is not useful enough per se, IMO.)
WDYT?
--
Bastien
Bastien <bzg@gnu.org> writes:
> Ihor Radchenko <yantar92@posteo.net> writes:>>> The "All" tab in the report list shows all the report types mixed>> together. >> Yes. That's because once you have distinct URLs for patches, bugs,> etc., then you need the home (aka "/") URL to list all reports.
I can see how it can be useful for RSS consumption, but visually it is
confusing. Especially as a default summary.
Also, certain report types require different kind of fields. Like
"Votes" field in requests. Cramping everything together either requires
displaying all the possible fields together or omitting some. Either way
is not great for display.
>> I find the previous version with reports grouped by type more>> readable.>> Are other tabs not useful enough?
They are. I am mostly concerned about usefulness of the "default" view,
which, IMHO, should serve as a quick overview of what is going on in the
ML.
> While providing several tables in the "All" tab is possible in theory,> I find it would break the "one tab = one table" UI expectations.
I'd say that one tab = one table is not UI, but rather API. UI
expectations are for easier human consumption.
> Perhaps sorting by subject could group report by types and then sort> subjects by alphabetical order? (Only sorting by alphabetical order> is not useful enough per se, IMO.)>> WDYT?
This sounds confusing.
In any case, I am mostly interested to have a good overview of all the
active reports. To quickly scroll and grasp the situation; without
clicking anything.
Cramping everything together is not ideal, IMHO.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
Ihor Radchenko <yantar92@posteo.net> writes:
> I can see how it can be useful for RSS consumption, but visually it is> confusing. Especially as a default summary.
Yes, I get the feeling. I also kinda miss the previous single page.
Probably we can have a default single-page theme, and other themes can
explore using tabs.
One question though: what default order or the sections in the default
page? Would "News / Bugs / Patches / Requests" be natural?
--
Bastien
[TASK] Rework the default UI/theme, testing the single-page approach
Bastien <bzg@gnu.org> writes:
> The default themes (both bulma/plain) should expose reports in a> single page, with one section per report type.
One thing to remember when experimenting with this idea: the index
page can contain *a lot* of reports, especially since Woof can track
several mailing lists.
Does it make sense to display patches from several different lists
in a section called "Patches"?
What about index pages with >1000 entries?
The current design is made to allow pagination below the index table.
Having the single-page design optionally available as the default one
for per-source page (e.g. https://woof.bzg.fr/source/woof/) is worth
exploring, though.
--
Bastien Guerry
Re: [TASK] Rework the default UI/theme, testing the single-page approach
Bastien Guerry <bzg@gnu.org> writes:
> Having the single-page design optionally available as the default one> for per-source page (e.g. https://woof.bzg.fr/source/woof/) is worth> exploring, though.
Another idea could be to have the home page proposing sections for
each report type, but limited to a number of entries in each section
(e.g. 10?).
Entries would be sorted by priority then date, so that you can the
10 most important/urgent/recent bugs, patches, etc. from all mailing
lists (in the home page) or from one mailing list (in the one-source
view.)
--
Bastien Guerry
Bastien <bzg@gnu.org> writes:
> One question though: what default order or the sections in the default> page? Would "News / Bugs / Patches / Requests" be natural?
I feel like News / Requests / Bugs / Patches will be better.
The first two are what we want more people to see.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>