User: Password:
|
|
Subscribe / Log in / New account

Seigo: Plasma.next()?

Seigo: Plasma.next()?

Posted Jan 29, 2013 15:13 UTC (Tue) by jpfrancois (subscriber, #65948)
Parent article: Seigo: Plasma.next()?

What if there are several app to open a given file, and the default suck ? Should I go in some device configuration menu to specify the application.

Viewer != Editor

Premature Simplification is the root of all evil. All this 'The computer can magically find what you want to do' has already failed numerous time before.
I hope lesson have been learned and the computer program has more intelligence than previous attempt at helping the poor user by making wrong choice for him.


(Log in to post comments)

Seigo: Plasma.next()?

Posted Jan 29, 2013 15:20 UTC (Tue) by jpfrancois (subscriber, #65948) [Link]

Hmm, I am ashamed I did not read the entry before jumping to conclusion based on LWN's carefully chosen quote ;)

My viewer != editor problem is adressed (vaguely) in the paragraph below LWN's quote.

Seigo: Plasma.next()?

Posted Jan 29, 2013 17:08 UTC (Tue) by drag (subscriber, #31333) [Link]

> What if there are several app to open a given file, and the default suck ?

Change the defaults?

The application launching stuff is standardized pretty well. Change your defaults.list file and you should change the defaults for everything.

https://wiki.archlinux.org/index.php/Default_Applications

Seigo: Plasma.next()?

Posted Jan 29, 2013 19:11 UTC (Tue) by arekm (subscriber, #4846) [Link]

What if default sucks for some files and other variant suck for different files (eg pdfs with bunch of text (okular is nice for these) vs pdfs with huge svg (okular is crap for these)) ?

Seigo: Plasma.next()?

Posted Jan 30, 2013 10:16 UTC (Wed) by aseigo (guest, #18394) [Link]

the invention of possibilities, though unrealized in practice, is the #1 cause of UI erosion through feature extension.

we have yet to run into the possibility you highlight on devices. note that on desktop it is common, and the workflow there remains as it always has been as a result of that.

(this is why it is so important to keep in mind that we design for different F+I+U [form factor + input method + use case] when creating different Plasma Workspaces. yes, they share 98% of the code and are highly interoperable .. they also present different workflows appropriate to the F+I+U tupple. so the touch focused UI works differently from the desktop one in this case)

as for the touch case .. if we find that this indeed becomes an issue on tablet as well, then we will address it in the UI there. my expectation would be to go the route of something like "long tap to select an alternate viewer", but that's just an immediate thought pulled by from my rear facing protrusion ;)

Seigo: Plasma.next()?

Posted Jan 30, 2013 17:56 UTC (Wed) by drag (subscriber, #31333) [Link]

> What if default sucks for some files and other variant suck for different files (eg pdfs with bunch of text (okular is nice for these) vs pdfs with huge svg (okular is crap for these)) ?

Oh.

Well for Apple they 'solved' this problem originally years ago through their use of resource forks in the file system.

http://en.wikipedia.org/wiki/Resource_fork

The file manager would read the resource fork for a file and would launch the appropriate application when you opened a file. So while there were defaults for all the file types Mac OS would keep track of the application that created a particular file and things of that nature. That way the system could intuitively deal with applications on a per file basis.

I think Windows has some sort of mechanism for managing per-file stuff, but I don't know what it is.

And, of course, nothing I've noticed in Linux addresses this.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds