I’m thinking about trying to integrate Perch into a Carousel so my client can make updates to the Carousel. Has anyone tried this and if so how did it work for you?
There is no reason why this couldn’t be integrated into Perch ie upload the images via Perch but the Slider code is part of the FW page and references the images such as /pathto/perchuploads/image1.jpeg /pathto/perchuploads/image2.jpeg etc.
As long as the images were named correctly it would work - changing the quantity of images would probably have to be done in the FW page though. And of course this is purely working with images - no overlaid text etc.
I’m thinking about trying to integrate Perch into a Carousel so my client can make updates to the Carousel. Has anyone tried this and if so how did it work for you?
There is no reason why this couldn’t be integrated into Perch ie upload the images via Perch but the Slider code is part of the FW page and references the images such as /pathto/perchuploads/image1.jpeg /pathto/perchuploads/image2.jpeg etc.
As long as the images were named correctly it would work - changing the quantity of images would probably have to be done in the FW page though. And of course this is purely working with images - no overlaid text etc.
David
This is pretty cool. So how would you insert the Wow Slider code into a FWP document?
This is pretty cool. So how would you insert the Wow Slider code into a FWP document?
Kelly, this is pretty easy. The directions in my Backdraft docs for this are generic (in other words, they will work equally with or without Backdraft). Check 'em out here.
I was interested to read your method for incorporating Wow Slider into a Freeway file. I have usually just added the code using ‘Insert Markup Item’. Is your method required to make sure it becomes responsive or is this an approach I should be using for non-responsive inline websites as well?
Using the Markup Item will insert a P around the DIV in your code, so you will end up with this:
<p>
<div> (your carousel stuff here) </div>
</p>
Now this is illegal, so every browser on earth will correct it by moving the p before or after the div, like this:
<p></p>
<div> (your carousel stuff here) </div>
It is entirely up to the browser whether to put the P before or after the div, and how to style such an empty p. That’s because the code you provided was wrong, and so the browser was free to do whatever with it. When you use valid code, the browser has to stick to the letter of the spec.
The result of this might look okay in your browser, and entirely wrong in another, and that’s not the browser’s fault.
Walter
On Jan 1, 2014, at 3:21 PM, Caleb Grove wrote:
Gordon,
Feel free to use the “Insert Markup Item” instead of the Crowbar action. I just tend to use Crowbar because it doesn’t create the junk
Using the Markup Item will insert a P around the DIV in your code,
so you will end up with this:
(your carousel stuff here)
Now this is illegal, so every browser on earth will correct it by
moving the p before or after the div, like this:
(your carousel stuff here)
It is entirely up to the browser whether to put the P before or
after the div, and how to style such an empty p. That’s because the
code you provided was wrong, and so the browser was free to do
whatever with it. When you use valid code, the browser has to stick
to the letter of the spec.
The result of this might look okay in your browser, and entirely
wrong in another, and that’s not the browser’s fault.
Walter
Presumably using a markup of
</p>
<div> ... </div>
<p>
resulting in
<p></p>
<div> ... </div>
<p></p>
would at least allow you to control the non-styling of the Ps.
David
–
David Ledger - Freelance Unix Sysadmin in the UK.
email@hidden www.ivdcs.co.uk
Ah, so could that explain why I sometimes have to put a markup item inside another DIV for it to behave correctly? I guess, though, there must be some instances when the markup structure is correct else why would a Freeway do it?
Looks like I need to revisit some of my sites…
All the best
Gordon
On 2 Jan 2014, at 12:06 am, Walter Lee Davis email@hidden wrote:
Using the Markup Item will insert a P around the DIV in your code, so you will end up with this:
An inline Markup Item (an item you have inserted at a flashing text cursor) will always be wrapped with a P or an LI or another text container. It is best to think of the inline MI as a single character of text rather than anything else – Freeway won’t let it go out into the page all by itself. In contrast, a Markup Item you created by clicking on the pasteboard (so nothing is currently selected) and then choosing Insert / Markup Item from the main menu, will generate a DIV or a TD (depending on the current layout modality) and will allow your code to express HTML containing block-level tags like DIV or UL.
CrowBar allows for the possibility of an inline Markup Item. It also does a couple of other tricks, too. If a CrowBar is added as the first or last character of a run of text, the code contained in the CrowBar will be shifted outside of the text block container, so that this:
<p>[CrowBar code]Some text here</p>
becomes
[CrowBar code]<p>Some text here</p>
This can be handy if your code determines whether that line of text should appear or not, or if you want to inject a block-level element before the run of text, maybe floated right.
Walter
On Jan 2, 2014, at 5:10 AM, Gordon Low wrote:
Ah, so could that explain why I sometimes have to put a markup item inside another DIV for it to behave correctly? I guess, though, there must be some instances when the markup structure is correct else why would a Freeway do it?
Looks like I need to revisit some of my sites…
All the best
Gordon
On 2 Jan 2014, at 12:06 am, Walter Lee Davis email@hidden wrote:
Using the Markup Item will insert a P around the DIV in your code, so you will end up with this: