Sometime around 17/5/08 (at 12:34 -0400) Tonsils said:
Is it possible in FW Pro 5 to actually create individual html pages
and then be able to export them to an individual file, onto my file
system?
Freeway does create individual HTML files for each page that you
have in your Freeway site document. This is what it produces whenever
you preview, publish or upload.
The HTML files and related elements are stored in the document’s
nominated site folder in the Finder. Look in there and you’ll find
everything.
(Note: don’t try editing those files, as they’ll be replaced with new
ones the next time you preview/publish/upload from Freeway.)
If you want to end up with one HTML file and associated elements
without anything that relates to other pages, just copy and paste a
page from the Site panel of one document into a fresh one. Publish
that new document into its own dedicated site folder, and that will
contain everything that’s needed for that page… and nothing that
isn’t.
I’m not sure that I understand what your goal is. Every page in a Freeway document already exports as a separate html file. You could create several 1-page Freeway projects, but that just seems unnecessarily difficult.
On Sat, May 17, 2008 at 9:34 AM, Tonsils wrote:
Hi,
I am wanting to create individual .html files that I will like to call from some javascript routines that I have written.
Is it possible in FW Pro 5 to actually create individual html pages and then be able to export them to an individual file, onto my file system?
Sometime around 17/5/08 (at 09:52 -0700) Ernie Simpson said:
I’m not sure that I understand what your goal is. Every page in a
Freeway document already exports as a separate html file. You could
create several 1-page Freeway projects, but that just seems
unnecessarily difficult.
Absolutely. I should have added that caveat to my last post.
Part of Freeway’s strength is how it handles multiple pages within a
single document. For starters, this is why link management is robust,
reliable and automatic, and image content is normally shared (the
same item referenced in multiple pages) to keep things efficient.
One mistake new users sometimes make is thinking that a Freeway
document is a web document. This often leads to a number of
mistakes - naming the Freeway document with “.html” at the end of the
name, making a new Freeway document for each page, and uploading the
Freeway document to the web site, to name a few.
Understanding how Freeway works and working with that really will
lead to an easier and more productive web-designing life.
('Course, if you’re Ernie it also leads to figuring out how to push
the envelope in new and interesting ways - so the ‘easier’ part
doesn’t always apply… at least at first.
Tonsils’ problem peaked my curiosity as I am currently rebuilding a site that has grown weighty to manage, so I’m using html includes to build the common parts that get called into the other pages. I wondered if that was what he was doing.
On Sat, May 17, 2008 at 10:04 AM, Keith Martin wrote:
('Course, if you’re Ernie it also leads to figuring out how to push
the envelope in new and interesting ways - so the ‘easier’ part
doesn’t always apply… at least at first.
Take a look at my TemplateHelper Action, or Tim Plumb’s Simple
Include Action. Both of those let you carve up a page into a kit of
parts.
Walter
On May 17, 2008, at 1:39 PM, Ernie Simpson wrote:
Tonsils’ problem peaked my curiosity as I am currently rebuilding a
site that has grown weighty to manage, so I’m using html includes
to build the common parts that get called into the other pages. I
wondered if that was what he was doing.
On Sat, May 17, 2008 at 10:04 AM, Keith Martin wrote:
('Course, if you’re Ernie it also leads to figuring out how to push
the envelope in new and interesting ways - so the ‘easier’ part
doesn’t always apply… at least at first.
Hey Ernie - that was exactly what I was getting at.
Walter - will take a look at both yours and Tim’s Actions specified.
T.
On 17 May. 2008, 5:40 pm, The Big Erns wrote:
Tonsils’ problem peaked my curiosity as I am currently rebuilding a site
that has grown weighty to manage, so I’m using html includes to build the
common parts that get called into the other pages. I wondered if that was
what he was doing.
Thanks for making that clear Tony. Now that I know what you’re up to, let me say that making the includes in the same Freeway document helps avoid style problems. When the includes are built either in separate Freeway projects or externally (without Freeway), the styles they are built with are not included unless they are inline styles.
FW5 has the ability to insert content directly into the PageDiv element (which I think is cool). Double-click a blank page and you’re doing it. Because my include call markup is already inside of the “target” div, creating the include html in the PageDiv means it is inserted without inserting another enclosing div.
Walter - I haven’t yet worked out how to use your TemplateHelper action, but I swear that I will. Your adjusted PHP Make Include Page is working very nicely for me now.
Hopefully I can get an example up soon. Now I am too sleepy
Tonsils wrote:
Hey Ernie - that was exactly what I was getting at.
Are you using FW4 or 5 now? I can send you a quick example document
either way.
Walter
On May 18, 2008, at 3:12 AM, Ernie Simpson wrote:
Walter - I haven’t yet worked out how to use your TemplateHelper
action, but I swear that I will. Your adjusted PHP Make Include
Page is working very nicely for me now.
Are you using FW4 or 5 now? I can send you a quick example document
either way.
Walter
On May 18, 2008, at 3:12 AM, Ernie Simpson wrote:
Walter - I haven’t yet worked out how to use your TemplateHelper
action, but I swear that I will. Your adjusted PHP Make Include
Page is working very nicely for me now.
Thanks Walt. Just trying to get my head around the reason for the TemplateHelper action. Just for a bit of clarification, under what circumstance would someone want to have an element on a page to be recreated (or relocated) in another location on the same page?
That’s actually not the core reason for doing this. Let’s say you had a page that might have one of several different bits of content loaded into one spot, depending on some server-driven decision point. Or more likely, let’s say you had made a template that you reused for all of your news stories, which get populated inside of a loop by the server. You make one instance of the template for a news story, apply the TemplateHelper to it and set it to save a partial. Inside that template you have bits of script that print back the various parts of the story – the author, the headline, the date stamp, etc. Your one template stands in for all of your stories.
Thanks Ern, that helps a bit, and I understand the template concept. What confused me is the fact that the action is applied to an html item with no content other than color. If the content was external (a little tricky in a demo of course) it would have been more obvious for me. I’ll mess around with it to see what’s possible.