Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.os.linux.misc
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion New Project: Kool Desktop Environment. Programmers wanted!
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Daniel Ridge  
View profile  
 More options Oct 29 1996, 3:00 am
Newsgroups: comp.os.linux.misc, comp.os.linux.development.apps
From: Daniel Ridge <n...@cesdis.gsfc.nasa.gov>
Date: 1996/10/29
Subject: Re: New Project: Kool Desktop Environment. Programmers wanted!
Print | View thread | Show original | Report this message | Find messages by this author

> Such people expect to see pop-up diaglogs when they wish to configure
> their programs, they cannot, will not, be able to deal with resource
> files.

> The obvious compromise is to build a resource file reader/parser/lint/writer
> tool, and simply do not tell anybody that the resource files still exist,
> though of course this allows for installation "problems".

Honestly! You're on the right track with a resource tool for Mentally
Infirm, but Never Never Never create a tool that can import and write a
legacy human readable file but that can't tolerate the humans changing
that same file with a text editor the way they always have. There just is
never a good excuse for burning those sorts of bridges.

If you are a soul posessed with the notion of building a killer
/etc/printcap Mighty Printin' Power Tool, you had better be able to import
_any_ valid printcap file, and furthermore, if you need to change the
file, you had better preserve the formatting of the original rather than
reconstructing a whole new printcap from the internal database you created
when you read the printcap in the first place -- because the user might
have (and this is a blow to the ego of tool writers) Other Tools that
they use on those same files that extract meaning from comment fields and
the like.

Cheers,
        Dan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\___/~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   Daniel Ridge                      |   USRA  CESDIS
   Research Minion, Beowulf Project  |   Code 930.5
   email: n...@cesdis.gsfc.nasa.gov  |   Nimbus Rd., Bldg. 28, Rm. W274
   tel:   301-286-3062               |   Goddard Space Flight Center
   fax:   301-286-1777               |   Greenbelt, MD.  20771
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\_|_/~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                http://cesdis.gsfc.nasa.gov/people/newt


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google