You did mention 'Tango' but you didn't specify which version so I'll guess that it is Tango 2000 or higher.
Whenever possible, I try to put similar functions in one taf file, rather than two. I have actions in many tafs where the complete Results Attribute (or Results Action) is enclosed in an <@IF...> <@ELSE> </@IF> block. It's a trick that I saw first with the old Bank of Montreal stuff to handle English/French. It makes it easier for development work because I know that if a change is made in one block of the code, it is usually required in the other block as well. An alternative that I've used more often in recent development work is the use of TCFs. By structuring the methods in the TCFs, and passing the right parameters from the calling TAF, you can acheive the same result with only one set of TAFs. There are many problems with the use of branching, the biggest one is that the names of the destination actions are hard-coded. Also the rule of not branching to anything but a top-level must be followed which can sometimes throw you if you try to change the destination TAF. At first glance of the description that you've given us, it looks like you've duplicated many of the actions which is something you'll want to avoid. Hope this helps, Steve Smith Oakbridge Information Solutions Office: (519) 624-4388 GTA: (416) 606-3885 Fax: (519) 624-3353 Cell: (416) 606-3885 Email: [EMAIL PROTECTED] Web: http://www.oakbridge.ca > -----Original Message----- > From: Nicholas Froome [mailto:[EMAIL PROTECTED] > Sent: May 27, 2003 11:42 AM > To: [EMAIL PROTECTED] > Subject: Witango-Talk: Branching with LocalHeader tip > > > This may seem incredibly obvious and straightforward for the > experts out there, but bear with me - it was a major step forward > for my Tango development! > > > > When developing a Cars for Sale TAF I was having problems keeping > track of which functions required user Login, and which not, so I > split it into two TAFs - advert.taf to place ads, and > marketplace.taf to view them > > Simple enough. But I wanted to share a design and popup menu > system between them - which I couldn't do if the Popup options > spanned two TAFs > > So what I did was to share the popup (as a variable) and to > create results pages for all options (Search, Cars for Sale, etc) > in both TAF files. For the options that needed to call the other > TAF, I put an HTTP redirect to the other TAF in the results page, eg: > > <@ASSIGN NAME=Local$httpHeader VALUE="HTTP/1.0 302 > Moved<@CRLF>Location: > http://www.bolide.co.uk/actions/advert.taf?page=<@ARG > page><@CRLF><@CRLF>"> > > This means all menu options work in both TAFs, they can share a > navigation system and I don't have to duplicate functionality > > > > Any comments or simpler ways of doing this? > > > > > Bolide Marketplace > http://www.bolide.co.uk/marketplace > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
