Hey Dude, I might be going out on a limb, but maybe this is what you were looking for:
http://xml-extra.net/webpage.xmlx?node=84 This was of my own doing - but With has not objected to it's existence. I've used the "XML" tactic ever since T2K came out and has helped more than hindered me. It's one think to get a blank stare from a customer - but it's another to get a blank stare from another developer :-} As for 3rd party product integration - it is quoted in the Pervasive Documentation that one of the "advantages" of the XML format is so that other products (and Server processes) could be used to write a TAF or TCF dynamically. Which can get a person to thinking..... Hope this helps. Cheers.... Scott Cadillac VP, Research and Development Plus International Corp. 403-281-6090 [EMAIL PROTECTED] http://www.plusinternational.com Does your company have an Enterprise Information Portal? Check out Salsa at www.plusinternational.com/flash/salsa.htm ----- Original Message ----- From: "John McGowan" <[EMAIL PROTECTED]> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> Sent: Friday, January 10, 2003 7:25 AM Subject: Re: Witango-Talk: What to call it > Dude, > > I believe the term they're all throwing around is "XML Execution Engine" > > Personally I think the term sucks. "ASCII Execution Engine" would be > just as descriptive. These types of deceptive tactics will only slow > the growth and popularity of Witango. People need to know what we're > using, *and why* so they tell all their friends about it. > > I would never use that term, because I'd feel silly if it made it's way > to someone who knows what they're talking about, someone who understands > how proprietary Witango really is. The usage of XML in the saved file > format is no more usefull than the fact that it's in ASCII. Especially > when you consider the changes that With made to the license agreement. > I can't find a copy of the agreement right now, but I'm pretty sure it > states that you aren't allowed to use the XML generated by the dev > studio for anything but running on the app server, or editing with the > dev studio. Which makes using things like JT a violation of the license > agreement. So, ASCII, Binary, XML, Hindu, It really doesn't matter > what format the taf and tcf files are saved in. > > The only good thing about the file format is that you can open it up in > notepad to fix a problem when the dev studio decides to corrupt it for > you... I'd better check the license agreement about using that third > party tool with the source code though. ;) > > /John > > P.S. I'm not trying to start any kind of flame war here... Those of you > that met me at the developers conference already know how I feel about > this issue. I already know I'm alone on this, and don't need to be > reminded... > > > Web Dude wrote: > > > I saw this somewhere on the list before but can't seem to find it now. > > > > I have a perspective client I have been trying to land for the last > > month. It is looking good, but they are asking for a list of > > development tools that will be used in the project. I am worried that > > stating I use Witango, will give me the blank stare I have seen from > > other perpective clients I have tried to woo. > > > > Someone on the list in the past came up with an excellent short > > explanation of what Witango is or does using the word XML which is > > definitely a buzzword these days. > > > > I need some good examples of what to tell this client so I can have a > > good shot at the deal. Any ideas???? > > > > Thanks! > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
