Path: utzoo!mnetor!uunet!husc6!mailrus!ames!oliveb!amdahl!kim
From: kim@amdahl.uts.amdahl.com (Kim DeVaughn)
Newsgroups: comp.sys.amiga
Subject: Re: The Resource Problem
Message-ID: <25973@amdahl.uts.amdahl.com>
Date: 31 Mar 88 01:39:13 GMT
References: <4595@garfield.UUCP> <2442@unicus.UUCP>
Organization: Amdahl Corporation,  Sunnyvale, CA 94086
Lines: 48
Summary: and for an example (albeit a limited one), look at vt100 ...

In article <2442@unicus.UUCP>, craig@unicus.UUCP (Craig D. Hubley) writes:
> In article <4595@garfield.UUCP> john13@garfield.UUCP (John Russell) writes:
> 
> >Nothing's stopping anybody from creating resource files that look like:
> >
> >[myprog.res]
> >menu 1 is 5 items
> >	item 1 is "Open" shortcut O
> >	...
> >	item 5 is "Quit" shortcut Q
> >etc
> >
> >window background pen is 2
> >window foreground pen is 3
> >
> >window startup is
> >	position 100 50
> >	size 200 by 100
> 
> Good starting point.  Even pretty readable.  The *real* problem here is to 
> build a library of routines that make the reading of these files transparent
> and quick.

While some standards/guidelines would be nice, they aren't an absolute
necessity.  The vt100 terminal emulation and comm program has always
allowed window colors, type, etc. to be specified.  Tony added the ability
to define one's one "shortcut key" bindings in v2.7.

All you have to do is read in a config/init file, and set things to what
the *user* wants.

Perhaps not as "elegant" as a resource "hunk", but it *works*.  Now.
Today.

Only point I'm trying to make, is that if you wait for standards, etc. to
come out, you will (likely) be waiting a *long* time.  Ever notice that
most standards, etc. seldom spring full blown on a waiting audience, but
tend to evolve from "current practices", instead?

/kim


-- 
UUCP:  kim@amdahl.amdahl.com
  or:  {sun,decwrl,hplabs,pyramid,ihnp4,uunet,oliveb,cbosgd,ames}!amdahl!kim
DDD:   408-746-8462
USPS:  Amdahl Corp.  M/S 249,  1250 E. Arques Av,  Sunnyvale, CA 94086
CIS:   76535,25