https://bugs.documentfoundation.org/show_bug.cgi?id=98754

--- Comment #8 from Göktuğ Kayaalp <[email protected]> ---
For Calc in particular, implementing pixelwise scroll would be a
differentiating addition, because currently the only major spreadsheet app with
support for that is Google Sheets. IIUC Excel lacks this feature, and IIRC
OnlyOffice also lacks it.

Below I will describe a couple use cases where this change would be very useful
and possibly give LO Calc an edge over other desktop spreadsheets.

In my use case I use Calc to maintain source material lists for my graduate
research (History), as well as timetables for my PhD. I have a "phd process"
spreadsheet for example, where one sheet is for planning the whole 4-year
process month-by-month, and then one sheet per semester with one week per cell,
with deadlines and major tasks listed for those weeks. Save for the annoyance
of scrolling due to current behaviour, it's an excellent way to plan these
things. I used a similar setup to plan my applications a few months ago, and am
now using a similar thing again to plan another bout of applications for
switching to a different university. It's allowed me to plan three concurrent
application processes precisely and productively.

I know that it's not just me doing this sort of thing because you see such
approaches recommended online.

As I said I also use it for managing sources. I have readings that need to be
organised, and using a spreadsheet for that task allows me to build a table
where I have one bibliographic item per row, where a shorthand reference is
side by side with a little note explaining why the thing is worth reading for
me (i.e. why its relevant to my studies, what salient things are in there), and
with another cell holding identifying info such as a full reference and some
links. I also track where the reading notes for the thing are, and the status
of the item (e.g. is it in my active readings list, is it read already, is it
cancelled).

This can be done by a reference manager app like Zotero or JabRef (I tried..)
but for such reading lists I found them substantially inferior to the above
approach because the way the metadata information and notes are presented is
not as easily browsed as the above method, and also because these apps are for
bibliographies first and foremost, they're rather rigid with the data you can
associate with your material. A spreadsheet is a much nicer way to present this
data, and it doesn't then pose the risk of filling up your reference manager
with bad metadata and a lot of shiny interesting little things you find on the
internet, making it unmanageable and having it generate bogus bibliographies
once you're writing (speaking from experience here). Another upside of this way
of doing is you don't really need to think about bibliographic metadata while
collecting stuff that you don't even know yet if you'll read or chuck away.
It's a really low friction way of doing things, so I prefer it over reference
managers or even maintaining a list in something like Markdown.

I've learned this method from a PhD YouTuber and literally the only downside
there is to it is problems with spreadsheet apps' UIs.

As I've said I've seen others doing similar things or recommending similar
usages. A cursory search on the web also shows that there are tutorials,
templates, recommendations, etc on how to use spreadsheets, usually Excel or
Google Sheets, in similar ways.

Hopefully this comment helps as an example of who'd be helped with such an
improvement and what are the use cases like.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to