Re: web development tools-Dreamweaver vs. Frontpage 2003

From: Kevin Spencer (kspencer_at_takempis.com)
Date: 11/12/04 

Date: Fri, 12 Nov 2004 11:35:09 -0500

> The single best feature in FP is site management
> - especially live online thru http

I've got to agfree with you there Stefan. There are quite a few software
packages for editing HTML. But FrontPage is probably the best in terms of
managing web sites. 

-- 
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Neither a follower
nor a lender be.
"Stefan B Rusynko" <sbr_enjoy@hotmail.com> wrote in message
news:Oyt5$3MyEHA.3844@TK2MSFTNGP12.phx.gbl...
> The single best feature in FP is site management
> - especially live online thru http
>
> Agree
> The webbots are tools for those that don't know how to do it
> - just as DW "tools" don't do anything an experienced developer can't do
w/ notepad if needed
>
> -- 
>
> _____________________________________________
> SBR @ ENJOY (-:              [ Microsoft MVP - FrontPage ]
> "Warning - Using the F1 Key will not break anything!"  (-;
> To find the best Newsgroup for FrontPage support see:
>   http://www.net-sites.com/sitebuilder/newsgroups.asp
> _____________________________________________
>
>
> "Murray" <forums@HAHAgreat-web-sights.com> wrote in message
news:%23LW1%23HMyEHA.3368@TK2MSFTNGP15.phx.gbl...
> | > There are things you can do in FrontPage that
> | > you can't do in Dreamweaver, and vice versa.
> |
> | To be fair, I would say it this way -
> |
> | There are things that FP does "automatically", or via the intervention
of
> | some wizard, that must be done manually (or via the intervention of some
3rd
> | party script) in Dreamweaver (examples would be guestbooks, form
processing,
> | slide shows, etc.).  To be truthful, most of these things are things
that
> | *I* would want to do manually anyhow, but that's not really fair,
because I
> | *know* how to do them already. 8)  Some of them are things that you can
find
> | 3rd party extensions for (a concept similar to the FP design-time
> | extensions).
> |
> | In general, wizard code is fragile code, in my experience....
> |
> | -- 
> | Murray
> |
> | "Kevin Spencer" <kspencer@takempis.com> wrote in message
> | news:uqDM7$LyEHA.4004@tk2msftngp13.phx.gbl...
> | >> If the outside developer spices up our
> | >> web site with drop-down menus and mouse-over effects, will Frontpage
> | >> still
> | > be
> | >> able edit the code created with Dreamweaver.
> | >
> | > It depends on what the code IS, and what the code DOES. If your site
uses
> | > a
> | > lot of FrontPage proprietary components, esp. Themes, Shared Borders,
> | > Naviagation, etc., you are pretty well stuck with FrontPage. On the
other
> | > hand, many FrontPage web sites don't use these proprietary
conveniences,
> | > and
> | > can be worked on with virtually any toolset.
> | >
> | >> Are there any incompatiblity
> | >> issues with a web page created by Dreamweaver and Frontpage edits.
> | >
> | > Same answer.
> | >
> | >>Our major
> | >> concern is that the handful of resident web authors will need to be
> | >> re-trained with Dreamweaver. My understanding is that Frontpage can
do
> | >> anything that Dreamweaver can. Is this correct?
> | >
> | > HTML is HTML. Some web components in FrontPage are proprietary, but
> | > anything
> | > that isn't can be manipulated in either program. As to FrontPage being
> | > able
> | > to do anything that Dreamweaver can do, well, again, we have to
> | > differentiate between common HTML and things like proprietary
components,
> | > server-side programming, etc. There are things you can do in FrontPage
> | > that
> | > you can't do in Dreamweaver, and vice versa. But the bulk of a web
site is
> | > simply HTML.
> | >
> | > -- 
> | > HTH,
> | > Kevin Spencer
> | > .Net Developer
> | > Microsoft MVP
> | > Neither a follower
> | > nor a lender be.
> | >
> | > "lkhntr" <lkhntr@discussions.microsoft.com> wrote in message
> | > news:D7E5EBE0-160C-41AB-AAD7-5B99A8C9C787@microsoft.com...
> | >> Please advise on any difference between Macromedia Dreamweaver and
> | > Microsoft
> | >> Frontpage. We have a situation where an outside developer is wanting
to
> | > use
> | >> Dreamweaver to spice up our website. If the outside developer spices
up
> | > our
> | >> web site with drop-down menus and mouse-over effects, will Frontpage
> | >> still
> | > be
> | >> able edit the code created with Dreamweaver. Are there any
incompatiblity
> | >> issues with a web page created by Dreamweaver and Frontpage edits.
Our
> | > major
> | >> concern is that the handful of resident web authors will need to be
> | >> re-trained with Dreamweaver. My understanding is that Frontpage can
do
> | >> anything that Dreamweaver can. Is this correct?
> | >
> | >
> |
> |
>
>
Loading