THanks! So basically with a nested if action, you have to pass two parameters, one for the "parent" if action, and one for the embedded. That clarifies a lot.
John On Sunday, May 26, 2002, at 05:53 AM, Robert Garcia wrote: > When you create a builder app, it uses the "_function" argument to > determine > which "action" to process. To do multiple levels of actions, if I > understand > you, you must add another argument for each level. For this example, use > "_condition". Let assume this is a file to maintain your video > collection. > > IF _condition=VHS > IF _function=sform > ELSEIF _function=list > ELSEIF _function=detail > ELSEIF _function=upate > ELSEIF _function=delete > ELSE Error. <--Not necessary > ELSEIF _condition=DVD > IF _function=sform > ELSEIF _function=list > ELSEIF _function=detail > ELSEIF _function=upate > ELSEIF _function=delete > ELSE Error. <--Not necessary > ELSEIF _condition=LD > IF _function=sform > ELSEIF _function=list > ELSEIF _function=detail > ELSEIF _function=upate > ELSEIF _function=delete > ELSE Error. <--Not necessary > ELSE Error. <--Not necessary > RETURN > > If I want to link to VHS List, it would be: > <a > href="<@appfile>?_condition=VHS&_function=list&<@userreferenceargument>"> > > That�s it. You also have to modify all of the links in the builders to > include their respective "_condition" argument, so they work properly. > > -- > > Robert Garcia > BigHead Technology > 21053 Devonshire Suite 206 > Chatsworth, Ca 91311 > Phone 818.773.8162 > Fax 818.773.8164 > http://www.bighead.net/ > [EMAIL PROTECTED] > > >> From: John Newsom <[EMAIL PROTECTED]> >> Reply-To: [EMAIL PROTECTED] >> Date: Sat, 25 May 2002 18:52:57 -0700 >> To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]> >> Subject: Witango-Talk: builder methodology >> >> I have a really basic methodology question: whether or how to insert >> builder actions inside if actions. Take the following taf, >> >> if menu >> elseif add this >> elseif add that >> elseif search >> >> I'd like to insert a new record builder into if actions add this, add >> that, and search, but of course, the browser can't find the embedded if >> arguments created by the builder. So here's the question: >> >> should I make a new taf for each of the else if actions I want a >> builder >> for, or drag the builder if actions out to the same level as the main >> if actions, thereby have a ton of if and else if actions. I couldn't >> find a way to embed builder actions. >> >> Of course, I am also exhibiting newbieness about different basic >> approaches to creating a simple application. >> >> Thanks in advance for the anticipated list sagacity! >> >> John >> >> by the way, I will be starting a new job in June, as director of >> Technology for Lakeside School, which some of you may recognize as the >> ground zero of microsoft. I plan on introducing the school to the joys >> of Witango. >> >> ________________________________________________________________________ >> 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 > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
