????  No one is "bashing" anything, that was uncalled for.
This is a list to give opinions and options to help others
with their problems, is it not?  I hear all the time at HTML
lists I belong to; to stay away from WYSIWYG editors (esp.
FPX) since they induce errors in HTML code.  If you run some
page created with FPX though a validator, you'll see all the
errors.  Hence the information to HELP Larry.  If FP2000 is
better, then good.  Since this is not an HTML design list, I
did not want to get into details.

Larry and I have discussed off list on several occasions
regarding his website and I've tried to help him with problems
and give him some helpful pointers and tips since he's new to
websites......one being: to do your own HTML code instead of
using an editor.  When you do you own HTML code and not rely
on an editor, you learn much quicker just what HTML code is,
learn to 'speak the language', and learn to easily and quickly
fix any errors.  If one (NOT necessarily YOU, but a newbie to
websites) continues to use a WYSIWYG editor, they won't learn
the proper way to create webpages, and it will continue to be
sort of a 'crutch'.  They are faster in the beginning just to
get a FIRST page started, yes; however, not worth it in the
long run.

My advice (to anyone creating their first website, or new to
it) is to pick any webpage you sort of like (NO FRAMES, too
confusing for a newbie).  Save the page "as HTML only" (you
won't see the images) or "HTML complete" (with images) (IE) to
somewhere on your HD.  Then click the page, then "edit", "view
source" or right click and 'view source' to see the code, then
mess around with it.  Make changes in the now open Notepad
file, "X" out of it while saying 'yes' to saving the changes,
then 'refresh' the page to see your changes.  Changes can be
made instantly, and results seen instantly.  When you're
finished with the page, FTP it, or just paste the code into
the page via your online website control panel's 'file
manager'.

When you have a layout to your liking, use it as a template
from then on for the rest of a site's pages.  Simply "copy and
paste" the code from it as the template for the rest of one's
pages and modify as necessary to fit the specific criteria of
the additional pages (change the title tag, description &
keywords tag while leaving all or most of the other tags in
place and just modifying the content within header or font
tags).  This way one never has to rely on a WYSIWYG (What You
See Is What You Get) editor.

But, that's just one opinion.......
-Clint

God Bless Us All
Clint Hamilton, Owner
Want to exchange links with us?
http://OrpheusComputing.com �

----- Original Message -----
From: "Linda F. Johnson" <[EMAIL PROTECTED]>

Not really, Clint...it's a definite glitch in FrontPage
(somewhat improved
in FrontPage 2002 extensions)...but, with FrontPage 2000, if
you ftp a few
pages, it doesn't seem to hurt anything...but if you ftp a
bunch of pages,
the FrontPage extensions get corrupt and need to be
reinstalled by your
host.

And FP doesn't REALLY create "gobs of html errors"....the
errors come from
the users who don't take the time to clean up the code (like
me, LOL)....I
know some pretty smart people who use FrontPage and have very
clean code
(not me, LOL)

Most FP code bloat is caused in the font tags...if you change
the fonts, FP
leaves a lot of garbage behind....other than that, FP 2002
really doesn't
create nearly as much bloat as it used to.

Please...no FP wars in here, OK?  Since Larry chooses to use
FP, let the FP
users help him instead of bashing his choice of
software....fair enough?

Linda


-----Original Message-----

..and if you can get away from FPX or FP2000, the better off
you'll be.  They create gobs of HTML errors.
============= PCWorks Mailing List =================
Don't see your post? Check our posting guidelines &
make sure you've followed proper posting procedures,
http://pcworkers.com/rules.htm
Contact list owner <[EMAIL PROTECTED]>
Unsubscribing and other changes: http://pcworkers.com
=====================================================

Reply via email to