Well it does let you use the data API and a pair of Collections, even if you're not using scrolling.
-Josh On Tue, Aug 26, 2008 at 3:04 PM, Doug McCune <[EMAIL PROTECTED]> wrote: > I think you might be asking the wrong question. You asked how to know if > the area that the user dropped an item was the empty space or the space > taken up by other items in the container. But then you want all the items in > the container to resize to become smaller to accomodate more items in the > container if the user drops too many. Why not just let the user drop items > anywhere in the container and just add them to the container? Then all you > have to do is create a container that scales the children to make sure that > they always fit within the bounds. > > If you force the children to always be the same width then this should be > really easy to figure out what scaling you should apply to the children. If > not then you'll have to do more complex measurement. I'd suggest starting > with teh flowbox container in FlexLib (flexlib.net), and if that doesn't > suit your needs then either extend that or try using the Tile container. It > doesn't sound like you want to use a list control (ie TileList) because you > always want all the children visible, so you never want the list to scroll, > and therefore you don't benefit from itemrenderers, so using a list will > just complicate things unneccesarily. > > Doug > > On Mon, Aug 25, 2008 at 9:42 PM, Josh McDonald <[EMAIL PROTECTED]> wrote: > >> I agree, I'd use a couple of TileLists and a simple inline >> itemrenderer. Shouldn't be too difficult really. >> >> -Josh >> >> >> On Tue, Aug 26, 2008 at 2:31 PM, Alex Harui <[EMAIL PROTECTED]> wrote: >> >>> TileList? >>> >>> >>> ------------------------------ >>> >>> *From:* [email protected] [mailto:[EMAIL PROTECTED] *On >>> Behalf Of *Rick Winscot >>> *Sent:* Monday, August 25, 2008 7:47 PM >>> *To:* [email protected] >>> *Subject:* Re: [flexcoders] Need Help and Guidance desperately >>> >>> >>> >>> The seconds link was to a flow layout that would set you in the right >>> direction... The other option was the first link which uses static >>> positioning. Really, it depends on what you want the user experience to be >>> like. If you could sketch out the solution – we could throw some code >>> around. >>> >>> Rick Winscot >>> >>> >>> On 8/25/08 10:24 PM, "anuj sharma" <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>> >>> Hi Rick >>> Thanks for the reply. Are there any recommendations about which layout >>> component or container should i use or do i need to create my custom >>> component for achieving this target. I am not sure which way to handle that >>> layout. Please help me out >>> Again Thanks a lot. >>> Anuj >>> >>> On Mon, Aug 25, 2008 at 5:18 PM, anuj181 <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>> >>> Hi >>> I am using HBOX container to load images letting user drag image from >>> one HBOX and dropping them in another (2nd)HBOX. I need to calculate >>> the real estate of the HBOX in which the image has been dropped (i-e >>> 2nd HBOX). The reason is that because I need the dropped image to get >>> placed in an empty space within the 2nd HBOX. >>> Is there any way I can calculate which space is empty in the HBOX and >>> let my objects (images) to be placed only in the empty spaces within >>> the HBOX (not the sapce already occupied by the placed images).Once >>> the HBOX is full then I need to code in a way that images starts >>> shrinking(upto some level) to accommodate more images. >>> Please help me out in figuring out this problem. Any type of >>> help/documentation/links in this direction will be highly appreciated. >>> Thanks >>> Anuj >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> -- >> "Therefore, send not to know For whom the bell tolls. It tolls for thee." >> >> :: Josh 'G-Funk' McDonald >> :: 0437 221 380 :: [EMAIL PROTECTED] >> > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
