Groups | Search | Server Info | Login | Register
Groups > comp.arch.embedded > #32297
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: Dealing with "past" events |
| Date | 2024-11-24 21:26 +0000 |
| Organization | To protect and to server |
| Message-ID | <vi05m1$apok$1@paganini.bofh.team> (permalink) |
| References | (3 earlier) <vhu26q$7ck4$1@paganini.bofh.team> <vhu77j$23cfd$1@dont-email.me> <vhva4c$9bj4$1@paganini.bofh.team> <vi0029$2c9o2$3@dont-email.me> <vi00qt$2cbg0$1@dont-email.me> |
Don Y <blockedofcourse@foo.invalid> wrote:
> On 11/24/2024 12:50 PM, Don Y wrote:
>>> I should have been clearer. The "home automation system" consisted
>>> of devices (which ATM are of no interest) and user interface/scheduler
>>> working as a normal application on standard OS. User interface
>>> was supposed to be easy but allows users to define various
>>> actions. The point is that in making it "easy" (and probably
>>> simple to implement) user interface got crippled so that resonable
>>> thing was hard to do.
>>
>> That's an opportunity for a supplier to offer an "assistant"
>> (if they don't control the actual system) to assist the user.
>> Eventually, the original developer will come to realize
>> THEY should offer the assistant's functionality in the base
>> product. But, that only needs to be at some level of
>> abstraction between the user and the hardware. It need not
>> be part of the OS itself (even if the user THINKS of it as
>> part of the "OS")
>
> I.e., the "original system" offers the mechanisms (to talk to the
> various "devices") but the policy about how to use those mechanisms
> is embodied in the "assistant".
>
> [Of course, if the system is (completely) closed, then the user is stuck
> with whatever assumptions the developer baked into the application]
AFAIK the system was open-source, so theoreticaly third parties could
add any improvements they wished. But it seems that original
developer considered UI as major added-value and there were no
official/documented way to decouple UI from other parts (there were
documented way to add new devices).
There is also question of project dynamics, there are competing
projects and this one probably did not attract much interest
among outside developers. And of course software evolves,
so this could be solved in the future.
--
Waldek Hebisch
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar
Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-03 16:53 -0700
Re: Dealing with "past" events George Neuner <gneuner2@comcast.net> - 2024-11-04 12:36 -0500
Re: Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-04 13:29 -0700
Re: Dealing with "past" events George Neuner <gneuner2@comcast.net> - 2024-11-05 18:21 -0500
Re: Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-05 17:05 -0700
Re: Dealing with "past" events George Neuner <gneuner2@comcast.net> - 2024-11-06 17:25 -0500
Re: Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-06 17:13 -0700
Re: Dealing with "past" events George Neuner <gneuner2@comcast.net> - 2024-11-08 01:25 -0500
Re: Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-08 00:52 -0700
Re: Dealing with "past" events George Neuner <gneuner2@comcast.net> - 2024-11-10 12:54 -0500
Re: Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-10 13:12 -0700
Re: Dealing with "past" events antispam@fricas.org (Waldek Hebisch) - 2024-11-14 20:54 +0000
Re: Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-14 15:18 -0700
Re: Dealing with "past" events antispam@fricas.org (Waldek Hebisch) - 2024-11-24 02:14 +0000
Re: Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-23 20:40 -0700
Re: Dealing with "past" events antispam@fricas.org (Waldek Hebisch) - 2024-11-24 13:36 +0000
Re: Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-24 12:50 -0700
Re: Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-24 13:03 -0700
Re: Dealing with "past" events antispam@fricas.org (Waldek Hebisch) - 2024-11-24 21:26 +0000
Re: Dealing with "past" events Don Y <blockedofcourse@foo.invalid> - 2024-11-24 14:41 -0700
csiph-web