big problems with browser compatibility!

S

Surfin Local

You have been more than kind today. Thank you for your time. You know, I was
very happy with the site - able to use the "tools" I was familiar with and
make it look the way I wanted. It functioned great from my computer and some
others that I had checking. I am amazed that so many of the features offered
are quite disfunctional or "particular" in the broader scope. Obviously,
experience in page layout is helpful but only a small part of the picture. I
suppose that Microsoft assumes a person using the software has some knowledge
of web design software but it sure would have been great to have some "do's
and don'ts" way back at the Getting Started point! I'm hoping that a Miller
Lite will help me decide whether to take your help and try again or take out
my wallet and pay for someone else's knowledge! Sue/Surfin Local, Inc.
 
S

Surfin Local

P.S. "Experienced and beginner Web developers can pick up FrontPage and start
using it right out of the box." As stated by Microsoft. Hmmm. Sounded good to
me.
 
R

Ronx

Tom,
I use the stats at http://www.w3schools.com/browsers/browsers_stats.asp
which shows that 800x600 screens are used by 34% of users (October)
and 61% use 1024x768 or greater.
For the purposes of this post I consider 34% to be "nearly half".
However, I do not know how "trustworthy" these stats (or those on echoecho)
are: People visiting these sites tend to be web developers, who, by
visiting, may be influencing the stats. unduly.

Most of the people I know, or have seen, using a browser at full screen
either build web sites or use 800x600 resolution.
 
R

Ronx

Have another go.
Draw a grid on a sheet of paper, with 1/2 inch margins - that's very roughly
an 800px wide browser.
Place the text and other components of your page into the grid, changing the
rows and columns to suit.
Open FrontPage, open your web and start a new page.
Insert a table with the same rows and columns, and place the components into
the table cells.
Basic page layout done.

For your word art, use Word to make the Word Art, Copy it to the clip-board,
then paste into a graphics editor. Crop the image, then save as a .jpg.
Import the image into FrontPage.

If you get stuck, post back here.
 
C

Clark

Out of curiosity, why would a user at 800 by 600 have to scroll
horizontally at 740 wide site? A browser that is not maximized?

I use 600 wide as a width just to be extra sure, but probably that is
being too conservative --
 
M

Murray

Out of curiosity, why would a user at 800 by 600 have to scroll
horizontally at 740 wide site? A browser that is not maximized?

Yes - just so. How many people do you see who browser in a maximized
viewport? Not many. Nobody on a Mac does.
 
S

Surfin Local

OK. So just to be sure: Don't use autoshapes. Don't use wordart. How about
the simple rectangles/lines etc.? Basically don't use anything on the drawing
toolbar? Are the web components safe? Also, I am confused on why you don't
want me to accomodate NN in the authoring properties. And I hate to ask this
question but I will. I looked at demos of other web design software
(dreamweaver/go live). Liked the simplicity of FP much more. But do you think
they have the capacity for creating these graphic design elements
"internally" or no matter what software is used, the elements are best
created elsewhere and imported as images?
 
M

Murray

But do you think
they have the capacity for creating these graphic design elements
"internally" or no matter what software is used, the elements are best
created elsewhere and imported as images?

Your last statement is the correct one. No matter what you use as an
authoring system, you are best advised to use images for such effects.

The issue is not authoring systems, it's the capabilities of HTML to
display/render such things.

Given the questions you have asked, I think you have made the right choice
for authoring systems - at least for the short term.
 
S

Surfin Local

Thanks, Murray. I guess Ronx is either busy or tired of me! Any way you could
address the other issues I presented in my last post to him?
 
R

Ronx

In general, don't use anything on the drawing toolbar.

Lines, arrows rectangles, shapes all use VML graphics which use absolute
positioning, and are only visible in IE5.5 on Windows.

Most of the web components are safe. The database components depend on your
server - must be Windows, others require FP2002 extensions.

Setting FrontPage to accommodate Netscape actually turns off some features
that Netscape can handle, or which will fail gracefully in Netscape. NN4
users (according to the stats.) amount to about 2% of users in the browser
wars. The other Netscape versions can do whatever IE can do (except VML
graphics and the marquee - and NN7 can use the marquee). It is a question
of compromise - maximise the featureset or maximise the audience, and how
far back in ancient browsers do you design for?
If you restrict the site to IE5.5 users and above (about 80% of users), use
anything on the drawing toolbar. If you want the other 20%, don't use that
toolbar.

I've never used Dreamweaver - never got through the learning curve. In my
opinion graphics should be done in a graphics program, use a tool designed
for the job.

Rectangles and lines can be constructed with tables, cell borders and other
HTML tricks in conjunction with CSS.

With experience and testing in different browsers you will learn what will
work, what will fail.

And if there is a problem, ask in this newsgroup.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top