scouchman2 — Mon, 01 Dec 2003 05:47:44 +0000

I have used dreamweaver for several years, it is my favorite program, simple, and great designs. Try to learn Dreamweaver quickly, and you should be able to fix your problem pretty quick. Hope that helps.

Thanks,

Chig P.
All new Buddy Icons and great jokes!!
Email: [email=Shawncouchman2@hotmail.com]Shawncouchman2@hotmail.com[/email]
AIM: scouchman2

JeevesBond — Fri, 28 Nov 2003 12:56:59 +0000

Just wanted to add something to the comment regarding stopping people from viewing your source code...

You can't, and shouldn't be able to. The pages are downloaded to the local hard drive of whoever is viewing the page, even if you stop right-clicks the user will easily be able to view the pages from their temporary Internet Files directory (or equivalent according to their browser).

As well as being ineffective, this presents usability issues: Web designers should not try to affect the way a browser works outside of users expectations, this will at best cause annoyance, and at worse mean the user will never come back.

A good web site to learn such things is http://www.alistapart.com as is http://www.zeldman.com/.

Suzanne — Mon, 09 Jun 2003 17:03:54 +0000

If you get better quality images, they should look better and display slower, unless you change how they are displayed. i.e. save the text as a transparent gif, put the background colour in the CSS, and save the side images as jpegs. Slicing up the image and removing parts that can repeat by themselves (the solid colour) will most likely help you with all aspects -- with getting the site to fit any screen resolution, with improving quality and with reducing download times.

isadmin3 — Mon, 09 Jun 2003 14:25:39 +0000

Thanks for your help Suzanne.

I'm actually looking into getting my hands on Dreamweaver and playing around with that, but I would like to fix as many of the problems with the FP site as I can so that it will stay live while I learn Dreamweaver.

About the image quality...if I get a copies of the border images that aren't as compressed would that solve my problem or will it look the same and just load slower?

Suzanne — Mon, 09 Jun 2003 14:11:26 +0000

http://www.google.com/search?q=no+right+click+javascript

Suzanne — Mon, 09 Jun 2003 14:09:29 +0000

Well, looking at the code, you can use a stylesheet with this in it:

body {
margin: 0;
padding: 0;
}

And change the widths on your tables to be 100% (within FP). That will resolve a number of issues right off the bat.

It's probably better that you put FP down now and either learn HTML properly or pick up Dreamweaver as a WSYIWYG editor. FP is highly prejudiced towards IE. Dreamweaver has a built in syntax checker that will help you find errors, and will export (when told to, of course).

However, if you choose not to, FP does have manual editing options which you can use to tweak settings as you learn.

Anyway, about the image quality -- I'm not sure why it's looking good in IE, the images are heavily compressed, which is causing artifacting, or distortion. You may want to rethink how you're achieving the design effect, perhaps using more separate images so that the table can stretch out instead of causing scroll at 800x600.

Hopefully more people will have more specific suggestions for you. You may wish to post your site to the critiques forum for more advice and help.

isadmin3 — Mon, 09 Jun 2003 14:00:48 +0000

while I'm asking....

How do you right click protect a site or make a page "read only" so no one is able to copy images off of it?

isadmin3 — Mon, 09 Jun 2003 13:59:41 +0000

Yes I did use FP version 2002 and WYSIWYG my butt!
FP has been a real pain...everything looks great in Explorer (microsoft) but when you start looking at it in other browser it's entirely different.

the url is http://www.ivettesosa.com

Any help is much appreciated.

Suzanne — Sun, 08 Jun 2003 19:39:42 +0000

1. yes, AOL compresses images -- you can change the settings, but I don't recall how -- try googling for "AOL image compression"

2. "Shared borders"? Are you using FP?

3. When you have a problem such as this, please provide an url for others to test the problem. It's easiest to troubleshoot when we can actually see the problem.