PageBuilder Advanced Editing MethodsUSING STYLE TAGSThe style tag method is identical the script tag method – it is legal within the head tag of a document, and will cause very few validation errors with the method I suggest here. Here I use the standard practice of enclosing the style tag content in HTML comment tags, and use the C/C+++ multiline comment tags to effectively block-out, actually comment-out and hide, the PageBuilder built-in body tags. The basic syntax; using: blue text for the title box entry, red text where the blocked-out PageBuilder code appears, and black text for the first "Add text" box at the top of the document; is: Webpage Title Here</title> <style> <!-- /* blocked-out PageBuilder body tag and beginning table tags appear here */ --> </style> </head> <body bgcolor="#??????" text="#??????" link="#??????" vlink="#??????" background="http://URLofYourBackgroundImage"> <p> <table> <td> <tr> Note in the code above, that the HTML comment tags inside the style tags hides style code from non-style browsers that do not recognize the style tag; while the multiline comment tags hide, and block-out, the PB built-in body tag by making it appear to be a style code multiline comment to style-compliant browsers. The table tags in the above code are added to replace the blocked-out, built-in, beginning table tags you see in the source code. Also note in the code above that you can add any other style code, link tags, meta tags. and javascript in an extended head tag by inserting the added code between the advanced editor closing style tag and the closing head tag. You can enclose multiple styles and scripts in one set of style or script tags, or use separate style and script tags for each indivdual style group or script! You can have as many separate style or script tags inside the head tag as you desire. As a supplement to this webpage, I wrote another tutorial about using this method with a CSS style sheet for the body tag style. I also wrote a tutorial about using external style sheets in PageBuilder documents. Check them out. This is a legitimate method, fully compliant with the HTML DTD; but, may not be a very popular method, because it is plagued with the same "closed" basic editor screen that caused the unpopularity of H17's original comment method, until Paul Dutton discovered his "Defeat" method to keep an open basic editor screen. Using this method will require that you "Edit title" to disable both the style tag and beginning HTML comment tag to open the basic editor screen, by removing the beginning angle bracket of the style tag and the trailing dash of the comment tag, in the title text box; like this: style> <!- You can work around this limitation during editing, even while the basic editor screen is closed, by ckicking on the "Change text" thumbnail in the "Recent" panel to bypass the closed basic editor screen. You can also temporarily save any basic editor screen as a favorite and put it on a temporary hot key to bypass the closed basic editor screen. But, be careful – always be sure you restore the deleted angle bracket and dash before you publish or re-publish, or it will not work with your added body tag! Always replace the removed items and publish your webpage from a closed basic editor screen. Then after you publish the webpage, you can come back and disable the tags again, to have an open editor for future changes to the webpage. Which may take a few extra seconds to open and close the basic editor screen! Is this too much trouble to make it a viable PB AE method? Yeah I guess, according to others who want to hype their own methods as being superior; although this method's HTML code syntax is as legal as any other method, and looks OK on all the major browsers! At the time, I didn't think this method would be popular because my Noscript and Script methods allowed an "always open" basic editor screen. So that's why I just let the method die in my PB AE file folder as a few notes and test pages. |
|
|
| |
|
|
||
|
|
||
|
|
||