 |
 |
 |
|
 |
daverj's actions for GoLive
The Golive actions available at the bottom of this page are ones that I wrote to try and help out the people that use Adobe Golive. These actions are free and so are the tuorials on this site. I created GoliveTutor.com as a place to host the actions and tutorials, as well as links to some other actions and tutorials that I felt might be of use to users of GoLive.
If you would like to help me pay for the hosting and bandwidth for this site, take a browse over to my RedTengu shop, linked by the banners on the right of this page. There may be some funny hats, tee-shirts, or other stuff that you like.
I hope you enjoy the actions. If you have questions or problems with any of them, post a message on the Adobe Golive Windows forum and I should spot it within a day or so.
Thanks,
-- Dave "daverj" Jones
There are currently 20 actions in this group.
AutoFrameset & IntoFrameset actions
These actions are used together. They allow pages that belong in a frameset to force the frameset around them. This is useful when a page is linked via a search engine. The search engines tend to index the indivual pages, without the frameset.
The "AutoFrameset" action is placed in the head section of the frameset page. It has no parameters to set up. Just place it in a Head Action that is in the head section of the page, and set the Head Action to "OnParse" (instead of the default "OnLoad").
The "IntoFrameset" action is placed into the head section of all of the pages that go inside the frameset. This head action also should be set to "OnParse". In this action you select the URL of the frameset page that it should be loaded into. There are also 2 checkboxes. The first is "Force to top". When this is selected, the frameset will break itself out of any framesets surrounding it. For example, some people link to a page within a frame of their own frameset. This stops that. Don't check this if you want to allow nested framesets.
The other checkbox is "Nav page". When this is checked, and that page is loaded by itself, the frameset will load with it's default pages. Pages that go in the frameset, but are not in the main frame of the frameset should have this box checked, even if they are not nav pages (like banner pages, border pages, etc...). All pages that go into the main frame of the frameset should not have this checked.
You don't really need to use this action at all on pages other than those going into the main frame, but it won't hurt, and if they ever get indexed by a search engine then it certainly would be good to have them force your default frameset.
Important: You must use the IntoFrameset action in the default page that goes into the frame of your frameset where you want the other pages to show up. These actions will not work if you do not do this.
PrintPage action
This action is used to add a print button to your page. Place a text or graphic link, set the link URL to "#" and then add this action to the Mouse Click event. It has a checkbox to select "All Frames" when it is in a frame within a frameset. However, this has no affect in Netscape 4, which will only print the current frame.
SuperSlide set of actions
This is a set of several actions. The main action is "SuperSlide". It is for making slideshows, or automatically changing sets of images. Place this action in the Head section of the page, inside a Head Action. In it you will select the name assigned to an image on the page. That image, and the other slide images must have names that end in sequential 3 digit numbers, like mypic001.jpg, mypic002.jpg, etc... The part of the name before the number (and the filetype) must match on all of these images. In this action you also set the amount of time between image changes, whether to loop back to the start when the sequence is over, whether to play forward or backward, and whether to start sequencing the images when the page is loaded or not.
You can have as many different slideshows as you want on a page, and each slideshow can have up to 999 images in it. If you have a lot of slideshows on one page, and they change quickly, the browser may not keep up smoothly.
The other actions in this set are "SuperSlidePause", which is used to pause and restart the slideshow. "SuperSlideGoto" is used to go to the first image, the last image, the previous image, the next image, or a specific image number. "SuperSlideSpeed" is used to change the speed of playback either to a specific speed, or incrementally up or down. "SuperSlideRev" is used to make the slideshow play forward or backward, or to reverse whatever direction it is already going. "SuperSlideIf" is used as the condition of a Condition action. It can test to see if the slideshow is paused (useful to set a button image for play/pause). It can also test the current image number or speed to see if they are a specific number, or higher/lower than a specific number.
You can also use my "Snippet" action (described below) to read certain parameters of the slideshow. The parameters are accessed by referencing them as DJSSvars["imagename"].property where "imagename" is replaced by the name assigned to your image (in the More tab of the image inspector). You must use the quotes around the image name. And "property" is one of the following:
| Property | Purpose |
| num | current image number |
| paused | 1 if slideshow is paused, otherwise 0 |
| rev | 0 if playing forward, 1 if playing backwards |
| loop | 1 if slideshow is set to loop, 0 if not |
| speed | current interval between images (in thousandths of a second) |
See a couple of demo pages here.
SlideShow999, SlideShowAuto999, and SlideShowAutoStop999 actions
NOTE: Do not use these actions for new slideshows. They are included here only so that people who used them before won't have to remove them from their pages. For new pages, use the SuperSlide action set above.
These actions are modified versions of the Adobe Slide Show actions written by Cédric Ménard, that are in the ActionsPlus group of actions. These ones raise the limit of images to 999 instead of 99. Otherwise they act exactly the same. Make sure all images are in the same folder and have names that end in 001, 002, 003, etc...
If Current Folder action
The If Current Folder action is used as the condition in a Condition action. It compares the name of the folder that the current page is in with a name you specify in the inspector. This can be used in a component to test if the page the component is on is in a specific folder, and if so (or not) then you can execute another specific action (like SetImageURL). For example, to change a logo based on which folder the page with the component is in. To match the root folder, leave the name blank.
Current Date action
This action will display the current date on the screen. Drag a Body Action (from the Smart tab of the Objects palette) over to the body of your page and set it to this action. If you want text styles to apply, drag across the Body Action icon to highlight it and either apply font/size/color/etc.. from the top toolbar or menus, or select an inline style from the style tab of the inspector to apply a CSS class.
(updated 6/2/01)
This action will move a Floating Box back to it's original position when the user scrolls the web page. It has 3 settings in it. You select the Floating Box that will be controlled, the initial position of the box (hit the "Get" button to set this to the current position of the box on the page), and the "Smoothness" of the movement. It is never 100% smooth, but you adjust the speed at which it moves back into position. If you set smoothness to 1 then the box immediately jumps into position. 2 and above are smoother. The movement is "1/smoothness", meaning that when set to "2" the box will get 1/2 way closer each step. When set to 100 it goes 1/100th of the way each step. Install this action in a Head Action set to OnLoad. This action was updated on June 2nd, 2001 to support multiple floating layers.
Open Window 1.2 action
Open Window 1.2 is based on the original GoLive "Open Window" action. It includes the addition of the Left and Top position for the new window that Matt Ridley's "Open Window 1.1" has, but this one also contains a checkbox to force the new window to fill the full screen. In addition it leaves all the checkboxes unchecked by default, since most people seem to prefer that in their new windows.
If Current Page action
The If Current Page action is used as the condition in a Condition action. It compares the name of the current page with a name you specify in the inspector. This can be used in a component to test if the page the component is on is a specific page, and if so (or not) then you can execute another specific action. For example, to change a logo based on which page the component is in. To match the home page , leave the name blank, since usually just a domain name is entered to get to a web site's home page and there is no file name shown in the URL.
Set With Code action
This is a very powerful, general purpose action. It allows you to set a GoLive variable with the result of a snippet of javascript. When you use this action you are presented with a box to select a GoLive variable that you have previously defined in a Head Action, using the Declare Variable action. You are also presented with a box labeled "Javascript" in which you can enter a small piece of javascript.
This piece of javascript can be any valid javascript expression that returns a value. For example, if you declared a function in a script section of the Head section, lets say called "myFunc", then in the Set With Code action you could enter "MyFunc()" and the action would call your function and then place the return value from the function into the GoLive variable you selected. Another example might be if you were to enter "window.location" in the action. This would set the variable to contain the URL of the current page. The possibilities are limited only by your understanding of javascript. For example, if you had a form named "myform" that had a text field named "myfield", then you could enter "document.myform.myfield.value" in the action and the variable would be set to contain the same text that is currently in that form field.
Because the data goes into a GoLive variable, it can then be tested using the Test Variable action. If you place a Condition action somewhere, and use the Test Variable action as the condition, then it can test your variable and cause other things to happen.
Send To Code action
This action is the reverse of the action above. This action will take the value of a GoLive variable and stick it into a javascript variable. The interface in the inspector looks the same as the Set With Code action, except this one evaluates the javascript you enter and assuming it evaluates to a variable, the action puts the value from the GoLive variable into it.
This is useful for setting browser parameters, or passing variables back to javascript variables where they might be used by javascript functions. If the javascript you enter does not define a variable, you may get an error in the browser.
Snippet action
The snippet action allows you to execute a simple piece of javascript code from an action. This is meant for times when you might just need a single javascript statement, and it isn't worth creating a full javascript function and using the Call Function action. An example might be to set a variable, or set the value in a form field, or use a javascript "method".
Installation
Download the Windows daverj actions.
Download the Mac daverj actions
To install these actions, download the above zip file (for Windows) or the .sit file (for Mac). Uncompress this using the appropriate program for your platform (such as Winzip on Windows, or Stuffit on Mac). The enclosed files should then be placed in a folder called "daverj" inside the Modules/Jscripts/Actions folder inside your Golive program folder.
If GoLive was running when you installed the actions, you must shut GoLive down and start it again before it will see the new actions. When you run GoLive you will now find a new group of actions called "daverj" and within that are the new actions.
