Date: Fri, 23 Mar 2007 19:43:59 -0400
From: DAVE GOURD
To: All
Subject: the new template\custom folder
Newsgroups: winserver.public.gamma.testing
Message-ID: <1174697039.40.0@winserver.com>
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 25

I more or less understand that http requests override dupe files in the \template dir to use those same filenames in \template\custom if they exist, so is it correct to assume we do NOT have to address those \custom files directly?

i.e., I have

\template\custom\somefile.ext

in my html/coding do I need to use a url of

\template\custom\somefile.ext ?

Seems to me if I do not, when I code \template\somefile.ext which is REALLY
in the template dir and not the custom sub-dir.

And confirm that this custom folder is also for AUP overwrite protection?

I keep reading the aup help files and the logic escapes me. I haven't tried coding the custom files yet, just want to be sure.


--
Dave
FoxRiver.NET
--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Sat, 24 Mar 2007 02:06:53 -0400
From: HECTOR SANTOS
To: DAVE GOURD
Subject: RE: the new template\custom folder
Newsgroups: winserver.public.gamma.testing
Message-ID: <1174720013.40.1174697039@winserver.com>
References: <1174697039.40.0@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 64

On 2007-03-23 7:43 PM, DAVE GOURD wrote to All:

I more or less understand that http requests override dupe files in the \template dir to use those same filenames in \template\custom if they exist, so is it correct to assume we do NOT have to address those \custom files directly?

That is 100% correct assumption. :-)

Just code it as always. Any reference to the template folder will trigger
a check to the custom subfolder first and if not found, then it looks in
the template folder.

I guess you could be specific and go direct, hmm, maybe not, have not
tried, but I naturally say that because the WILDCAT ALIAS NAME system is
pretty tight on specfic folder that it looks for. Anything else is
considered an ACCESS violation. In other words, CUSTOM is not part of the alias name system. But TEMPLATE is, so to get to the custom folder, you
have to use TEMPLATE only first and once its inside the TEMPLATE folder, it then checks for the optional subfolder CUSTOM.

Its not a foriegn concept in Wildcat. WCBASIC applications work the same way.

WILDCAT.WCL contains the compiled binary images for all the WCX
applications and library that makes up the ANSI/TELNET and WEB client interfaces. The source code to ~150+ WCX modules is called the WCBASIC
PLUS PACK - an Add-on product to the WCBASIC compiler system.

So if you had a need to customize a specific WCX, like HTML-CREATE
MESSAGE.WCX, or anything else, then you can override the internal
WILDCAT.WCL copy of this WCX by creating a separate HTML-CREATE MESSAGE.WCX module and placing it in the same folder as WILDCAT.WCL (which is pretty
much fixed at the ROOT \WCx installation folder).

So whenever there is a request to load/run a WCX, Wildcat! will also look
for the WCX:

- as a standalone WCX, and if not found,
- check WILDCAT.WCL and use the stock image to load and run.

if not found at all, the "program module XXXXX not found" or something like that is shown.

If you wanted to completely REPLACE your ANSI/TEXT mode, just create your
own MAIN.WCX and this will become your new "BBS" We have quite a few coporate customers who have gone that far to customise thier own login
logic with highly simplified but very tight entry connection logic. Once
the user is in, they utilitze the Upload/Download and/or mail features,
etc. Among the more recent support incidences, the CIA does this with its highly secured MODEM file exchanges with very simple IN AND OUT stuff. Not
even the CIA trust the internet. Verizon has their own login logic totally bypassing the builtiin menu system 100% tied in with backend servers and mainframes FTP exchanges. Many do this simple to avoid update issues too.
Taking complete control of the interface works well for those who at that highly private need to do so. :-)

--







--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)

Date: Sat, 24 Mar 2007 19:30:21 -0400
From: DAVE GOURD
To: HECTOR SANTOS
Subject: RE: the new template\custom folder
Newsgroups: winserver.public.gamma.testing
Message-ID: <1174782621.40.1174720013@winserver.com>
References: <1174720013.40.1174697039@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 88

Ya know - I really really do have to get up with the wcbasic - wish could
find an old manual somewhere... makes me feel so inadequate when you and a couple others throw that stuff around so freely - have had it here 1yr+,
only thing have actually finished is "Hello world" and a lot of reading - confusing somewhat, and embarrassing since I used to be very proficient in BASIC programming circa. 1979, Even have ASTs in computer programming technology - machine and basic, and Comp Science and Technology (AST -
Another Stupid Technician with papers), just never went any farther and
BASIC is not BASIC anymore - no line numbers, and who uses machine language anymore? HaHa. 8(

I played with the template\custom a bit this morning. Yes, you can hard
code the \custom or not. I can see possible issues without having to hard
code it (maybe you want 2 versions of something), but understand and desire
it as is now. This would work for AUP's and for the sysop or
designer/author. I vote leave it alone now.

Maybe though, expand that to files under \public which are subject to AUP,
i.e. the \graphics folder, (I use \images for my stuff, leave \graphics for
wc defaults/aup), the default template files (login.wct, printloginform, etc.).

--
D



On 2007-03-24 2:06 AM, HECTOR SANTOS wrote to DAVE GOURD:

On 2007-03-23 7:43 PM, DAVE GOURD wrote to All:

I more or less understand that http requests override dupe files in the \template dir to use those same filenames in \template\custom if they

exist,

so is it correct to assume we do NOT have to address those \custom files directly?

That is 100% correct assumption. :-)

Just code it as always. Any reference to the template folder will trigger
a check to the custom subfolder first and if not found, then it looks in
the template folder.

I guess you could be specific and go direct, hmm, maybe not, have not
tried, but I naturally say that because the WILDCAT ALIAS NAME system is pretty tight on specfic folder that it looks for. Anything else is considered an ACCESS violation. In other words, CUSTOM is not part of the alias name system. But TEMPLATE is, so to get to the custom folder, you
have to use TEMPLATE only first and once its inside the TEMPLATE folder, it then checks for the optional subfolder CUSTOM.

Its not a foriegn concept in Wildcat. WCBASIC applications work the

same way.

WILDCAT.WCL contains the compiled binary images for all the WCX
applications and library that makes up the ANSI/TELNET and WEB client interfaces. The source code to ~150+ WCX modules is called the WCBASIC PLUS PACK - an Add-on product to the WCBASIC compiler system.

So if you had a need to customize a specific WCX, like HTML-CREATE MESSAGE.WCX, or anything else, then you can override the internal WILDCAT.WCL copy of this WCX by creating a separate HTML-CREATE MESSAGE.WCX module and placing it in the same folder as WILDCAT.WCL (which is pretty much fixed at the ROOT \WCx installation folder).

So whenever there is a request to load/run a WCX, Wildcat! will also look for the WCX:

- as a standalone WCX, and if not found,
- check WILDCAT.WCL and use the stock image to load and run.

if not found at all, the "program module XXXXX not found" or something like that is shown.

If you wanted to completely REPLACE your ANSI/TEXT mode, just create your own MAIN.WCX and this will become your new "BBS" We have quite a few coporate customers who have gone that far to customise thier own login
logic with highly simplified but very tight entry connection logic. Once
the user is in, they utilitze the Upload/Download and/or mail features,
etc. Among the more recent support incidences, the CIA does this with its highly secured MODEM file exchanges with very simple IN AND OUT stuff. Not even the CIA trust the internet. Verizon has their own login logic totally bypassing the builtiin menu system 100% tied in with backend servers and mainframes FTP exchanges. Many do this simple to avoid update issues too.
Taking complete control of the interface works well for those who at that highly private need to do so. :-)

--

--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)