[Here is an update for this]
Here is the beginnings of a full featured open-source continuous scroll thumbnail component for Flex. It is rough right now, but I plan to polish it and make it something useful. This format is really appealing, as it gives the user a seamless view of a gallery, without any jumps or aggravating scroll bars. Up until now I have been using H and V Lists in flex for my thumbnailing, but they are ugly and don't provide as rich of an experience.
The Scroll Panel from AFComponents was my first choice. It is a very nice component, well priced, and would be just what I need, if not for the fact that my project is open-source and using a commercial component sorta kills the whole thing. After scouring the internet I finally stumbled upon the work Peter Wright has put in on a perpetual scrolling list.
I've modified it to accept an XML list of image objects, as well as perform horizontally. It is also functioning as a slideshow, and I want to allow it to go either H or V depending on the need. It should shape up to be a nice reusable component. Much thanks to Peter for supplying the code to get me started.
Source Enabled
Hey,I am so interested about that you had ever used the ‘TransformTool’ library in your Flex project. But there is little examples showing how to use it in flex, Would you please share some example about how to use ‘TransformTool’ in Flex? I have tried as such a way:
but it failed at line
canvas.addChild(defaultTool);
Can you give any hints? Thanks.
Like most pure AS3 display classes, the TransformTool needs to be added to a UIComponent wrapper to function properly in Flex.
Source.
Rogue Development's ObjectHandles is a great component. It is simple to use and provides all of the functionality that I was looking for in a transformation modifier. Prior to implementing this, I was using the TransformTool from senocular.com's library. This is also a great utility, but it wants to scale my content, and that was a deal breaker in my current project. ObjectHandles does NOT resize the child components. There are use cases for both approaches, but ObjectHandles allows me to decide when to scale.
<?xml version="1.0" encoding="utf-8"?>
<ObjectHandles
xmlns="com.roguedevelopment.objecthandles.*"
xmlns:mx="http://www.adobe.com/2006/mxml"
allowRotate="false"
objectMovedEvent="objectUpdatedHandler( event )"
width="{image.width}"
height="{image.height}" >
<mx:Script>
<![CDATA[
import com.roguedevelopment.objecthandles.ObjectHandlesMouseCursors;
public static const CHANGE:String = "imageBoxChanged";
private function objectUpdatedHandler( event:Event ):void
{
dispatchEvent( new Event( CHANGE, true ) );
}
]]>
</mx:Script>
<mx:Image id="image" source="@Embed(source='/assets/cower.png')" />
</ObjectHandles>
