From: Fred Holmes 
@Date: Sat, 25 Jan 2003 14:48:54 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au



I don't think all of us are worried about keeping tse.ui virgin.  Let those 
who want to mess with it do so.  Until we solve the issue of making all of 
the procedures in tse.ui public, there are some things that are a quick 
change of a few characters on one line in tse.ui, but require extracting 
several called procedures to a macro that is outside of tse.ui. Changing 
the format/content of the text in the Windows title bar is one of them.

But for those who don't like having to mess with tse.ui for each/every 
upgrade/beta/change of whatever sort, there needs to be a way of avoiding 
it -- which there is.  The method perhaps isn't so obvious from a casual 
perusal of the documentation -- hence the need for this 
forum.  #include.  Autoload Macro.  Append code to tse.ui without modifying 
the virgin code internally. . . .

There are so many different ways of approaching it that it's hard to decide 
-- so what else is new with SAL?

The other issue is how to find out what copy of tse.ui is the current 
virgin copy.  Sometimes an upgrade/patch involves a change to tse.ui, 
sometimes not.  I'm personally confused on that at the moment, but can 
probably figure it out from my archives.

Fred Holmes

At 01:16 PM 1/25/2003, James C. Sewell wrote:
>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

--
TSEPro mailing list



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