Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #485408 > unrolled thread
| Started by | "F. Russell" <frussell@random.info> |
|---|---|
| First post | 2019-01-21 16:47 +0000 |
| Last post | 2019-01-21 17:10 -0800 |
| Articles | 20 on this page of 362 — 27 participants |
Back to article view | Back to comp.os.linux.advocacy
The Sad and Disgusting Story of Panotools "F. Russell" <frussell@random.info> - 2019-01-21 16:47 +0000
Clearly, Russell is just a NEGATIVE piece of shit. Simon bar Sinister <john.h.gohde@gmail.com> - 2019-01-21 13:19 -0800
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-21 19:52 -0500
Re: The Sad and Disgusting Story of Panotools "F. Russell" <fr@random.info> - 2019-01-22 00:55 +0000
Re: The Sad and Disgusting Story of Panotools Amanda KoXXX <iscariot694me@simplivr4.org> - 2019-01-22 01:23 +0000
Re: The Sad and Disgusting Story of Panotools silverslimer <silver@slim.er> - 2019-01-22 14:22 -0500
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-21 21:48 -0500
Re: The Sad and Disgusting Story of Panotools Steve Carroll <frelwizzen@gmail.com> - 2019-01-21 19:15 -0800
Fabian's bra. Jeff-Relf.Me @. - 2019-01-22 02:17 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-01-22 02:50 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-01-22 18:37 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-01-22 14:01 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-01-22 19:07 +0000
Re: Fabian's bra. Hadron Quark <hadronquark@gmail.com> - 2019-01-31 15:07 +0100
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-01-31 14:57 +0000
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-01-31 12:42 -0600
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-01-31 19:42 +0000
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-01-31 11:52 -0800
Re: Fabian's bra. Snit <usenet@gallopinginsanity.com> - 2019-01-28 11:55 -0700
Re: Fabian's bra. silverslimer <silver@slim.er> - 2019-01-22 14:35 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-01-22 19:46 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-01-22 16:08 -0500
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-01-22 13:29 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-01-23 01:00 +0000
I've written C# macros and extensions to automate Visual Studio 2017. Jeff-Relf.Me @. - 2019-01-22 17:06 -0800
Re: I've written C# macros and extensions to automate Visual Studio 2017. Steve Carroll <frelwizzen@gmail.com> - 2019-01-22 17:39 -0800
Re: I've written C# macros and extensions to automate Visual Studio 2017. Amanda KoXXX <iscariot694me@simplivr4.org> - 2019-01-23 20:42 +0000
Re: I've written C# macros and extensions to automate Visual Studio 2017. Steve Carroll <frelwizzen@gmail.com> - 2019-01-23 13:59 -0800
I'll film it, so it's a porn vid, making it 100% legal. Jeff-Relf.Me @. - 2019-01-23 14:48 -0800
Re: I'll film it, so it's a porn vid, making it 100% legal. Steve Carroll <frelwizzen@gmail.com> - 2019-01-23 15:03 -0800
Re: I've written C# macros and extensions to automate Visual Studio 2017. silverslimer <silver@slim.er> - 2019-01-23 18:48 -0500
Re: I've written C# macros and extensions to automate Visual Studio 2017. Steve Carroll <frelwizzen@gmail.com> - 2019-01-23 17:54 -0800
Re: I've written C# macros and extensions to automate Visual Studio 2017. chrisv <chrisv@nospam.invalid> - 2019-01-24 07:32 -0600
Re: Fabian's bra. silverslimer <silver@slim.er> - 2019-01-22 20:06 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-01-23 01:19 +0000
Re: Fabian's bra. silverslimer <silver@slim.er> - 2019-01-23 12:31 -0500
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-01-23 13:24 -0600
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-01-23 11:54 -0800
Re: Fabian's bra. Snit <usenet@gallopinginsanity.com> - 2019-01-28 12:02 -0700
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-01-23 13:50 -0600
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-01-23 12:24 -0800
Re: Fabian's bra. Amanda KoXXX <iscariot694me@simplivr4.org> - 2019-01-23 20:35 +0000
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-01-23 07:00 -0600
Re: Fabian's bra. Snit <usenet@gallopinginsanity.com> - 2019-01-28 11:57 -0700
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-01 23:49 -0500
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-01 21:16 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-02 06:09 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-02 15:56 +0000
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-02 08:45 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-02 14:13 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-03 01:39 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-02 12:32 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-02 18:36 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-03 09:46 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-03 18:43 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-03 11:00 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-03 23:42 -0500
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-03 21:39 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 09:19 -0800
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-04 07:19 -0800
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-04 15:53 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-04 08:14 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 08:32 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 08:17 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-04 16:35 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-04 09:03 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-04 17:54 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-04 10:02 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 10:55 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-04 20:00 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-04 15:19 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-04 20:59 +0000
Re: Fabian's bra. Snit <usenet@gallopinginsanity.com> - 2019-02-04 21:52 +0000
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 14:31 -0800
Re: Fabian's bra. flyer <snowflyer09o@gmail.com> - 2019-02-04 22:46 +0000
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 15:17 -0800
Re: Fabian's bra. Snit <usenet@gallopinginsanity.com> - 2019-02-05 00:32 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 10:07 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 07:44 -0800
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 07:51 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 10:53 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 07:58 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 11:09 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 08:17 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 12:08 -0500
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-06 17:18 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 13:32 -0500
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-06 18:49 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 14:28 -0500
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-06 19:19 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 14:50 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 12:15 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 15:21 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 12:50 -0800
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 13:00 -0800
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 13:03 -0800
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 13:06 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 19:17 -0500
Re: Fabian's bra. vallor <vallor@cultnix.org> - 2019-02-06 21:55 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 14:02 -0800
Re: Fabian's bra. "F. Russell" <fr@random.info> - 2019-02-07 00:29 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 20:03 -0500
Re: Fabian's bra. "F. Russell" <fr@random.info> - 2019-02-07 21:42 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-08 19:41 -0500
Re: Fabian's bra. "F. Russell" <fr@random.info> - 2019-02-09 14:46 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-09 23:11 -0500
Re: Fabian's bra. "F. Russell" <fr@random.info> - 2019-02-10 13:57 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-10 13:09 -0500
Re: Fabian's bra. Ratchetjaw <ratchetjaw@mail.com> - 2019-02-10 18:17 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-11 14:45 -0500
Re: Fabian's bra. "F. Russell" <fr@random.info> - 2019-02-10 14:34 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-10 12:23 -0500
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 20:38 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-06 17:53 +0000
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 00:13 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 19:53 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 01:12 +0000
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 01:39 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 17:48 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 20:51 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 18:16 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 21:41 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 19:02 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-07 18:42 -0500
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-07 10:30 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-07 07:41 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 15:53 +0000
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 02:20 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 21:36 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 18:57 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 22:17 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 19:28 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 03:28 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 19:40 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 06:06 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-07 06:39 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-07 09:55 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 15:46 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-07 09:40 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 21:45 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-07 14:48 -0800
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-07 14:54 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-07 18:46 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-07 16:39 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-08 00:21 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-08 07:33 -0800
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-08 07:57 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-08 11:55 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-08 09:14 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-08 13:01 -0500
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-08 13:08 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-08 14:09 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-08 18:26 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-08 16:18 -0800
Re: Fabian's bra. Snit <usenet@gallopinginsanity.com> - 2019-02-09 15:26 -0700
Re: Fabian's bra. Snit <usenet@gallopinginsanity.com> - 2019-02-09 15:26 -0700
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-08 11:19 -0500
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-08 13:37 -0500
Re: Fabian's bra. Snit <usenet@gallopinginsanity.com> - 2019-02-08 22:05 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-08 14:30 -0800
Re: Fabian's bra. Snit <usenet@gallopinginsanity.com> - 2019-02-09 15:27 -0700
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 08:10 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-12 04:25 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 20:35 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 23:14 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 20:33 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 06:11 +0000
Re: Fabian's bra. Hadron Quark <hadronquark@gmail.com> - 2019-02-07 09:04 +0100
Re: Fabian's bra. vallor <vallor@cultnix.org> - 2019-02-07 09:16 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-07 06:44 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-07 15:49 +0000
Re: Fabian's bra. Chris Ahlstrom <OFeem1987@teleworm.us> - 2019-02-09 19:05 -0500
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-02-06 11:02 -0600
Re: Fabian's bra. Chris Ahlstrom <OFeem1987@teleworm.us> - 2019-02-09 19:06 -0500
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-02-11 07:48 -0600
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-11 14:03 +0000
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-02-11 08:22 -0600
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-11 14:51 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 07:32 -0800
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-02-11 11:23 -0600
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-11 18:02 +0000
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-02-11 12:36 -0600
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-11 14:10 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 13:09 -0800
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-11 21:18 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 13:27 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-12 22:08 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 13:31 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-11 18:16 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 15:49 -0800
Re: Fabian's bra. "F. Russell" <fr@random.info> - 2019-02-12 00:41 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-11 20:06 -0500
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-02-12 07:20 -0600
Re: Fabian's bra. Ratchetjaw <ratchetjaw@mail.com> - 2019-02-11 15:01 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 07:31 -0800
Does your "smart" phone do this ? Jeff-Relf.Me @. - 2019-02-11 14:29 -0800
Re: Does your "smart" phone do this ? Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 14:52 -0800
Can you do this, with your own custom vocabulary, backed up ? Jeff-Relf.Me @. - 2019-02-11 18:42 -0800
Re: Can you do this, with your own custom vocabulary, backed up ? Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 19:58 -0800
Re: Can you do this, with your own custom vocabulary, backed up ? owl <owl@rooftop.invalid> - 2019-02-12 04:11 +0000
Re: Can you do this, with your own custom vocabulary, backed up ? Steve Carroll <fretwizzer@gmail.com> - 2019-02-11 20:32 -0800
Re: Can you do this, with your own custom vocabulary, backed up ? owl <owl@rooftop.invalid> - 2019-02-12 05:28 +0000
Re: Can you do this, with your own custom vocabulary, backed up ? Steve Carroll <fretwizzer@gmail.com> - 2019-02-12 07:26 -0800
Re: Can you do this, with your own custom vocabulary, backed up ? DFS <nospam@dfs.com> - 2019-02-12 10:32 -0500
Re: Can you do this, with your own custom vocabulary, backed up ? owl <owl@rooftop.invalid> - 2019-02-12 17:21 +0000
Re: Can you do this, with your own custom vocabulary, backed up ? Steve Carroll <fretwizzer@gmail.com> - 2019-02-12 09:32 -0800
Re: Can you do this, with your own custom vocabulary, backed up ? Melzzzzz <Melzzzzz@zzzzz.com> - 2019-02-12 17:34 +0000
Re: Can you do this, with your own custom vocabulary, backed up ? owl <owl@rooftop.invalid> - 2019-02-12 17:46 +0000
Re: Can you do this, with your own custom vocabulary, backed up ? Melzzzzz <Melzzzzz@zzzzz.com> - 2019-02-12 18:03 +0000
Re: Can you do this, with your own custom vocabulary, backed up ? Steve Carroll <fretwizzer@gmail.com> - 2019-02-12 10:21 -0800
Re: Can you do this, with your own custom vocabulary, backed up ? owl <owl@rooftop.invalid> - 2019-02-12 19:49 +0000
Re: Can you do this, with your own custom vocabulary, backed up ? Steve Carroll <fretwizzer@gmail.com> - 2019-02-12 12:59 -0800
Re: Can you do this, with your own custom vocabulary, backed up ? Sir Gaygory's Owner's Owner 🐶笛 <root@127.0.0.1> - 2019-02-12 12:22 -0600
Re: Can you do this, with your own custom vocabulary, backed up ? owl <owl@rooftop.invalid> - 2019-02-12 18:46 +0000
Re: Can you do this, with your own custom vocabulary, backed up ? owl <owl@rooftop.invalid> - 2019-02-12 17:45 +0000
I'm the Queen of England. Jeff-Relf.Me @. - 2019-02-12 15:00 -0800
Re: I'm the Queen of England. Ratchetjaw <ratchetjaw@mail.com> - 2019-02-12 23:08 +0000
I can't post it to YouTube, of course. Jeff-Relf.Me @. - 2019-02-12 15:43 -0800
Re: Can you do this, with your own custom vocabulary, backed up ? owl <owl@rooftop.invalid> - 2019-02-12 17:12 +0000
Re: Does your "smart" phone do this ? "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> - 2019-02-11 17:56 -0500
Re: Does your "smart" phone do this ? % <persent@.gmail.com> - 2019-02-11 16:01 -0700
Jeff Bezos sent me another fucking DickPic. Jeff-Relf.Me @. - 2019-02-11 18:49 -0800
Re: Jeff Bezos sent me another fucking DickPic. Serg Io <invvalid@invalid.com> - 2019-02-11 21:37 -0600
Re: Jeff Bezos sent me another fucking DickPic. Bob Robertson <bobrobertsontsy66@gmail.com> - 2019-02-11 21:46 -0600
Re: Jeff Bezos sent me another fucking DickPic. "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> - 2019-02-12 09:23 -0500
Kooks jerking-off to sick Jeff Bezos fantasies chrisv <chrisv@nospam.invalid> - 2019-02-12 08:29 -0600
Re: Jeff Bezos sent me another fucking DickPic. Checkmate <ricksabian1@gmail.com> - 2019-02-12 09:31 -0800
Did you teach it "dick" ( not "Dick" ) ? Jeff-Relf.Me @. - 2019-02-12 14:41 -0800
Re: Did you teach it "dick" ( not "Dick" ) ? "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> - 2019-02-12 18:25 -0500
Re: Did you teach it "dick" ( not "Dick" ) ? % <persent@gmail.com> - 2019-02-12 16:32 -0700
Your "smart" phone ain't so smart. Jeff-Relf.Me @. - 2019-02-12 16:20 -0800
Re: Your "smart" phone ain't so smart. "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> - 2019-02-12 19:46 -0500
I'm inoculated against women and money. Jeff-Relf.Me @. - 2019-02-12 18:46 -0800
Re: Your "smart" phone ain't so smart. Checkmate <ricksabian1@gmail.com> - 2019-02-12 19:20 -0800
Re: Your "smart" phone ain't so smart. % <persent@gmail.com> - 2019-02-12 20:24 -0700
PeeScent can't read or write properly, can't Google, etc. Jeff-Relf.Me @. - 2019-02-12 20:03 -0800
Re: PeeScent can't read or write properly, can't Google, etc. % <persent@gmail.com> - 2019-02-13 07:54 -0700
Re: Your "smart" phone ain't so smart. Checkmate <ricksabian1@gmail.com> - 2019-02-12 22:46 -0800
Re: Your "smart" phone ain't so smart. "Sir Gregory Hall, Esq." <greghall@yacht_maester.fake> - 2019-02-13 09:44 -0500
Re: Your "smart" phone ain't so smart. % <persent@gmail.com> - 2019-02-13 07:55 -0700
Re: Your "smart" phone ain't so smart. Checkmate <ricksabian1@gmail.com> - 2019-02-13 13:43 -0800
Once a month, maybe. Jeff-Relf.Me @. - 2019-02-13 14:39 -0800
Re: Did you teach it "dick" ( not "Dick" ) ? "Colonel Edmund J. Burke" <burkesbabes@bigass-babes.com> - 2019-02-13 07:19 -0800
Re: Does your "smart" phone do this ? Melzzzzz <Melzzzzz@zzzzz.com> - 2019-02-12 05:58 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-12 22:11 -0500
Re: Fabian's bra. "F. Russell" <fr@random.info> - 2019-02-13 11:05 +0000
Re: Fabian's bra. "F. Russell" <fr@random.info> - 2019-02-13 11:10 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 08:04 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 11:18 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 08:32 -0800
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-06 16:54 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 12:40 -0500
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-06 18:38 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 09:45 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-06 17:38 +0000
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 12:28 -0800
Re: Fabian's bra. "F. Russell" <fr@random.info> - 2019-02-05 00:06 +0000
Re: Fabian's bra. flyer <snowflyer09o@gmail.com> - 2019-02-05 00:32 +0000
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 17:38 -0800
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-04 18:22 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-04 22:04 -0500
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-04 22:46 -0500
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 19:58 -0800
Re: Fabian's bra. silverslimer <silver@slim.er> - 2019-02-05 11:59 -0500
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-05 09:45 -0800
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-05 06:47 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-05 16:24 +0000
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-05 08:43 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 09:38 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-06 15:19 +0000
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-02-06 11:10 -0600
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 13:14 -0800
Re: Fabian's bra. "F. Russell" <frussell@random.info> - 2019-02-04 17:39 +0000
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-04 10:00 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 10:08 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-04 22:10 -0500
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 10:39 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 12:59 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-03 11:16 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-03 20:21 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-03 23:12 -0800
Re: Fabian's bra. Ratchetjaw <ratchetjaw@mail.com> - 2019-02-10 00:38 +0000
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-02 15:31 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-03 05:01 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-03 09:10 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-03 01:54 -0800
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-04 21:59 -0500
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-05 03:17 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-04 22:36 -0500
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 19:42 -0800
Re: Fabian's bra. owl <owl@rooftop.invalid> - 2019-02-05 04:21 +0000
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 20:29 -0800
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 20:45 -0800
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-05 06:59 -0800
Re: Fabian's bra. "F. Russell" <fr@random.info> - 2019-02-06 00:07 +0000
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-05 22:56 -0500
Re: Fabian's bra. Steve Carroll <fretwizzer@gmail.com> - 2019-02-06 07:35 -0800
Re: Fabian's bra. Hadron Quark <hadronquark@gmail.com> - 2019-02-07 00:50 +0100
Re: Fabian's bra. Chris Ahlstrom <OFeem1987@teleworm.us> - 2019-02-09 19:01 -0500
Re: Fabian's bra. chrisv <chrisv@nospam.invalid> - 2019-02-11 07:00 -0600
Re: Fabian's bra. DFS <nospam@dfs.com> - 2019-02-06 09:33 -0500
Re: Fabian's bra. Steve Carroll <frelwizzen@gmail.com> - 2019-02-04 19:27 -0800
Re: The Sad and Disgusting Story of Panotools Hadron Quark <hadronquark@gmail.com> - 2019-01-31 15:06 +0100
Re: The Sad and Disgusting Story of Panotools silverslimer <silver@slim.er> - 2019-01-22 14:21 -0500
Re: The Sad and Disgusting Story of Panotools Steve Carroll <frelwizzen@gmail.com> - 2019-01-22 12:11 -0800
Re: The Sad and Disgusting Story of Panotools "F. Russell" <fr@random.info> - 2019-01-23 01:07 +0000
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-23 01:18 +0000
Re: The Sad and Disgusting Story of Panotools "F. Russell" <fr@random.info> - 2019-01-23 08:50 +0000
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-23 16:13 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <frelwizzen@gmail.com> - 2019-01-23 08:29 -0800
Re: The Sad and Disgusting Story of Panotools "F. Russell" <frussell@random.info> - 2019-01-23 16:35 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <fretwizzer@gmail.com> - 2019-01-23 08:37 -0800
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-23 17:30 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <fretwizzer@gmail.com> - 2019-01-23 09:36 -0800
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-23 17:34 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <frelwizzen@gmail.com> - 2019-01-23 10:19 -0800
Re: The Sad and Disgusting Story of Panotools Amanda KoXXX <iscariot694me@simplivr4.org> - 2019-01-23 20:45 +0000
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-22 23:22 -0500
Re: The Sad and Disgusting Story of Panotools Steve Carroll <frelwizzen@gmail.com> - 2019-01-22 23:22 -0800
Re: The Sad and Disgusting Story of Panotools "F. Russell" <fr@random.info> - 2019-01-23 08:41 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <frelwizzen@gmail.com> - 2019-01-23 01:11 -0800
Re: The Sad and Disgusting Story of Panotools silverslimer <silver@slim.er> - 2019-01-23 18:13 -0500
Re: The Sad and Disgusting Story of Panotools "F. Russell" <fr@random.info> - 2019-01-24 00:31 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <frelwizzen@gmail.com> - 2019-01-23 16:53 -0800
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-24 09:00 -0500
Re: The Sad and Disgusting Story of Panotools Steve Carroll <fretwizzer@gmail.com> - 2019-01-24 08:13 -0800
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-24 11:43 -0500
Re: The Sad and Disgusting Story of Panotools Steve Carroll <fretwizzer@gmail.com> - 2019-01-24 08:59 -0800
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-24 18:49 -0500
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-24 21:25 +0000
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-24 18:26 -0500
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-25 00:40 +0000
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-25 12:33 -0500
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-25 18:13 +0000
Re: The Sad and Disgusting Story of Panotools "F. Russell" <frussell@random.info> - 2019-01-25 18:44 +0000
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-25 19:26 +0000
Re: The Sad and Disgusting Story of Panotools "F. Russell" <frussell@random.info> - 2019-01-25 19:39 +0000
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-25 19:50 +0000
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-25 15:44 -0500
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-26 15:57 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <fretwizzer@gmail.com> - 2019-01-26 08:47 -0800
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-26 17:04 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <fretwizzer@gmail.com> - 2019-01-26 09:18 -0800
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-26 13:13 -0500
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-26 19:07 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <fretwizzer@gmail.com> - 2019-01-26 11:11 -0800
Re: The Sad and Disgusting Story of Panotools "F. Russell" <fr@random.info> - 2019-01-25 10:15 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <fretwizzer@gmail.com> - 2019-01-25 07:03 -0800
Re: The Sad and Disgusting Story of Panotools "F. Russell" <frussell@random.info> - 2019-01-25 15:30 +0000
Re: The Sad and Disgusting Story of Panotools Steve Carroll <fretwizzer@gmail.com> - 2019-01-25 07:39 -0800
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-25 16:22 -0500
Re: The Sad and Disgusting Story of Panotools Steve Carroll <frelwizzen@gmail.com> - 2019-01-31 06:53 -0800
Re: The Sad and Disgusting Story of Panotools chrisv <chrisv@nospam.invalid> - 2019-01-24 06:57 -0600
Re: The Sad and Disgusting Story of Panotools RonB <ronb02NOSPAM@gmail.com> - 2019-01-24 18:09 +0000
Re: The Sad and Disgusting Story of Panotools Amanda KoXXX <iscariot694me@simplivr4.org> - 2019-01-23 20:38 +0000
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-24 09:01 -0500
Re: The Sad and Disgusting Story of Panotools owl <owl@rooftop.invalid> - 2019-01-24 15:04 +0000
The Sad and Disgusting Story of "DFS" chrisv <chrisv@nospam.invalid> - 2019-01-24 10:35 -0600
Re: The Sad and Disgusting Story of Panotools DFS <nospam@dfs.com> - 2019-01-24 19:00 -0500
Re: The Sad and Disgusting Story of Panotools silverslimer <silver@slim.er> - 2019-01-23 18:11 -0500
Re: The Sad and Disgusting Story of Panotools Steve Carroll <frelwizzen@gmail.com> - 2019-01-23 15:34 -0800
Re: The Sad and Disgusting Story of Panotools Steve Carroll <frelwizzen@gmail.com> - 2019-01-21 17:10 -0800
Page 18 of 19 — ← Prev page 1 … 16 17 [18] 19 Next page →
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2019-01-26 08:47 -0800 |
| Message-ID | <43c6c88b-19a1-4124-82ce-2f71be842dea@googlegroups.com> |
| In reply to | #485999 |
On Saturday, January 26, 2019 at 8:57:33 AM UTC-7, owl wrote: > DFS <nospam@dfs.com> wrote: > > On 1/25/2019 1:13 PM, owl wrote: > >> DFS <nospam@dfs.com> wrote: > >>> On 1/24/2019 7:40 PM, owl wrote: > >>>> DFS <nospam@dfs.com> wrote: > >>>>> On 1/24/2019 4:25 PM, owl wrote: > >>>>>> DFS <nospam@dfs.com> wrote: > >>>>>>> On 1/23/2019 7:31 PM, F. Russell wrote: > >>>>>>>> and it is undeniably true that > >>>>>> > >>>>>>>> LO equals Microshit in most areas > >>>>>>> > >>>>>>> That is a BULLSHIT statement. LO in 2019 is even far behind the ancient > >>>>>>> MS Office 2003 in a variety of very important ways: > >>>>>>> > >>>>>>> * you can't attach code directly to an object - you have to save the > >>>>>>> code as a standalone macro, then attach the macro to the object. > >>>>>>> Ridiculous. > >>>>>>> > >>>>>>> * listboxes and comboboxes can show only one column of data at a time. > >>>>>>> Absurd. It makes LO worthless as an app development tool. > >>>>>>> > >>>>>> > >>>>>> What is the purpose of having multiple columns in a combobox? Are selections > >>>>>> still by row or do you select cells? > >>>>> > >>>>> > >>>>> The purpose is to display data, make boss happy, get paid, eat wings, > >>>>> watch SB on big screen, invite Mrs Owl down to the boat. > >>>>> > >>>>> Ask her if she doesn't like comboboxes... > >>>>> > >>>>> You select one row (and after the selection it shows only one cell), but > >>>>> you can always address all the rows and columns of a combobox via > >>>>> 0-based code. > >>>>> > >>>> > >>>> When would it be useful to do so? And how do you label the combobox > >>>> so that it is clear to the user what happens when he selects a column, > >>>> or a cell, vs a row? > >>> > >>> > >>> It would be useful to address the data in the combobox via code whenever > >>> you need to do so. You can read the data in the combobox, set the > >>> datasource, show/hide columns, bind columns, even make it dropdown > >>> automatically. All via code. > >>> > >> > >> Of course. But how does the user know what data is being read? > >> IOW, if he selects a row, which column(s) will actually be processed? > >> > >> (Maybe you could mock up an example on imgur to clarify?) > > > > The data being read is up to the dev, but you don't want to confuse the > > user so you show a value in the cbobox (but your code will generally use > > a hidden ID field if you designed the db correctly). > > > > rowsource = "SELECT id, name, age FROM tbl ORDER BY name;" > > columncount = 3 > > columnwidths = "0in;1in;0.5in" > > columnheads = Yes > > boundcolumn = 1 (designtime setting. Default is 1, max is columncount, > > Code will by default read the bound column nbr, but you can explicitly > > choose which column you want.) > > > > ctl.column(0) = 1 'column property is 0-based > > ctl.column(1) = "owl" > > ctl.column(2) = 83 > > > > > > That code just fills the combobox. It doesn't illustrate the > need for multiple columns. > > > > >>> And because of limited screenspace you don't generally label the > >>> combobox to explain what happens after selection - you add the > >>> explanation to the StatusBarText property of the combobox. > >> > >> So it's a mysterybox until he makes a selection? > > > > > > What happens after an item is selected is always a mystery, but > > generally nothing until you click the Go button. > > > > As soon as the control gets focus (either tabbed to or clicked > > on/inside), the status bar text shows up (if you set it - and you always > > should if the app goes out to users). > > > > Access (and VB and Gambas and Qt and other such widget tools) are great > > for data display. But they're a pain to distribute. > > > > Are you bored, or trolling, or genuinely interested? > > I'm genuinely interested in how a multicolumn combobox is a better > interface for the user a user than multiple single-column comboboxes would > be. Are you talking about: <https://streamable.com/xemlr> >I saw one example online with song lists showing artist/album/song > in the combobox. I can imagine that being a jumbled mess with a large > collection. It would be much better to select artist and see a list of > albums, then select album and see a list of songs, then select song.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-01-26 17:04 +0000 |
| Message-ID | <s9z90b3ta.3@rooftop.invalid> |
| In reply to | #486009 |
Steve Carroll <fretwizzer@gmail.com> wrote: > On Saturday, January 26, 2019 at 8:57:33 AM UTC-7, owl wrote: >> DFS <nospam@dfs.com> wrote: >> > On 1/25/2019 1:13 PM, owl wrote: >> >> DFS <nospam@dfs.com> wrote: >> >>> On 1/24/2019 7:40 PM, owl wrote: >> >>>> DFS <nospam@dfs.com> wrote: >> >>>>> On 1/24/2019 4:25 PM, owl wrote: >> >>>>>> DFS <nospam@dfs.com> wrote: >> >>>>>>> On 1/23/2019 7:31 PM, F. Russell wrote: >> >>>>>>>> and it is undeniably true that >> >>>>>> >> >>>>>>>> LO equals Microshit in most areas >> >>>>>>> >> >>>>>>> That is a BULLSHIT statement. LO in 2019 is even far behind the ancient >> >>>>>>> MS Office 2003 in a variety of very important ways: >> >>>>>>> >> >>>>>>> * you can't attach code directly to an object - you have to save the >> >>>>>>> code as a standalone macro, then attach the macro to the object. >> >>>>>>> Ridiculous. >> >>>>>>> >> >>>>>>> * listboxes and comboboxes can show only one column of data at a time. >> >>>>>>> Absurd. It makes LO worthless as an app development tool. >> >>>>>>> >> >>>>>> >> >>>>>> What is the purpose of having multiple columns in a combobox? Are selections >> >>>>>> still by row or do you select cells? >> >>>>> >> >>>>> >> >>>>> The purpose is to display data, make boss happy, get paid, eat wings, >> >>>>> watch SB on big screen, invite Mrs Owl down to the boat. >> >>>>> >> >>>>> Ask her if she doesn't like comboboxes... >> >>>>> >> >>>>> You select one row (and after the selection it shows only one cell), but >> >>>>> you can always address all the rows and columns of a combobox via >> >>>>> 0-based code. >> >>>>> >> >>>> >> >>>> When would it be useful to do so? And how do you label the combobox >> >>>> so that it is clear to the user what happens when he selects a column, >> >>>> or a cell, vs a row? >> >>> >> >>> >> >>> It would be useful to address the data in the combobox via code whenever >> >>> you need to do so. You can read the data in the combobox, set the >> >>> datasource, show/hide columns, bind columns, even make it dropdown >> >>> automatically. All via code. >> >>> >> >> >> >> Of course. But how does the user know what data is being read? >> >> IOW, if he selects a row, which column(s) will actually be processed? >> >> >> >> (Maybe you could mock up an example on imgur to clarify?) >> > >> > The data being read is up to the dev, but you don't want to confuse the >> > user so you show a value in the cbobox (but your code will generally use >> > a hidden ID field if you designed the db correctly). >> > >> > rowsource = "SELECT id, name, age FROM tbl ORDER BY name;" >> > columncount = 3 >> > columnwidths = "0in;1in;0.5in" >> > columnheads = Yes >> > boundcolumn = 1 (designtime setting. Default is 1, max is columncount, >> > Code will by default read the bound column nbr, but you can explicitly >> > choose which column you want.) >> > >> > ctl.column(0) = 1 'column property is 0-based >> > ctl.column(1) = "owl" >> > ctl.column(2) = 83 >> > >> > >> >> That code just fills the combobox. It doesn't illustrate the >> need for multiple columns. >> >> > >> >>> And because of limited screenspace you don't generally label the >> >>> combobox to explain what happens after selection - you add the >> >>> explanation to the StatusBarText property of the combobox. >> >> >> >> So it's a mysterybox until he makes a selection? >> > >> > >> > What happens after an item is selected is always a mystery, but >> > generally nothing until you click the Go button. >> > >> > As soon as the control gets focus (either tabbed to or clicked >> > on/inside), the status bar text shows up (if you set it - and you always >> > should if the app goes out to users). >> > >> > Access (and VB and Gambas and Qt and other such widget tools) are great >> > for data display. But they're a pain to distribute. >> > >> > Are you bored, or trolling, or genuinely interested? >> >> I'm genuinely interested in how a multicolumn combobox is a better >> interface for the user a user than multiple single-column comboboxes would >> be. > > Are you talking about: > > <https://streamable.com/xemlr> > Yes, sort of like that. A multicolumn box would just display everything at once, with "race" entries listed multiple times, once for each associated "subclass." IOW, a jumbled mess. >>I saw one example online with song lists showing artist/album/song >> in the combobox. I can imagine that being a jumbled mess with a large >> collection. It would be much better to select artist and see a list of >> albums, then select album and see a list of songs, then select song. > > >
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2019-01-26 09:18 -0800 |
| Message-ID | <c18848ca-bb3e-479f-9518-6d0f9ed735f9@googlegroups.com> |
| In reply to | #486012 |
On Saturday, January 26, 2019 at 10:04:23 AM UTC-7, owl wrote: > Steve Carroll <fretwizzer@gmail.com> wrote: > > On Saturday, January 26, 2019 at 8:57:33 AM UTC-7, owl wrote: > >> DFS <nospam@dfs.com> wrote: > >> > On 1/25/2019 1:13 PM, owl wrote: > >> >> DFS <nospam@dfs.com> wrote: > >> >>> On 1/24/2019 7:40 PM, owl wrote: > >> >>>> DFS <nospam@dfs.com> wrote: > >> >>>>> On 1/24/2019 4:25 PM, owl wrote: > >> >>>>>> DFS <nospam@dfs.com> wrote: > >> >>>>>>> On 1/23/2019 7:31 PM, F. Russell wrote: > >> >>>>>>>> and it is undeniably true that > >> >>>>>> > >> >>>>>>>> LO equals Microshit in most areas > >> >>>>>>> > >> >>>>>>> That is a BULLSHIT statement. LO in 2019 is even far behind the ancient > >> >>>>>>> MS Office 2003 in a variety of very important ways: > >> >>>>>>> > >> >>>>>>> * you can't attach code directly to an object - you have to save the > >> >>>>>>> code as a standalone macro, then attach the macro to the object. > >> >>>>>>> Ridiculous. > >> >>>>>>> > >> >>>>>>> * listboxes and comboboxes can show only one column of data at a time. > >> >>>>>>> Absurd. It makes LO worthless as an app development tool. > >> >>>>>>> > >> >>>>>> > >> >>>>>> What is the purpose of having multiple columns in a combobox? Are selections > >> >>>>>> still by row or do you select cells? > >> >>>>> > >> >>>>> > >> >>>>> The purpose is to display data, make boss happy, get paid, eat wings, > >> >>>>> watch SB on big screen, invite Mrs Owl down to the boat. > >> >>>>> > >> >>>>> Ask her if she doesn't like comboboxes... > >> >>>>> > >> >>>>> You select one row (and after the selection it shows only one cell), but > >> >>>>> you can always address all the rows and columns of a combobox via > >> >>>>> 0-based code. > >> >>>>> > >> >>>> > >> >>>> When would it be useful to do so? And how do you label the combobox > >> >>>> so that it is clear to the user what happens when he selects a column, > >> >>>> or a cell, vs a row? > >> >>> > >> >>> > >> >>> It would be useful to address the data in the combobox via code whenever > >> >>> you need to do so. You can read the data in the combobox, set the > >> >>> datasource, show/hide columns, bind columns, even make it dropdown > >> >>> automatically. All via code. > >> >>> > >> >> > >> >> Of course. But how does the user know what data is being read? > >> >> IOW, if he selects a row, which column(s) will actually be processed? > >> >> > >> >> (Maybe you could mock up an example on imgur to clarify?) > >> > > >> > The data being read is up to the dev, but you don't want to confuse the > >> > user so you show a value in the cbobox (but your code will generally use > >> > a hidden ID field if you designed the db correctly). > >> > > >> > rowsource = "SELECT id, name, age FROM tbl ORDER BY name;" > >> > columncount = 3 > >> > columnwidths = "0in;1in;0.5in" > >> > columnheads = Yes > >> > boundcolumn = 1 (designtime setting. Default is 1, max is columncount, > >> > Code will by default read the bound column nbr, but you can explicitly > >> > choose which column you want.) > >> > > >> > ctl.column(0) = 1 'column property is 0-based > >> > ctl.column(1) = "owl" > >> > ctl.column(2) = 83 > >> > > >> > > >> > >> That code just fills the combobox. It doesn't illustrate the > >> need for multiple columns. > >> > >> > > >> >>> And because of limited screenspace you don't generally label the > >> >>> combobox to explain what happens after selection - you add the > >> >>> explanation to the StatusBarText property of the combobox. > >> >> > >> >> So it's a mysterybox until he makes a selection? > >> > > >> > > >> > What happens after an item is selected is always a mystery, but > >> > generally nothing until you click the Go button. > >> > > >> > As soon as the control gets focus (either tabbed to or clicked > >> > on/inside), the status bar text shows up (if you set it - and you always > >> > should if the app goes out to users). > >> > > >> > Access (and VB and Gambas and Qt and other such widget tools) are great > >> > for data display. But they're a pain to distribute. > >> > > >> > Are you bored, or trolling, or genuinely interested? > >> > >> I'm genuinely interested in how a multicolumn combobox is a better > >> interface for the user a user than multiple single-column comboboxes would > >> be. > > > > Are you talking about: > > > > <https://streamable.com/xemlr> > > > > Yes, sort of like that. A multicolumn box would just display everything > at once, with "race" entries listed multiple times, once for each associated > "subclass." IOW, a jumbled mess. I don't get it, either... but I haven't read much in this thread.
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2019-01-26 13:13 -0500 |
| Message-ID | <5r13E.109501$wz4.17277@fx10.iad> |
| In reply to | #485999 |
On 1/26/2019 10:57 AM, owl wrote: > DFS <nospam@dfs.com> wrote: >> On 1/25/2019 1:13 PM, owl wrote: >>> DFS <nospam@dfs.com> wrote: >>>> On 1/24/2019 7:40 PM, owl wrote: >>>>> DFS <nospam@dfs.com> wrote: >>>>>> On 1/24/2019 4:25 PM, owl wrote: >>>>>>> DFS <nospam@dfs.com> wrote: >>>>>>>> On 1/23/2019 7:31 PM, F. Russell wrote: >>>>>>>>> and it is undeniably true that >>>>>>> >>>>>>>>> LO equals Microshit in most areas >>>>>>>> >>>>>>>> That is a BULLSHIT statement. LO in 2019 is even far >>>>>>>> behind the ancient MS Office 2003 in a variety of very >>>>>>>> important ways: >>>>>>>> >>>>>>>> * you can't attach code directly to an object - you >>>>>>>> have to save the code as a standalone macro, then >>>>>>>> attach the macro to the object. Ridiculous. >>>>>>>> >>>>>>>> * listboxes and comboboxes can show only one column of >>>>>>>> data at a time. Absurd. It makes LO worthless as an >>>>>>>> app development tool. >>>>>>>> >>>>>>> >>>>>>> What is the purpose of having multiple columns in a >>>>>>> combobox? Are selections still by row or do you select >>>>>>> cells? >>>>>> >>>>>> >>>>>> The purpose is to display data, make boss happy, get paid, >>>>>> eat wings, watch SB on big screen, invite Mrs Owl down to >>>>>> the boat. >>>>>> >>>>>> Ask her if she doesn't like comboboxes... >>>>>> >>>>>> You select one row (and after the selection it shows only >>>>>> one cell), but you can always address all the rows and >>>>>> columns of a combobox via 0-based code. >>>>>> >>>>> >>>>> When would it be useful to do so? And how do you label the >>>>> combobox so that it is clear to the user what happens when >>>>> he selects a column, or a cell, vs a row? >>>> >>>> >>>> It would be useful to address the data in the combobox via >>>> code whenever you need to do so. You can read the data in the >>>> combobox, set the datasource, show/hide columns, bind columns, >>>> even make it dropdown automatically. All via code. >>>> >>> >>> Of course. But how does the user know what data is being read? >>> IOW, if he selects a row, which column(s) will actually be >>> processed? >>> >>> (Maybe you could mock up an example on imgur to clarify?) >> >> The data being read is up to the dev, but you don't want to >> confuse the user so you show a value in the cbobox (but your code >> will generally use a hidden ID field if you designed the db >> correctly). >> >> rowsource = "SELECT id, name, age FROM tbl ORDER BY name;" >> columncount = 3 columnwidths = "0in;1in;0.5in" columnheads = Yes >> boundcolumn = 1 (designtime setting. Default is 1, max is >> columncount, Code will by default read the bound column nbr, but >> you can explicitly choose which column you want.) >> >> ctl.column(0) = 1 'column property is 0-based ctl.column(1) >> = "owl" ctl.column(2) = 83 >> >> > > That code just fills the combobox. It doesn't illustrate the need > for multiple columns. > >> >>>> And because of limited screenspace you don't generally label >>>> the combobox to explain what happens after selection - you add >>>> the explanation to the StatusBarText property of the combobox. >>> >>> So it's a mysterybox until he makes a selection? >> >> >> What happens after an item is selected is always a mystery, but >> generally nothing until you click the Go button. >> >> As soon as the control gets focus (either tabbed to or clicked >> on/inside), the status bar text shows up (if you set it - and you >> always should if the app goes out to users). >> >> Access (and VB and Gambas and Qt and other such widget tools) are >> great for data display. But they're a pain to distribute. >> >> Are you bored, or trolling, or genuinely interested? > > I'm genuinely interested in how a multicolumn combobox is a better > interface for the user a user than multiple single-column comboboxes > would be. Depends on the data and the interface. There's no one-size-fits-all multi-columns-are-always-the-best-way. > I saw one example online with song lists showing artist/album/song > in the combobox. I can imagine that being a jumbled mess with a > large collection. If you have to scroll thru a lot of data, yeah. > It would be much better to select artist and see a > list of albums, then select album and see a list of songs, then > select song. Now you're talking about listboxes instead of comboboxes, but what you just described can be accomplished well with either. I much prefer listboxes if you have enough screen space. You put the listboxes across the top (say the top third or fourth of the screen), and the result set in the bottom. Listboxes usually require less clicking and scrolling than comboboxes. You've seen this screen in my Usenet app: https://imgur.com/a/af9vcp2
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-01-26 19:07 +0000 |
| Message-ID | <908z880bz.3@rooftop.invalid> |
| In reply to | #486022 |
DFS <nospam@dfs.com> wrote: > On 1/26/2019 10:57 AM, owl wrote: > >> It would be much better to select artist and see a >> list of albums, then select album and see a list of songs, then >> select song. > > Now you're talking about listboxes instead of comboboxes, but what you > just described can be accomplished well with either. > > I much prefer listboxes if you have enough screen space. You put the > listboxes across the top (say the top third or fourth of the screen), > and the result set in the bottom. Listboxes usually require less > clicking and scrolling than comboboxes. > > You've seen this screen in my Usenet app: > https://imgur.com/a/af9vcp2 > There are differing definitions for what constitutes a combobox. But I just can't see a case where a multi-column box is preferrable to multiple single-column boxes. A selection is still going to key on just one column (the bound column, right?), and with a single-column box, what you are actually selecting is more obvious.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2019-01-26 11:11 -0800 |
| Message-ID | <ca054f4a-3edb-4a71-8452-7f139f786f88@googlegroups.com> |
| In reply to | #486025 |
On Saturday, January 26, 2019 at 12:07:34 PM UTC-7, owl wrote: > DFS <nospam@dfs.com> wrote: > > On 1/26/2019 10:57 AM, owl wrote: > > > > >> It would be much better to select artist and see a > >> list of albums, then select album and see a list of songs, then > >> select song. > > > > Now you're talking about listboxes instead of comboboxes, but what you > > just described can be accomplished well with either. > > > > I much prefer listboxes if you have enough screen space. You put the > > listboxes across the top (say the top third or fourth of the screen), > > and the result set in the bottom. Listboxes usually require less > > clicking and scrolling than comboboxes. > > > > You've seen this screen in my Usenet app: > > https://imgur.com/a/af9vcp2 > > > > There are differing definitions for what constitutes a combobox. > But I just can't see a case where a multi-column box is preferrable > to multiple single-column boxes. A selection is still going to key > on just one column (the bound column, right?), and with a single-column > box, what you are actually selecting is more obvious. I'd guess it could clear up some ambiguity of what you're selecting in certain cases.
[toc] | [prev] | [next] | [standalone]
| From | "F. Russell" <fr@random.info> |
|---|---|
| Date | 2019-01-25 10:15 +0000 |
| Message-ID | <q2enj802r85@news2.newsguy.com> |
| In reply to | #485902 |
On Thu, 24 Jan 2019 09:00:59 -0500, DFS wrote: > > in a variety of very important ways: > So? Who the fuck cares? Only a supreme asshole or a brain-dead corporate lackey would care -- and the two cases are actually the same. Furthermore, the description of being "very important" is also highly subjective and coming from a brain-dead corporate lackey like YOU it is easily dismissed as nonsense. The INTELLIGENT user will make do with whatever is available in a highly creative manner. The brain-dead corporate lackey -- and that's YOU -- will only invoke meaningless and useless comparisons. American corporations CANNOT compete globally and that sad fact is largely due to the brain-dead lackey that is exemplified by YOU. After WWII, American industry was the only game in town but when the former war-torn nations began to rebuild the American corporations were faced with a force that they, and their brain-dead lackey staffers, could not withstand. Combo Box! Ha, ha, ha, ha, ha! Only Tiffany, the brain-dead secretary, or Kimberly, the brain-dead VP, would ever be impressed -- and the American corp is chock full of such imbecilic lackeys. But let's check out some of your accusations: > > they can't even handle data copying correctly. Open a Base table and > try to mouse- or keyboard-select a subset of data (say rows 3-6 out of > 10, and columns 2-4 out of 8). It can't be done. > The fuck if it can't. I just did it and it works very well. The subsequent "paste" operations allows for many options including field selection. So the lackey is full of shit, as usual. > > * there's no dedicated report or form designer in Base; it just uses the > Writer component with menu items enabled/disabled. > Wrong again, lackey. There is no Writer component. The form object belongs to ALL components and that's EXACTLY how it should be. You are just a stupid one-trick pony. All you've ever accomplished is Microshit Access and as a consequence you believe, falsely, that Access is some sort of standard. Well, the world says: "Fuck you, lackey! We do things OUR way." > > Access forms and reports have conditional formatting that can be > applied programmatically or via GUI at design time. Still not > available in LO Base. > Who the fuck would ever want or need conditional formatting? Just make up your mind and get on with it, asshole. But here is what the lackey stooge is after: If user = "Brain-Dead Tiffany" Then Button = Sparkly Blue Else If user = "Brain-Dead Kimberly" Then Combobox = "Pretty Yellow" Else If user = "Dumb-Fuck Stooge" Then Load Asshole-Dummy Theme Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha! I could go on and on and on and on but regarding the dumb-fuck lackey stooge it would be all just more of the same.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2019-01-25 07:03 -0800 |
| Message-ID | <0346c554-7d2c-4751-9164-c1fee3a683ac@googlegroups.com> |
| In reply to | #485937 |
On Friday, January 25, 2019 at 3:16:02 AM UTC-7, F. Russell wrote: > On Thu, 24 Jan 2019 09:00:59 -0500, DFS wrote: > > > > > in a variety of very important ways: > > > > So? Who the fuck cares? People who must generate reports care.
[toc] | [prev] | [next] | [standalone]
| From | "F. Russell" <frussell@random.info> |
|---|---|
| Date | 2019-01-25 15:30 +0000 |
| Message-ID | <q2fa2c03hh@news1.newsguy.com> |
| In reply to | #485943 |
On Fri, 25 Jan 2019 07:03:46 -0800, Steve Carroll vomited this verbiage that I considered to be worthy of my attention for one of a variety of possible reasons: > > People who must generate reports care. > Oh, so you have carefully interviewed every person in the world who "must" generate reports. Wow! This guy sure gets around! [Snicker... snicker... what a fucking asshole! ... snicker] My advice is simple and ultimately effective: If reports "must" be generated then enlist/hire someone who has BRAINS. The case is closed. Life is simple when one knows how.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2019-01-25 07:39 -0800 |
| Message-ID | <30c1443c-0129-41cb-b04c-39c15146f68b@googlegroups.com> |
| In reply to | #485947 |
On Friday, January 25, 2019 at 8:31:16 AM UTC-7, F. Russell wrote: > On Fri, 25 Jan 2019 07:03:46 -0800, Steve Carroll vomited this verbiage > that I considered to be worthy of my attention for one of a variety of > possible reasons: > > > > > People who must generate reports care. > > > > Oh, so you have carefully interviewed every person in the world > who "must" generate reports. Nah, I just applied the common sense idea that avoids hoop jumping, which is what IT departments are doing. > My advice is simple and ultimately effective: > > If reports "must" be generated then enlist/hire someone who > has BRAINS. Right, don't let software solve that if it can, you know, one of things that *you* have crowed loudest over. > The case is closed. Yes, you're a hypocrite... you crow about software solving problems, yet, you push getting someone with " BRAINS" to do a job software is perfectly capable of doing. > Life is simple when one knows how. Irony.
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2019-01-25 16:22 -0500 |
| Message-ID | <M5L2E.68661$fB2.32072@fx16.iad> |
| In reply to | #485937 |
On 1/25/2019 5:15 AM, F. Russell wrote: > On Thu, 24 Jan 2019 09:00:59 -0500, DFS wrote: > >> >> in a variety of very important ways: >> > > So? Who the fuck cares? You care, a lot. That's why you're fuming and cursing and insulting all throughout your reply. > Only a supreme asshole or a > brain-dead corporate lackey would care -- and the two > cases are actually the same. So you're unemployed? 'Cause I could've sworn you worked for a corporation. > Furthermore, the description of being "very important" > is also highly subjective and coming from a brain-dead > corporate lackey like YOU it is easily dismissed as > nonsense. Don't take it so hard. You won't be doing real dev with LibreOffice anyway, so you won't run into these very important issues. Your lame-ass 'doc mgmt/payroll' system will have one form and one button that runs a stupid, inflexible shell script, which you'll force the employer to pay you to update each year because you're too incompetent to make an easy to use LO system that will last some years. > The INTELLIGENT user will make do with whatever is available > in a highly creative manner. Sorry, idiot, but one CANNOT overcome most of the built-in LibreOffice shitware limitations. Some people - but not you - could probably hack a solution to some of the issues I listed (which, being a puss, you snipped), but they will be half-ass hacks. > The brain-dead corporate lackey > -- and that's YOU -- will only invoke meaningless and > useless comparisons. As opposed to your meaningless and useless comparisons: > American corporations CANNOT compete globally They can and they do. You, however, cannot even compete locally. > and that > sad fact is largely due to the brain-dead lackey that > is exemplified by YOU. After WWII, American industry > was the only game in town but when the former war-torn > nations began to rebuild the American corporations were > faced with a force that they, and their brain-dead lackey > staffers, could not withstand. > > Combo Box! Ha, ha, ha, ha, ha! Only Tiffany, the brain-dead > secretary, or Kimberly, the brain-dead VP, would ever be impressed > -- and the American corp is chock full of such imbecilic lackeys. > > But let's check out some of your accusations: > >> >> they can't even handle data copying correctly. Open a Base table and >> try to mouse- or keyboard-select a subset of data (say rows 3-6 out of >> 10, and columns 2-4 out of 8). It can't be done. >> > > The fuck if it can't. I just did it and it works very well. > The subsequent "paste" operations allows for many options > including field selection. > > So the lackey is full of shit, as usual. No, it does NOT work here on Windows. At all. I'll try it on Linux later. >> * there's no dedicated report or form designer in Base; it just uses the >> Writer component with menu items enabled/disabled. >> > > Wrong again, lackey. > > There is no Writer component. There's this: C:\Program Files\LibreOffice\program\swriter.exe If Base isn't using Writer for a form designer, they did a good job cloning it and using a subset of icons and menus. https://imgur.com/a/LFf09vO How bad is it, you ask? It's so bad the database "form designer" has a menu option for "Chapter Numbering". They apparently forgot to remove it. > The form object belongs to ALL > components and that's EXACTLY how it should be. You don't know what you're talking about. There is no "form object" (you meant form designer?) for anything except Base. And Base forms go with the .odb they were created in. And the more I test that crap the worse it gets. Drop a label on the "form" and try to enter text directly into it. You can't. You have to open the control Properties dialog and enter the text in the Label field of the Properties. And even though the "form designer" shows icons for left/center/right align, they're disabled when the label control has focus and you can't use them to align the text in the label. You have to go back to the Properties dialog and align the text from there. It gets even more fucked up. I set the label font to 16 bold and it worked, but it won't allow me to set the font color. It just stays gray. Version: 6.1.3.2 (x64) Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb CPU threads: 4; OS: Windows 6.3; UI render: default; Locale: en-US (en_US); Calc: CL I tried to connect LO to an existing Access 2003 db, but the shitware fails at that, then crashes. https://imgur.com/a/WxFHJ07 I had a 64-bit Java runtime environ installed (which LO recognized and added when I installed LO). Thinking the Access connection issue might be related to the jre, I installed a 32-bit jre. But the LO crapware refused to let me add it. https://imgur.com/a/BKBG2pV No matter which folder selected, it refused to work. It's just a big, fat pile of kludgey, unstable shit. MS developers make total mincemeat of the part-time undedicated amateurs who work on LibreOffice. They should quit their hobby. > You are just a stupid one-trick pony. All you've ever accomplished > is Microshit Access You're just a stupid zero-trick pony who hasn't accomplished anything since leaving grad. school. > and as a consequence you believe, falsely, that Access is some sort of standard. Of course it's the standard for desktop databases all across the world. Hundreds of millions of installs. > Well, the world says: "Fuck you, lackey! We do things OUR way." No. In reality the world says "Fuck you LO. I have real work to do. You're not up to the task." >> Access forms and reports have conditional formatting that can be >> applied programmatically or via GUI at design time. Still not >> available in LO Base. >> > > Who the fuck would ever want or need conditional formatting? Every single company in the world. How do you think you highlight negative results in red? With Access you set the form view to continuous and add a little code (and you can even let the user change the colors at runtime, for that extra oomph the boss didn't ask for, but takes you no time to add). With LeeberOffice you throw up your hands, tell your boss it can't be done, and skulk away defeated by undedicated MS-hating hobbyists who can't nearly keep up with MS developers. > Just make up your mind and get on with it, asshole. > > But here is what the lackey stooge is after: > > If user = "Brain-Dead Tiffany" Then > Button = Sparkly Blue > Else > If user = "Brain-Dead Kimberly" Then > Combobox = "Pretty Yellow" > Else > If user = "Dumb-Fuck Stooge" Then > Load Asshole-Dummy Theme If crapware = "LibreOffice" Then Speed = Significantly Reduced Functionality = Significantly Reduced Income = Significantly Reduced EndIf > Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha! > > I could go on and on and on and on but regarding the > dumb-fuck lackey stooge it would be all just more of > the same. Where 'the same' is you shitting your pants after LibreOffice shits it's pants.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <frelwizzen@gmail.com> |
|---|---|
| Date | 2019-01-31 06:53 -0800 |
| Message-ID | <515d240e-285b-4307-a800-aa974161be6e@googlegroups.com> |
| In reply to | #485902 |
On Thursday, January 24, 2019 at 7:00:14 AM UTC-7, DFS wrote:
> On 1/23/2019 7:31 PM, F. Russell wrote:
> > On Wed, 23 Jan 2019 18:13:58 -0500, silverslimer wrote:
> >
> >>
> >> LibreOffice has yet to catch up to the
> >> standard WordPerfect Office and Microsoft
> >>
> >
> > What the fuck do you know? Asshole idiot.
> >
> > You do NOTHING with a computer. NOTHING.
>
> Which is EXACTLY what you do with a computer.
>
>
>
> > But I am EXTREMELY VERSED in all aspects of Microshit
> > as well as LibreOffice
>
> Lying sack of shit. You're EXTREMELY LOST when it comes to programming
> MS Office or LeeberOffice.
>
> Two days ago:
>
> <quote>
> Coding is busy work for brain-dead lackeys.
>
> Yep. I have it all worked out in my head. The "programming"
> is finished. Now I just need to "code" it all.
>
> I need to train some stupid bitch to do the coding for me...
> </quote>
>
>
> Why are you scared to do it yourself? Probably because you know LO
> Basic is convoluted and verbose.
>
> =======================================================================
> read some data in LO Base (from pg 161 of the LibreOffice 3 Basic Guide
> =======================================================================
> Dim DatabaseContext As Object
> Dim DataSource As Object, Connection As Object
> Dim Statement As Object, ResultSet As Object
> DatabaseContext = createUnoService("com.sun.star.sdb.DatabaseContext")
> DataSource = DatabaseContext.getByName("Customers")
> Connection = DataSource.GetConnection("","")
> Statement = Connection.createStatement()
> ResultSet = Statement.executeQuery("Customer")
> If Not IsNull(ResultSet) Then
> While ResultSet.next
> MsgBox ResultSet.getString(1)
> Wend
> End If
>
>
> 13 lines (50% more than VBA). Shortened from the original 21 lines.
>
>
> ==========================================================
> read data in MS Access (2003) using DAO library
> ==========================================================
>
> Dim db As Database, rs As Recordset
> Set db = CurrentDb() 'or Set db = OpenDatabase(path)
> Set rs = db.OpenRecordset("TRAVEL")
> While Not rs.EOF
> MsgBox rs("State") & " - " & rs("City")
> rs.MoveNext
> Wend
> End Sub
>
>
> 8 lines
> ==========================================================
>
> MS is doomed.
>
>
>
>
> > and it is undeniably true that
> > LO equals Microshit in most areas
>
> That is a BULLSHIT statement. LO in 2019 is even far behind the ancient
> MS Office 2003 in a variety of very important ways:
>
> * you can't attach code directly to an object - you have to save the
> code as a standalone macro, then attach the macro to the object.
> Ridiculous.
>
> * listboxes and comboboxes can show only one column of data at a time.
> Absurd. It makes LO worthless as an app development tool.
>
> * there's no dedicated report or form designer in Base; it just uses the
> Writer component with menu items enabled/disabled. What a silly
> kludge - it's a shortcut taken because real life gets in the way of
> hobbyist development.
>
> * Access forms and reports have conditional formatting that can be
> applied programmatically or via GUI at design time. Still not
> available in LO Base.
>
> * they can't even handle data copying correctly. Open a Base table and
> try to mouse- or keyboard-select a subset of data (say rows 3-6 out of
> 10, and columns 2-4 out of 8). It can't be done. You can only
> highlight-copy the entire table in LO Base.
>
> Or go the other way: try to append a bunch of data from Calc into a
> Base table. It's easy to do in Excel->Access, of course, but it won't
> work at all in LO Base. LO devs were asleep that day in 1995 when
> Microsoft developers mastered simple data exchange between apps. It's
> actually unbelievable.
>
> * the Base report object doesn't let you format a field as a running sum
> (over group or over all). Access 2003 does, of course.
>
> * the Calc macro recorder generates insane amounts of code to do even
> the simplest things.
>
> * it's God-awful slow for the most part. File open/save is tortuous.
>
>
> I could go on and on and on about the deficiencies in that slopware, but
> it falls on deaf ears. Uninformed, inexperienced, biased idiots like
> you and wRonG will still claim LibreOffice is as good as or better than
> MS Office.
>
> On the plus side, it [claims to] open a huge number of file formats. In
> practice it's a mixed bag; 20-30 seconds to open a 798KB .pdf file
> (Sumatra opens nearly all .pdf files in <1 second - even 70MB ones).
>
> Anyway, disregard the lousy Base component, and the LO Basic debacle,
> and it's a decent program for free. That's the best that can be said
> about it.
>
> But sometimes $0 is not a cost worth bearing, and in my opinion
> LibreOffice is a prime example.
>
>
>
> > with the exception
> > of Power Pivot, a.k.a. Self-Service Business Intelligence
> > (although LO is well developed regarding data models).
>
>
> I don't know what advancements are in place in later versions of Access
> and Excel (2007, 2010, 2013, 2016, 2019), but it'll likely be another
> decade before LO gets to cloning them.
>
>
>
> > Furthermore, LO will only get vastly better in time
> > due to the massive community involvement,
>
> They've had nearly 1400 recorded contributors working on (and off) that
> hobbyware over the last two decades, and it's still slow and bumbling
> and lagging features in good commercial office suites.
>
> https://www.libreoffice.org/about-us/credits/
>
>
> > whereas Microshit continues to degenerate towards extortionate
> > practices.
>
> Idiot liar.
>
>
> > So go back to your asshole games, little boy.
> > Your opinions and judgments are worth less than
> > pig flatus.
>
> Slimer's opinions are FAR MORE valuable than your constant, stupid,
> ignorant, screeching rants about "Microshit".
>
>
>
> > Problem for your sorry ass:
> >
> > Describe how to determine, programmaticaly, the last row
> > of a date ranga in ALL major spreadsheets, including
> > LO and Microshit.
> >
> > Ha, ha, ha, ha, ha, ha, ha, ha, ha!
>
>
> "last row of a date range"?
>
> That doesn't make sense, moron.
>
>
>
> > The asshole idiot will run away hoping to hide his
> > disgrace.
>
> You frequently do that.
How is barely used a universal consciousness tied to flatlining brain waves in any way going to lead to reasoned usenet dialog?
Are you being like Troll Master Steve Carroll on purpose? Troll Master Steve Carroll wants to hurt the whole group: If he and his shills can't be the focus here then his flooding crap will.
--
Top 15 Ways Troll Master Steve Carroll Trolls
http://www.5z8.info/how-to-build-a-bomb_h2o1be_peepshow
https://www.youtube.com/watch?v=0ZNxaaKD7-c
http://www.5z8.info/how-to-build-a-bomb_o8n9lg_racist-raps
Jonas Eklundh Communication
[toc] | [prev] | [next] | [standalone]
| From | chrisv <chrisv@nospam.invalid> |
|---|---|
| Date | 2019-01-24 06:57 -0600 |
| Message-ID | <o3dj4ed0dqm3pn8n95gh52j0km27rr4jrb@4ax.com> |
| In reply to | #485855 |
silverslimer wrote: >DFS does make an excellent point No, it's a garbage point. >in stating that LibreOffice has yet to catch up to the >standard WordPerfect Office and Microsoft Office set at the onset of >the 21st century. Even if true, doesn't need to. It needs to be a competitive value, and it is. Only a small percentage of users, in this, or any, market, are going to find the best value in the "high end" product. -- "OO does not offer any advantage over MS Office other than saving a few dollars on purchase price" - "True Linux advocate" Hadron Quark
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2019-01-24 18:09 +0000 |
| Message-ID | <q2cv0v$v12$3@dont-email.me> |
| In reply to | #485899 |
On 2019-01-24, chrisv <chrisv@nospam.invalid> wrote: > silverslimer wrote: > >>DFS does make an excellent point > > No, it's a garbage point. > >>in stating that LibreOffice has yet to catch up to the >>standard WordPerfect Office and Microsoft Office set at the onset of >>the 21st century. > > Even if true, doesn't need to. It needs to be a competitive value, > and it is. > > Only a small percentage of users, in this, or any, market, are going > to find the best value in the "high end" product. Most people don't use 95% of the features in a word processor. With email and social media it's probably getting to the point where 90% of the people don't use a word processor at all. Just another area where Microsoft's monopoly is becoming less and less relevant. -- The more I see of Windows, the more I like Linux.
[toc] | [prev] | [next] | [standalone]
| From | Amanda KoXXX <iscariot694me@simplivr4.org> |
|---|---|
| Date | 2019-01-23 20:38 +0000 |
| Message-ID | <q2ajcc$163b$6@gioia.aioe.org> |
| In reply to | #485738 |
On Tue, 22 Jan 2019 23:22:16 -0500, DFS wrote: > On 1/22/2019 8:07 PM, F. Russell wrote: > >> POSIX, the global standard for OS interopability, and the standard that >> Microshit does not adopt because to do so would mean it would have to >> fairly compete. > > > Spare us. ONLY GuhNoo and Linux compete unfairly by giving away all > their work for free. > > If someone walked into your workplace and offered to do your job for > free you'd scream bloody murder. > > To that I can only offer these condolences: boo fuckin' hoo Microsoft gave Windows 10 away for free. Granted it was time limited so get it before it's gone.
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2019-01-24 09:01 -0500 |
| Message-ID | <tyj2E.109352$S24.34793@fx19.iad> |
| In reply to | #485835 |
On 1/23/2019 3:38 PM, Amanda KoXXX wrote: > On Tue, 22 Jan 2019 23:22:16 -0500, DFS wrote: > >> On 1/22/2019 8:07 PM, F. Russell wrote: >> >>> POSIX, the global standard for OS interopability, and the standard that >>> Microshit does not adopt because to do so would mean it would have to >>> fairly compete. >> >> >> Spare us. ONLY GuhNoo and Linux compete unfairly by giving away all >> their work for free. >> >> If someone walked into your workplace and offered to do your job for >> free you'd scream bloody murder. >> >> To that I can only offer these condolences: boo fuckin' hoo > > Microsoft gave Windows 10 away for free. > Granted it was time limited so get it before it's gone. They gave a free upgrade to Win7/8/8.1 licensees. So you had to have already paid.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2019-01-24 15:04 +0000 |
| Message-ID | <9z088b3.aguo3@rooftop.invalid> |
| In reply to | #485903 |
DFS <nospam@dfs.com> wrote: > On 1/23/2019 3:38 PM, Amanda KoXXX wrote: >> On Tue, 22 Jan 2019 23:22:16 -0500, DFS wrote: >> >>> On 1/22/2019 8:07 PM, F. Russell wrote: >>> >>>> POSIX, the global standard for OS interopability, and the standard that >>>> Microshit does not adopt because to do so would mean it would have to >>>> fairly compete. >>> >>> >>> Spare us. ONLY GuhNoo and Linux compete unfairly by giving away all >>> their work for free. >>> >>> If someone walked into your workplace and offered to do your job for >>> free you'd scream bloody murder. >>> >>> To that I can only offer these condolences: boo fuckin' hoo >> >> Microsoft gave Windows 10 away for free. >> Granted it was time limited so get it before it's gone. > > They gave a free upgrade to Win7/8/8.1 licensees. So you had to have > already paid. > Why are you resisting?
[toc] | [prev] | [next] | [standalone]
| From | chrisv <chrisv@nospam.invalid> |
|---|---|
| Date | 2019-01-24 10:35 -0600 |
| Subject | The Sad and Disgusting Story of "DFS" |
| Message-ID | <2ooj4edndt2e3bkqofqr2kfqi34rge6oc5@4ax.com> |
| In reply to | #485909 |
>>> DumFSck wrote: >>>> >>>> ONLY GuhNoo and Linux compete unfairly by giving away all >>>> their work for free. Liar. There is lots of free software, besides GNU/Linux. Why aren't you whining about, say, Notepad++, you hypocrite? Oh, that's right, because there is no competing Micro$oft product. Neither is Free software "unfair". FOSS is an extremely efficient new paradigm, and this efficiency allows new business models. Everything from the "donation" model, to the "advertizing" model, are facilitated. As with any other paradigm shift, companies must adapt. Only shitty, pathetic losers, like Dumfsck, whine that "the old ways" are no longer competitive, in some markets. There are still plenty of market opportunities for closed-source software. Generally speaking, cutting-edge, or specialized, software lends itself to the closed-source model. Word processors and Web browsers, on the other hand, do not. >>>> If someone walked into your workplace and offered to do your job for >>>> free you'd scream bloody murder. But no one will, because it does not make sense for anyone to do so. Likewise, it would make no sense to contribute to FOSS, unless something is gotten in return. For the 8 billionth time, FOSS is not about working for free, you dumb fscking arsehole. People (and companies) give, but they also get. While there is some "charity" in the world, rational people generally want something in return, for any significant investment. The FOSS community is rational. Many for-profit companies, including Micro$oft, participate and contribute. -- 'So why do GPL morons cry "Freedom" while dissing the other [licenses] which are Freer?' - "True Linux advocate" Hadron Quark
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2019-01-24 19:00 -0500 |
| Message-ID | <gis2E.92058$375.22619@fx40.iad> |
| In reply to | #485909 |
On 1/24/2019 10:04 AM, owl wrote: > DFS <nospam@dfs.com> wrote: >> On 1/23/2019 3:38 PM, Amanda KoXXX wrote: >>> On Tue, 22 Jan 2019 23:22:16 -0500, DFS wrote: >>> >>>> On 1/22/2019 8:07 PM, F. Russell wrote: >>>> >>>>> POSIX, the global standard for OS interopability, and the standard that >>>>> Microshit does not adopt because to do so would mean it would have to >>>>> fairly compete. >>>> >>>> >>>> Spare us. ONLY GuhNoo and Linux compete unfairly by giving away all >>>> their work for free. >>>> >>>> If someone walked into your workplace and offered to do your job for >>>> free you'd scream bloody murder. >>>> >>>> To that I can only offer these condolences: boo fuckin' hoo >>> >>> Microsoft gave Windows 10 away for free. >>> Granted it was time limited so get it before it's gone. >> >> They gave a free upgrade to Win7/8/8.1 licensees. So you had to have >> already paid. >> > > Why are you resisting? I ran it for a day or two, not long after it was released. Underwhelmed. Didn't like the start menu. Plus the hassles of minimizing forced updates and telemetry. And I don't want to give MS one red cent if I can help it. But I'll eventually head that way. I have an old Win8 license key, but I think it's for the 32-bit version and I'm not sure I can use it to upgrade to Win10 x64. The free upgrade supposedly passed a while back, but I've read about people successfully using it recently.
[toc] | [prev] | [next] | [standalone]
| From | silverslimer <silver@slim.er> |
|---|---|
| Date | 2019-01-23 18:11 -0500 |
| Message-ID | <u4th4ehln6qn3rsdfgeiq3de6avh24luad@4ax.com> |
| In reply to | #485738 |
On Tue, 22 Jan 2019 23:22:16 -0500, DFS <nospam@dfs.com> wrote: >On 1/22/2019 8:07 PM, F. Russell wrote: > >> POSIX, the global standard for OS interopability, and the >> standard that Microshit does not adopt because to do so >> would mean it would have to fairly compete. > > >Spare us. ONLY GuhNoo and Linux compete unfairly by giving away all >their work for free. > >If someone walked into your workplace and offered to do your job for >free you'd scream bloody murder. > >To that I can only offer these condolences: boo fuckin' hoo Fabian's job, apparently, is to whine endlessly. I hate to break it to you but most people do his job for free.
[toc] | [prev] | [next] | [standalone]
Page 18 of 19 — ← Prev page 1 … 16 17 [18] 19 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web