Re: Flex Datagrid: MX vs Spark

2015-01-08 Thread Alex Harui
On 1/7/15, 4:55 PM, DavidM dmos...@gmail.com wrote: Your answer explains why I didn't see any performance difference, however, isn't it still a bug for a layout not not respect height=100% when useVirtualLayout='true' ? Yeah, that’s probably a bug, but I don’t know how many folks leverage that

Re: Flex Datagrid: MX vs Spark

2015-01-07 Thread DavidM
Thanks, the reason for putting it on the layout is because useVirtualLayout is not exposed as a public property on Spark Datagrid. Your answer explains why I didn't see any performance difference, however, isn't it still a bug for a layout not not respect height=100% when useVirtualLayout='true'

RE: Flex Datagrid: MX vs Spark

2015-01-06 Thread Kessler CTR Mark J
/spark/components/DataGrid.html#lockedColumnCount [2] http://flex.apache.org/asdoc/spark/components/DataGrid.html#lockedRowCount -Mark -Original Message- From: DavidM [mailto:dmos...@gmail.com] Sent: Monday, January 05, 2015 10:22 PM To: users@flex.apache.org Subject: Re: Flex Datagrid: MX

RE: Flex Datagrid: MX vs Spark

2015-01-06 Thread DavidM
Thanks Mark, if I'm reading those links correctly, you need SDK 4.13 to build that functionality, but only Flash Player 10 to deploy it, correct? I'm currently still using the 4.6 SDK, because I don't want my users to have to upgrade anything beyond Player 11.1. I'll look into 4.13 again,

Re: Flex Datagrid: MX vs Spark

2015-01-06 Thread DavidM
Wow Justin, that's news to me. I've been avoiding any version 4.6.0. The notion that I can get all the bug fixes and new features all the way up to 4.13.0, and also not have to increase Player requirements is huge. I wish I'd have known that earlier - is it described anywhere in the

Re: Flex Datagrid: MX vs Spark

2015-01-06 Thread DavidM
BTW, I'm using 50 columns, and 100 rows, with 2 locked columns, and 4 locked rows. -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Flex-Datagrid-MX-vs-Spark-tp9314p9327.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Flex Datagrid: MX vs Spark

2015-01-06 Thread DavidM
Thanks Justin. -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Flex-Datagrid-MX-vs-Spark-tp9314p9328.html Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Flex Datagrid: MX vs Spark

2015-01-06 Thread DavidM
can't honestly say that I see any real difference between useVirtualLayout='true' vs 'false. could be that my table is just too small, or that my machine fairly powerful (quad core macbook pro retina with 16 Gb ram). Looking at the activity monitor, I do see slightly greater CPU usage with

Re: Flex Datagrid: MX vs Spark

2015-01-06 Thread Justin Mclean
Hi, The Spark Datagrid seems to use a canvas to scroll and is much, much, more responsive that the MX Datagrid. The performance of theMX data grid has had significant improvement to performance of it in 4.13 over 4.6 you may want to test that first before moving to the spark datagrid. It

Re: Flex Datagrid: MX vs Spark

2015-01-06 Thread Justin Mclean
Hi, The notion that I can get all the bug fixes and new features all the way up to 4.13.0, and also not have to increase Player requirements is huge. I wish I'd have known that earlier - is it described anywhere in the documentation? Yep in the README [1] Is there a list of new features

Re: Flex Datagrid: MX vs Spark

2015-01-06 Thread Alex Harui
Make sure your Spark DG has useVirtualLayout = true otherwise it isn’t a fair comparison and you’ll use up a lot of memory for large data sets. On 1/6/15, 2:08 PM, DavidM dmos...@gmail.com wrote: The Spark Datagrid seems to use a canvas to scroll and is much, much, more responsive that the MX

Re: Flex Datagrid: MX vs Spark

2015-01-06 Thread Alex Harui
David, it looks like you are using useVirtualLayout on the container, not the DataGrid. I just remembered that Spark DG (and MX DG) always use virtualLayout. Sorry for the bad info earlier. -Alex On 1/6/15, 4:07 PM, DavidM dmos...@gmail.com wrote: Getting some weird and unexpected behavior.