Rauhnee wrote:
> The way the page is designed, you open that title graphic in a graphic
> program and resize it to 650-700 pixles max.

I'd make it a max of 600 pixels width so that people who don't maximize their
windows or who have a resolution of 640x480 will still see the entire title
graphic.

Okay, let's see, Lisa...

[P ALIGN=Center][EMBED autostart="true" hidden="true" SRC="media/hey hey.mp3"]

While I surf on a computer that doesn't have sound (on purpose, because I'm
usually watching TV or listening to MP3s on my other computer), for those who
don't *please* be kind and make that music optional.  Instead of having it start
automatically, put the play/stop/volume thingie on the page and "click play to
hear a great song!"  Music can crash browsers and computers and few people come
back to a site that forces them to reboot.  And think of your fellow fans who
are are work, surfing at lunch or on a break and you've just announced to the
entire office that they're playing on the net.

// (C) 2000 www.CodeLifter.com
// http://www.codelifter.com
// Free for all users, but leave in this  header
// NS4-6,IE4-6
// Fade effect only in IE; degrades gracefully

This does work in N4, but your first pic:

[td width="77%"][img
src="../Noodle%20Site/New%20%20Colin%20Site/orangejacket.jpg" name='SlideShow'
width=261 height=207][/td]

isn't in the location specified.  I think you need to change the url to
"pics/orangejacket.jpg" like you have in the script.  That url looks like a
folder on your hard drive or something.

What are all these for?

[div align="center"] [/div]
[div align="center"] [/div]
[div align="center"] [/div]
[div align="center"] [/div]
[div align="center"] [/div]
[div align="center"][/div]
[div align="center"] [/div]
[div align="center"] [/div]
[div align="center"] [/div]
[div align="center"] [/div]
[div align="center"] [/div]
[div align="center"] [/div]
[div align="center"] [/div]

I'd suggest removing any extraneous code or leaving only one if you need a
sample, waste of space, inflates your page, makes it difficult to track what's
happening and different browsers will do different things with excess code.

and then this:

[table width="51%" height="211" align="left" bordercolor="#000000"]
  [tr]
    [td width="13%"] [/td]
    [td width="87%"]
      [div align="center"]
        [table width="93%" bordercolor="#000000"]
          [tr]
            [td][img src="pics/cc5.jpg" width="418" height="288"][/td]
          [/tr]
        [/table]
      [/div]
    [/td]
  [/tr]
[/table]

oh boy!  First, avoid nesting tables unless it's necessary and it isn't
necessary here.  You have a two cell table to display one pic and you stuck the
pick inside another table in the one cell.  And it's left aligned, then you have
another table next to it.

Why not just make a simple two cell table, put the pic of Colin in the left
cell, the slide show in the right cell, center the table on the page and put
cellpadding of whatever you want to keep them slightly apart?  Like this:

(and do you realize that the black border is pretty much useless because it's
basically invisible against the mostly black background? hmm, or were you doing
that because of Netscape?  If so, see my comments further down about how to fix
Netscape and then you can remove the bordercolor.)

[div align="center"]
[table cellpadding="20" cellspacing="0" border="0"]
  [tr]
    [td width="418"][img src="pics/cc5.jpg" width="418" height="288"][/td]
    [td width="261"][img src="pics/orangejacket.jpg" name='SlideShow' width=261
height=207][/td]
  [/tr]
[/table]
[/div]

there, see how simple and light that code is?  You know, wysiwyg html editors
look great and they can help you learn how to code but they can also really
explode the code, putting all sorts of extra stuff that makes the page break or
display differently on different browsers.  It's not cheating and I used
FrontPage Express (horrid thing! :-)) when I first started, but you have to keep
an eye on the code and not let the program take over.  Read the code, play with
it, take stuff out, see what happens, simplify stuff, that's the best thing you
can do to make better pages.

[title]index.html[/title]

hmm, this needs to be in the [head] area, not the [body] of the page.

      [td width="48%"][div align="center"][a
href="%20http://www.colincunningham.com/main.html";]
          [/a] [a href="main.html"][/a] [a
href="http://www.colincunningham.com/main.html";]
          [/a]

This is a real good example of how wysiwyg editors can make a real mess.  I see
*three* links to your main.html page but when I view the page, there's nothing
to click on because there's not text or image between the [a href="main.html"]
and [/a]!  So all that code does absolutely nothing and visitors can't enter
your site.

[img src="pics/IE.gif" width="88" height="31"]

As purely my personal pet peeve, I don't like those "best viewed things", it's
kind of rude (imho) to tell the visitor what browser they should use.  And
anyway, your site will look fine in N4 even so there's no reason to tell people
they should be using IE.  Lots of people have no control over what browser they
use, they may be on a computer at school or a friend's or a net cafe or their
parents.

Also for those borders you're seeing, in every [img src=""] tag, put border="0"
in it.  Most browsers default to border="1" if you don't specify.  And in all
your [table] tags, put cellpadding="0" cellspacing="0 border="0", otherwise you
end up with padding and spacing where you don't want it and a default border of
1.

> The distortion in the Mac I'm talking about comes from Colin himself. He
> tells me that the banner "colincunningham.com" on the intro page shows up so
> large that it is off the screen when viewed on his Imac laptop. The graphics
> are also slightly distorted. He is however, able to view the slideshow.

ah, he's probably on a smaller resolution, than you.  I would suggest reducing
the images all around, the title, the pic of Colin and the slideshow pics too so
that they would fit on a 640x480 resolution (allowing room for the scroll bar,
so no wider than 600 pixels total).

Plus he's on a Mac and they have a different pitch in their screen display.  And
you have things like this which may be causing problems:

[table width="51%" height="211" align="left" bordercolor="#000000"]
<snip>
[td][img src="pics/cc5.jpg" width="418" height="288"][/td]

You've specified a height for the table (which isn't necessary anyway) and it's
shorter than the image height.  Colin's Mac (and other people's
computers/browsers) make force the image to table height instead of the image
height.  And like I said it's not necessary to specify the height for the table
so just take it out.

One thing to keep in mind when viewing your page in IE is that the browser is
extremely forgiving, it will display all kinds of strange and broken code,
guessing at what's missing and making the page work.  But Netscape 4 isn't as
nice, it breaks when the code if broken so it's a great browser to test in!
Because if your page shows properly in N4, then it will likely work in most
other browsers.

> Regarding the table borders, it's interesting. When I have the value as
> "0" - they show up invisible in IE, but solid and visible in Netscape. When
> I leave
> the value totally blank, they become invisible in Netscape.

That's because N4 displays borders and cellspacing differently.  If you make the
border 0 but don't specify 0 for cellspacing, N4 defaults to a cellspacing of 20
(iirc) and that's what you're seeing, not a border so much, but the space
between the cells.  You also have to specify cellpadding as 0, otherwise it
defaults to 20 (iirc).  Or it maybe a default of 10 for padding and spacing, one
of those, but not 0.

And are you validating your pages?  Especially with a wysiwyg editor, it's
important to do that, to help catch some of the flaws the editor may put in.
You can validate your pages at the W3C website for free:

http://validator.w3.org/

That's all I can see right off on the index page.  If you'll fix that link to
your main.html page so that it's around your flash image instead of all before
it, then we (and your other visitors) will be able to get to that page and we
can talk about that. :-)

And I've changed all the <>'s to []'s so that you can see the code, rather than
your email program (and everyone else's) trying to display it as html.

alice ttlg


http://idiotbox.populli.net/
~ * ~ * ~     ~ * ~ * ~     ~ * ~ * ~     ~ * ~ * ~     ~ * ~ * ~
Things are going to get a lot worse before they get worse. -- Lily Tomlin





_______________________________________________
Fanficwebdesign mailing list
[EMAIL PROTECTED]
http://populli.net/mailman/listinfo/fanficwebdesign_populli.net

Reply via email to