Skip to main content
news

Re: spreadsheet ergonomics

owl
SubjectRe: spreadsheet ergonomics
Fromowl
Date2017-04-05 05:59 (2017-04-05 03:59)
Message-ID<i88vz003.pvh4e2@rooftop.invalid>
Client
Newsgroupscomp.os.linux.advocacy
FollowsSnit
FollowupsSnit (33m) > owl

Snit <usenet@gallopinginsanity.com>wrote:

Snit
On 4/4/17, 7:05 PM, in article javz903.abu@rooftop.invalid, "owl" <owl@rooftop.invalid>wrote:

owl
Snit <usenet@gallopinginsanity.com>wrote:

Snit
On 4/4/17, 6:14 PM, in article avx89zb.f8c9a@rooftop.invalid, "owl" <owl@rooftop.invalid>wrote:

owl
Snit <usenet@gallopinginsanity.com>wrote:

Snit
On 4/4/17, 3:38 PM, in article ahbiz003.buyr@rooftop.invalid, "owl" <owl@rooftop.invalid>wrote:

...

owl
How long does it take in Numbers to create a sheet with 52000 tables with locked formulas and labels (A-Z with 2000 tables in each column, each table with a label{#} at the top, and a sum the bottom, summing 10 rows)? And how long does it take to navigate to a specific such table?

2.57 seconds here with sc.

Snit
I assume you are sending it instructions with some script... but even if I did that I am SURE Numbers would take much longer. That is the type task Numbers sucks at -- no argument here. And I also realize that there are many instances where people DO want spreadsheets similar to what you speak of to deal with large amounts of data and number crunching.

Well, try it and let's see the results.

For that matter, did you ever even get a set of tables on a single sheet where you can update any table and have it flow through without flickering? If so would love to see how.

owl
You are aware that sc only presents one sheet at a time. It is necessary to use multiple sheets to have floating tables.

Snit
Yes... I know of that limitation of it.

owl
This has been shown to you multiple times already, and, aside from the Mack fluff, ever functional aspect has been addressed.

Snit
What do you mean by "fluff" -- can you be specific?

owl
Emphasis on style instead of substance.

Snit
You tend to label things which benefit usability as "fluff" or just "style" when they, often, are key to how tools are used.

To Mack, everything is a flyer.

...

LOL! Yeah, no assuming you have enough common sense to figure out people do not want to lose data. Repeatedly.

owl
Where is the "common sense" in renaming an open file?

Snit
Has already been discussed MANY times with me giving specific examples of when I have done so. Just off the top of my head:

* Downloaded a video and opened it... then realized it is was in the place I store it nor with the name (or label) I prefer. No reason to close it just to rename and move it (and add a label)!

* Opened files named "[Whatever] - New" and "[Whatever]" and, as I worked with them, realize I had related files with a different naming scheme... and saved in different folders. So renamed them to "[Whatever]" and "[Whatever] - OLD" and also moved them to their correct folders.

owl
None of that represents "common sense."

Snit
So it makes more sense to close the files, rename them, move them, and then open them? Heck, even if you do it that way it is STILL easier on macOS -- you can (for most programs) just use the recent items lists!

So even doing that rather non-intuitive, inefficient, workaround for a lack of a simple ability to rename and move files without closing them Linux still does not do a very good job.

Nobody even cares to do that. Mack is only a small percentage of computers, and it's the only one that does that insanity.

Why in situations such as that, as well as any other similar one, would you want to HAVE to close the file just to rename it or move it. That is a pretty big limitation!

owl
"Save As..."

Snit
That creates a copy.

So?

owl
And I believe I read something about people complaining about not having a "Save As..." and so they put it back, along with a "Duplicate" choice. The Apple crew is just a bunch of clods.

Snit
I think it is good to have both available -- they do different things and both are of value!

So "duplicate" deletes the original?

Right... your solution for one program, not built in and never explained, and with the video with bizarre zooming (curious why you did that... does not really hurt it but just weird).

owl
It may remain a mystery. I keep some magic to myself.

Snit
Meaning faked or, more likely, some significant weaknesses you will not share. OK.

It's not faked. It's very real. And by the way that "bizarre zooming" is xmag, which has been around since the dawn of time. I'm surpised you didn't recognize it. My window manager doesn't support zooming, so I use xmag.

But it shows your thinking in terms of one program

owl
Once again you try to move the goal posts. Your specification was for doing it LibreOffice.

Snit
The idea is to have it be, largely, system wide. And I have noted where the macOS environment, while doing a better job at it, is far from perfect.

That's the idea *now*.

and not the system... while showing something I did not expect you to so, sure, well done. Curious why you never shared it... I suspect you had different instances of LO or other weaknesses.

owl
Nope.

Snit
If there was not a significant weakness you would happily share it. Not going to play guessing games to try to figure out what, but clearly there is.

Wouldn't want you to get a virus.

If nothing else you cannot just drag and drop from your file browser.

owl
My browser?

Snit
<https://en.wikipedia.org/wiki/File_manager> ----- A file manager or file browser is a computer program that provides a user interface to manage files and folders. The most common operations performed on files or groups of files include creating, opening (e.g. viewing, playing, editing or printing), renaming, moving or copying, deleting and searching for files, as well as modifying file attributes, properties and file permissions. Folders and files may be displayed in a hierarchical tree based on their directory structure. Some file managers contain features inspired by web browsers, including forward and back navigational buttons. -----

This is a common way of moving and renaming files. And, of course, with Linux if you do that without closing a file first you are far more likely to run into problems.

Nope.

owl
It is your responsibility to detail everything you expect from a solution.

Snit
The assumption of basic common sense is included in everything I say.

owl
A written specification represents the totality of the requirments.

Snit
So you do not assume and take into consideration common sense with your work. Fair enough. That is just one other way we look at things differently. For me common sense and thinking in terms of risks is important and just comes naturally. For you that is not the case.

owl
You wrote the specification. It's your FAIL. I can't help it if you are unable to put a coherent request to paper.

Snit
As I said, I made the assumption of common sense from you... and, yes, clearly that was my failure.

Nope. You just fucked up your specification. Simple as that.

Snit (33m) > owl