[flexcoders] TextFlow CSSFormat Resolver...

2010-08-28 Thread grimmwerks
I've got a lot of little TextFormats sprinkled throughout an application in 
other components, itemRenderers and the like.. 

is there a way I can use the application's css as the css for a 
CSSFormatResolver?  How does one get what external css is attributed to an app?

Thanks all



Garry Schafer
grimmwerks
gr...@grimmwerks.com
portfolio: www.grimmwerks.com/







[flexcoders] Re: 3D Carousel in Flex 4?

2010-08-28 Thread hdave_123
Thanks -- got their coverflow working, but am stuck trying to create a carousel 
layout!

--- In flexcoders@yahoogroups.com, claudiu ursica  wrote:
>
> You'll get that by implementing a custom coverflow layout class. 
> 
> http://www.rialvalue.com/blog/2010/04/14/carroflow-another-3d-layout-for-flex4/
> 
> http://www.flexstuff.co.uk/2009/12/23/flex-4-coverflow-layout/
> 
> This should get you started...
> 
> Cheers,
> Claudiu
> 
> 
> 
> 
> 
> From: hdave_123 
> To: flexcoders@yahoogroups.com
> Sent: Tue, August 24, 2010 7:18:38 AM
> Subject: [flexcoders] 3D Carousel in Flex 4?
> 
>
> I am desperate to get a 3D Carousel in my Flex 4 web app.  I found this 
> example:
> 
> http://dougmccune.com/blog/2007/11/19/flex-coverflow-performance-improvement-flex-carousel-component-and-vertical-coverflow/
> 
> 
> It has been last updated in 2008.  Does anyone where know of where I can get 
> a 
> component I can use in a Flex 4 project?  Has it been updated?
>




[flexcoders] Re: Problem getting compiler to recognize a custom class

2010-08-28 Thread Amy


--- In flexcoders@yahoogroups.com, "colin.ashe"  wrote:
>
> Hi,
> 
> I've been banging my head on the wall for the last few days over this problem 
> - hopefully one of you can help.
> 
> I'm writing a program to visualize the movement of some particles and I've 
> written a class, which extends UIComponent as the main visual element.  This 
> class then uses the Flint Particle System library to handle the actual 
> particle dynamics.  I'm using Flash Builder 4 and spark components wherever 
> possible.  Here's the problem: every time I compile, I get:
> 
> 1046: Type was not found or was not a compile-time constant: OilApp.  
> 
> I've checked the compiler settings and told it to look in the appropriate 
> package/folder for the class file.  I've set the appropriate XML namespace 
> and the IDE knows about the class and will autocomplete code related to the 
> class.  However, evidently, the compiler doesn't know about it.  
> 
> Could anyone suggest what I could do to fix this.  My head (and wall) can 
> only take so much more of this.

Usually, that just means you did not include an import statement to import the 
class into the class that is using it.

HTH;

Amy



[flexcoders] Preventing selected item in List from auto scrolling into view

2010-08-28 Thread dorkie dork from dorktown
When I select an partially visible item/row in a vertical Spark List the
item will scroll into view but only the bare minimum. So if there are 5 rows
on the screen and I click row 3, 4 or 5 then that row will expand but it
will usually stay at the Y position it is at leaving rows 1 and 2 visible
above it. I'd like to make sure that the row that is selected is flush
against the top edge of the List.

Is the only way to prevent the List from auto scrolling that item into view
to extend and override that method? I believe the method is that is doing
this is called ensureIndexIsVisible().

I've been able to position it flush against the top without overriding the
above method but then there are two tweens going on and it doesn't always
position correctly or look right.

Here is the code I've been using in the List changing event handler:
var newRow:DisplayObject = list.dataGroup.getChildAt(newIndex);

if (newIndex != contentCount) {
itemY = newRow.y;
itemY -= oldIndex < newIndex ? oldRow.height - newRow.height : 0;
}
else {
itemY = maxVerticalScrollPosition;
}

// move item to the top of the list
TweenLite.to(list.dataGroup, 1.5, {verticalScrollPosition:itemY});

JP


[flexcoders] FB4 + 3.5 Compiler

2010-08-28 Thread artgrater
I have a project substantially completed in Flex 3.  While feature-complete, 
substantial maintenance and improvement will continue indefinitely.  My 
understanding is that importing it to FB4 could require nontrivial rework. 

Should I continue in Flex 3 -- or upgrade to FB4 and compile against 3.5x?  
That is, are there development benefits using FB4 without using the 4.x 
compiler for Spark, etc?





Re: [flexcoders] Constraining one components location to another component

2010-08-28 Thread Akshar Kaul
you can use states. or try using Hbox and Vbox..

---> Akshar Kaul <---



On Fri, Aug 27, 2010 at 19:46, Haykel BEN JEMIA  wrote:

>
>
> Hi,
>
> I think the best way is to create a new component that will hold the image
> and the floating components and handle visibility of these components
> through states.
>
> Example:
>
> 
>  xmlns:fx="http://ns.adobe.com/mxml/2009";
> xmlns:s="library://ns.adobe.com/flex/spark"
> xmlns:mx="library://ns.adobe.com/flex/mx"
> >
>
> 
> 
> 
> 
> 
>
> 
> 
> 
>
>  id="image"
> source="{source}"
> complete="{currentState = 'normal'}"
> progress="{currentState = 'loading'}"
> ioError="{currentState = 'error'}"
> />
>
> 
> 
> 
>
>
> Of course you can put any states you like and also set states from outside
> with : mainImage.currentState = "".
>
> Hope this helps,
>
> Haykel Ben Jemia
>
> Allmas
> Web & RIA Development
> http://www.allmas-tn.com
>
>
>
>
>
> On Thu, Aug 26, 2010 at 9:50 PM, dorkie dork from dorktown <
> dorkiedorkfromdorkt...@gmail.com> wrote:
>
>>
>>
>> Is there a way to constrain one component to another component? I've
>> looked at constraint rows and constrain columns in the past but I haven't
>> got it to work myself. IE,
>>
>> 
>>  > horizontalCenter="0"/>
>> 
>>
>> >right="[Right edge of main image]" top="[Top edge of main image]"/>
>>
>> In this example the download icon would float in the upper right corner of
>> the image component as the image component floats in the middle of the
>> container it is in. FYI In this project there are additional components that
>> will float relative to the location and size of the image as well.
>>
>> JP
>>
>
>  
>