Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!bloom-beacon!XEROX.COM!Pabbisetty.henr
From: Pabbisetty.henr@XEROX.COM (Nagesh Pabbisetty)
Newsgroups: comp.windows.x
Subject: Re: WHITE PAPER:  Enhancing the X resource file syntax
Message-ID: <900925-095525-1085@Xerox>
Date: 25 Sep 90 16:55:03 GMT
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 46

The current resource-naming syntax is:
	MyApp*file_menu.btn1.foreground:  white
	MyApp*file_menu.btn1.background:  black
	MyApp*file_menu.btn1.borderColor: red
	....
	MyApp*file_menu.btn1.xxxx:        yyyy

Martin Brunecky proposed the following:
	MyApp*file_menu.btn1.foreground: white
      	-.background:                    black
     	-.borderColor:                   red


Using the convention I propose, the above example will be translated into:

	[MyApp*file_menu.btn1]
	foreground:  white
	background:  black
	borderColor: red
	....
	xxxx:        yyyy

PROPOSED CONVENTION
--------------------
Here, the top portion in square brackets represents the entire widget
hierarchy upto the last level. The last level items are specified in this
section. We can require successive sections to be separated by one or more
blank lines.

This way, it could force all the application defaults related to a
widget/tool to be grouped at one location in the defaults file. So, in
parsing, all that needs to be done is to search for the path (which is
enclosed in brackets) and then read all defaults until a blank line is
read.

Any comments?

- nagesh

-------------------------------------------------------------------------------
Intelnet: 8*227-5458				MaBell: (716)427-5458
Pup	: Pabbisetty.henr			Snail Mail: 
NS	: Pabbisetty:Henr801C:xerox		  801-27C, 1350 Jefferson Road,
Arpa	: pabbiset@arisia.xerox.com		  Rochester, NY 14623.

-------------------------------------------------------------------------------