Okay,
Here is what iam after, I would consider actions as object in witango application program. Therefore I want to organize actions into maybe .taf or .tcf or etc. so in my project i can call that same action (object, in this case maybe a search on employee) in other modules(action or group of actions performing the a particular task).. In other words , I want to reuse my actions instead of creating the same actions all over again in my project. I understand that witango is not a programming language but I thought may be you could organize actions to mimick oop style. This would give witango more robust application. I know you all know this, and so this is what I am asking the list for. I have started to implement and re-use action in my other pilot project but I thought maybe others here on the list has some input. I appreciate your thought and inputs (Mr.Cadillac and Mr.Gauthier) Thank you. Tabi Run --- Scott Cadillac <[EMAIL PROTECTED]> wrote: > Hi Tabi, > > This is a difficult question to answer because I > don't think Witango can be > classified as a Object Oriented Programming > language. > > The Witango 'language' consists of two dialects, so > to speak, XML and > Metatags. > > The TAF and TCF files are written and organized in > XML format, which > primarily contains the 'higher-level logic' of your > application. The > Witango XML is defined and written dynamically by > the 'Actions' you > drag-and-drop into a file using the Witango Editor - > this is an automatic > process and no knowledge of XML is required by the > developer. > > For more 'low-level' control of your application > logic and functionality, > there are Witango Metatags which allow you to code > by hand some of the more > complex capabilities of the Witango environment, as > well as set dynamic > properties of 'Actions'. > > The closest description of the Witango language that > fits in the current > market place, is that it is a 'tag' language not > un-like ColdFusion or even > Lasso, PHP, ASP and JSP - but with more capabilities > of course :-). > > I know this doesn't answer your question directly, > so maybe I'm not > understanding what you are saying exactly - is there > something in > particular you are after? Or just trying to > incorporate a particular > development style? > > > Note: Because the Witango 'language' is formatted in > XML - TAF and TCF > files can be created or modified by an external > process, or another > language environment that could be OOP compliant and > has XML support. > > Supplement: Witango Include files (INC) or TML files > are written with just > Metatags. And of course HTML and other client-side > languages (JavaScript, > etc,,,) can be typed in all file types for output. > > Hope this helps. Cheers.... > > ----- Original Message ----- > From: "run run" <[EMAIL PROTECTED]> > To: "Multiple recipients of list witango-talk" > <[EMAIL PROTECTED]> > Sent: Monday, September 23, 2002 3: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
