| From: | Rafael Vicar�a Alloza |
| Date: | 20 Sep 2000 at 20:14:19 |
| Subject: | Re: AMIOPEN: GUI Standardization |
Hello Juan,
On Wednesday, 20-Sep-00, 08:30:52,
<open@amiga.com> wrote about:
Re: AMIOPEN: GUI Standardization:
> From: Rafael Vicar�a Alloza <rafael.vicaria@ibm.net>
>> *all* configuration files should be ASCII, so humans can read
>> and understand it. No exceptions.
> Or, all configuration files could use a binary format, and only one
> tool to edit them all. There could be advantages, like being
> impossible to make syntax mistakes, and with some work, the universal
> config file editor (COFEE 8^) could provide a tree structure to see
> settings for all programs, swap them quickly for testing purposes,
> take care to notify applications that use them, and functions to copy
> and paste blocks, automate backups and the like. Now, if someone
> thinks I'm talking Windows registry here, perhaps that's the idea,
> only better. What do you think?
IMHO, I think that is exactly the wrong path, just because your proposal
introduces many failure modes. Let's see.
1.- only one tool to edit them all.
Unproven technology. Such tool doesn't exist yet.
Moreover. Is it "only one tool" an advantage?
What's wrong with text editors? They are very reliable, and
very mature, some are too mature indeed, have you ever tried vi? ;-)
2.- being impossible to make syntax mistakes
Yeah, right! How do you do that? Is it feasible?
And you could have the syntax right, but the intention wrong.
3.-
> a tree structure to see
> settings for all programs, swap them quickly for testing purposes,
> take care to notify applications that use them, and functions to copy
> and paste blocks, automate backups and the like.
I can't see there anything either innovative (automate backups), or that
cannot be made without ASCII config files (a tree structure to see
settings for all programs, swap them quickly for testing purposes)
And, "paste blocks", well, may be you could rethink it and get a
bit more specific.
Best regards
---Rafa
Subscribe/Unsubscribe: open-request@amiga.com
Amiga FAQ: http://www.amiga.com/faq.html