Tabi, I think it would be very useful for you in regards to this topic to review the work that Ritchie Carroll did in the StoreFront demo which came as a demo with Tango 2000. The way he separates logic and presentation is illuminating, his use of tcf and objects and variables to provide an immense level of functionality from a small amount of code. It provides a very good basis on which to design future apps.
cheers Garth At 08:42 24/09/02, you wrote: >Thanks Greatly for your input on this matter. > >I totally understand taf file functioning sort of >.tcf because right now I do the same. >I will explore more on presentation action and .tcf. > >I currently use branch action to branch to each taf >file (I have condensed to do one task) and so >therefore >my application is mostly consisted of branch action >if else action, and html results that mostly contain >varibale and @include file calls.. > >I want to create or construct an assignment statement >that will recognize a relative path from the webroot >of the webserver so regardless of a different >directory structure from my development environment to > >live production my branch-action and all my relative >path references will work properly. > >I hope this is the right direction, any comments.. > >Thank you Chris Smith and the list, > >Tabi Run > > > > > >***************************************************** > > > > > >--- Chris Smith <[EMAIL PROTECTED]> wrote: > > Here is the way I organize my work around Witango to > > implement what I > > consider to be object oriented. I began doing this > > prior to the > > implementation of Presentation Actions Witch Help > > even more to make > > separation of business logic, presentation and data > > more of an attainable > > model. > > So here goes: > > > > I use 1 taf as if it were a class object so for > > instance lets take something > > like users and providing 1 sharable/reusable set of > > code to call to interact > > with this class called users. I then in witango > > studiobuild the outer > > application tree for the class, which would be > > comparable to methods, with > > some kind of ifelse decision tree. > > IF <@arg _method> = memberServices > > if <@arg _mod>=manageAccount > > <@arg _function>=listAccountProfile > > <@arg _function>=updateAccountProfile > > elseif<@arg _mod>=manageOrders > > <@arg _function>=searchOrders > > <@arg _function>=viewCurrentOrders > > <@arg _function>=viewUnbalancedOrders > > else ERROR > > ELSEIF <@arg _method> = userAdmin > > Then another tree as above however custom to the > > functionality of user admin > > add a user, update the profile etc.... > > ELSEIF <@arg _method> = userAdmin > > > > > > the standard I use is _method for the outer most IF > > _mod (for module) for each module of the class, most > > often you find these > > break down along the lines of oop concept of public, > > private and protected > > methods > > _function for the underlying function that is to be > > preformed. > > > > so at the very least a URL string must contain all > > of these args or else the > > app will error. > > > > The next step is what to you do inside the function. > > In the past I either > > placed custom business logic or a builder in place > > at that level, the trick > > here is not to cross the line and begin using > > results or accumulated results > > to display the html output to your users but rather > > as I did in the past use > > the results to interpret some piece of data returned > > in an if/else decision > > tree that determined which presentation file to > > include. > > > > Since I'm recently new to the 4.5 Witango editor and > > have been slogging > > along for years with my old tried and true version > > 3.52 the implementation > > of presentation actions is a great addition. I've > > been experimenting with > > these and they work great and if you can keep your > > cursor out of the results > > editor you stand a chance of not placing > > presentation in the taf object. > > > > I would even like to experiment more with the tango > > class files because from > > what I see there, I have a great deal of taf that is > > doing the work of tcf. > > and could be moved there. > > > > just my spin on things, but by no means a completely > > accurate oop use of > > Witango. I've done some work with OO Design using > > Rational Rose and Visio > > UML model and have implemented some of these models > > in java(Jakarata and > > Cocoon 2.0) and most recently in .Net and what I've > > found is no matter which > > mouse trap you are using you must first understand > > the nature of the mouse > > you are trying to trap and define it. > > > > csmith > > > > > > > > ----- Original Message ----- > > From: "run run" <[EMAIL PROTECTED]> > > To: "Multiple recipients of list witango-talk" > > <[EMAIL PROTECTED]> > > Sent: Monday, September 23, 2002 5:57 PM > > Subject: Witango-Talk: witango programming style > > question. > > > > > > > > > > Hello list, > > > > > > How do you write witango files as to conform with > > > object oriented programming style? > > > > > > I would appreciate your input on this matter. > > > > > > thanks, > > > > > > tabi run > > > > > > __________________________________________________ > > > Do you Yahoo!? > > > New DSL Internet Access from SBC & Yahoo! > > > http://sbc.yahoo.com > > > > > >________________________________________________________________________ > > > 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 > > >__________________________________________________ >Do you Yahoo!? >New DSL Internet Access from SBC & Yahoo! >http://sbc.yahoo.com >________________________________________________________________________ >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
