PB Script Method AE

PageBuilder Script Method Advanced Editor

INTRODUCTION
This is a demo of using the <script> tags and javascript multi-line comment tags instead of HTML comment tags to create WebTV PageBuilder Advanced Editor webpages. Here I use the <script> /*... */ </script> tags to block-out the PageBuilder built-in body tag so a new body tag can be added. I also position the script tags to block out the PageBuilder built-in closing </head> tag so I can extend the head section of the webpage for the addition of <script> ... </script>, <style> ... </style>, and a new relocated <title> ... </title> code. Use the Thunderstoneй Source Code Viewer at the bottom of this webpage to see the structure of the script tags used in this procedure.

GENERAL DESCRIPTION

The javascript multi-line comment tags, in this syntax: <script> /*...*/ </script>, I use in this method, are used exactly the same way as the comment tags are used in other PB AE methods Ц to block-out the selected PageBuilder background style body tag, and also to block-out the built-in closing </head> tag so scripts, styles, and meta tags can be added to an extended head tag. Then a new custom body tag is added after the extended head tag, which is the basic purpose of all the PageBuilder advanced editing methods - ie: to add body tag background style choices that PageBuilder does not provide!

It works great by blocking the PageBuilder selected built-in body background tags from webpage table template structure on the webservers. Javascript-enabled browsers, basically see an empty script tag because the content between the script tags, which is the PageBuilder blocked-out built-in tags, are contained within the javascript multiline comment tags and will be ignored by javascript-enabled browsers.

Non-javascript browsers, as well as MSN-TV browsers with the JS bug will not recognized the script and comment tags, and will mark-up the built-in body tag, unless they are enclosed in comment tags (see comments below), instead of the new added body tag Ц but, this is a moot point because I use an MSN-TV JS bug warning and warning fo PC users!

Therefore, immediately following the new added body tag, I replace the blocked-out PageBuilder paragraph and table template tags; and add a javascript bug warning for MSN-TV browsers, and a notice to PC users that they must have javascript enabled to view the webpage.

Here's the code I used at the top of this document. Try to generally familiarize yourself with this basic structure, and refer to it when I discuss the step-by-step procedure below.

Beginning with the title text box, I use:

PageBuilder Script Method Advanced Editor</title> <script> /*

Note: That's all you need to enter in the title text box; but, I added notes you will see in this webpage's source code that tells you where the advanced editor comment tags that block-out the PageBuilder built-in body, paragraph, and table tags begin and end. Therefore I had to relocate the title as explained below, because the title and notes were too long for the title box. Read the explanation below and you will understand your options for titles using this method, or any other PB AE method.

Then, in an "Add text" box at the top of your webpage, you use code similar to this:

*/ </script> <script language="javascript"> function welcome() {alert("Welcome to my webpage, folks! I will appreciate any comments you have about this method! Please test it anyway you like. Let me know about any problems you find. View the source code with the viewer at the bottom of the page. -JaxRed-"); window.setTimeout('window.status="WELCOME to my webpage, folks! -JaxRed-"', 5000); window.setTimeout('window.status="PageBuilder Script Method Advanced Editor"', 10000);} function goodbye() {alert("Thanks for visiting my webpage, folks! Did you print out the source code for this webpage? Have a nice day! -JaxRed-");};</script> <meta name="publication_date" content="Mon, 15 Jan, 2001 19:45:00 GMT"> <meta name="author" content="JaxRed@webtv.net"> <style>  </style> <title>PageBuilder Script Method Advanced Editor</title> </head> <body text="white" link="green" vlink="cyan" transition="spinoutin" onLoad="welcome()" onUnload="goodbye()"> <p> <table> <tr> <td> <embed src="http://www.transload.net/~jaxred/music/midi/bootscoot.mid" hidden="true" autostart="true" loop="-1"> <br> <noframes> <font color="red"> <limittext value="WARNING: WebTV JAVASCRIPT BUG! Ц Please RELOAD (Cmd-R)!"> </font> </noframes> <noscript> <font color="red">NOTICE: PC Users Must Have JavaScript Enabled To View This Webpage!</font> </noscript> <h1 align="center"> <font color="#ffd700">PageBuilder Script Method Advanced Editor</font> </h1> </plaintext> </font><br> <br> Note: This code is all-inclusive, and may seem complicated to beginning PageBuilders - see the simpler brief description in the step-by-step procedure below. Here, for simplicity; ie, to keep from typing many different separate options, I included all the options this method allows for the extended head tag; such as: additonal meta tags, scripts, style code, and a relocated title tag within the head tag, as noted below. Just remember: you will not usually have to relocate your title tag because generally you will have enough space in the title text box to enter the webpage title and script tags.<br> <br> In this code, you see that I added my scripts to the head tag because they are called by the new body tag and must be defined before being called! I used the style tag within the head tag to call the background image for this webpage, to illustrate an option with the style tag.<br> <br> The noframes and limittext tags are for the MSN-TV javascript bug warning; and the noscript tags are for detecting PC's with javascript disabled. The noframes tags are used exclusively to detect the MSN-TV javascript bug; and the proprietary MSN-TV limittext tag's value string can only be dsplayed by the MSN-TV browser, which makes this combination the preferred MSN-TV JS bug detection method! The noscript tags detect and display the notice to non-javascript browsers. The MSN-TV browser does not recognize the noscript tag, even when the infamous JS bug strikes, because we cannot disable javascript as computers can Ц so only computers with javascript disabled can read the content between the noscript tags!<br> <font color="#ffd700"> <h3> <u>ADDITIONAL NOTES</u> </h3> </font><br> The script method advanced editor is a perfectly legal method under the W3C HTML DTD. The script tag is legal within the head tag of an HTML document. This method does receive warning from some webpage validators that "markup inside the javascript comment tags may confuse some browsers" Ц we all know this warning is wrong because it's accepted scripting practice to disable uneeded script code, which may incude document.write HTML, with javascript single and multiline comment tags.<br> <br> You may get warnings from validators that say something like: "body tags should not be used inside the script tags," This is correct - it is illegal to use script tags around a body tag, unless the body tag is in a document.write statement - but, this minor HTML syntax error doesn't matter, because the unwanted built-in body tag is purposely being disabled by the script tags to allow this Advanced Editor procedure to properly function. Also, some validators may warn: "markup within comments may confuse some browsers," which is incorrect Ц webpage authors typically use HTML and javascript comment tags to disable, and/or store code for future use.<br> <br> The various online webpage validators produce somewhat different results that need careful evaluation for needed webpage corrections. For additional information see Pwilliamandx's webpage validation <a href="http://community-2.webtv.net/willxwill/comparisons/">comparisons</a> tutorial. I suggest that you always have your webpages previewed in all the MSN-TV browsers and upgrade versions and all the major computer browsers - PC's and Macs!<br> <br> I used the multiline javascript comment tags in this method because they are container tags; ie: with beginning (/*) and ending (*/) tags that surrounds the HTML body tag and beginning paragraph and table tag code that needs to be commented out, so the new custom body tag can be added! While I was testing this method with WebTV, I noted that the single line (//) javascript tag also worked OK; but, it's not an all-inclusive container tag that's preferable to use! Also, if the comment following the single line comment tag spills over to the following line, computers will show an error alert. Since it appears to me that the blocked-out built-in HTML code spans multiple lines, I think the javascript multiline comment tags are more appropriate for this method!<br> <br> This past December 2001, several expert PageBuilders in the <a href="news:alt.pagebuilder.help">news:alt.pagebuilder.help</a> NG considered other comment tag variations when testing this method. Concensus of opinion among others suggested that the following syntax be used:<br> <br> <font color="#ffd700"><script>  </script></font><br> <br> This works OK. It's even better for MSN-TV, because the PageBuilder program kills everything between the regular HTML comment tags inside script tags - that's why you cannot use HTML comment tags inside your scripts to hide from non-script browsers in PageBuilder webpages! And with this variation, even when you have the infamous MSN-TV javascript bug, the built-in body tag is hidden by the comment tags - which is a moot point because I suggest the use of a javascript bug alert script on all PB AE webpages, and not only pages with scripts, because the bug can strike any time! The problem is within our browser's "lean programming code" in our comparatively small ROM, that does not contain sufficient javascript "error-checking" program codes! <br> <br> But, javascript enabled browsers read the script tag and know that all text between the HTML comment tags, except text between javascript comment tags noted above, is javascript code to be interpreted and executed. The syntax shown above, causes syntax errors in some browsers because the right-angle bracket of the ending HTML comment tag is not properly "delimited" by a single line javascript comment tag (//), which is standard scripting practice! Therefore, I made these comments in the PageBuilder NG during the discussion of this variation, and suggested that this script syntax must be used:<br> <br> <font color="#ffd700"><script>  </script></font><br> <br> I suggest you must use this syntax, with the javascript single-line comment tag preceeding the ending HTML comment tag, like this: // -->, if you use the HTML comment tags within your script method AE tags!<br> <br> However, this does not mean that I am suggesting this variation is the way to go, which many of the scripting technocrats may feel is the absolute correct, pure script way to go? I feel that my original method of using only multiline javascript tags with a JS bug warning script is simple enough, and just as effective, for beginners who may want to use this method! I just prefer the simplicity of the multiline comment tags. Use your own preferences, folks; this choice will separate the "techies" from the "keep-it-simple" folks, like me!<br> <br> Again, I suggest you always use a MSN-TV javascript bug script on your webpages whether you have scripts or not on your webpage! Why? Because our MSN-TV browsers frequently catch the JS bug, and will not display the webpage title in our status bars, or properly display a frames webpage. This effect is independent of whether you have scripts or not on the page! I suggest you always use a bug alert script to tell your viewers that the page must be reloaded; because many viewers may not know that the missing title, no functioning javascripts, and possible display problems are caused by our infamous JS bug that has always plagued our browsers! Use the bug warning message text inside the proprietary <limittext> tag so only our MSN-TV browsers will see the alert!<br> <h3><font color="#ffd700"><u>THE STEP-BY-STEP PROCEDURE</u></font></h3><br> The procedure is as follows: <br> <br> ааааа(1) Go to your PageBuilder Index and choose "Create" on the sidebar. Choose a "Background style" that you would like to work with in the Basic Editor screen. Many PageBuilders select the "Grey" background to open the Basic Editor screen.<br> <br> ааааа(2) Put an appropriate short title, typically four (4) to seven (7) letters long, you want to apear in your webpage URL in the "Add title" text box and click "Publish." <br> <br> ааааа(3) Complete your webpage "Description" and "Uncheck" (or leave as is) the option to have the title appear on your webpage Ц the advanced editor script tags block out the paragraph and heading tags that the title box entry is placed in on your webpage, so the webpage chechoff option doesn't work Ц this applies to all the PB AE methods also! <br> <br> Note: When using any PB AE method you must put the appropriate webpage title that you want to appear on your webpage in a text box at the top of your document, following your new body tag, where your body tag markup content begins Ц this webpage title can be formated text, images, banners, or other suitable webpage title content. Then "Publish" the webpage again after you complete the description. Click "Done" and return to the Basic Editor screen with your "Back" key.<br> <br> ааааа(4) Now click "Edit title" and enter, in the title text box, the following: the title that you want to appear in your viewer's browser status bar, which can be only 35 characters or less or you'll get elipises in the status bar; then a closing title (</title>) tag; followed by a beginning script (<script>) tag, and a beginning javascript multiline comment (/*) tag; like this:<br> <br> <font color="#ffd700">Your Webpage Title Here </title> <script> /*</font><br> <br> Then click "Done," then click "Add an item," then click "Add text" to begin step (5) below.<br> <br> Note: At this point I suggest you should consider a little added explanation about your webpage title. Before the December 1999 PageBuilder upgrade, we could not do much with the title text box Ц it was mandatory that we use the title box if we wanted the webpage title to appear in our title bars; and, the title automatically appeared on our webpage!<br> <br> But, the '99 PB upgrade changed the webpage title procedure and allowed separation of title box entry for the status bar title and the webpage for use of formated text and graphics webpage titles! In my original PB AE Procedure webpage, I noted that we could not relocate the title text box in an extended head tag Ц the PB software javascript wouldn't pick it up! But; since the upgrade, we can relocate the <title> ... </title> tags in an AE extended head tag!<br> <br> In fact; in addition to showing the simple syntax for using the title text box above, I also relocated the title as a demo of the relocated title I explained above. See this relocated title in the source code for this webpage. It's an option you may need to use if you have a title that, along with the script and comment tags, is longer than the character capacity of the title text box. This is what happened here when I added the note about where the script method tags begins that you will see in the source code.<br> <br> Also, remember: when you use a PB AE method, you must always add your title to the top of your webpage, because you cannot check the box to add the title to your webpage! Why? Because the PB AE method tags blocks out the paragraph and header tags that PageBuilder uses for your title to be placed on your webpage. So, you always have to enter a webpage title at the top of your webpage when you use any PB Advanced Editor method!<br> <br> (5) Then use an "Add text" box at the top of your webpage for the following: an ending javascript multiline comment (*/) tag, and a closing script (</script>) tag; then add your additional script tags with the the functions you want to run on the webpage; followed by your CSS style code, new (relocated) title tags, closing head tag , then add your new custom body tag with your new bgcolor, background image, text, links, gradcolor, and transitions code; and, finally, add the table template tags that must replace the blockd-out beginning table tag code. Always leave this text box as "Item #1" on your webpage. This Advanced Editor layout sequence described above allows the Basic Editor screen to always remain open so the user can easily access all the text boxes and change styles, scripts, and body tag attributes and webpage content as desired.<br> <br> Here's the a brief description of the code shown above that is placed in the first "Add text" box at the top of your webpage:<br> <br> <font color="#ffd700"> <plaintext> */ <script> <meta name="?" content="?"> (add additional meta tags here) <script language="javascript"> ... add your scripts here ... </script> <style type="text/css">  </style> <title> ... add a relocated title here if desired, instead of a title in title text box ... </title> </head> <body ... needed body tag attributes, including transitions and onLoad/onUnLoad event handlers here ...> <p> <table> <tr> <td> (these are the replaced table template formating tags I suggest you add as explained in the procedure) <embed src="http://URLofyourBackgroundSoundFile"> (your MSN-TV JS bug warning script and noscript warning for computers here) (your formatted webpage title here at the top of the page) </plaintext> </font><br> <br> As shown in the code above, I suggest you use separate script tags for your script method editor tags, that block the built-in code, and any other scripts you add in the extended head tag! The javascript purists may say you can put your added scripts in the editor tag following the multiline comment tag, and that's absolutely correct! It will work OK; but, I prefer, and recommend, that you keep your script editor tags separate from your other added scripts! You can use as many separate script tags as you desire in the head or body tag. In fact, many scripters prefer to separate complex scripts from each other by using separate script tags, which allows easy reconition of the script boundaries, and future editing, of each script. Use you own preference here, folks! <br> <br> Note: When you close-off the title (</title>) text box before your beginning script editor tag, and relocate your the new title in the extended head tag, this new title correctly displays in our WebTV status bars at the bottom of the screen, and appears correctly in the computer window title bars at the top of computer window screens! But, I suggest you always use the tile text box unless your title is too long, in which case, you will have to place it within an extended head tag.<br> <br> And here's a bonus for using this method: this is an open editor method! You can always see most of your webpage content in the Basic Editor screen - it's not closed off like the original comment method! However; with this method, the meta, script, style codes in the extended head tag, and new body tag code disappears from the Basic Editor screen, and you will have to click on the text box to see this code. <br> <br> ааааа<a name="addtags"></a>(6) Now add all the rest of your webpage content using HTML or any of the options provided in the PageBuilder program. And when you finally get your webpage content as you want it, you need to publish your webpage and view the source code to verify all the beginning paragraph and table tags used by the PageBuilder webpage table template that are blocked out by the script tags and replace them in the exact sequence FOLLOWING YOUR NEW CUSTOM BODY TAG! And, always check to make sure the opening table tags match the closing tags at the end of the first text box, in correct sequence.<br> <br> Therefore, with the Grey background color, you must add: <font color="#ffd700"><p> <table> <tr> <td></font> to provide the missing tags. If you use an "Add heading" text box at the top of your webpage, you only need to replace a beginning paragraph tag and a header tag, like this: <font color="#ffd700"><p> <h2></font>! Here I used small letters in the replaced tags code in the template above, so you could recognize my added tags, to match the PB built-in capital letter tags.<br> <br> Remember, the replaced table tags will be added at the end of your new added custom <body> tag. This insures that the basic "table" template of the PageBuilder webpages will be formatted correctly by the various browsers. The latest browsers, especially Netscape, have trouble correctly displaying PageBuilder webpages with HTML table tag syntax errors, which usually occur when we use any of the PageBuilder Advanced Editor methods that block out a portion of the PageBuilder editor beginning table tags. Always check the source code of the basic PageBuilder background style you select to see the blocked-out table and paragraph tags; then replace them in the exact sequence following your new added <body> tag. Then check the source code of your finished webpage to verify that you have the required beginning table and paragraph tags. <br> <br> Note: You may end this first "Add text" box here, because you will not need to access your webpage PB AE head tag and custom body tag code as frequently as you will add content to succeeding text boxes and pages after page breaks. But, be aware that under some circumstances this will add some extra undesirable space between the successive text boxes when viewed with the latest browser upgrades. The full effect of this problem has not been entirely resolved in the PB NG's! Because of this problem, some of the PB experts are suggesting that you put all webpage content into a single text box, and use pagebreaks to keep individual pages to a manageable size!<br> <br> The above six steps completes the AE procedure. The rest of the webpage is completed by adding additional photos, text boxes, headings, lists, links, HTML markup, scripts, inline style, and other webpage content as you desire to complete your webpage. It is best to add each item as separate entry boxes, so each individual item loads much faster than one large webpage; and you will have lots of flexibility in rearranging items, moving them up and down, if you limit the size of individual items.<br> <br> If you have a complex document with lots of HTML tags, it requires close attention to the code to verify the correctness and legality of the code, especially with nested tables and divisions! But, there's a very simple way to check HTML tag closing and nesting Ц simply check your webpage with a source code validator, that also has a "display parse tree" option. A "parse tree" of your webpage code, will show the hierachical order, properly indented, of all your HTML tags from top-to-bottom of your document. From the "parse tree" print-out, you can immedately see missing and improperly nested tags! Always use "parse tree" structured HTML tag printouts for complex documents! I use the "parse tree" option with the W3C validator, at: <font color="#ffd700"><a href="http://validator.w3.org/">http://validator.w3.org/</a></font>.<br> <br> The parse tree printout should be used for complex documents; but, a simple source code viewer or online webpage validator may be used to view all the HTML tags in your document. I suggest you carefully inspect your document for missing and incorrectly nested HTML tags. Some of the PageBuilder experts in the PageBuilder NG's are suggesting that it's unnecessry to replace the blocked-out built-in tags this AE method causes at the top of the text boxes; but, I insist that you must correctly add missing HTML tags to properly close the PageBuilder table template - not doing so may be permissible for many "loose DTD" browsers; but is bad practice!<br> <br> If you build PageBuilder multi-page documents, just remember that you must have a new body tag for each page. Just follow the instructions in (5) above for each page in your document, which starts with the ending javascript multiline comment tag and closing script tag. But, be careful when rearranging items on your webpage between pagebreaks. Always make sure that your comment tag, closing script tag, scripts, styles, new body tag, and webpage title is in a text box at the top of each new page following a pagebreak, and that each page's content was designed for that particular page scripts and styles! It's easy to get multipage contents and pagebreaks really mixed up if you don't be careful keeping track of webpage items locations when shuffling items up and down! Check out my tutorials about PageBuilder Advanced Editor multi-page documents listed below.<br> <font color="#ffd700"> <h3> <u>SUMMARY</u> </h3> </font><br> To demonstrate the functionality of this PB AE method, I put scripts, style code, and a new title in the extended head tag of this document. My webpage body tag loading and unloading alert scripts, and status bar welcome message are functions defined in the extended head tag ahead of the new body tag, which calls the scripts with event handlers. The new body tag has a blue-white bgcolor and the head section style tag loads a body background gif image from my images website.<br> <br> Try it, folks. It works great; and, being an open-editor method, does not have the problem of H17's original PB AE method which requires disabling of the beginning comment tag to open the Basic Editor screen!<br> <br> This is just one of many new PageBuilder AE methods that have been introduced using the basic concept, first demonstrated by Webber H17, of blocking-out the PB buitl-in body tag so we can add new custom body tags with our choice of backgrounds not provided by the PageBuilder program. I still insist that the full credit for discovering the PageBuilder Advanced Editor concept belongs only to Uncle Huey, aka <font color="#ffd700"><a href="mailto:H17@webtv.net">H17@webtv.net</a></font>, who I believe is no longer with us, or has his email turned-off. No matter what variations of Advanced Editor we subsequently discover, including this method that does not use HTML comment tags as other PB AE methods, credit for the "original premise" of disabling the PageBuilder built-in body tag so we could add our own background code belongs only to H17, and no one else! Don't ever forget that folks, and don't let anyone else try to tell you anything different!<br> <br> Thanks to a few of my friends who tested this method and offered their comments when I first published this method! A special thanks goes to a couple of my javascript and CSS guru friends who tested this method with many scripts, styles, backgrounds, and multiple alignment techniques for photos and text!<br> <br> When I first published this method in January 2001, and had it listed in the Expert-HTML newsletter, I got practically no response from others in the PB NG's! My friend, <a href="mailto:Pwilliamandx@webtv.net">Pwilliamandx@webtv.net</a>, listed it in his PB AE methods <a href="http://community-2.webtv.net/willxwill/ae_methods/">tutorial</a> after I emailed him about it. But, at the time; others seemed to be avoiding even commenting on it, much less trying it on their webpages!<br> <br> Then beginning in December 2001, others begin to test the method with the comment tag variations I noted above, and began to tout these small variations as a new script method they just "discovered" - whoa, do tell? In fact, a friend of mine that saw a temporary webpage demo I used with the added HTML comment tags, as explained above, said he noticed that I was now using "his" script method - incredible? Since when does a small variation to a method constitute a new method discovery? This would be like me claiming H17's original PB AE comment method when I published my <a href="http://community-2.webtv.net/jaxred/PBMeta/">variation</a> of H17's method that showed how to extend the head tag of a PB AE document for adding additional meta tags, scripts, and styles! I have always credited H17 with first publishing the basic PB AE "conceptual premise" with his comment method; and do so in this tutorial, even though this script method uses different HTML tags than the HTML comment method! I will always credit H17 with the basic premise of the PB AE procedure - blocking the PB built-in body tag code so we can add our own custom body tags. All PB AE methods use this basic premise! <br> <br> And finally, I request that others continue to test this method and promote it's use where appropriate, to increase our knowledge base of PB AE methods! It's a great help to all others when the experts make helpful posts and great webpage tutorials on the many recently discovered PB AE methods! It expands our available options for advanced editing of our PageBuilder webpages!<br> <br> I extend my thanks and appreciation to the thousands of gracious PageBuilder helpers we meet every single day in the NG's! All I present in my tutorials, I learned from the huge knowledge base of others who were gracious enough to share their knowledge with us in the PageBuilder NG's! I urge all PageBuilders to thoroughly explore all new PageBuilder editing methods that are announced in the PB NG's. Write your own tutorials about the new methods, adding your own personal variations and preferences. All of us have widely diversified ideas about the many different ways to do any PB editing procedure - pass your ideas on to others. But, I remind you, as a common courtesy, you should always acknowledge the works of others that you use in your tutorials, and give full credit to others when appropriate!<br> <br> Folks, we are all together in this great PageBuilder adventure. We all learn from, and help each other to the full extent of all the skills and special interests our Creator has blessed us with! All our knowledge is not about any individual or group of persons; but, is the sum total of all our efforts to help each other in our great PageBuilder family. Surely folks, our Lord is pleased with our Works!<br> <br> All of our expert PageBuilders have published may great tutorials on every conceivable PageBuilder editing subject! All the help you will ever need for building PageBuilder webpages is available from the expert's tutorials. Post any PageBuilder editing problem you may have, and search out a tutoral on any subject you need help with in the PageBuilder NG's! You will not only usually get immediate answers to your problem, but many links to great resources that you can use to understand the solutions to your problem. I have published several PageBuilder advanced editing tutorials you may receive help from, which are listed below.<br> <p align="center">My original PageBuilder Advanced Editor tutorial is at:<br> <br> <a href="http://community-2.webtv.net/jaxred/PBMeta/">http://community-2.webtv.net/jaxred/PBMeta/</a><br> <br> And, the webpage with the source code for my original Advanced Editor tutorial with many more additional comments about the PageBuilder Advanced Editor structure, is at:<br> <br> <a href="http://community-2.webtv.net/jaxred/Source/">http://community-2.webtv.net/jaxred/Source/</a></u><br> <br> I also published a tutorial explaining the use of <noscript> tags for a PageBuilder Advanced Editor method, at:<br> <br> <a href="http://community-2.webtv.net/jaxred/noscript/">http://community-2.webtv.net/jaxred/noscript/</a><br> <br> I also published two PageBuilder Advanced Editor Multipage document tutorials. The first PB AE Multipage document tutorial uses the comment tags method and is at:<br> <br> <a href="http://community-2.webtv.net/jaxred/Test/">http://community-2.webtv.net/jaxred/Test/</a><br> <br> The second PB AE Multipage document tutorial uses the noscript method and is a more thoroughly explained procedure that beginning PageBuilders can easily understand. Also, both these multipage document methods can be used as guides for other multipage documents using any other advanced editor method Ц just substitute the AE tags of your favorite method where I use the comment tags and noscript tags in these tutorials. Check it out at:<br> <br> <a href="http://community-2.webtv.net/jaxred/NSMulPge/">http://community-2.webtv.net/jaxred/NSMulPge/</a><br> <br> And, recently I published a demo tutorial on seven (7) new PB AE methods, that uses various other HTML tags, at:<br> <br> <a href="http://community-2.webtv.net/jaxred/misc_ae/">http://community-2.webtv.net/jaxred/misc_ae/</a><br> <br> I also recently published a PB AE tutorial using a CSS style sheet for body tag style code in an expanded head tag, at:<br> <br> <a href="http://community-2.webtv.net/jaxred/style1/">http://community-2.webtv.net/jaxred/style1/</a><br> <br> Recently two of our fellow PageBuilders, <a href="mailto:SolarBunny@webtv.net">SolarBunny@webtv.net</a> and <a href="mailto:ctpaso@webtv.net">ctpaso@webtv.net</a>, collaborated on a new PB AE method that works with the latest MSN-TV browser 2.7 upgrade, and upgrades 2.5.5 and earlier, that is very simple to use. This PB AE method will not work with upgrade versions 2.6 and 2.6.1. I wrote a short tutorial on this method, at:<br> <br> <a href="http://community-2.webtv.net/jaxred/SimPBAE/">http://community-2.webtv.net/jaxred/SimPBAE/</a> <br> <hr><br> <br> Thanks for visiting my webpage, folks! I hope you received some helpful information that can make your PageBuilder webpage advanced editing more enjoyable and productive! Have a nice day, my friends! My best wishes to all PageBuilders, their families, friends, and neighbors!</p> </TD></TR></TABLE> </P> <P> <TABLE> <TR><TD> <P ALIGN=left> <p align="center"> <a href="mailto:jaxred@webtv.net?subject=PB%20AE%20Script%20Method%20-%20"> <font size="7">Jax</font> <font color="red" size="7">Red</font> </a> <hr width="22%"> </p> <p align="center"><form method="post" action="http://www.thunderstone.com/texis/demos/dox?demo=http://community-2.webtv.net/jaxred/script/"> <font color="#ffffff">View the <input type="submit" name="demo" value="Source Code" onClick="form.submit()" borderimage="file://rom/borders/buttonborder3.bif" usestyle> of this webpage with the Thunderstoneй WebTVЩ Source Code Viewer. Put a "Source Code" <a href="http://community-2.webtv.net/jaxred/Viewers/"> <u>Viewer</u> </a> on your webpages.</font> </form> </p><p align="center"><a href="http://www.wunderground.com/US/FL/Jacksonville.html"><img src="http://banners.wunderground.com/banner/gizmotimetempbig/US/FL/Jacksonville.gif" alt="Click for Jacksonville, Florida Forecast" height=40 width=467></a><br><a href="http://www.wunderground.com/about/faq/weathersticker.asp"> <font size="3" color="#ffd700">й 2000 The Weather Underground, Inc.</font> </a> </p> <p align="center"> <table width="80%"> <tr> <td align="center" valign="center"> <FONT SIZE="3" COLOR="#ffd700"> <b>Site<br>Visitors</b> </FONT> </td> <td align="center">  <A HREF="http://www.beseen.com/hc-index.html"> <IMG SRC="http://pluto.beseen.com/hit.counter?account=556146&font=BlackOnWhite&base=0" BORDER="0"> </A>  </td> <td align="center" valign="center"> <FONT SIZE="3" COLOR="#ffd700"> <b>Since<br>04/20/00</b> </td> </tr> </table> </p> <HR> <BR> <center> <FONT SIZE="4" COLOR="#ffd700"> <b>Thanks For Visiting My Site, Folks!</b> </FONT> </center> <br> <br> <HR WIDTH="62%" ALIGN="CENTER"> </TD></TR></TABLE> </P> <table border="0" cellpadding="0" cellspacing="2" width="100%"> <tr height=0> <td height=0> <spacer type=block width=30% height=0> <td height=0> <spacer type=block width=30% height=0> <td height=0> <spacer type=block width=30% height=0> </tr> <tr> <td colspan="3"> <hr> </td> </tr> <tr> <td valign=middle width=30%> <font face="Arial,Helvetica,Geneva,Swiss,SunSans-Regular"> <b> </b></font></td> <td valign=middle width=30%> <center> <font face="Arial,Helvetica,Geneva,Swiss,SunSans-Regular" size=-2><I> <a href="http://www.msntv.com">Powered by MSN TV</a> </I></font></center> </td> <td align=right valign=middle width=30%> <font face="Arial,Helvetica,Geneva,Swiss,SunSans-Regular"> <b> </b></font></td> </td> </tr> <tr> <td colspan="3"> <hr> </td> </tr> </table> </BODY> </HTML>