| From: | Harold Grovesteen |
| Date: | 20 Sep 2000 at 12:28:51 |
| Subject: | Re: AMIOPEN: GUI Standardization |
Java can do most of these things with some measure of programming ease.
The properties files are textual and can contain anything. They can
then be read to create property objects within the program which can
then be serialized out to a file. Funtions exist to easily extract
information from this source. It would be interesting if Ami were using
Java for some of the new things we see hints of in this list.
Today all I see are ports of Unix stuff, turning the new Amiga
environment into a Unix clone. From a developers standpoint that may be
OK. I realize we have to bootstrap from somewhere and familiar tools
are helpful to those who are familiar with them. Many of the things
discussed here have been addressed and are being addressed by the Java
community with Swing/AWT, although I gathere there are some issues for
Ami providing this support. There is even a company that just provides
Java support for various languages, which is a hugely complex arena when
discussing languages using scripts other than the Latin derived ones.
Even here there are issues such as the keyboard differences I have been
seeing discussed.
Some of what I see is reinventing the wheel. Graphics support in Java
might solve a lot of that. It might not be the answer for some of the
highpowered gaming folks, but for many other applications it has much to
offer. Borrowing some of the ideas may also work. Even without the
graphics support in Java, other features may be useful to the cause. We
have not scratched the surface yet of what Java can contribute to the
new Amiga.
Harold Grovesteen
Jim Peters wrote:
>
> On Wed, Sep 20, 2000 at 08:30:52AM +0200, Juan Carlos Marcos Rodr�guez wrote:
> > 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?
>
> There may be some elements here in common with the `no-files' approach
> of the as-yet-unseen Amiverse object world thing. Everything
> (including settings) is an object, which gets stored somehow or other
> - we don't care how, so long as it looks the same next time we see it.
> Presumably the desktop is the interface to these objects (your COFEE
> editor), and there will be hundreds of helpful tools to let you change
> things.
>
> Possible, maybe ? We'll have to wait and see.
>
> Jim
>
> --
> Jim Peters / __ | \ Aguazul
> / /| /| )| /| / )|| \
> jim@aguazul. \ (_|(_|(_|(_| )(_|I / www.aguazul.
> demon.co.uk \ ._) _/ / demon.co.uk
> Subscribe/Unsubscribe: open-request@amiga.com
> Amiga FAQ: http://www.amiga.com/faq.html
Subscribe/Unsubscribe: open-request@amiga.com
Amiga FAQ: http://www.amiga.com/faq.html