redrocketcms.components.RRGallery
The Gallery component works directly with the Album to render the Album photos with 3rd party Components such as SlideShowPro.
Static. This id is the sybolID linkage necessary for dynamic attachment using attachMovie().
Example Usage. Identical functionally to dropping the Gallery component on the stage:
Write-only. Sets the name of the component to use as the 3rd party Component. This should be the same name as the Component linkage from the library. As of the time of this writing, there are 3 possible values:
Default
Right now, this dosent work, but shortly, in the near future, it will be a super simple generic fade-in-fade-out album that will avoid the necessity of a 3rd party plugin, and cut down on file size.
SlideShowPro
Uses SlideShowPro. This is easily the simplest way to go. The plusses are many, and this is the only one you can actually modify the transition mechanism (using SlideShowBro’s hack). By using the display property, you can fully modify any property of this component making it the most versatile renderer of the pack. You really need to read through the documentation for SSP to understand how to configure it the way to want it to look. Some minuses are it’s incredibly steep learning curve, and it’s pretty beefy.
IMG Thumbnail Gallery
A simple component from http://www.afcomponents.com/. Not nearly as robust as SSP, but simple, light and clean-looking. Certainly a more techy look right out the box, and is customizable using the display property. The documentation for this component is online here. A pretty big fault here is how it handles scaling. Basically, it auto-scales the image to fit the size of the component stage, disregarding the aspect ratio. So, this one works best if you know ahead of time the size of your images and keep them the same size.
Flipping Book
This component comes to us from the guys at http://www.page-flip.com. This one is certainly cool, and is very robust. There are two ways to get this one to work for you. The simplest approach is to do nothing. just drop it down, and you are ready to go. Some basic properties are available using the display property, but really, the power of this component is in it’s actionscript API, which is very nice, but not exactly easy to figure out. To tap into this you can do one of two things: either create swf’s to load into each page using the documentation as a guide, or you can also specify a movieclip in your libray with linkage of "FlippingBookPageShim". This "shim" will be used in place of the source files in the album. However, in the scope of that movieclip, there will be an object named "params" tha contains all the information you need to render the page on your own (maybe by using the Graphic component) and you can still use the API from the documentation.
Read-only. Returns the movieclip instance of the component. Use this reference to modify/style/setup the instance however you need to.
Write-only. You can create an intermediary function that parses the array of photos going into the renderer. You can use this feature to do manual sorting, hard-code links, or remove items that you plan on rendering seprately. Below is an example that removes the first photo (seemingly because we’ll render it elsewhere):
redrocketcms.classes.collector.Auditable
The auditable is the class adds the first set of Component Inspectable properties. Any library-based Components will become a child of this class.
Write-only. The horizontal size policy instructs the component to resize itself to match the maximum width of the component’s containing objects.
Write-only. The vertical size policy instructs the component to resize itself to match the maximum height of the component’s containing objects.
redrocketcms.classes.Collector
The Collector class searches for data within it’s heirarcy. It will search for the closeset Provider and store the data.
The data property is a dump of the data that feeds the Component/Class. Typically, this is an object with properties or sub-objects that have exhaustive data realting to the component.
To find out what is in the data object you could write something like this:
thetainteractive.classes.architecture.Component
This is the base class for any class that is a Libray-based component. This class sets up the EventDispatcher, and base functions.
Sets the size of the bounding box of the component.
param width:Number
the size, in pixels of the width of the component. pass null if you do not want to set a width.
param height:Number
the size, in pixels of the height of the component. pass null if you do not want to set a height.
see also:
width
height
Sets the size of the component width in pixels.
Sets the size of the component height in pixels.
Moves the component.
param x:Number
moves the component x pixels horizontally.
param y:Number
moves the component y pixels vertically.
The invalidate function is a very important function. Usually, invalidate is called internally by other methods to redraw the component.
However, it is a public method, and by calling invalidate() on any component that uses an invalidation routine essentially "redraws" the entire component.
Care should be taken not to continually call invaidate() on any one component on a loop or onEnterFrame() function. invalidate is usually processor and memory intensive for one frame, so be sure to call it when you are sure that you want the component to redraw.
Another note is that many of the components are nested within other components, and they are linked together visually. Therefore, calling invalidate() on one component may cause multiple ares to redraw, again, another reason to use sparingly.
Event dispatched to listeners when the setSize() method is called. Note: this is also called if the width/height propeties are set.
Event Dispathced when the component is moved using the move() method.