how to capture online content into FW site?

I I have a site up which was created with an earlier version of FW on a PowerPC Mac, which was stolen. My new version of FW on an Intel Mac can’t open the files - how can I download or copy or capture my pages online into a new site file on my computer?
Any ideas
(cross posted in Dynamo forum … not sure which is more appropriate)


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Hi,

Your best bet is following these instructions.

www.softpress.com/kb/article.php?id=207

(Do you know what version of FW was on your PPC Mac? I would think that the current version could open more than just v3.)


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thanks Joe. I appreciate the ref. I’ll do that, although I was hoping for a quicker “grab” option since the web site in question is around 60 pages long.

Guess I’ll just get busy!

thanks,


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Try this app - Site Sucker
http://www.sitesucker.us/home.html

You’ll at least be able to get all the HTML and graphics files in a neat package… It’s donation-ware so if you really use it and like it…

Too bad that new FW revs don’t support their own old files - not even through an "import’ routine. It’s a scary thought to have to rebuild entire sites from scratch to keep up with version changes. Hope that’s the last of that?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Sometime around 18/1/08 (at 18:36 -0500) igirl said:

Try this app - Site Sucker
http://www.sitesucker.us/home.html

You’ll at least be able to get all the HTML and graphics files in a
neat package… It’s donation-ware so if you really use it and like
it…

And of course any FTP client will let you download the entire site,
including uploaded but unused content that tools such as Site Sucker
won’t be able to see. But Site Sucker can be used to capture sites
without having FTP access details.

Too bad that new FW revs don’t support their own old files

Just to make sure we all know the score, Freeway is able to open
older Freeway documents. What it doesn’t do is import HTML
documents, at least not very well.

What you have to keep in mind is that the HTML pages that you publish
with Freeway are equivalent (in a sense) to the printed pages that
you make with InDesign or QuarkXPress. You wouldn’t expect to be able
to import that sort of output into the originating program. Even an
exported PostScript file isn’t going to allow you to regenerate your
original page layout document in InDesign or QuarkXPress. Freeway
doesn’t work ‘in’ HTML, that’s simply the final output that it
exports, so that needs to be seen in that light.

The HTML output is a frozen, detail-light, non-rich snapshot of the
rich, flexible, malleable layouts that are your Freeway documents.
You can never reverse engineer something that’s such a boiled-down
construct back into the multiple-layered whole that was put together
to generate it.

I too wish it was possible to import existing HTML pages, but I know
that there are so many issues to do with this that it is unlikely to
happen. There is a basic import feature, but it is very basic; it
isn’t likely to be much help at all.

Backups are the answer for the situation originally described. And
sympathy, although that doesn’t provide any material help.

k


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I was told by FW techs that since the original site was created with FW on a PowerPC Mac, the newer FW version running on my newer IntelMac couldn’t read it. PPC FW won’t talk to Intel FW apparently


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 19 Jan 2008, at 19:36, STEPcoach wrote:

I was told by FW techs that since the original site was created
with FW on a PowerPC Mac, the newer FW version running on my newer
IntelMac couldn’t read it. PPC FW won’t talk to Intel FW apparently

That’s news to me. I’ve been happily opening and editing Freeway
documents, created on PPC Macs and versions of Freeway pre-v.4, using
an Intel Mac and Intel Freeway.

Which “FW techs” were these?

Heather


“Freeway - Web Design for All”


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

??? I dunno, just wrote to support and asked how I could do so. My files, transferred from the earlier computer (which was stolen) just show up as UNIX files and can’t be opened.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

As an alternative, is there a free FTP program I can use to get to my files? I used to use Fetch, but it’s no longer included on Mac.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 19 Jan 2008, at 21:04, STEPcoach wrote:

just show up as UNIX files and can’t be opened

Try adding the extension .freeway to a file and see if it opens then.

:o)

Heather


“Freeway - Web Design for All”


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 19 Jan 2008, at 21:04, STEPcoach wrote:

just show up as UNIX files and can’t be opened

Try adding the extension .freeway to a file and see if it opens then.

:o)

Heather

WOW!!! Heather you ROCK!!! Lookit me doing handsprings and all in your honor! It worked. I feel like such a DUH! but you ab rock!

thanks!!!

BTW … any suggestions about FTP? Since Fetch bit the dust I dont’ know how to access FTP.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 19 Jan. 2008, 2:21 pm, thatkeith wrote:

Just to make sure we all know the score, Freeway is able to open
older Freeway documents.

My misunderstanding then - this post and some other things I’ve read surfing around, seemed to indicate incompatibilities between V4/5 and opening an earlier (v1 or 2?) doc. Would make sense though, that all revs are supported in newer versions.

What it doesn’t do is import HTML
documents, at least not very well.

Yes, I’ve tried it…not very useful.

The HTML output is a frozen, detail-light, non-rich snapshot of the
rich, flexible, malleable layouts that are your Freeway documents.
You can never reverse engineer something that’s such a boiled-down
construct back into the multiple-layered whole that was put together
to generate it.

Yes, BUT it would be very nice to have the option to output/export/save-as, a “finished” site as a HTML site including the CSS. Mostly what they have done here is create a proprietary CSS wrapper on the output side (probably to copy-protect some bits of code). The design interface part of the software is the “selling point” IMHO. Allowing the owner of the software to create an additional, alternate “universal” HTML version of their sites for backup would be nice.

Other webdesign packages in this category do the proprietary thing too though…so Softpress are not unique in this practice.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 19 Jan 2008, at 21:41, STEPcoach wrote:

BTW … any suggestions about FTP? Since Fetch bit the dust I dont’
know how to access FTP.

I use and recommend Transmit from Panic Software, and I know others
here do the same.

I’m pleased my suggestion worked for you, but please tone down the
celebrations a little. I am British, after all. Cool and reserved,
don’t you know?

;o)

Heather


“Freeway - Web Design for All”


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

This statement is pretty far from the truth.

A Freeway document is a binary thing, a proprietary format, etc.
You can open it with the same version of Freeway that last saved it,
or any newer version (within limits). Sometimes opening a document
created in an earlier version of Freeway necessitates a translation
step, and there is usually a warning dialog about that if it is
necessary. Just so we are clear, a Freeway document contains the
entire site, all the pages, all the images and other resources, in
short, everything for the entire site.

A published site created with Freeway (namely, anything you upload
to your server) is a plain-vanilla, standards-compatible HTML-and-
associated-resources Web site. The published site consists of as many
plain-text HTML files as you have pages, and all of the images or
other resources that you placed on those pages, neatly managed and
resampled for you. You can open the finished pages using any tool you
like, ranging from the very basic text editors to the most expensive
pseudo-WYSIWYG design tools like GoLive or Dreamweaver. There is
nothing proprietary about the content of a finished site, otherwise
you would not be able to view it in a browser.

Yes, it is a shame that Freeway can’t do a better job of reverse-
engineering HTML content. But considering that its internal layout
model has more in common with PostScript than HTML, that’s hardly
surprising. The internal precision and richness of the object model
in Freeway exceeds anything that current versions of HTML or XHTML
can express. That model contains more information about your design
intent than HTML can show a browser, and thus it is possible to use
the same exact layout to output HTML 3.2, HTML 4, HTML 4.1 Strict,
and XHTML Transitional and Strict. Each page in your site can be set
to a different output format if you like, and you can change back and
forth non-destructively, because you aren’t actually creating any
HTML until you publish. As Keith mentioned earlier, publishing HTML
in Freeway is analogous to printing from a DTP app to a LaserWriter.
The act of publishing a page consists largely of “dumbing down” the
internal design model to the desired level of HTML, (sort of like an
Oxford don talking to a three-year-old in some cases).

Hope this helps,

Walter

On Jan 19, 2008, at 4:56 PM, igirl wrote:

Yes, BUT it would be very nice to have the option to output/
export/save-as, a “finished” site as a HTML site including the
CSS. Mostly what they have done here is create a proprietary CSS
wrapper on the output side (probably to copy-protect some bits of
code). The design interface part of the software is the “selling
point” IMHO. Allowing the owner of the software to create an
additional, alternate “universal” HTML version of their sites for
backup would be nice.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 19 Jan 2008, at 21:56, igirl wrote:

Yes, BUT it would be very nice to have the option to output/
export/save-as, a “finished” site as a HTML site including the CSS

That’s exactly what Freeway does.

Mostly what they have done here is create a proprietary CSS wrapper
on the output side (probably to copy-protect some bits of code).

No it isn’t. When you publish your site, the folders that contain it,
some of which Freeway makes, contain a real HTML web site. That is
the ‘finished’ site you’re wanting. It’s standard, high quality HTML.
The CSS is generated by you, when you make styles in Freeway.

The design interface part of the software is the “selling point” IMHO.

Of course it is. What Freeway outputs is plain vanilla HTML, and you
can write that by hand if you know how, there’s nothing special about
it and it’s hardly what you’d call a selling point. I think you’re
getting Freeway all wrong, not understanding what it does. The design
interface is the whole point of Freeway. The HTML it outputs is
just HTML, not much different to the output of any web design
application. It’s the way Freeway allows you to get there that is
important.

Allowing the owner of the software to create an additional,
alternate “universal” HTML version of their sites for backup would
be nice.

Just go to your site folder; it’s there. It’ll run on any platform,
any server, any browser, anywhere. It can also be edited by any other
Web designer, using any other software, except, ironically, possibly
Freeway, as it’s HTML import is so sketchy.

Other webdesign packages in this category do the proprietary thing
too though…so Softpress are not unique in this practice.

If they didn’t, there’d be not much point in having them, Freeway
included. Freeway gives you a total design environment, just like
Quark or InDesign and just about as rich. It allows you to do things
you couldn’t dream of, quite easily, and at the end, it outputs a
standard HTML site. Freeway doesn’t use HTML itself though, because
HTML simply isn’t sophisticated enough to support many of the design
techniques it allows. Similarly, Indesign works in a ‘proprietory’
format internally, as do most applications of this kind. What they
output is always a drastically simplified version of what they store
internally, whether it’s a printed page or HTML.

best wishes

Paul Bradforth

http://www.paulbradforth.com


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thank you Walter and Paul!

I think I’m beginning to understand a bit better now - I was incorrectly thinking that somehow since the sitename.freeway document was uploaded with all the other files, there was some sort of proprietary interdependency. (It must really get uploaded so the whole project remains in one piece). I was curious so took a FW site into Dreamweaver and it ran just fine. So then that .freeway doc holds the pre-published design info that is not useful to the published site, but only useful to the APP when it comes time to redesign from the last saved design stage…all the pointers to all the objects and their various states etc.

Anyway I appreciate your explanations - helpful to me and hopefully others who have the same kids of questions!


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

You don’t need to ever upload the .freeway file to your Web server.
It’s only useful on your Mac.

If you let Freeway do the upload for you, you will see precisely what
needs to be put on your server: the HTML files, the Resources folder,
and any sub-folders you have made in the process of designing your site.

Walter

On Jan 19, 2008, at 7:22 PM, igirl wrote:

Thank you Walter and Paul!

I think I’m beginning to understand a bit better now - I was
incorrectly thinking that somehow since the sitename.freeway
document was uploaded with all the other files, there was some sort
of proprietary interdependency. (It must really get uploaded so the
whole project remains in one piece). I was curious so took a FW
site into Dreamweaver and it ran just fine. So then that .freeway
doc holds the pre-published design info that is not useful to the
published site, but only useful to the APP when it comes time to
redesign from the last saved design stage…all the pointers to all
the objects and their various states etc.

Anyway I appreciate your explanations - helpful to me and hopefully
others who have the same kids of questions!


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Free open source ftp app I recommend is Cyberduck:

http://cyberduck.ch/

Fills my needs perfectly. Updated often. Quite user friendly.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

On 20 Jan 2008, at 00:22, igirl wrote:

I think I’m beginning to understand a bit better now - I was
incorrectly thinking that somehow since the sitename.freeway
document was uploaded with all the other files, there was some sort
of proprietary interdependency.

Ah, but the .freeway document isn’t uploaded with all the other
files! I’m not sure why you thought it was, but it ain’t. Here’s a
shot of the folder layout of one of my old sites:

The folder called ‘Media’ I made myself, and that’s just to hold the
pictures that are used in the site. Not the actual pictures that are
uploaded, but the TIFFs and Photoshop files that go into Freeway,
which it uses to produce the output JPEGs and GIFs. There is another
folder I made, just outside the screenshot to the left, called ‘My
2006 site’, and that’s the folder I made when Freeway initially asked
me where I wanted to save my .freeway file. The folder called
‘2006site’ I made when Freeway asked me to choose a Site folder
(output folder) the first time I published the site. It is the
contents of this folder that get uploaded to the server. Not the
folder itself, just what’s inside.

It wouldn’t be a good idea for Freeway to upload the .freeway file;
some of my site files are 30Mb, which would slow down any upload
enormously. In that example above, the site folder is only 416Kb,
whereas the .freeway file is 8Mb.

best wishes

Paul Bradforth

http://www.paulbradforth.com


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Well! there you go - Freeway helps international relations, too. I’m Irish-American, which explains my exuberance. Thanks again.

On 19 Jan 2008, at 21:41, STEPcoach wrote:

BTW … any suggestions about FTP? Since Fetch bit the dust I dont’
know how to access FTP.

I’m pleased my suggestion worked for you, but please tone down the
celebrations a little. I am British, after all. Cool and reserved,
don’t you know?

;o)

Heather


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options