Check out the following 3 screenshots.:

Global Navigation XML + Gaia site XML together in one file

As you can see, this is how it used to be up to now (Global Navigation version 1.57a). The attributes of both Gaia and Global Navigation together in one file.

Gaia site.xml without Global Navigation

This is the normal Gaia site.xml without the Global Navigation.

The new Global Navigation XML source file

This is the new Global Navigation navig.xml file. Yellow marked you can see that the new attribute “id” is the same as the page IDs of the Gaia site.xml above. The root node can be of any name, but the “navigation” and “button” nodes have to be named like that.

Ok, but what is so exciting about this?

The fact that you don’t have to handle the button IDs by yourself is one thing, the other is that this is one of the last pieces of my own Flash Website Framework called “FLEB” which is based on the Global Navigation. One of the key features of this framework is SEO. Stay tuned!

Visit the docs to download the source files and classes.

.

The new methods are:

keep the roll over state of the parent button:
setKeepRolloverStatus(true)
Hide the children again, regardless of their button state. Either after a time specified by setFadeOutTimerDelay(3) or if the user clicks anywhere off the navigation:
setAlwaysHideChildren(true)

And the undocumented methods are used for depth handling:

Sets the submenu that is fading in behind the parent button. In the SWF below I have used a shadow on the parent button to demonstrate it
setFadeInDepth(“back”)

You can even set the depth of each button state (rollOver, rollOut, Press, release):
setBtnDepths(“back”,”front”,”front”,”front”)

.

Explore and compare these two SWFs. At first glance they look the same. But there is a difference.

.

Settings in the SWF above:

navigationManager.setKeepRolloverStatus(false);
navigationManager.setAlwaysHideChildren(false);
navigationManager.setBtnDepths(“front“,”back“,”back“,”front”)
navigationManager.setFadeInDepth(“front“);

Download source,  demo files and documentation

.

How does it work?

It takes the content (movieclip or sprite), resizes it (keeping its aspect ratio) so that the width fits to the width of the selected paper format (landscape or portrait) and calculates the number of pages.

Try it out in the SWF below:

You can find the documentation and download of all source files here.

Here is a real example that makes use of the multipage printing class.

.

Here is the difference.

Old version:

// Imports
import net.kaegi.navigation.NavigationManager;
import net.kaegi.navigation.NavigationButton;
import net.kaegi.events.NavigationEvent;
import net.kaegi.events.EventCentral;

// create NavigationnavigationManager = new NavigationManager(this, "xml/site.xml");
navigationManager.setFadeInOnMouseOver(false);
navigationManager.setFade(true);
navigationManager.setFadeInChainDelay(0.3);

// Event Listeners
EventCentral.getInstance().addEventListener(NavigationEvent.MC_ACTIVATED, btnActivateHandler,false,0,true);
EventCentral.getInstance().addEventListener(NavigationEvent.MC_FADE_IN, btnsFadeIn,false,0,true);
EventCentral.getInstance().addEventListener(NavigationEvent.MC_FADE_OUT, btnsFadeOut, false, 0, true);
EventCentral.getInstance().addEventListener(NavigationEvent.LOADING_COMPLETE, loadingCompleteHandler, false, 0, true);

//.......

Version 1.56:

// Imports
import net.kaegi.navigation.NavigationManager;
import net.kaegi.navigation.NavigationButton;
import net.kaegi.events.NavigationEvent;

// create NavigationnavigationManager = new NavigationManager(this, "xml/site.xml");
navigationManager.setFadeInOnMouseOver(false);
navigationManager.setFade(true);
navigationManager.setFadeInChainDelay(0.3);

// Event Listeners
navigationManager.addEventListener(NavigationEvent.MC_ACTIVATED, btnActivateHandler,false,0,true);
navigationManager.addEventListener(NavigationEvent.MC_FADE_IN, btnsFadeIn,false,0,true);
navigationManager.addEventListener(NavigationEvent.MC_FADE_OUT, btnsFadeOut, false, 0, true);
navigationManager.addEventListener(NavigationEvent.LOADING_COMPLETE, loadingCompleteHandler, false, 0, true);

//.......

Download + Documentation

.

Cheers!

I’ve included the TweenLite/TweenMax classes as well, but again, be sure to get the latest version of the Tweening classes.

———————————————————————————————————–
Download global navigation (includes Gaia v3.0.4 and all sample files)
Download global navigation classes only
I removed the downloads here, because I have set up an online documentation with all the downloads:

Global Navigation Downloads + Documentation

Introduction to global navigation
How to, Showcase, Infos, Samples
———————————————————————————————————–

Real examples: websites using the global navigation

WITKA
Data Logistix AG
Impact Unlimited
Hunziker Betatech AG
eXtenso IT Services

Version history

(Please visit the documentation for the latest info)

1.51

• Small adjustement in LoadChildAsset class. remove Listener when loading is cancelled. LoadChildAsset.as is used to load the button swfs. This fix was in fact not really necessary, because the loading of the buttons is not cancelled. But nevertheless, if you want to use LoadChildAsset.as by itself, this fix was important.
  

1.50

• It is now possible to include a path to your btn swfs –> new NavigationManager(ref:MovieClip, xmlFile:String, btnPath:String = “”). This can be helpfull if your btn swfs are in a different location and you want to keep the xml file clean (btnSWF=”mainBtn.swf” looks better than btnSWF=”http://www.yourdomain.com/folder/anotherfolder/buttonfolder/mainBtn.swf”)

1.49

• “btnHide” attribute added. This is used when the button itself should not be visible, but it needs to be loaded for proper alignment etc. This is often the case with the “home” button: The functionality should be in the navigation but it is triggered by a click on the logo and not specific “home”-button.

1.48

• Bugfix when the last btn had sub-buttons (Type Error #1010 with btns[nextSiblings[0]].makeRoomAddSpace)

1.47

• I took almost all code that was in the btn swf and encapsulated it in the NavigationButton class, so now it is much easier (especially for the designer) to layout and arrange the graphics and button labels in the fla.
• Bugs fixed concerning loading issues
• There is a new NavigationEvent LOADING_COMPLETE. When the NavPage loads, the afterTransitionIn Event is hijacked. After the global navigation is completely loaded, Gaia is released.
• The examples uses the newest Gaia Version 3.0.2.
• …and many small improvements.

1.46

• Initial release

.

See life demo

How does it work?
The global navigation consists of 3 parts: a SWF of a single button with rollover, rollout, press etc. states and a text label, an XML file containing the structure and a class (in fact there are 3 main classes, but you don’t need to worry about them), which mixes everything together and spits out a neat navigation.

See samples and download source code here.

.