Re: The Guru Speaks-Is That Really the Only Manuel?

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 20209
interpreted = N
texte = Is there a limit to the physical size of the webpages products are displayed on in order for WebCat to function?No. WebCatalog's whole purpose in life is to help you make HTML. Believe it or not, pictures have absolutely nothing to do with WebCatalog -- except that sometimes you store some text in a database field that happens to be the *name* of a picture file somewhere (maybe on your server, maybe a URL leading somewhere else). But in the end, all WebCatalog does is squirt out some HTML that a browser then interprets and the browser decides to go grab pictures from the web server. I have larger graphics with many products displayed on them with the Buy now and product info next to where the product is on the page. Will WebCat work this way? In the manuel it seems like its designed to work with a separate graphic (or no graphic at all) per product.It's entirely up to you. We provide some examples, but you can always add more fields to your database that contain other picture names, and you can always change the templates to make them look like anything. I have sites I've designed with softwares such as Adobe PageMill, Adobe ImageReady, Dreamweaver, Photoshop etc. I had thought that Webcat could run on top of Webten and beneath the pages I'd made, so to speak. Does it work in this way? And if so, where do I find info on how to tie it in?You may do your initial layouts with those packages, but once you've done that you need to get in there with a text editor like BBEdit and tweak the HTML by hand. Graphical editors always hide too much of the WebDNA (or worse, chew it up) so you never get a real picture of what's going on under the hood.If there are sources for basic newbie and really starting to panic here type questions I am used to studying like mad till I get up to speed but . . .Have you gone thru the TeaRoom tutorial in the manual? I recommend you do the following: visit each page in the TeaRoom and do a View Source in your browser, then compare that to the actual raw template which shows the WebDNA. Notice how the WebDNA is replaced by plain HTML. While the TeaRoom is not the most sophisticated site in the world, it provides a *basic* understand of the possible flow of a selling site.I'd also look at the GeneralStore and do the same thing. Anywhere you want an extra picture, go look at the original WebDNA template and look at how the first picture was put there, then extrapolate from there. That may mean you have to edit the database file to add another column which contains the field name you want for your picture.I think the basic concept you're going to learn is that all WebDNA things are done in raw HTML using a plain text editor, rather than one of those graphical tools. You've got to get your hands dirty and start typing those WebDNA [xxx] things into the text of the file. I'd start by trying to get the GeneralStore as close to looking like your final site as possible (even if it's limited by not having your extra pictures and stuff), and then go back and start adding features. You have to start small and work your way up. Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: The Guru Speaks-Is That Really the Only Manuel? (PCS Technical Support 1998)
  2. Re: The Guru Speaks-Is That Really the Only Manuel? (Kenneth Grome 1998)
  3. Re: The Guru Speaks-Is That Really the Only Manuel? (Susie 1998)
Is there a limit to the physical size of the webpages products are displayed on in order for WebCat to function?No. WebCatalog's whole purpose in life is to help you make HTML. Believe it or not, pictures have absolutely nothing to do with WebCatalog -- except that sometimes you store some text in a database field that happens to be the *name* of a picture file somewhere (maybe on your server, maybe a URL leading somewhere else). But in the end, all WebCatalog does is squirt out some HTML that a browser then interprets and the browser decides to go grab pictures from the web server. I have larger graphics with many products displayed on them with the Buy now and product info next to where the product is on the page. Will WebCat work this way? In the manuel it seems like its designed to work with a separate graphic (or no graphic at all) per product.It's entirely up to you. We provide some examples, but you can always add more fields to your database that contain other picture names, and you can always change the templates to make them look like anything. I have sites I've designed with softwares such as Adobe PageMill, Adobe ImageReady, Dreamweaver, Photoshop etc. I had thought that Webcat could run on top of Webten and beneath the pages I'd made, so to speak. Does it work in this way? And if so, where do I find info on how to tie it in?You may do your initial layouts with those packages, but once you've done that you need to get in there with a text editor like BBEdit and tweak the HTML by hand. Graphical editors always hide too much of the WebDNA (or worse, chew it up) so you never get a real picture of what's going on under the hood.If there are sources for basic newbie and really starting to panic here type questions I am used to studying like mad till I get up to speed but . . .Have you gone thru the TeaRoom tutorial in the manual? I recommend you do the following: visit each page in the TeaRoom and do a View Source in your browser, then compare that to the actual raw template which shows the WebDNA. Notice how the WebDNA is replaced by plain HTML. While the TeaRoom is not the most sophisticated site in the world, it provides a *basic* understand of the possible flow of a selling site.I'd also look at the GeneralStore and do the same thing. Anywhere you want an extra picture, go look at the original WebDNA template and look at how the first picture was put there, then extrapolate from there. That may mean you have to edit the database file to add another column which contains the field name you want for your picture.I think the basic concept you're going to learn is that all WebDNA things are done in raw HTML using a plain text editor, rather than one of those graphical tools. You've got to get your hands dirty and start typing those WebDNA [xxx] things into the text of the file. I'd start by trying to get the GeneralStore as close to looking like your final site as possible (even if it's limited by not having your extra pictures and stuff), and then go back and start adding features. You have to start small and work your way up. Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ PCS Technical Support

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:

appleshare/ip (1997) Rhapsody? (1997) Separate SSL Server (1997) WebCat2 - Getting to the browser's username/password data (1997) Three new problems, maybe a fourth (1997) Does this still work (2006) Format of Required fields error message (1997) system crashes, event log (1997) HELP - NONE STOP DIGESTS. Digest for 4/24/97) (1997) Fun with dates (1997) Error Log.db --however (1997) [cart] not being interpreted inside [founditems] (1997) [format 40s]text[/format] doesn't work (1997) Nav. 4 probs with cart - Serious problem (1997) Multiple Newcarts (1996) Maybe minor bug report (1997) Running _every_ page through WebCat-error.html (1997) Reversed words (1997) WebCat cannot handle compatible search parameters? (1997) Is this google friendly? (2003)