So how much pain am I in for?

G

Guest

Can no longer publish our fp web to Linux server so boss says get
Dreamweaver......oh yeah and can you have everything published by Monday.

I've never used Dreamweaver, don't know html or css but have used FP for
years. Currently using 2003.

What kind of problems should I expect when I try to import fp pages into
dreamweaver to work on them? Will my photogallery work? Shared borders?

It's gonna be a long weekend. :(
 
T

Thomas A. Rowe

Why can't you use FP to publish?
--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage
==============================================
Agents Real Estate Listing Network
http://www.NReal.com
==============================================
 
M

Murray

I've never used Dreamweaver, don't know html or css but have used FP for
years. Currently using 2003.

You need to start reading about HTML first, and then CSS. Without a basic
understanding of those technologies, Dreamweaver will be a journey from one
mysterious problem to another, since it removes all of the "wizard cloaks'
that are present in FP.
What kind of problems should I expect when I try to import fp pages into
dreamweaver to work on them? Will my photogallery work? Shared borders?

For sure, your shared borders will no longer work, and perhaps your
photogallery, depending on what you have used. Nothing that uses FP SE's
will work - you will need to find ways to re-implement those in DW. In
addition, FP themes will not work, either. Here's what I tell people on the
DW forum when they want to work on an FP site ================

Before doing anything else, take a couple of weeks to gothrough the DW
tutorials, and also to study HTML and CSS. The more you know about those,
the easier your transition will be. DW expects alot more from you than FP
did, and as a result, you may find it much more frustrating to have the raw
reality of web development staring you in the face rather than the wizards
of FP.
Is there a way to convert a Frontpage site into a
Dreamweaver site

1. I'd define a Dreamweaver site that points to a location on your hard
drive for the local site's root, and to the current FP site on the web as
the remote site
2. I'd use Dreamweaver (if your host supports FTP connections) to download
the remote site to the root of the site you just defined on the hard drive.
This will pick up all the pages *after* webbot action so that shared borders
and all are already present in the page HTML. This will also pick up all of
the server scripting. Note - in the event that you are not able to connect
using FTP since some FP hosts block that protocol, you will have to use a
third party 'site copier' like Black Widow, QuadSucker, or WebCopier, (or
even the DW extension called SiteAssist from WebAssist) to connect and
download using http protocols. Doing it this way will *not* retrieve any of
your server-script code, if any (unless you have used the WebAssist
extension).

3. I'd create a DW template for the pages, that captures the "shared
border"
effect you had in FP.
4. I'd copy and paste content from each FP pages to a new template child
page and then save the new child page with an easily identifiable
nomenclature that is distinct from what was used on the FP site (since you
are saving the new child pages into the same local site as the FP pages).
5. When the basic site is completed, I'd upload the new DW pages to some
staging area/webspace, and by using the browser, I'd verify that the site
(as it now exists remotely) is complete.
6. Then I'd create a *new* DW site in a new location on the hard drive, and
connect to and download all the files from the staging site.
7. You can now delete the original FP site from your local system if you
want.

You now have a complete site (minus any of the FP extension server-side
code) that has no FP footprint.

If you have used any FP server extension functions on the original FP site
(form processing, guestbooks, tables of contents, etc.), you will have to
recreate those functions in DW using 3rd party scripts, or scripts that you
write yourself.
 
T

Tom Willett

It's gonna be a very loooooooooooooong weekend. And it won't be a two-day
weekend ;-)
--
===
Tom Willett
Microsoft MVP - FrontPage
---
FrontPage Support:
http://www.frontpagemvps.com/
===
|> I've never used Dreamweaver, don't know html or css but have used FP for
| > years. Currently using 2003.
|
| You need to start reading about HTML first, and then CSS. Without a basic
| understanding of those technologies, Dreamweaver will be a journey from
one
| mysterious problem to another, since it removes all of the "wizard cloaks'
| that are present in FP.
|
| > What kind of problems should I expect when I try to import fp pages into
| > dreamweaver to work on them? Will my photogallery work? Shared
borders?
|
| For sure, your shared borders will no longer work, and perhaps your
| photogallery, depending on what you have used. Nothing that uses FP SE's
| will work - you will need to find ways to re-implement those in DW. In
| addition, FP themes will not work, either. Here's what I tell people on
the
| DW forum when they want to work on an FP site ================
|
| Before doing anything else, take a couple of weeks to gothrough the DW
| tutorials, and also to study HTML and CSS. The more you know about those,
| the easier your transition will be. DW expects alot more from you than FP
| did, and as a result, you may find it much more frustrating to have the
raw
| reality of web development staring you in the face rather than the wizards
| of FP.
|
| > Is there a way to convert a Frontpage site into a
| > Dreamweaver site
|
| 1. I'd define a Dreamweaver site that points to a location on your hard
| drive for the local site's root, and to the current FP site on the web as
| the remote site
| 2. I'd use Dreamweaver (if your host supports FTP connections) to download
| the remote site to the root of the site you just defined on the hard
drive.
| This will pick up all the pages *after* webbot action so that shared
borders
| and all are already present in the page HTML. This will also pick up all
of
| the server scripting. Note - in the event that you are not able to
connect
| using FTP since some FP hosts block that protocol, you will have to use a
| third party 'site copier' like Black Widow, QuadSucker, or WebCopier, (or
| even the DW extension called SiteAssist from WebAssist) to connect and
| download using http protocols. Doing it this way will *not* retrieve any
of
| your server-script code, if any (unless you have used the WebAssist
| extension).
|
| 3. I'd create a DW template for the pages, that captures the "shared
| border"
| effect you had in FP.
| 4. I'd copy and paste content from each FP pages to a new template child
| page and then save the new child page with an easily identifiable
| nomenclature that is distinct from what was used on the FP site (since you
| are saving the new child pages into the same local site as the FP pages).
| 5. When the basic site is completed, I'd upload the new DW pages to some
| staging area/webspace, and by using the browser, I'd verify that the site
| (as it now exists remotely) is complete.
| 6. Then I'd create a *new* DW site in a new location on the hard drive,
and
| connect to and download all the files from the staging site.
| 7. You can now delete the original FP site from your local system if you
| want.
|
| You now have a complete site (minus any of the FP extension server-side
| code) that has no FP footprint.
|
| If you have used any FP server extension functions on the original FP site
| (form processing, guestbooks, tables of contents, etc.), you will have to
| recreate those functions in DW using 3rd party scripts, or scripts that
you
| write yourself.
|
|
| --
| Murray
| --------------
| MVP FrontPage
|
|
| | > Can no longer publish our fp web to Linux server so boss says get
| > Dreamweaver......oh yeah and can you have everything published by
Monday.
| >
| > I've never used Dreamweaver, don't know html or css but have used FP for
| > years. Currently using 2003.
| >
| > What kind of problems should I expect when I try to import fp pages into
| > dreamweaver to work on them? Will my photogallery work? Shared
borders?
| >
| > It's gonna be a long weekend. :(
|
|
 
R

Rob Giordano \(Crash\)

If you've never used DW tis gonna be a long weekend...buy some beer...it
won't help get the site converted but may lessen the pain.

It's NOT a realistic deadline.



| Can no longer publish our fp web to Linux server so boss says get
| Dreamweaver......oh yeah and can you have everything published by Monday.
|
| I've never used Dreamweaver, don't know html or css but have used FP for
| years. Currently using 2003.
|
| What kind of problems should I expect when I try to import fp pages into
| dreamweaver to work on them? Will my photogallery work? Shared borders?
|
| It's gonna be a long weekend. :(
 
P

P@tty Ayers

...you may find it much more frustrating to have the raw reality of web
development staring you in the face rather than the wizards of FP.

Eloquently said, Murray! :) And that's the essence right there.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top