Results 1 to 6 of 6
  1. #1
    New Lounger
    Join Date
    Jun 2001
    Location
    Montrose, Colorado, USA
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Bloated Front Page Code (2000)

    I've gotten complaints about unnecessary code in Front Page. I've found a site by Paul Colligan who is selling FrontPage Power Edit which is supposed to eliminate unneeded code in Front Page. Has anyone used this, does it work and do you recommend it? Thanks, Kate <img src=/S/compute.gif border=0 alt=compute width=40 height=20>

  2. #2
    4 Star Lounger
    Join Date
    Dec 2000
    Location
    Faifax, Virginia, USA
    Posts
    542
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Bloated Front Page Code (2000)

    Hi Kate ~

    Would you be so kind as to elaborate a bit about what unnecessary code is, and how it was so determined?

    E.g., i use a lot of "unnecessary" code in my *.ASPs to trace execution. I can turn execution of the code on and off. It's like a parachute: "unnecessary" most of the time.

  3. #3
    billeger
    Guest

    Re: Bloated Front Page Code (2000)

    Kate,

    "Unnecessary code" must be in the mind of the beholder. In my view, for example, when you convert a WORD document to HTML you get the supreme example of "unnecessary code." But that has nothing to do with FrontPage unless you put it in a page in that format rather than, say, just copying the document as a text file and pasting it into a FrontPage table. Very little code that way. So if you would let us know what you mean by bloated code, it would be very helpful. Or, perhaps, what the author selling his work means. <img src=/S/hello.gif border=0 alt=hello width=25 height=29>
    <font face="Snap ITC">Hawai'i Bill</font face=snap>

  4. #4
    New Lounger
    Join Date
    Jun 2001
    Location
    Montrose, Colorado, USA
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Bloated Front Page Code (2000)

    Hi:

    Here is a sample of what "they" say is bloated: <html>

    <head>
    <meta http-equiv="Content-Language" content="en-us">
    <meta name="GENERATOR" content="Microsoft FrontPage 5.0">
    <meta name="ProgId" content="FrontPage.Editor.Document">
    <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
    <title>New Page 1</title>
    </head>
    <body>


    <font face="Arial" size="2">We're doing a quick example of FrontPage Power
    Edit here.</font></p>


    <font face="Arial" size="2">We know you'll like what it does.</font></p>


    <font face="Arial" size="2">Why does FrontPage produce so much HTML?</font></p>


    </p>
    </body>
    </html>

    and here is their solution:

    <html><head><title>New Page 1</title></head><body> <font face="Arial" size="2">We're doing a quick example of FrontPage Power Edit here.

    We know you'll like what it does.

    Why does FrontPage produce so much HTML?</font>



    </body></html>

    By the way, the reason I'm concerned is that I use FP to create a newsletter and the service is limiting KBs and point to the fact that FP adds extra code.

    Thanks for your help!

  5. #5
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: Bloated Front Page Code (2000)

    Well, there's no single "right way" to do HTML. Yes, there are official standards, and yes there are de facto standards (i.e., what MSIE supports), and yes there are "good coding conventions." I think if slimness of code is the top priority, this tool might be a good idea. But you can change your habits for writing pages, give the HTML pane a quick tune-up, and get pretty good results with FrontPage. (Certainly you don't need those meta tags.)

    So my code might look like this:

    <html>
    <head>
    <title>New Page 1</title>
    <style>
    body, p, td {font-family: Arial, Helvetica, sans-serif;
    font-size: 10pt}
    </style>

    </head>
    <body>


    We're doing a quick example of FrontPage Power Edit here.</p>


    We know you'll like what it does.</p>


    Why does FrontPage produce so much HTML?</p>
    </body>
    </html>

    By defining your default body, paragraph tag, and table cell tag styles, you can get rid of all those annoying <font> tags. Personally, I tend to copy from other pages rather than use FP's styles dialog each time, but you can do it either way. Hope this helps.

  6. #6
    Super Moderator WebGenii's Avatar
    Join Date
    Jan 2001
    Location
    Redcliff, Alberta, Canada
    Posts
    4,066
    Thanks
    2
    Thanked 5 Times in 5 Posts

    Re: Bloated Front Page Code (2000)

    I'm going to go on a bit of a rant here, so if you want skip over this. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    <img src=/S/ranton.gif border=0 alt=ranton width=66 height=37>
    I've said it before; the reason FP gets such a bad rap about its' code is not the product - but it is the way people use it. To be fair however, MS sells FP on the rational that you don't have to know HTML to use it. So most people use FP like a word processor and wind up with the kind of code you've shown. However, FP can create reasonably lean code. To be honest I don't sweat the metatag stuff, it's the rest of the page that matters to me. You will find unusual code if you are using the workflow features in FP:
    <pre>--[if gte mso 9] xml
    mso:CustomDocumentProperties
    mso:Categories msdt:dt="string" /mso:Categories
    mso:Approval_x0020_Level msdt:dt="string" Approved /mso:Approval_x0020_Level
    mso:Assigned_x0020_To msdt:dt="string"></mso:Assigned_x0020_To
    /mso:CustomDocumentProperties
    /xml ![endif]--
    </pre>

    I've edited that a bit, by taking out the brackets. Much to my embarrassment, for the first little while I removed that code stubbornly through the HTML window and then was annoyed when FP kept "losing" the Approval category and other workflow settings I was trying to use. So, I really have to walk my own talk <img src=/S/grin.gif border=0 alt=grin width=15 height=15> and that is understand the product I am working with and the language it is handling (HTML). With those two principles in mind, I think anyone can make educated decisions about how they want to use FP. Yeah, there are going to be some "excess tags" I'm going to live with - because they are going to help me keep track of large numbers of pages. But I'm also going to plan ahead with style sheets when ever possible, to keep my pages well structured and the code within them as lean as possible. I'm going to be fanatic about cleaning up documents converted from other MS apps, because they have all sorts of <img src=/w3timages/censored.gif alt=censored border=0> in them. I won't worry about the metatags, since there are macros we've been discussing in this forum to strip those out of pages (and to add metatags in).
    And that is really where I think FP shines in comparison to some of the other products in the marketplace. You do have the workflow tools and the VBA capabilities for an entry level price and with a relatively approachable interface. (That's where I believe MS, should be making improvements). Competetive products are either more expensive or require you to buy additional products to support those features.
    Okay <img src=/S/rantoff.gif border=0 alt=rantoff width=66 height=37>
    Did this answer your question, no probably not...
    [b]Catharine Richardson (WebGenii)
    WebGenii Home Page
    Moderator: Spreadsheets, Other MS Apps, Presentation Apps, Visual Basic for Apps, Windows Mobile

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •