I am using several actions to create three different features on a home page. All features work great independently but when I put them in the sand box together the scroll feature stops working. I can fiddle with the actions and get something to work but it all seems a little random.
Slide Show Ad feature comprised of - Target Show/Hide Layer, Rollover, Show On Slave Trigger and Hide Slaves (Alternate).
Overlay feature comprised of - Target Show/Hide Layer, Rollover.
Gallery feature comprised of - Showcase Gallery
Scrolling content feature with graphic thumbnail - Protaculous using Walts code and Scriptaculous set to packed. The other setting causes a Java Script error
var s = new Control.Slider(‘Thumb’,‘Track’, {axis:‘vertical’});
var f = function(value){
var inner = $(‘ScrollContent’);
var h = (inner.getHeight() - inner.up(‘div’).getHeight());
inner.style.top = (Math.round(value * h) * -1) + ‘px’;
}
s.options.onChange = function(value){
f(value);
};
s.options.onSlide = function(value){
f(value);
};
The link has been updated to show all the actions on one page and a page with just the scrolling affect and freeways galley functioning. The scrolling feature comes from Walter’s site.
It looks like one of the Actions on this page is restricting its load
of Scriptaculous to the Effects module, rather than including the
Control module that the slider requires. This is going to be down to
the load order of Actions, which is difficult to control. You can try
this (one may work and the other will definitely not, no idea which
way you need to go here):
Option 1: Remove all of the FreewayFX Actions from the page, and build
your popup element in place (covering the page) with its slider. Make
sure it works. Then add the Target Show/Hide stuff second, set your
popup to hide, and away you go.
Option 2: Essentially the opposite. Build your popup and set it to
show/hide. Then add the Protaculous Action to the page and wire up the
slider.
If this really doesn’t work, then get rid of all FX actions, and
replace them with hand-coded equivalents using Protaculous and
Observer. That’s hopefully not what you have to do, but it might
become necessary unless you want to hack your copies of the FX Actions
so they load the entire Scriptaculous stack.
Walter
On Oct 31, 2010, at 9:15 PM, TeamSDA wrote:
Hi All,
The link has been updated to show all the actions on one page and a
page with just the scrolling affect and freeways galley functioning.
The scrolling feature comes from Walter’s site.
In both options 1 & 2 am I using the Protaculous action as you did on you example? Our do your two ideas have to do with the order of things that are placed in freeway?
The way I built the example was by copy and pasting groups of pre-built features from other pages.
Yes, it has to do with which Action publishes “last”, as that’s the
one that will install the code libraries. I have had a brief
discussion with Joe Billings at Softpress, and he sent me some code to
work around this issue. We are going to have further discussions later
on to see if we can make this even easier for developers and for end-
users.
I’ll let you know when I have the updated Actions available.
Walter
On Nov 1, 2010, at 10:34 AM, TeamSDA wrote:
Hi Walt,
In both options 1 & 2 am I using the Protaculous action as you did
on you example? Our do your two ideas have to do with the order of
things that are placed in freeway?
The way I built the example was by copy and pasting groups of pre-
built features from other pages.
Okay, I’ve updated all of the Scripty Actions to better integrate with
Softpress’s FX Actions. Big thanks to Joe Billings for the code
examples.
You should now be able to put together a single page including
Protaculous, any of the FX Actions, or any of the single-purpose
Scripty Actions like Carousel, Accordion, CalendarView, or Lightbox.
Walter
On Nov 1, 2010, at 10:37 AM, Walter Lee Davis wrote:
Yes, it has to do with which Action publishes “last”, as that’s the
one that will install the code libraries. I have had a brief
discussion with Joe Billings at Softpress, and he sent me some code
to work around this issue. We are going to have further discussions
later on to see if we can make this even easier for developers and
for end-users.
I’ll let you know when I have the updated Actions available.
Walter
On Nov 1, 2010, at 10:34 AM, TeamSDA wrote:
Hi Walt,
In both options 1 & 2 am I using the Protaculous action as you did
on you example? Our do your two ideas have to do with the order of
things that are placed in freeway?
The way I built the example was by copy and pasting groups of pre-
built features from other pages.
I updated your Protaculous action as well as Freeway to 5.2.2 and all seems to be working. We will test later on other browsers and platforms. Thank you so much, you are awesome
QUESTION: How do I make the hand selectable on an iPhone/iPad?
I don’t think you can. The best you can get is that when you click on
the track, the thumb will jump to be under that point. But that’s
hidden behavior, not something a person will just know to do. I would
try hiding the entire scrollbar element when viewed in a touch-event
browser, and maybe remove the height of the parent object so it
expands to show its entire content.
Walter
On Nov 1, 2010, at 1:32 PM, TeamSDA wrote:
QUESTION: How do I make the hand selectable on an iPhone/iPad?