Whether you prefer developing in ASP, PHP or Colfusion, Adobe Dreamweaver and the WebAssist Super Suite extensions can turn an ordinary website into a dynamic database-driven workhorse that rivals those from professional developers costing tens of thousands of dollars.

Super Suite extensions for Dreamweaver

Just like a professional carpenter, the right set of tools can make all the difference in the finished product. In Dreamweaver, having the right set of extensions can not only allow you to build more extensive, usable websites, but they can also save you an immense amount of development time and frustration.

WebAssist Super Suite gives you The Power to Build Anything

The Super Suite extension package covers everything from website security, user administration, user login, site cookies, sessions, database administration, email processing, dynamic dropdowns, a full ecommerce shopping cart, a website import tool, Eric Meyer's CSS Sculptor, a full-featured text editor, dynamic Flash charts, dynamic Google map integration and a whole lot more!

Database-driven websites, e-commerce and more

The Super Suite set of extensions gives Dreamweaver users the tools to create every facet of a functional content management system, full featured forums with access-level rights, complete website database administration tools including search, add, edit, update and delete fuctions, full digital file upload and download features, and a complete ecommerce shopping cart system with fully customizable storefronts. All this is achieved through an extremely easy-to-use wizard interface which walks you through each step in simple, intuitive fashion.

Easy-to-use Dreamweaver wizard interface

Super Suite can be easily integrated into your current site Dreamweaver template. The wizards take you through the steps needed to configure your options, you choose your template, and Super Suite creates all necessary pages, navigation, recordsets, CSS and javascript. You simply upload the new pages and files to your server, and the new functionality is live, with the look and feel of your existing website.

Create advanced Dreamweaver websites without knowing any code

WebAssist Super Suite extensions are perfect for Dreamweaver users who are hesitant to dig into the code. The extensions create all the code for you, and you can easily return to the wizard at any time to make changes. Super Suite has some similar functions to Adobe Dreamweaver Developer Toolbox, but it includes one-of-a-kind extensions like the iRite WYSIWYG editor for integrating FCKeditor into your Dreamweaver websites, CSS Sculptor which allows you to create complete standards compliant websites in one easy operation, and Site Import which allows you to import complete websites including all HTML, CSS, script, Flash and image files onto your local drive.

Advice from a Super Suite user

As a Super Suite user, I have used all their extensions extensively in my client websites. The ease-of-use and the Dreamweaver integration make them a must-have extension bundle if you want to develop websites faster, create more intuitive and complex websites, and make more money as a website designer or developer.

Adobe Dreamweaver Compatibility

The WebAssist Super Suite package is an all-inclusive Dreamweaver toolkit which provides developers with all the necessary tools to make dynamic database-driven websites in Adobe Dreamweaver. The extensions are compatible with Dreamweaver 8 and Dreamweaver CS3 on both PC and Mac. PHP, ASP and ColdFusion are supported by all the extensions.

Some working knowledge of J2EE or JSF is assumed for this article.

Like some of you I've been frustrated with this technology known as JSF or Java Server Faces. There are several different flavors out there that are built on the shoulders of JSF. For instance Oracle's ADF (Application Development Framework). Oracle ADF Faces Components is a set of over a 100 JSF components that let you build a richer user interface for your Java EE applications. Oracle ADF Faces also includes many of the framework features most needed by JSF developers today.

That is great, and in many ways it will make life easier to develop in a JSF environment. Some items you will find available in these "add on" packages have a real benefit. For instance, as of the date of this article, I was very surprised that a File Upload is a feature still not implemented in JSF in respect to using natural jsf tags. There are ways to accomplish this task in JSF but they are not native JSF approaches. The process is a "no brainer" in just about every other framework available today, including asp.net.

Another simple task (I thought) was having a data table present the results of a query in an editable format. Possibly to update a user record or shopping cart. After working in other technologies it was very efficient to return a result set to a data table object and let that object take care of some of the trivial behaviors and characteristics of the table itself. When I started exploring JSF I was frequently and at every turn becoming more and more frustrated in trying to duplicate some of the most basic of processes similar to managing records through data tables.

There are not a whole lot of resources out there yet on JSF although it is growing steadily, and I found that all too often the resources that I was finding on the internet either didn't apply to the more simple tasks or the information was just completely wrong. One example of that was that it was stated in one article I read that you cannot use command buttons inside of a JSF data table. The recommendation was to use JSF hyperlinks instead when trying to perform an action from a data table due to a bug in the framework that prevented command button actions to fire if the button resided inside of a data table.

At first I thought "you've got to be kidding me"! Then I remembered that I've been finding a fair amount of "bogus" information in regards to JSF development so I decided to do further research and discovered that information to be less than accurate as well.

I simply had to find a way to populate a data table through a result set and get a command button to fire an action and pass all of the data in the data table to the backing bean to update the record. Multiple command buttons would exist as well as hidden fields pertaining to id numbers and so forth. Pretty basic stuff and we've all done it before with relative ease.

It turned out that the solution was in fact a simple one. "Binding". You've heard about it and read about it. But this approach was something a little different as far as I could find.

Many of the blogs and articles that I read dealt with passing the values as parameters and following the steps to define the parameters in faces.config files etc., then retrieving the parameters in a backing bean. Processing the passed data required another set of procedures to utilize mapping to each of the field parameters passed and then processing could begin.

That seemed like a whole heck of a lot to me just to retrieve form data. Then it occurred to me that I should be able to "bind" a text field component on a page to a backing bean. Once it is bound then all I have to do is extract the data. And that's all there is to it. My query returned results and pre-populated a data table including text fields with the values of the query pre-populated in the text fields.

Each one of those text fields was bound to a "HtmlInputText" type in my backing bean. It was not a String type like other approaches define. Doing that does require you to map parameters and populate that String variable through your set methods once the form is submitted.

What I found is that if I bind my text field to a property of text field type that it solved my problem of passing values from a data table, and I didn't have to define parameter fields anywhere in any xml file. Now that I had that figured that out I needed to figure out how to get the value of that property that I've bound my form field to, well why not getValue()?

I personally hadn't seen any examples online or in books for retrieving the value from a form binding it to the type of form element it was and simply use the getValue() to pull out the value of the object. Used like this getParameterFromForm().getValue().

Let me clarify that I am NOT saying that trying this approach isn't documented anywhere, I find it hard to believe that I've had some stroke of genius that no one has had before in the world of java, especially since I'm coming from .NET and ColdFusion.

After doing that I no longer had any problems passing form data to my backing bean. I was able to dynamically populate data tables with any number of records including any number of command buttons within that data table and I didn't have to concern myself with remembering to define parameters in any other areas of the application.

So put simply you can bind your form fields to properties of the same type in your backing bean, and then extract the value of that object using getValue() if you prefer over utilizing parameter string mapping and similar approaches for processing form data. I found it to be easier and less time consuming which has costs associated to it as well.

There are many factors that you need to consider when hiring a webmaster, you need to ensure that you will get customer satisfaction as well as good value for money. You would hate to choose an inexperienced webmaster who cannot meet your requirements because you would have to go through the whole process again to get the job done. It means if you made any partial payment you may lose that which will then lower your budget when looking for another webmaster.

Firstly you have to identify the places that you can find these talented webmasters who have the skills to complete you job. There are many relevant forums such as DigitalPoint, WickerFire and Web Talk Forums where you will be able to post exactly what you need and people who are capable will get in contact stating a price if you haven't set a maximum budget. Aside from the forums there are specific websites that aims to connect freelances with clients so that you can get all your work done much easier and in a timely manner. You could also ask your friends and family to see if they have been in the market in the past for something similar and found a reliable good webmaster, this will also take a lot of the risks out because you know that they are here to make a living and not out to scam unsuspecting people.

If you are going to search the forums or websites for a webmaster you should be very cautious about what you state in your thread and make sure you don't miss any important information out that may prolong the process.

This is the kind of information you should always state when creating a project on a forum or freelance website:

• Exactly what you need doing, try to include as much detail as possible as it will make it easier for the webmaster to quote you an accurate price. It will also prevent the conversation in between telling the webmaster what they need to do. If you can do this successfully they should have everything they have to get started as soon as you accept the quote.
• Deadline, one of the most important things for a webmaster is to know the maximum deadline. This will also remove the factor of them having to rush a job to get it done to an unexpected deadline because if the webmaster was to miss any deadlines it will look bad from their side which may deter many other people from using them in the future.
• Maximum budget, this is quite important in the fact that it will eliminate any webmasters that charge over your budget so is well worth putting into the pitch somewhere.
• Any additional information that you feel will be beneficial to the chosen webmaster.

After you have set your project up you will get overwhelmed with responses and quotes from people who believe they are capable of meeting your requirements. You then have to go through the responses one by one to see if anyone stands out from the crowd, your budget will be a major deciding point at this stage because if anyone has quoted an amount over your budget you can discard that right away.

You should always ask for samples of previous work so that you will be confident in your decision and don't choose anyone that is simply after your money. Any reputable webmaster will have a portfolio showcasing their talents and strengths ready for you to take a look at. Each forum or website will have a rating system in place so you can see how successful they have been since starting as a freelance webmaster. Take a look at their history and feedback to see what comments past customers have left as this will be the only information you can rate them on.

When you have found the webmaster you want to take on, the next step is to arrange payment. Many people will require a 50% upfront or a deposit of some sort to show the webmaster that you are serious about this and want the working doing. If you are new to the freelance website/forum you will not have built any reputation or feedback so they may request full payment upfront to secure the job. Check their feedback before you make any payments but if it seems to be 100% positive then everything should run smooth.

You can use payment methods such as escrow or paypal to make things a little safer as if you don't get what was promised you can file a charge back and have a good chance to get some, if not all of your money back. Try to build a good reputation on these websites so that in future if you need any work doing it will be a lot easier to have a smooth transaction.