Re: Witango-Talk: Witango Talk - Include Meta Tag - Sharing .tafs in multiple sights without recopying it

[Atrix Wolfe]

well...yeah you have a couple options as i see it...   1 idea is you could store various switches and settings in the database which are loaded when the page is to be displayed and there are if's and such to handle these.  If there arent a whole lot of differences and the differences are simple, this would be a good one.   Another option is getting a hold of the <@query> tag from Ben Johansen's site (dont know the link sorry) and with that it allows you to do database actions with a metatag.  This way you could <@include> witango functionality, but they would have to be a html file with metatags in it.   And a third option would be to store the dynamic code in the database.  Lets say you stored this in the database:   <h1>10 input boxes</h1> <@for stop=10>   <@currow>:<input type=text name=input<@currow> value=""> </for>   you could select it from the database, store it in local$Code and then wherever you wanted this code in your file you could do this:   <@var local$Code encoding=METAHTML>   and it will evaluate it just as if that was part of your code!  An advantage over this method would be that you could make changes to your code without having to re-upload a file.  You could also still get the <@query> tag and then in your custom code stored in the database youd be able to make database calls as well.   ----- Original Message ----- From: Gerard To: Multiple recipients of list witango-talk Sent: Friday, December 20, 2002 9:56 AM Subject: Witango-Talk: Witango Talk - Include Meta Tag - Sharing .tafs in multiple sights without recopying it Hello,   I am presently working on a project, that would be greatly simplified by performing what I will describe below.   Situation: We are developing web sites, that will be owned by different companies, using the exact same .taf, each having their own database.  The variables within the .taf will allow them to have their own personalized look, and distinct information.  To state the obvious, much of the sites info and appearance is dynamic.  In the long term, there will be thousands of sites sharing an identical .taf.  Each time we make a change, we will be forced to copy the modified .taf into each and every site.  We will have enough of a challenge making changes, if a change requires that we add / modify a column to their database.   Problem: During testing, I referenced a .taf that was working perfectly, in it's own folder, from a .taf in another folder, with the <@include file="displayTAF.taf"> tag, within a "Results" field.  The result that I got was:       first,  A header that said "Form Page" that I could not find with a "Find" search     second, SQL info, in simple English, as acronyms.     followed by, all the pages of the .taf, separated by "]]>" at the beginning and the end of each.   I then added the "_function" call, to specify a page, but got no results, at all.   My Question: Is there a way for us to make a change to one page, where all the different web sites will benefit from the changes, shy of putting "<@INCLUDE file="">, everywhere on there site.  Realizing that this will only work for simple changes, and useless if structural changes are made.   Thank you, Gerard