Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #317512 > unrolled thread
| Started by | Nobody <nobody@invalid.com> |
|---|---|
| First post | 2015-08-29 14:33 -0500 |
| Last post | 2015-08-29 14:29 -0700 |
| Articles | 20 on this page of 127 — 12 participants |
Back to article view | Back to comp.os.linux.advocacy
Just click "like" Nobody <nobody@invalid.com> - 2015-08-29 14:33 -0500
Re: Just click "like" vallor <vallor@cultnix.org> - 2015-08-29 21:12 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-29 14:23 -0700
Re: Just click "like" vallor <vallor@cultnix.org> - 2015-08-29 23:20 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-29 16:36 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-30 00:37 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-29 17:43 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-30 01:23 +0000
Re: Just click "like" vallor <vallor@cultnix.org> - 2015-08-30 01:36 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-29 19:58 -0700
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-29 19:53 -0700
Re: Just click "like" vallor <vallor@cultnix.org> - 2015-08-30 01:18 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-29 19:17 -0700
Re: Just click "like" Nobody <nobody@invalid.com> - 2015-08-30 03:53 -0500
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-30 10:58 -0700
Re: Just click "like" Steve Carroll <fretwizzen@gmail.com> - 2015-08-30 13:44 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-30 21:03 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-30 14:38 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-30 22:00 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-30 15:15 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-30 22:43 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-30 17:33 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-31 03:25 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-30 21:06 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-31 05:11 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-30 22:18 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-31 05:35 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-30 22:37 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-31 05:50 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-30 22:55 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-31 06:18 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-30 23:39 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-31 07:15 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 00:20 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-31 12:42 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 09:25 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-31 20:55 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 14:04 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-31 21:56 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 16:45 -0700
Re: Just click "like" Peter Köhlmann <peter-koehlmann@t-online.de> - 2015-09-01 01:51 +0200
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 17:07 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 00:34 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 17:55 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 01:10 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 18:25 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 02:11 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 19:21 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 03:10 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 20:35 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 04:11 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 21:45 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 16:32 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 10:00 -0700
Re: Just click "like" vallor <vallor@cultnix.org> - 2015-09-01 17:10 +0000
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 17:30 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 10:40 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 22:16 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 15:41 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 22:53 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 16:12 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 23:19 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 16:28 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 23:39 +0000
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 23:56 +0000
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 00:11 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 17:57 -0700
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 17:42 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 00:47 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 17:58 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 01:13 +0000
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 04:17 +0000
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 05:23 +0000
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 04:09 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 21:50 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 05:16 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 10:38 -0700
Re: Just click "like" Peter Köhlmann <peter-koehlmann@t-online.de> - 2015-09-01 20:46 +0200
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 12:13 -0700
Re: Just click "like" Peter Köhlmann <peter-koehlmann@t-online.de> - 2015-09-01 21:43 +0200
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 13:42 -0700
Re: Just click "like" ronb <ronbNOSPAM@gmail.com> - 2015-09-01 22:01 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 15:07 -0700
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 15:08 -0700
Re: Just click "like" William Poaster <wp@dev.null> - 2015-09-01 23:14 +0100
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 15:42 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 22:14 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 15:35 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 22:43 +0000
Re: Just click "like" vallor <vallor@cultnix.org> - 2015-09-01 22:46 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 16:14 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 23:30 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 17:36 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 00:49 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 17:59 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 01:16 +0000
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 04:14 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 21:53 -0700
Just click "like" and Snit Michael Glasser fails Peter Köhlmann <peter-koehlmann@t-online.de> - 2015-09-02 10:18 +0200
Re: Just click "like" and Snit Michael Glasser fails Snit <usenet@gallopinginsanity.com> - 2015-09-02 05:07 -0700
Re: Just click "like" and Snit Michael Glasser fails Peter Köhlmann <peter-koehlmann@t-online.de> - 2015-09-02 14:31 +0200
Just click "like" and Snit Michael Glasser fails completely Peter Köhlmann <peter-koehlmann@t-online.de> - 2015-09-02 14:41 +0200
Re: Just click "like" and Snit Michael Glasser fails completely Peter Köhlmann <peter-koehlmann@t-online.de> - 2015-09-02 16:13 +0200
Re: Just click "like" and Snit Michael Glasser fails JEDIDIAH <jedi@nomad.mishnet> - 2015-09-03 11:37 -0500
Re: Just click "like" vallor <vallor@cultnix.org> - 2015-09-02 08:08 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-02 05:03 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 04:21 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-09-01 16:09 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 23:15 +0000
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 04:36 +0000
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-02 05:25 +0000
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 00:21 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 17:46 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-09-01 01:04 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 18:17 -0700
Re: Just click "like" Nobody <nobody@invalid.com> - 2015-08-30 21:49 -0500
Re: Just click "like" chrisv <chrisv@nospam.invalid> - 2015-08-31 07:35 -0500
Re: Just click "like" GreyCloud <cumulus@mist.com> - 2015-08-30 15:21 -0600
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-30 14:39 -0700
Re: Just click "like" GreyCloud <cumulus@mist.com> - 2015-08-31 13:32 -0600
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-31 12:49 -0700
Re: Just click "like" GreyCloud <cumulus@mist.com> - 2015-09-01 11:38 -0600
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-30 00:35 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-29 17:46 -0700
Re: Just click "like" owl <owl@rooftop.invalid> - 2015-08-30 00:56 +0000
Re: Just click "like" Snit <usenet@gallopinginsanity.com> - 2015-08-29 19:16 -0700
Re: Just click "like" John Gohde <john.h.gohde@gmail.com> - 2015-08-29 14:29 -0700
Page 2 of 7 — ← Prev page 1 [2] 3 4 5 6 7 Next page →
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-08-30 22:43 +0000 |
| Message-ID | <sfmcnvi8.aef@rooftop.invalid> |
| In reply to | #317875 |
Snit <usenet@gallopinginsanity.com> wrote: > On 8/30/15, 3:00 PM, in article res.jfd90@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: >> Snit <usenet@gallopinginsanity.com> wrote: >>> On 8/30/15, 2:03 PM, in article se93.afpe3@rooftop.invalid, "owl" >>> <owl@rooftop.invalid> wrote: >> >>>> >>>> You really don't "get" the desktop metaphor, do you? Not to mention your >>>> hipocrisy of crowing about how the OS X Print Dialog is a *system-wide* >>>> feature available to any app that prints, but now acting like this same >>>> Print Dialog is somehow "part of the application." >> >>> Again, you can work to not understand, but not sure it offers any value. >> >>> It is a part of the system AVAILABLE in the application... not by going to >>> your desktop. That is the point. >> >> The OS X Print Dialog is NOT "part of the application." It is not "inside" >> the application. Whenever you use it, you are going *outside* the application >> to perform a SYSTEM-WIDE function -- running a COMMON SYSTEM PRINT DIALOG. > Yes, we can play semantic games all day... but you know what is meant. Yes, I know what is meant by "going outside the application." You obviously do not.
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-08-30 17:33 -0700 |
| Message-ID | <D208EEFB.59570%usenet@gallopinginsanity.com> |
| In reply to | #317881 |
On 8/30/15, 3:43 PM, in article sfmcnvi8.aef@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: > Snit <usenet@gallopinginsanity.com> wrote: >> On 8/30/15, 3:00 PM, in article res.jfd90@rooftop.invalid, "owl" >> <owl@rooftop.invalid> wrote: > >>> Snit <usenet@gallopinginsanity.com> wrote: >>>> On 8/30/15, 2:03 PM, in article se93.afpe3@rooftop.invalid, "owl" >>>> <owl@rooftop.invalid> wrote: >>> >>>>> >>>>> You really don't "get" the desktop metaphor, do you? Not to mention your >>>>> hipocrisy of crowing about how the OS X Print Dialog is a *system-wide* >>>>> feature available to any app that prints, but now acting like this same >>>>> Print Dialog is somehow "part of the application." >>> >>>> Again, you can work to not understand, but not sure it offers any value. >>> >>>> It is a part of the system AVAILABLE in the application... not by going to >>>> your desktop. That is the point. >>> >>> The OS X Print Dialog is NOT "part of the application." It is not "inside" >>> the application. Whenever you use it, you are going *outside* the >>> application >>> to perform a SYSTEM-WIDE function -- running a COMMON SYSTEM PRINT DIALOG. > >> Yes, we can play semantic games all day... but you know what is meant. > > Yes, I know what is meant by "going outside the application." You obviously > do not. > LOL! Come on, Owl. Going to the File > Print menu in a program is not going outside the program the way working with the desktop is. This is not even a debatable question. Yes, the system helps to define the print dialog, and the window decorations, and even widgets and the like - but those are in the program. The desktop is most certainly NOT in a word processor or other app. You are better than this, Owl. -- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-08-31 03:25 +0000 |
| Message-ID | <fsmckv03.ksdif@rooftop.invalid> |
| In reply to | #317912 |
Snit <usenet@gallopinginsanity.com> wrote: > On 8/30/15, 3:43 PM, in article sfmcnvi8.aef@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: >> Snit <usenet@gallopinginsanity.com> wrote: >>> On 8/30/15, 3:00 PM, in article res.jfd90@rooftop.invalid, "owl" >>> <owl@rooftop.invalid> wrote: >> >>>> Snit <usenet@gallopinginsanity.com> wrote: >>>>> On 8/30/15, 2:03 PM, in article se93.afpe3@rooftop.invalid, "owl" >>>>> <owl@rooftop.invalid> wrote: >>>> >>>>>> >>>>>> You really don't "get" the desktop metaphor, do you? Not to mention your >>>>>> hipocrisy of crowing about how the OS X Print Dialog is a *system-wide* >>>>>> feature available to any app that prints, but now acting like this same >>>>>> Print Dialog is somehow "part of the application." >>>> >>>>> Again, you can work to not understand, but not sure it offers any value. >>>> >>>>> It is a part of the system AVAILABLE in the application... not by going to >>>>> your desktop. That is the point. >>>> >>>> The OS X Print Dialog is NOT "part of the application." It is not "inside" >>>> the application. Whenever you use it, you are going *outside* the >>>> application >>>> to perform a SYSTEM-WIDE function -- running a COMMON SYSTEM PRINT DIALOG. >> >>> Yes, we can play semantic games all day... but you know what is meant. >> >> Yes, I know what is meant by "going outside the application." You obviously >> do not. >> > LOL! Come on, Owl. Going to the File > Print menu in a program is not going > outside the program the way working with the desktop is. This is not even a > debatable question. Yes, the system helps to define the print dialog, and > the window decorations, and even widgets and the like - but those are in the > program. > The desktop is most certainly NOT in a word processor or other app. > You are better than this, Owl. https://vid.me/TWyY
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-08-30 21:06 -0700 |
| Message-ID | <D20920CF.595C8%usenet@gallopinginsanity.com> |
| In reply to | #317942 |
On 8/30/15, 8:25 PM, in article fsmckv03.ksdif@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: > Snit <usenet@gallopinginsanity.com> wrote: >> On 8/30/15, 3:43 PM, in article sfmcnvi8.aef@rooftop.invalid, "owl" >> <owl@rooftop.invalid> wrote: > >>> Snit <usenet@gallopinginsanity.com> wrote: >>>> On 8/30/15, 3:00 PM, in article res.jfd90@rooftop.invalid, "owl" >>>> <owl@rooftop.invalid> wrote: >>> >>>>> Snit <usenet@gallopinginsanity.com> wrote: >>>>>> On 8/30/15, 2:03 PM, in article se93.afpe3@rooftop.invalid, "owl" >>>>>> <owl@rooftop.invalid> wrote: >>>>> >>>>>>> >>>>>>> You really don't "get" the desktop metaphor, do you? Not to mention >>>>>>> your >>>>>>> hipocrisy of crowing about how the OS X Print Dialog is a *system-wide* >>>>>>> feature available to any app that prints, but now acting like this same >>>>>>> Print Dialog is somehow "part of the application." >>>>> >>>>>> Again, you can work to not understand, but not sure it offers any value. >>>>> >>>>>> It is a part of the system AVAILABLE in the application... not by going >>>>>> to >>>>>> your desktop. That is the point. >>>>> >>>>> The OS X Print Dialog is NOT "part of the application." It is not >>>>> "inside" >>>>> the application. Whenever you use it, you are going *outside* the >>>>> application >>>>> to perform a SYSTEM-WIDE function -- running a COMMON SYSTEM PRINT DIALOG. >>> >>>> Yes, we can play semantic games all day... but you know what is meant. >>> >>> Yes, I know what is meant by "going outside the application." You obviously >>> do not. >>> >> LOL! Come on, Owl. Going to the File > Print menu in a program is not going >> outside the program the way working with the desktop is. This is not even a >> debatable question. Yes, the system helps to define the print dialog, and >> the window decorations, and even widgets and the like - but those are in the >> program. > >> The desktop is most certainly NOT in a word processor or other app. > >> You are better than this, Owl. > > https://vid.me/TWyY > Yup... I miss the point you are trying to make. By all means spell it out. I see you calling a print dialog from a program but have no clue what value you think it might have, unless you are trying to incorrectly show that calling a print dialog from the File > Print menu in a program is going outside the program in the same way as clicking on the desktop. If that is the point you are making you are being silly... but if there is a real point I am missing by all means state it. Open to hearing your thoughts. -- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-08-31 05:11 +0000 |
| Message-ID | <aenfaenf99.f33@rooftop.invalid> |
| In reply to | #317951 |
Snit <usenet@gallopinginsanity.com> wrote: > On 8/30/15, 8:25 PM, in article fsmckv03.ksdif@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: >> Snit <usenet@gallopinginsanity.com> wrote: >>> On 8/30/15, 3:43 PM, in article sfmcnvi8.aef@rooftop.invalid, "owl" >>> <owl@rooftop.invalid> wrote: >> >>>> Snit <usenet@gallopinginsanity.com> wrote: >>>>> On 8/30/15, 3:00 PM, in article res.jfd90@rooftop.invalid, "owl" >>>>> <owl@rooftop.invalid> wrote: >>>> >>>>>> Snit <usenet@gallopinginsanity.com> wrote: >>>>>>> On 8/30/15, 2:03 PM, in article se93.afpe3@rooftop.invalid, "owl" >>>>>>> <owl@rooftop.invalid> wrote: >>>>>> >>>>>>>> >>>>>>>> You really don't "get" the desktop metaphor, do you? Not to mention >>>>>>>> your >>>>>>>> hipocrisy of crowing about how the OS X Print Dialog is a *system-wide* >>>>>>>> feature available to any app that prints, but now acting like this same >>>>>>>> Print Dialog is somehow "part of the application." >>>>>> >>>>>>> Again, you can work to not understand, but not sure it offers any value. >>>>>> >>>>>>> It is a part of the system AVAILABLE in the application... not by going >>>>>>> to >>>>>>> your desktop. That is the point. >>>>>> >>>>>> The OS X Print Dialog is NOT "part of the application." It is not >>>>>> "inside" >>>>>> the application. Whenever you use it, you are going *outside* the >>>>>> application >>>>>> to perform a SYSTEM-WIDE function -- running a COMMON SYSTEM PRINT DIALOG. >>>> >>>>> Yes, we can play semantic games all day... but you know what is meant. >>>> >>>> Yes, I know what is meant by "going outside the application." You obviously >>>> do not. >>>> >>> LOL! Come on, Owl. Going to the File > Print menu in a program is not going >>> outside the program the way working with the desktop is. This is not even a >>> debatable question. Yes, the system helps to define the print dialog, and >>> the window decorations, and even widgets and the like - but those are in the >>> program. >> >>> The desktop is most certainly NOT in a word processor or other app. >> >>> You are better than this, Owl. >> >> https://vid.me/TWyY >> > Yup... I miss the point you are trying to make. By all means spell it out. I > see you calling a print dialog from a program but have no clue what value > you think it might have, unless you are trying to incorrectly show that > calling a print dialog from the File > Print menu in a program is going > outside the program in the same way as clicking on the desktop. That print dialog does not belong to the script. It is being called from the script. > If that is the point you are making you are being silly... but if there is a > real point I am missing by all means state it. Open to hearing your > thoughts. Do you think the one-liner that forces Chrome to use the OS X system print dialog instead of its own somehow makes the OS X system print dialog part of Chrome?
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-08-30 22:18 -0700 |
| Message-ID | <D20931AD.59611%usenet@gallopinginsanity.com> |
| In reply to | #317973 |
On 8/30/15, 10:11 PM, in article aenfaenf99.f33@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: >>>> LOL! Come on, Owl. Going to the File > Print menu in a program is not going >>>> outside the program the way working with the desktop is. This is not even a >>>> debatable question. Yes, the system helps to define the print dialog, and >>>> the window decorations, and even widgets and the like - but those are in >>>> the >>>> program. >>> >>>> The desktop is most certainly NOT in a word processor or other app. >>> >>>> You are better than this, Owl. >>> >>> https://vid.me/TWyY >>> > >> Yup... I miss the point you are trying to make. By all means spell it out. I >> see you calling a print dialog from a program but have no clue what value >> you think it might have, unless you are trying to incorrectly show that >> calling a print dialog from the File > Print menu in a program is going >> outside the program in the same way as clicking on the desktop. > > That print dialog does not belong to the script. It is being called > from the script. Right. In your case you have a script call a print dialog. I am in reference to common application behavior. >> If that is the point you are making you are being silly... but if there is a >> real point I am missing by all means state it. Open to hearing your >> thoughts. > > Do you think the one-liner that forces Chrome to use the OS X system > print dialog instead of its own somehow makes the OS X system print > dialog part of Chrome? What? If I use: defaults write com.google.Chrome DisablePrintPreview -bool true Then Chrome uses the standard OS X print dialog. What do you mean is it a part of Chrome? Do you think Google coded Apple's print dialog? Never mind that... that is just into la-la land. Get back to your point. I admitted that if your point was NOT something absurd like trying to "show" using File > Print is going outside the program in the same way as clicking on the desktop then I do not get what your point is. So what is your point... assuming it is not that? -- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-08-31 05:35 +0000 |
| Message-ID | <fsa.mvjcz93.dfi@rooftop.invalid> |
| In reply to | #317974 |
Snit <usenet@gallopinginsanity.com> wrote: > On 8/30/15, 10:11 PM, in article aenfaenf99.f33@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: >>>>> LOL! Come on, Owl. Going to the File > Print menu in a program is not going >>>>> outside the program the way working with the desktop is. This is not even a >>>>> debatable question. Yes, the system helps to define the print dialog, and >>>>> the window decorations, and even widgets and the like - but those are in >>>>> the >>>>> program. >>>> >>>>> The desktop is most certainly NOT in a word processor or other app. >>>> >>>>> You are better than this, Owl. >>>> >>>> https://vid.me/TWyY >>>> >> >>> Yup... I miss the point you are trying to make. By all means spell it out. I >>> see you calling a print dialog from a program but have no clue what value >>> you think it might have, unless you are trying to incorrectly show that >>> calling a print dialog from the File > Print menu in a program is going >>> outside the program in the same way as clicking on the desktop. >> >> That print dialog does not belong to the script. It is being called >> from the script. > Right. In your case you have a script call a print dialog. I am in reference > to common application behavior. Common OS X application behavior is to use the system print dialog. That dialog does not belong to the application any more than the standalone print dialog kprinter4 belongs to my script. >>> If that is the point you are making you are being silly... but if there is a >>> real point I am missing by all means state it. Open to hearing your >>> thoughts. >> >> Do you think the one-liner that forces Chrome to use the OS X system >> print dialog instead of its own somehow makes the OS X system print >> dialog part of Chrome? > What? If I use: > defaults write com.google.Chrome DisablePrintPreview -bool true > Then Chrome uses the standard OS X print dialog. What do you mean is it a > part of Chrome? Do you think Google coded Apple's print dialog? Never mind > that... that is just into la-la land. Get back to your point. That's what I'm asking you -- if you think that the system print dialog is a part of chrome just because you set set chrome to use it. Obviously it is *not* part of chrome, so when you print from chrome with it set to use the system print dialog instead of its own, you are going *outside* of chrome to print. This is true of *all* OS X applications that make use of the system print dialog.
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-08-30 22:37 -0700 |
| Message-ID | <D209363B.5961A%usenet@gallopinginsanity.com> |
| In reply to | #317977 |
On 8/30/15, 10:35 PM, in article fsa.mvjcz93.dfi@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: ... >> Then Chrome uses the standard OS X print dialog. What do you mean is it a >> part of Chrome? Do you think Google coded Apple's print dialog? Never mind >> that... that is just into la-la land. Get back to your point. > > That's what I'm asking you -- if you think that the system print dialog > is a part of chrome just because you set set chrome to use it. Depends on what you mean by "part of Chrome" and I am not even slightly interested in that side issue semantic game. The question you have not answered: I admitted that if your point was NOT something absurd like trying to "show" using File > Print is going outside the program in the same way as clicking on the desktop then I do not get what your point is. So what is your point... assuming it is not that? > Obviously it is *not* part of chrome, so when you print from chrome with it > set to use the system print dialog instead of its own, you are going *outside* > of chrome to print. This is true of *all* OS X applications that make use of > the system print dialog. It sure seems like your "point" was to try to make the extremely absurd one I speak of above. Please tell me you had something better than that... if not you are just trolling at this point. -- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-08-31 05:50 +0000 |
| Message-ID | <fsmvnzx83.jdf@rooftop.invalid> |
| In reply to | #317978 |
Snit <usenet@gallopinginsanity.com> wrote: > On 8/30/15, 10:35 PM, in article fsa.mvjcz93.dfi@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: > ... >>> Then Chrome uses the standard OS X print dialog. What do you mean is it a >>> part of Chrome? Do you think Google coded Apple's print dialog? Never mind >>> that... that is just into la-la land. Get back to your point. >> >> That's what I'm asking you -- if you think that the system print dialog >> is a part of chrome just because you set set chrome to use it. > Depends on what you mean by "part of Chrome" and I am not even slightly > interested in that side issue semantic game. You are afraid of this. > The question you have not answered: > I admitted that if your point was NOT something absurd like trying to "show" > using File > Print is going outside the program in the same way as clicking > on the desktop then I do not get what your point is. Of course you are going outside the program if the program uses the system print dialog. > So what is your point... assuming it is not that? How many times to I have to say it before you quit asking what it is? >> Obviously it is *not* part of chrome, so when you print from chrome with it >> set to use the system print dialog instead of its own, you are going *outside* >> of chrome to print. This is true of *all* OS X applications that make use of >> the system print dialog. > It sure seems like your "point" was to try to make the extremely absurd one > I speak of above. Please tell me you had something better than that... if > not you are just trolling at this point. I sure seems like you are afraid of the point.
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-08-30 22:55 -0700 |
| Message-ID | <D2093A64.59620%usenet@gallopinginsanity.com> |
| In reply to | #317980 |
On 8/30/15, 10:50 PM, in article fsmvnzx83.jdf@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: ... >> The question you have not answered: >> >> I admitted that if your point was NOT something absurd like trying to "show" >> using File > Print is going outside the program in the same way as clicking >> on the desktop then I do not get what your point is. > > Of course you are going outside the program if the program uses the > system print dialog. And doing do in the same way as clicking on the desktop. LOL! OK, so you are just trolling. Got it. >> So what is your point... assuming it is not that? > > How many times to I have to say it before you quit asking what it is? Once was enough: you have made it clear you point was just to troll with that absurd and silly claim. OK, got it. >>> Obviously it is *not* part of chrome, so when you print from chrome with it >>> set to use the system print dialog instead of its own, you are going >>> *outside* of chrome to print. This is true of *all* OS X applications that >>> make use of the system print dialog. >>> >> It sure seems like your "point" was to try to make the extremely absurd one I >> speak of above. Please tell me you had something better than that... if not >> you are just trolling at this point. > > I sure seems like you are afraid of the point. Sure, your trolling over this nonsense claim frightens me terribly. You win. Now what? Can we get back to reality? I mean, come on, you are not so lost with computers that you think using the Print menu command is leaving the program in the same way clicking on the desktop is. You are NOT that ignorant about using computers. I simply do not believe you. -- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-08-31 06:18 +0000 |
| Message-ID | <adsf.3ae0@rooftop.invalid> |
| In reply to | #317981 |
Snit <usenet@gallopinginsanity.com> wrote: > On 8/30/15, 10:50 PM, in article fsmvnzx83.jdf@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: > ... >>> The question you have not answered: >>> >>> I admitted that if your point was NOT something absurd like trying to "show" >>> using File > Print is going outside the program in the same way as clicking >>> on the desktop then I do not get what your point is. >> >> Of course you are going outside the program if the program uses the >> system print dialog. > And doing do in the same way as clicking on the desktop. > LOL! > OK, so you are just trolling. Got it. >>> So what is your point... assuming it is not that? >> >> How many times to I have to say it before you quit asking what it is? > Once was enough: you have made it clear you point was just to troll with > that absurd and silly claim. OK, got it. >>>> Obviously it is *not* part of chrome, so when you print from chrome with it >>>> set to use the system print dialog instead of its own, you are going >>>> *outside* of chrome to print. This is true of *all* OS X applications that >>>> make use of the system print dialog. >>>> >>> It sure seems like your "point" was to try to make the extremely absurd one I >>> speak of above. Please tell me you had something better than that... if not >>> you are just trolling at this point. >> >> I sure seems like you are afraid of the point. > Sure, your trolling over this nonsense claim frightens me terribly. You win. > Now what? > Can we get back to reality? I mean, come on, you are not so lost with > computers that you think using the Print menu command is leaving the program > in the same way clicking on the desktop is. You are NOT that ignorant about > using computers. I simply do not believe you. Now what? Now you answer the question of whether you think that the system print dialog belongs to chrome after you set chrome to use it instead of its own print dialog.
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-08-30 23:39 -0700 |
| Message-ID | <D20944C7.5962A%usenet@gallopinginsanity.com> |
| In reply to | #317984 |
On 8/30/15, 11:18 PM, in article adsf.3ae0@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: > Snit <usenet@gallopinginsanity.com> wrote: >> On 8/30/15, 10:50 PM, in article fsmvnzx83.jdf@rooftop.invalid, "owl" >> <owl@rooftop.invalid> wrote: > >> ... >>>> The question you have not answered: >>>> >>>> I admitted that if your point was NOT something absurd like trying to >>>> "show" >>>> using File > Print is going outside the program in the same way as clicking >>>> on the desktop then I do not get what your point is. >>> >>> Of course you are going outside the program if the program uses the >>> system print dialog. > >> And doing do in the same way as clicking on the desktop. > >> LOL! > >> OK, so you are just trolling. Got it. > >>>> So what is your point... assuming it is not that? >>> >>> How many times to I have to say it before you quit asking what it is? > >> Once was enough: you have made it clear you point was just to troll with >> that absurd and silly claim. OK, got it. > >>>>> Obviously it is *not* part of chrome, so when you print from chrome with >>>>> it >>>>> set to use the system print dialog instead of its own, you are going >>>>> *outside* of chrome to print. This is true of *all* OS X applications >>>>> that >>>>> make use of the system print dialog. >>>>> >>>> It sure seems like your "point" was to try to make the extremely absurd one >>>> I >>>> speak of above. Please tell me you had something better than that... if not >>>> you are just trolling at this point. >>> >>> I sure seems like you are afraid of the point. > >> Sure, your trolling over this nonsense claim frightens me terribly. You win. > >> Now what? > >> Can we get back to reality? I mean, come on, you are not so lost with >> computers that you think using the Print menu command is leaving the program >> in the same way clicking on the desktop is. You are NOT that ignorant about >> using computers. I simply do not believe you. > > Now what? Now you answer the question of whether you think that the > system print dialog belongs to chrome after you set chrome to use it > instead of its own print dialog. What do you mean by "belongs to"? From a user perspective a user is in Chrome and then they print from Chrome. Not the desktop. Those are different things. Now with the print dialog, it is a tied to the system, much as the color selector is or the mouse pointer or the close button or even the menus themselves! Lots of things which are standardized because they are tied to code provided by the system. But, to get back to the print dialog, Chrome calls the system feature and sends information to it... different programs can even modify the dialog. But you know all of this. It is a side issue filled with absurdities where you want to make it seem like a user using the Print menu item in the program they are using is going "out" of the program in the same way that clicking on the desktop (which is not a part of the program at all) is going out of the program. False equivalency on your part. You know better. This is a sure sign you are just screwing around trying to make it seem like your desktop work-around method is similar. It is not. So now that we know this where do we go from here? -- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-08-31 07:15 +0000 |
| Message-ID | <fasm9fawe.ki@rooftop.invalid> |
| In reply to | #317985 |
Snit <usenet@gallopinginsanity.com> wrote: > On 8/30/15, 11:18 PM, in article adsf.3ae0@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: >> Snit <usenet@gallopinginsanity.com> wrote: >>> On 8/30/15, 10:50 PM, in article fsmvnzx83.jdf@rooftop.invalid, "owl" >>> <owl@rooftop.invalid> wrote: >> >>> ... >>>>> The question you have not answered: >>>>> >>>>> I admitted that if your point was NOT something absurd like trying to >>>>> "show" >>>>> using File > Print is going outside the program in the same way as clicking >>>>> on the desktop then I do not get what your point is. >>>> >>>> Of course you are going outside the program if the program uses the >>>> system print dialog. >> >>> And doing do in the same way as clicking on the desktop. >> >>> LOL! >> >>> OK, so you are just trolling. Got it. >> >>>>> So what is your point... assuming it is not that? >>>> >>>> How many times to I have to say it before you quit asking what it is? >> >>> Once was enough: you have made it clear you point was just to troll with >>> that absurd and silly claim. OK, got it. >> >>>>>> Obviously it is *not* part of chrome, so when you print from chrome with >>>>>> it >>>>>> set to use the system print dialog instead of its own, you are going >>>>>> *outside* of chrome to print. This is true of *all* OS X applications >>>>>> that >>>>>> make use of the system print dialog. >>>>>> >>>>> It sure seems like your "point" was to try to make the extremely absurd one >>>>> I >>>>> speak of above. Please tell me you had something better than that... if not >>>>> you are just trolling at this point. >>>> >>>> I sure seems like you are afraid of the point. >> >>> Sure, your trolling over this nonsense claim frightens me terribly. You win. >> >>> Now what? >> >>> Can we get back to reality? I mean, come on, you are not so lost with >>> computers that you think using the Print menu command is leaving the program >>> in the same way clicking on the desktop is. You are NOT that ignorant about >>> using computers. I simply do not believe you. >> >> Now what? Now you answer the question of whether you think that the >> system print dialog belongs to chrome after you set chrome to use it >> instead of its own print dialog. > What do you mean by "belongs to"? From a user perspective a user is in > Chrome and then they print from Chrome. The user's "perspective" is irrelevant. > Not the desktop. > Those are different things. > Now with the print dialog, it is a tied to the system, much as the color > selector is or the mouse pointer or the close button or even the menus > themselves! Lots of things which are standardized because they are tied to > code provided by the system. But, to get back to the print dialog, Chrome > calls the system feature and sends information to it... different programs > can even modify the dialog. Yes, because it is shared. It is not part of any particular program. > But you know all of this. It is a side issue filled with absurdities where > you want to make it seem like a user using the Print menu item in the > program they are using is going "out" of the program in the same way that > clicking on the desktop (which is not a part of the program at all) The system print dialog is not part of the program at all. > is going > out of the program. > False equivalency on your part. An equivalency is not false just because you wish it to be. > You know better. This is a sure sign you are > just screwing around trying to make it seem like your desktop work-around > method is similar. It is not. > So now that we know this where do we go from here? Well, where not going to the land of denial, which is where you're trying to drag us.
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-08-31 00:20 -0700 |
| Message-ID | <D2094E33.59636%usenet@gallopinginsanity.com> |
| In reply to | #317988 |
On 8/31/15, 12:15 AM, in article fasm9fawe.ki@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: ... >> What do you mean by "belongs to"? From a user perspective a user is in >> Chrome and then they print from Chrome. > > The user's "perspective" is irrelevant. When talking about workflow and usability it is ALL that matters. ... >> False equivalency on your part. > > An equivalency is not false just because you wish it to be. Straw man on your part. >> You know better. This is a sure sign you are just screwing around trying to >> make it seem like your desktop work-around method is similar. It is not. >> >> So now that we know this where do we go from here? > > Well, where not going to the land of denial, which is where you're trying > to drag us. LOL! How evil... I "deny" that using a Print menu item in a program is not leaving the program in the same way clicking on the desktop is. Really, Owl, you have no leg to stand on here. You are just being silly. * File > Print. This is a standard feature of most programs... which ties to system services. * Clicking the desktop: This is not going outside the program No matter how you try two twist things I think we can pretty much leave it here: you will never admit this is true because to do so shows you know Linux lacks a feature of another OS and admitting that is against your religion. -- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-08-31 12:42 +0000 |
| Message-ID | <fsanmv93.ki@rooftop.invalid> |
| In reply to | #317990 |
Snit <usenet@gallopinginsanity.com> wrote: > On 8/31/15, 12:15 AM, in article fasm9fawe.ki@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: > * File > Print. This is a standard feature of most programs... > which ties to system services. > * Clicking the desktop: This is not going outside the program Make up your mind, fool.
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-08-31 09:25 -0700 |
| Message-ID | <D209CDF8.596C7%usenet@gallopinginsanity.com> |
| In reply to | #318024 |
On 8/31/15, 5:42 AM, in article fsanmv93.ki@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: > Snit <usenet@gallopinginsanity.com> wrote: >> On 8/31/15, 12:15 AM, in article fasm9fawe.ki@rooftop.invalid, "owl" >> <owl@rooftop.invalid> wrote: > >> * File > Print. This is a standard feature of most programs... >> which ties to system services. > >> * Clicking the desktop: This is not going outside the program > > Make up your mind, fool. > Current debate with Owl: * Owl He engaged in some pretty cool advocacy. He showed he could do with Linux quite a few things that can be done on a Mac... though it quickly became clear he had to re-do his set up with what was and was not available. So he presented Linux as being configurable but not having as much connection with context as OS X. Fine. Each has strengths and we learned. Then Owl decided this was not good enough and that one should see clicking on the desktop to get a task done (leaving the program you are working on) to be the same as using File > Print because the print dialog is controlled by the system so it is also leaving the program. Utter nonsense. -- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-08-31 20:55 +0000 |
| Message-ID | <rlfdsk93.ajfj@rooftop.invalid> |
| In reply to | #318076 |
Snit <usenet@gallopinginsanity.com> wrote: > On 8/31/15, 5:42 AM, in article fsanmv93.ki@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: >> Snit <usenet@gallopinginsanity.com> wrote: >>> On 8/31/15, 12:15 AM, in article fasm9fawe.ki@rooftop.invalid, "owl" >>> <owl@rooftop.invalid> wrote: >> >>> * File > Print. This is a standard feature of most programs... >>> which ties to system services. >> >>> * Clicking the desktop: This is not going outside the program >> >> Make up your mind, fool. >> > Current debate with Owl: > * Owl > He engaged in some pretty cool advocacy. He showed he could do with Linux > quite a few things that can be done on a Mac... though it quickly became > clear he had to re-do his set up with what was and was not available. So he > presented Linux as being configurable but not having as much connection with > context as OS X. Fine. Each has strengths and we learned. How did I redo my system with something that's not available? > Then Owl decided this was not good enough and that one should see clicking > on the desktop to get a task done (leaving the program you are working on) > to be the same as using File > Print because the print dialog is controlled > by the system so it is also leaving the program. Utter nonsense. Did you ever answer my question about Chrome?
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-08-31 14:04 -0700 |
| Message-ID | <D20A0F81.59776%usenet@gallopinginsanity.com> |
| In reply to | #318167 |
On 8/31/15, 1:55 PM, in article rlfdsk93.ajfj@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: > Snit <usenet@gallopinginsanity.com> wrote: >> On 8/31/15, 5:42 AM, in article fsanmv93.ki@rooftop.invalid, "owl" >> <owl@rooftop.invalid> wrote: > >>> Snit <usenet@gallopinginsanity.com> wrote: >>>> On 8/31/15, 12:15 AM, in article fasm9fawe.ki@rooftop.invalid, "owl" >>>> <owl@rooftop.invalid> wrote: >>> >>>> * File > Print. This is a standard feature of most programs... >>>> which ties to system services. >>> >>>> * Clicking the desktop: This is not going outside the program >>> >>> Make up your mind, fool. >>> >> Current debate with Owl: > >> * Owl > >> He engaged in some pretty cool advocacy. He showed he could do with Linux >> quite a few things that can be done on a Mac... though it quickly became >> clear he had to re-do his set up with what was and was not available. So he >> presented Linux as being configurable but not having as much connection with >> context as OS X. Fine. Each has strengths and we learned. > > How did I redo my system with something that's not available? Did you not add and remove menu and panel items? >> Then Owl decided this was not good enough and that one should see clicking >> on the desktop to get a task done (leaving the program you are working on) >> to be the same as using File > Print because the print dialog is controlled >> by the system so it is also leaving the program. Utter nonsense. > > Did you ever answer my question about Chrome? Yes, but I focused more on the actual topic! -- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2015-08-31 21:56 +0000 |
| Message-ID | <asmbnc83.jidf@rooftop.invalid> |
| In reply to | #318170 |
Snit <usenet@gallopinginsanity.com> wrote: > On 8/31/15, 1:55 PM, in article rlfdsk93.ajfj@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: >> Snit <usenet@gallopinginsanity.com> wrote: >>> On 8/31/15, 5:42 AM, in article fsanmv93.ki@rooftop.invalid, "owl" >>> <owl@rooftop.invalid> wrote: >> >>>> Snit <usenet@gallopinginsanity.com> wrote: >>>>> On 8/31/15, 12:15 AM, in article fasm9fawe.ki@rooftop.invalid, "owl" >>>>> <owl@rooftop.invalid> wrote: >>>> >>>>> * File > Print. This is a standard feature of most programs... >>>>> which ties to system services. >>>> >>>>> * Clicking the desktop: This is not going outside the program >>>> >>>> Make up your mind, fool. >>>> >>> Current debate with Owl: >> >>> * Owl >> >>> He engaged in some pretty cool advocacy. He showed he could do with Linux >>> quite a few things that can be done on a Mac... though it quickly became >>> clear he had to re-do his set up with what was and was not available. So he >>> presented Linux as being configurable but not having as much connection with >>> context as OS X. Fine. Each has strengths and we learned. >> >> How did I redo my system with something that's not available? > Did you not add and remove menu and panel items? Was "Save to Recipes Folder" already there when you unboxed your Mack? >>> Then Owl decided this was not good enough and that one should see clicking >>> on the desktop to get a task done (leaving the program you are working on) >>> to be the same as using File > Print because the print dialog is controlled >>> by the system so it is also leaving the program. Utter nonsense. >> >> Did you ever answer my question about Chrome? > Yes, but I focused more on the actual topic! Jog my memory. Do you consider the system-wide Print Dialog to be a part of Chrome?
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2015-08-31 16:45 -0700 |
| Message-ID | <D20A3546.597CC%usenet@gallopinginsanity.com> |
| In reply to | #318194 |
On 8/31/15, 2:56 PM, in article asmbnc83.jidf@rooftop.invalid, "owl" <owl@rooftop.invalid> wrote: > Snit <usenet@gallopinginsanity.com> wrote: >> On 8/31/15, 1:55 PM, in article rlfdsk93.ajfj@rooftop.invalid, "owl" >> <owl@rooftop.invalid> wrote: > >>> Snit <usenet@gallopinginsanity.com> wrote: >>>> On 8/31/15, 5:42 AM, in article fsanmv93.ki@rooftop.invalid, "owl" >>>> <owl@rooftop.invalid> wrote: >>> >>>>> Snit <usenet@gallopinginsanity.com> wrote: >>>>>> On 8/31/15, 12:15 AM, in article fasm9fawe.ki@rooftop.invalid, "owl" >>>>>> <owl@rooftop.invalid> wrote: >>>>> >>>>>> * File > Print. This is a standard feature of most programs... >>>>>> which ties to system services. >>>>> >>>>>> * Clicking the desktop: This is not going outside the program >>>>> >>>>> Make up your mind, fool. >>>>> >>>> Current debate with Owl: >>> >>>> * Owl >>> >>>> He engaged in some pretty cool advocacy. He showed he could do with Linux >>>> quite a few things that can be done on a Mac... though it quickly became >>>> clear he had to re-do his set up with what was and was not available. So he >>>> presented Linux as being configurable but not having as much connection >>>> with >>>> context as OS X. Fine. Each has strengths and we learned. >>> >>> How did I redo my system with something that's not available? > >> Did you not add and remove menu and panel items? > > Was "Save to Recipes Folder" already there when you unboxed your Mack? Already answered. >>>> Then Owl decided this was not good enough and that one should see clicking >>>> on the desktop to get a task done (leaving the program you are working on) >>>> to be the same as using File > Print because the print dialog is controlled >>>> by the system so it is also leaving the program. Utter nonsense. >>> >>> Did you ever answer my question about Chrome? > >> Yes, but I focused more on the actual topic! > > Jog my memory. Do you consider the system-wide Print Dialog to be a > part of Chrome? Already answered and irrelevant... let's focus on your claim that clicking on the desktop to get a task done (leaving the program you are working on) to be the same as using File > Print because the print dialog is controlled by the system so it is also leaving the program. Utter nonsense... and hence why you try to play semantic games and change the topic when it is noted. Comes down to you know your position is completely indefensible. -- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
[toc] | [prev] | [next] | [standalone]
Page 2 of 7 — ← Prev page 1 [2] 3 4 5 6 7 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web