- Platform: Windows 2000 / XP
- Media: Software
- Item Quantity: 1
Product Details
|
FrontPage 2003 is a substantial improvement on earlier versions. The editor is well behaved, preserving hand-coded script or HTML code and a new split-view makes it easy to work with both the visual design and the underlying text. Strong new features include table-based layout tools, the ability to create a page design by tracing an image, nested or overlapping layers, better use of Cascading Stylesheets and templates that let you lock some content while making other parts of the page editable by other team members. Coding is enhanced by a quick tag editor and Intellisense statement completion. Flash movies are fully supported and there are tools for the easy display of XML data. There is also special integration with SharePoint services running on Windows 2003 Server, making FrontPage 2003 the natural choice for creating SharePoint intranets. FrontPage 2003 is a feature-rich product which enables good results without requiring knowledge of HTML, while also providing strong support for those who prefer to work with the underlying code. --Tim Anderson
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
Having said that, FrontPage 2003 is a great step in the right direction. Here are my feelings, broken down:
Site Management
Site Management has improved in FrontPage 2003, although the most bang for the buck will be Enterprise users who have decided to use SharePoint Portal Server in their organization. Much of the new data functionality relies on SharePoint. What this means is FrontPage 2003 gives a lot more power for those in the Microsoft world. Note that it is still backwards compatible with frontPage 2002 extensions, for those without SharePoint.
Behaviors
Much of the work in this area is like Dreamweaver and it is a mixed bag. On the positive side, behaviors are more flexible in FrontPage; on the negative, there are still many missing from FrontPage. The major behaviors are there, however, so I would give FrontPage a plus here.
Intellisense and coding
Microsoft has always lead the charge in this area and FrontPage is no exception. The Intellisense in FrontPage 2003 extends into ASP and ASP.NET code. For developers interested in altering the code created, everything is accessible. The death of FrontPage extensions are the reason, so those with backward compatible sites will have to deprecate some features if they use webbots. The small price is well worth the gain.
CSS
FrontPage has much greater support for CSS than previous versions, and is especially useful for those who like to work with graphical tools or those who like to work with code. The tag explorer, in Dreamweaver, wins for those who sit in the middle, however.
HTML Editing
The ability to go back and forth from code to design and retain positioning is a real godsend. This feature exists in Dreamweaver, as well, so it is not as stellar as some of the other tools. One of the nicest tools is the tag explorer, that allows you to see the nesting of your currently selected tag and easily navigate up and down the tree. In addition, there is a code editor that lets you isolate on a specific tag and use Intellisense to code its attributes. There is also a tool that allows you to quickly find a closing tag, which is a godsend for any developer working with nested HTML tables.
Themes and templates
Themes are much more easily edited in FrontPage 2003, which allows designers to alter templated sites to make nice looking custom built sites very quickly. FrontPage also has the ability to create "master page" style templates which are, possibly a surprise, fully compatible with Dreamweaver MX.
That pretty much covers the major features. Overall, I like the FrontPage methodology of using a side pane that focuses on the task at hand over Dreamweavers sliding tool palette, although I know people that are more fond of the Dreamweaver IDE.
One of the biggest benefits I have seen of FrontPage 2003, in the FrontPage/Dreamweaver battle, is Dreamweaver's tendency to lock up the OS when working on files on a shoddy network connection. As this does not apply to as many users, it is not reason enough to shy away from Dreamweaver. As I use both, I do not want to shy away from either, but here is how I would stack it up.
FrontPage wins with its table designer, Intellisense, coding aids (esp. ASP.NET) and flexibility in behaviors. Dreamweaver still wins with the number of eye candy features, strength of its added CSS tools and its flexibility in coding models (nice for developers who work in more than one language - Java, ColdFusion, ASP and ASP.NET included).
But why is that a problem with FrontPage? It handles CSS well, and the editor is darned easy to use, far easier than Macromedia Studio MX. But if your ISP server doesn't employ Frontpage Extensions (and many of them don't) then uploading pages created in Frontpage can be difficult if not impossible. However, for the average user, I have to say that FrontPage is the web designer of choice. It's far easier to get running than Macromedia, which really is not intuitive. FrontPage is intuitive, and most people will have excellent success right out of the box. Just watch out for the extension support when you choose a web space provider.