Re: Two submit buttons ?

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 11021
interpreted = N
texte = >Now the customer edits the quantity field. If the shopper decides to do >more shopping (Yay !) and goes back to the search page, then the quantity >edits aren't captured. If the shopper proceeds to the checkout, then the >edits are captured.HTML sucks. But given that we can't get around that (short of Java), there are a couple ways around this user-interface dilemma.1) Put an update quantity button next to each individual lineitem. That means a whole
per lineitem. When the user changes that quantity, the click the update button and it repaints.2) Use a graphic for the submit button. Graphical submit buttons automatically add x=12&y=7 coordinates to the form. So if your graphic LOOKS like 2 buttons next to each other, you can use the x,y information in the WebDNA to see which 'virtual' button was pressed, and act accordingly. I've never tried this, but it seems like it would work.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court, #453 | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

    
  1. Re: Two submit buttons ? (Grant Hulbert 1997)
  2. Two submit buttons ? (Sven U. Grenander 1997)
>Now the customer edits the quantity field. If the shopper decides to do >more shopping (Yay !) and goes back to the search page, then the quantity >edits aren't captured. If the shopper proceeds to the checkout, then the >edits are captured.HTML sucks. But given that we can't get around that (short of Java), there are a couple ways around this user-interface dilemma.1) Put an update quantity button next to each individual lineitem. That means a whole per lineitem. When the user changes that quantity, the click the update button and it repaints.2) Use a graphic for the submit button. Graphical submit buttons automatically add x=12&y=7 coordinates to the form. So if your graphic LOOKS like 2 buttons next to each other, you can use the x,y information in the WebDNA to see which 'virtual' button was pressed, and act accordingly. I've never tried this, but it seems like it would work.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court, #453 | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com Grant Hulbert

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Aquick question about replace (1999) linetiems in thankyou.tpl (1997) WebCat2b12 forgets serial # (1997) Re2: frames & carts (1997) Protect (1997) Final Receipt (1999) [TCPConnect] questions/problems (2001) WebCatalog can't find database (1997) Urgent WebCatalog problem (2000) Bad Code Contest (2007) splitting numbers in webDNA? (1997) nested showif? (1998) best way to limit # of attempts to login to protected page? (2000) SiteEdit Pro Update Announcement (1997) More on the email templates (1997) WCf2 and nested tags (1997) About WebDNA (2006) includes (2003) WebCat2 Append problem (B14Macacgi) (1997) WebDNA on RedHat ES 4 (2007)