Is there is trick to see the code? I know I can add stuff, but have not found the view option to see the backside of the code.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Nope. No option.
Todd
Is there is trick to see the code?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Todd,
thats what I was thinking. Seemed like the downside of freeway was that you can add and remove items visually, but not get inside of it and do some hardcore editiing.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Yep, that’s pretty much it. What you and I may consider a downside is what the majority of FW users consider an upside, I suppose. It would be useful all the same but given how FW functions internally such a feature just isn’t possible without a complete ground-up reworking of how the app works at the core level. I’m afraid we have to get our code “fix” from a separate app.
Todd
Todd,
thats what I was thinking. Seemed like the downside of freeway was that you can add and remove items visually, but not get inside of it and do some hardcore editiing.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
But the plus of that is a neater separation between style and logic.
You can use the Page / HTML Markup dialogs to add code into the
various canonical points of the HTML page (Before HTML, After /HEAD,
etc.), and the Insert / Markup Item to tweezer in some bit of code
within your visible layout. These elements are isolated from your
visual layout, and so they can be copied and pasted, dragged around,
or edited through a Master Page without having to actually diddle
around in the layout code that surrounds them.
When I use Freeway to build a dynamic page, I usually use a
programmer’s text editor and an external code library file containing
all the business logic and plumbing code. I then use one of the
Actions to link that code into the head of the page, or the Before
HTML section. Freeway tracks the current state of that file, only ever
uploads the one copy of it, and keeps everything in sync and up to
date. Then in my layout view, I just place little Markup Items with <?=
$foo?> in them, or instances of the CrowBar Action for finer control
over the placement of the output code. My library code takes care of
setting everything up so all I have to place in the layout is the
instruction to print something somewhere.
Walter
On Jun 23, 2011, at 11:29 AM, Shane wrote:
Todd,
thats what I was thinking. Seemed like the downside of freeway was
that you can add and remove items visually, but not get inside of it
and do some hardcore editiing.
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
One other trick. In your File / Preview / Browser Setup dialog, add
your favorite programmer’s text editor as a “browser”. Then you can
see the generated code – not edit it, mind you, but see it with line
numbers and syntax highlighting – as quickly as choosing File /
Preview in Browser / Textmate.
Walter
On Jun 23, 2011, at 11:29 AM, Shane wrote:
Todd,
thats what I was thinking. Seemed like the downside of freeway was
that you can add and remove items visually, but not get inside of it
and do some hardcore editiing.
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
On 23 Jun 2011, 3:03 pm, Shane wrote:
Is there is trick to see the code? I know I can add stuff, but have not found the view option to see the backside of the code.
Actually, if all you want to do is PREVIEW the code, you could open a published page with a text editor such as TextWrangler instead of a browser. Just select your text editor as a preview destination in the browser selection menu in Freeway. But bare in mind that you shouldn’t edit the code this way because Freeway will have no knowledge of the changes and will happily write over them on next publish.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I can just pop the source code out of the browser too, or pop open the files in my “site folder” that freeway creates.
I think I am nearing the point where I want to close down my freeway usage and start hard coding it.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Freeway could do it and offer a solution to this without causing a issue with the system.
Have a free coded box. Something we can just place onto the system and start coding it in.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
That’s precisely what a Markup Item is – if you place a Markup Item
on the page, it creates a DIV and any code you type into it appears
within that DIV. If you place an inline Markup Item, then it just
dumps the output of whatever code you typed into the nearest parent
text tag (usually a P).
Freeway offers a tremendous amount of control over both of these, and
Actions can take it much further.
Really, the thing to think about and to challenge yourself to do is to
reduce the amount of intermingling of code and layout in your page.
Think through the problem to extract the logical stuff to separate
text files that you can edit in a proper programmer’s editor (one that
will give you color-coded syntax, validation, lookups for function
names and code-block folding). That way you’re not bringing a knife to
a gun fight. Freeway cannot be beaten when it comes to writing terse,
unbreakable layout code. I challenge any hand-coder to this duel. But
when you program, you want to be able to see what you’re doing, and
know that you’ve closed a quote or a brace before you preview on the
server and get a big hairy error.
Sidebar: I worked the Softpress booth at Macworld San Francisco two
years running, and NYC once. I would get a lot of coders at the booth,
easily recognized by their colorful hairdos, multiple piercings and
tattoos, and folded-arms body language. I would rip through my demo,
then view source and show it to them. Jaws would drop, wallets would
open. It was great fun.
So horses for courses, as Richard Logan likes to say.
Walter
On Jun 23, 2011, at 12:30 PM, Shane wrote:
Freeway could do it and offer a solution to this without causing a
issue with the system.Have a free coded box. Something we can just place onto the system
and start coding it in.
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
Very well put Walter.
The key is really understanding how Freeway works so you can insert your custom code in the positions you need it. The time savings are great if you let Freeway handle all the layout and image work for you.
David
On 23 Jun 2011, at 17:47, Walter Lee Davis email@hidden wrote:
That’s precisely what a Markup Item is – if you place a Markup Item on the page, it creates a DIV and any code you type into it appears within that DIV. If you place an inline Markup Item, then it just dumps the output of whatever code you typed into the nearest parent text tag (usually a P).
Freeway offers a tremendous amount of control over both of these, and Actions can take it much further.
Really, the thing to think about and to challenge yourself to do is to reduce the amount of intermingling of code and layout in your page. Think through the problem to extract the logical stuff to separate text files that you can edit in a proper programmer’s editor (one that will give you color-coded syntax, validation, lookups for function names and code-block folding). That way you’re not bringing a knife to a gun fight. Freeway cannot be beaten when it comes to writing terse, unbreakable layout code. I challenge any hand-coder to this duel. But when you program, you want to be able to see what you’re doing, and know that you’ve closed a quote or a brace before you preview on the server and get a big hairy error.
Sidebar: I worked the Softpress booth at Macworld San Francisco two years running, and NYC once. I would get a lot of coders at the booth, easily recognized by their colorful hairdos, multiple piercings and tattoos, and folded-arms body language. I would rip through my demo, then view source and show it to them. Jaws would drop, wallets would open. It was great fun.
So horses for courses, as Richard Logan likes to say.
Walter
On Jun 23, 2011, at 12:30 PM, Shane wrote:
Freeway could do it and offer a solution to this without causing a issue with the system.
Have a free coded box. Something we can just place onto the system and start coding it in.
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
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Walter and Davis,
I totally agree with the concept of letting freeway handle all the layout work. It makes sooooo much more sense.
Right now we are going to push the NON-MYSQL back pages up first and then move to do a MYSQL pages in about 3 weeks. we can get away with it for now.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options