Forum Moderators: open

Message Too Old, No Replies

Frontpage vs. Mozilla and Netscape

Is there anyway to make them work together?

         

steelrane

10:26 pm on Dec 4, 2003 (gmt 0)

10+ Year Member



I've been trying to clean up my code so maybe my fp website would work in Mozilla and Nescape does anyone have good ideas how I can make this happen? I've tried tidy but it makes my site fall apart
Thanks

oilman

10:29 pm on Dec 4, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I use FrontPage <...pauses for audible gasp from other members...> and I don't run into any issues with NS or Moz. Usually you only get issues when you're using proprietary FP stuff like letting it create your mouseovers or css files etc. FP is getting better but there is still a bunch of stuff that you should do by hand after the fact IMHO. Could just be that I don't know how to make FP do what I really want :)

pleeker

10:33 pm on Dec 4, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I use FrontPage

GASP!

steelrane

10:34 pm on Dec 4, 2003 (gmt 0)

10+ Year Member



Whats IMHO?

steelrane

10:39 pm on Dec 4, 2003 (gmt 0)

10+ Year Member



I just got Go Live 6 & Dreamweaver mx but I've spent so many hours learn Front Page that I dont Know if its worth the time to move on any ideas on which is better

photon

11:55 pm on Dec 4, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



IMHO = In My Humble Opinion

pleeker

12:18 am on Dec 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



any ideas on which is better

Dreamweaver and GoLive are probably the two most popular choices among professionals who use editors. FrontPage has the reputation as the amateur's choice and the biggest complaint (and a very valid one) is that it produces incredibly bloated code that slows down your web pages.

I'm sure if you browse or search through this Forum you'll find some lengthy discussions about FP from people who love it and those who hate it.

bill

2:56 am on Dec 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Get rid of the themes and replace any shared borders with Include Pages. Then get rid of any component that relies on the FP server extensions (they aren't used in FP2003 anymore). Then you'll need to spend some time validating your HTML and tweaking things while checking in a couple of browsers. It's a bit of work, but you'll learn a lot.

caine

3:28 am on Dec 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



OILMAN >> I use FrontPage <...pauses for audible gasp from other members...>

utterly shocking revelation (your worried about what others think - that must have been a sweaty moment realising you were going to drop that one), now i think you need to be taught some SEO etiqitte from Hannah, go stand in the corner, looking at the wall. lol!

DM will do a lot of house cleaning regarding code, though it certainly ain't perfect. I think running a validator across some of the page's to see what it is about your code that does not validate, then reading up at W3C Validator [validator.w3.org] for the validation level that you wish the site too obtain will be a good start.

Personally as a DM person, i would be tempted to do the above then run DM's code cleaner, then edit by hand the rest of the code, but obviously that comes down to how many pages were talking about!

steelrane

7:43 pm on Dec 5, 2003 (gmt 0)

10+ Year Member



Can you tell me what DM is? Is it like tidy?

victor

8:10 pm on Dec 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



If you use any product that doesn't produce 100% valid HTML, aim for your money back.

There should be zero tolerance for failed software.

Dreamweaver is good, and getting better:
[webstandards.org...]