Trying to change the code to edit ScriptyFader settings…
If I view the code with Source code snooper, the settings arent there, but if I view the live pages code in Safari, I can see it. and I have been able to edit it using word with some success. I am trying to change the opacity of the scripty Fader thumbs in “inactive position”
Here is the code:
document.observe(‘dom:loaded’,function(){
var thumbs = $$(‘.SFthumb’);
var mains = $$(‘.SFmain’);
thumbs.each(function(elm){
elm.down(‘img’).setOpacity(0.4);
elm.observe(‘mouseover’, function(evt){
elm.down(‘img’).morph(‘opacity:1’,{duration:0.3});
});
elm.observe(‘mouseout’, function(evt){
if(!elm.hasClassName(‘active’)) elm.down(‘img’).morph(‘opacity:0.4’,{duration:0.3});
I’m not sure why that would be, ScriptyFader runs at fwAfterEndBody, and I believe Snooper runs at fwAfterEndHTML (to get all changes to the Freeway DOM before converting the whole thing to text).
I’m looking at another Action right now, I’ll pop a setting into the interface for this if you’ll pledge to the ActionsForge drive (hint, hint…)
Trying to change the code to edit ScriptyFader settings…
If I view the code with Source code snooper, the settings arent there, but if I view the live pages code in Safari, I can see it. and I have been able to edit it using word with some success. I am trying to change the opacity of the scripty Fader thumbs in “inactive position”
Here is the code:
document.observe(‘dom:loaded’,function(){
var thumbs = $$(‘.SFthumb’);
var mains = $$(‘.SFmain’);
thumbs.each(function(elm){
elm.down(‘img’).setOpacity(0.4);
elm.observe(‘mouseover’, function(evt){
elm.down(‘img’).morph(‘opacity:1’,{duration:0.3});
});
elm.observe(‘mouseout’, function(evt){
if(!elm.hasClassName(‘active’)) elm.down(‘img’).morph(‘opacity:0.4’,{duration:0.3});
I’d love to help out Walter… just made my pledge. You have been so helpful over the last couple years.
It’s pretty easy to change the code in the final html and then save it back to my site but the option of changing it from within Freeway would be great!
For this page, I changed all the .4 opacity setting to .7 and now I can see the thumbnail images much better and still get the great effect…
but now I have to remember to do this every time I upload the site : )
Okay, version 0.5, just released. You may need to remove the Actions from your elements, publish once (you don’t have to upload) and then re-apply the Actions.
Walter
On Jun 11, 2012, at 10:26 AM, Tychain wrote:
I’d love to help out Walter… just made my pledge. You have been so helpful over the last couple years.
It’s pretty easy to change the code in the final html and then save it back to my site but the option of changing it from within Freeway would be great!
For this page, I changed all the .4 opacity setting to .7 and now I can see the thumbnail images much better and still get the great effect…
but now I have to remember to do this every time I upload the site : )
When installing a bundle Action, you are running a chance that Freeway will not pick up the change in the Action, but will actually latch on to the cached version of the Action in the document itself. First, close all documents, then make a new minimal one-page document with a fader on it (just empty HTML boxes with color set) and see if it still works. It should. Then, try restarting and see if Freeway picks up the new Action. If that works, great. If not, then you will need to open the troubled document, remove all instances of the Fader from every page in the document, and publish once. Then you can add the Action back to each element and you will be fine.
Walter
On Jun 11, 2012, at 12:10 PM, Tychain wrote:
Hi Walter
I installed the new action and all pages with the old action stopped working. Not the end of the world but a lot of work to rebuild every page.
So I rebuilt the page I was working on and still, no go. : (
Do I have to remove all instance of ScriptyFader throughout the website in order to start rebuilding?
Any other way or things to try before I do all this work?
Dont get me wrong… I love the new option and appreciate you doing this so quickly. : )
Just tested a new simple page and version .5 still wont work.
I went to the Edit/Actions page and scrolled to the bottom and there are two ScriptyFader folders, one checked and one unchecked. So I checked the “off” version and unchecked the other… and version .31 came back… and my new simple page works.
Sorry, a typo crept in when I was replacing the hard-coded 0.4 with a variable. It’s fixed in 0.5.1
Walter
On Jun 11, 2012, at 12:42 PM, Tychain wrote:
Hi Walter
Just tested a new simple page and version .5 still wont work.
I went to the Edit/Actions page and scrolled to the bottom and there are two ScriptyFader folders, one checked and one unchecked. So I checked the “off” version and unchecked the other… and version .31 came back… and my new simple page works.