| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | [TSEPro] Re: Keeping tse.ui virgin |
From: "James C. Sewell"
@Date: Sat, 25 Jan 2003 16:57:25 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au
Question:
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?
For example, with the concepts of overwriting I have seen a lot of lately
in VB.NET and the "pass a pointer to a function so I can call it" aspects
of C / C++ I remember from years ago it _may_ be easy for Sammy to allow
something like:
MyGetFunctionStr
Function here
End Function
Register GetFunctionStr, MyGetFunctionStr
to replace the default one without making the UI into a hard to maintain
customized file that gets trashed on the next version release and causes us
to have to go in and reinstate our changes every time.
I don't think anyone would want to make their tool harder to maintain than
necessary, but I'm not sure this is the best solution. (But of course it
seems pretty good to me ).
Simply food for thought,
Jim
At 11:55 AM 1/25/2003 -0800, you wrote:
>I like being able to edit the file because I change some things.
>Particularly, I change the startup, main and file menus, add grep strings
>for the view functions mechanism and edit GetFunctionStr and OnChangingFiles
>to allow for other languages and extensions tse doesn't otherwise expect.
--
Jim Sewell Computing Solutions
Key West, Florida, USA
--
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™.