From: "James C. Sewell" 
@Date: Sat, 25 Jan 2003 13:16:10 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au


Sammy and all,
   I just had a new angle on this come to mind.

   If we are looking at ways to keep the .ui file virginal so that Sammy 
can rearrange it at will without breaking our editors...
   and if we are using our own macro files in most cases anyway...

   Why have the UI exposed at all (except maybe for instructional 
value)?  Should Sammy just make the UI read-only so we can see how he does 
things and then just add an official hook like   "USER.UI will be loaded 
after TSE.UI if it exists in the proper directory"  or say that we have to 
use autoload macros and keep night-night and keep day-day?

   We are used to the UI being the User Interface and totally open to 
configuration, but maybe it should be a "DEFAULT.UI" and
"AUX.UI" or 
"USER.UI" to avoid the whole problem.  After all, the other programs do it 
and don't even show us how they operate so we can learn from it.

Just a new perspective, comments?
   Jim

Jim Sewell Computing Solutions
Key West, Florida, USA

Visit these great sites:
         Covenant" target="new">http://www.covenantwordchurch.org/>Covenant Word Church
         Lighthouse" target="new">http://www.lcachildcare.com/>Lighthouse Christian Academy
        
Hideawayhttp://www.hideawaykeywest.com/>Hideaway;

Cottages - your new home in Key West
         Ultra" target="new">http://www.grandslamkw.com/>Ultra Grand Slam - the most fun 
you'll ever have fishing for the "big ones".



--
TSEPro mailing list



---
[sawasdi.apana.org.au] (3:800/846.13)