Zope
  Home arrow Zope arrow Page 8 - DTML Basics (part 2)
Dev Shed Forums 
Administration  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Forums Sitemap 
IBM® developerWorks 
Dedicated Servers 
E-Commerce Hosting 
Linux Web Hosting 
Managed Hosting 
Small Business Hosting 
Download TestComplete 
VPS Hosting 
Weekly Newsletter

 
Developer Updates  
Free Website Content 
IBM Developerworks
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
ZOPE

DTML Basics (part 2)
By: Harish Kamath, (c) Melonfire
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 4
    2002-06-05

    Table of Contents:
  • DTML Basics (part 2)
  • If Only...
  • Comparing Apples And Oranges
  • Welcome To The Matrix
  • Celluloid Dreams
  • Paring It Down
  • Deeper And Deeper
  • Submitting To The King

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
     
    ADVERTISEMENT

    Dell PowerEdge Servers

    DTML Basics (part 2) - Submitting To The King
    (Page 8 of 8 )

    You'll have noticed that in all the examples shown thus far, we've usedtwo Zope objects - a single DTML Document containing the form, and aseparate DTML Method which processes the form input and generatesappropriate output. However, DTML provides an elegant method to combinethose two pages into one via the "submit" variable.

    In order to better understand this, create a new DTML Document named"DualPurposeForm" and add the following DTML code to it:

    <dtml-var standard_html_header>

    <dtml-if submit>

    Welcome to Earth, <b><dtml-var species missing="Alien"></b> from the
    planet <b><dtml-var planet missing="Zorgo"></b>.
    <p>
    How was your journey? Travelling <b><dtml-var distance missing="so
    many"></b> light years must be quite a shock to the system. Why don't
    you relax and have a drink?

    <dtml-else submit>

    <form action="DualPurposeForm" method="POST">
    Species:
    <br>
    <input name="species">
    <p>
    Home planet:
    <br>
    <input name="planet">
    <p>
    Distance (light years) from Earth:
    <br>
    <input name="distance">
    <p>
    <input type="Submit" name="submit" value="Beam Me Up, Scotty"> </form>

    </dtml-if>

    <dtml-var standard_html_footer>
    In this case, the DTML "if" test will first check to see if the "submit"form variable exists. If it does, it implies that the form has beensubmitted, and the second half of the script, the actual form processor,comes into play. If it doesn't, it implies that the form has not yetbeen submitted, and so the initial, empty form is displayed.

    This technique makes it possible to reduce the number of objects used,and perhaps make your Zope object collection easier to handle.

    And that's about it for the moment. In this article, you learnt a littlemore about DTML, specifically about how to introduce decision-makinglogic into your Methods with DTML's numerous conditional statements. Youlearnt about the "if" and "unless" series of conditional statements, andsaw a few examples of the different variants possible. Finally, you sawhow all that theory can be put to practical use by implementing a simpleform processor for use on a Web page.

    In the next issue of DTML Basics, I'll be rounding out the fundamentalswith a look at the various loop constructs provided by DTML. As witheverything you've seen so far, DTML comes with its own twist (pardon thepun) on the traditional way of implementing loops. Come back next timeto see what I'm talking about...and, until then, go practise.

    Note: All examples in this article have been tested on Linux/i586 withZope 2.5.0. Examples are illustrative only, and are not meant for aproduction environment. Melonfire provides no warranties or support forthe source code described in this article. YMMV!
    DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

     

       

    ZOPE ARTICLES

    - Creating Zope Products
    - Plone Content Types With Archetypes
    - Flat User Management in Zope
    - Creating Basic Zope Applications
    - Getting started with Zope for Linux and Sola...
    - ZPT Basics (part 4)
    - ZPT Basics (part 3)
    - ZPT Basics (part 2)
    - ZPT Basics (part 1)
    - Exception Handling In DTML
    - DTML Basics (part 4)
    - DTML Basics (part 3)
    - DTML Basics (part 2)
    - DTML Basics (part 1)
    - Using Zope With Apache

     
    Accelerating Trading Partner Performance
     
    Competing on Analytics
     
    Cost Effective Scaling with Virtualization and Coyote Point Systems
     
    Five Checkpoints to Implementing IP Telephony
     
    Hosted Email Security: Staying Ahead of New Threats
     




    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 2 hosted by Hostway