Designing a Web Site using htmlAreaby Peter Lavin Originally published at DevArticles OverviewIf you wish to develop a web site that others can contribute to one option is to have text files sent as e-mail attachments, convert these to HTML and then upload the file. There is a better way. If the people making submissions to your site are capable of using a word processor then things can be done much more efficiently. This article will show you how to use a free component called htmlArea and a database to handle the addition and display of content on your web site. Some knowledge of HTML, databases and server-side scripts is assumed. IntroductionhtmlArea is a free WYSIWYG (what you see is what you get) editor created with Javascript. It can replace "textarea" fields in a web page and using it is akin to using a word processor. Text can be manipulated by using buttons on a toolbar and options in "select" controls. Foreground and background colours may be changed, images inserted, fonts adjusted – all manner of text manipulation that you might expect from a word processor. When any changes are made to text the appropriate HTML code is inserted. Press the "enter" key and a paragraph tag will automatically be inserted, the space bar and a non-breaking space is inserted. A toggle button is provided that allows you to view the HTML source. You may also expand the control and open it in a separate window. This item is available for free and may be downloaded from http://www.htmlarea.com/. - no strings attached and no trial period. You can even customise it if you want to. However, before going any further you should be aware that this component works only in Internet Explorer Version 5 or higher. This does not mean that your HTML code will not function if viewed in Netscape. It simply means that textareas will appear as textareas and not be replaced by an htmlArea. A beta version with cross-browser functionality is in the works but still lacks documentation. htmlArea is a very attractive and powerful component but it's only useful if its contents can be saved. This article will describe how to install this control and how to save and retrieve the HTML files that are created. Our solution will be implemented using PHP and MySQL though the principles will apply to any relational database and any server-side scripting language. Download and InstallExcellent installation instructions are provided by interactivetools at their site so follow them and install htmlArea. However, there is one change you will probably want to make. If you follow the instructions given in the link above, you will need to place any page that uses htmlArea in the "htmlarea" directory. It is much more likely that you will want to access this control from a page in your server's root directory. To do so change the line of code that reads, _editor_url = ""; to _editor_url = "htmlarea/";. You can embed an htmlArea control that will work from your root directory using the following code:
Save this code, upload it to your server's root directory and try it out. If you've done everything correctly you should see an htmlArea in place of the textarea named "contents". Try out the various features and see what it is capable of. Database TableLet's define the database table that will store the contents of an htmlArea. We'll name the table "items" and give it the following structure:
A few more fields than you imagined perhaps but they all do serve a purpose. The "id" field will be a unique identifier and should probably be "auto_increment" type. "title" and "author" are self explanatory and "contents" will hold what's typed into the htmlArea. The ‘whenadded' field is a ‘timestamp' data type so it will record the date and time that a record is added. Depending upon your needs, the ‘reviewed' field may or may not be necessary but it will allow you to vet content before it is posted to your site. For instance, a where clause in your SQL such as, "WHERE reviewed =1", would keep items not yet reviewed from showing up on your site. Saving ContentI don't intend to discuss here how a form is submitted from a web page. If you've read this far you probably know how to do this anyway. If not there are plenty of online tutorials available on this subject. Let's assume that our htmlArea control is part of a "form" and the "action" attribute has been set to a file in the current directory called "processform.php". For the sake of clarity, the topics used in the select control below have been hardcoded. In real-life these would most likely be created dynamically (or perhaps in this case magically) from a database. The HTML code for the form in your web page might look like the following:
The "textarea" named "contents" will become an htmlArea control but will not appear differently in the source code. When this form is submitted it does not need to be handled in any special way. Any formatting done by the user will be captured as HTML code in your database. Just as your form does not require any special coding nor does your server-side script.
Again, for the sake of simplicity, we have used a literal for the value of the variable "$user" and have not verified any of the data submitted. Also, functions to open the database are not shown but are assumed to be in the "dbfunctions.inc" file. How to Display the Saved ContentsThe contents will have been saved with the appropriate HTML code and when retrieved will need to be integrated into an HTML page. Assuming a hyperlink such as the following;
<a href="gettext.php?itemnumber=7">About
Hermione</a>,
the contents might be retrieved and displayed using the following "gettext.php" file :
You'll probably want to lay out your page in a more attractive fashion but the above code shows you how any formatting added by the user has been saved to the database and retrieved exactly as the user entered. ConclusionWe have seen how the combination of htmlArea and a database can greatly simplify adding content to a web site. This control converts a textarea into a "word processor" giving the user the freedom to format text as (s)he sees fit and it frees the webmaster from having to mark up text. You can cut out the middle man and have content added directly to your site. About the AuthorPeter Lavin runs a Web Design/Development firm in Toronto, Canada. He has been published in a number of magazines and online sites, including UnixReview.com, php|architect and International PHP Magazine. He is a contributor to the recently published O'Reilly book, PHP Hacks and is also the author of Object Oriented PHP, published by No Starch Press. Please do not reproduce this article in whole or part, in any form, without obtaining written permission. |
||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||
| top |
Copyright © 2013 softcoded -
the Toronto web design & development company |
|||||||||||||||||||||||||||