| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | [TSEPro] Re: Keeping tse.ui virgin |
From: "Sammy Mitchell"
@Date: Mon, 27 Jan 2003 20:55:26 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au
James Sewell wrote:
> Would it be better to allow us to edit the existing .UI
>or to make it protected with hooks or function calls to do
>what we want?
My long term goal is for the .ui file not to be required,
but, still give advanced users the ability to do anything
they can now.
Basically, I'd like the editor to have a default .ui
built-in. But users could (easily, with a nice
understandable syntax) override anything they want to.
I've got it all worked out except the "easily" part.
As you were saying in your message, the key seems to be some
way to replace existing .ui functions in some cases, and to
augment (be called before or after) existing .ui functions
in other cases.
Of course, if I ever release a version like that, I'll
immediately leave for a 6 month sabbatical, 'cause I don't
think I'll be able to stand the heat!
--
Sammy Mitchell
--
TSEPro mailing list
---
[sawasdi.apana.org.au] (3:800/846.13)
* Origin: apana>>>>>fidonetSEEN-BY: 633/267 270 @PATH: 800/846 1 640/954 774/605 123/500 106/1 379/1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.