[svn:fx-trunk] 8507: Making measureHeightOfItemsUptoMaxHeight consistent with the way we create rows in the datagrid .

Question

Revision: 8507
Author:   [email protected]
Date:     2009-07-10 10:13:11 -0700 (Fri, 10 Jul 2009)
Log Message:
Making measureHeightOfItemsUptoMaxHeight consistent with the way we create rows in the datagrid. MakeRow ensures reported row height is round to the nearest integer, measureHeightOfItemsUptoMaxHeight is now consistent.  Fixes a long standing PrintDataGrid issue.
Bugs: SDK-20237.
QE Notes: None
Doc Notes: None
Reviewer: Glenn/Alex
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-20237
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/DataGrid.as

Answer 1

Well, you could do the following:
1) Create a stored procedure that assembles the data into a rowset with rows and fields like the format you want.
2) Create stored procedures that handle insert, update, and delete.
3) Create an entity object definition with all transient attributes. Make the attributes match the elements of one row.
4) Override doDML() in the entity object class to call your procedures (the doc explains how to do this). You might also need to do a bit of research and figure out if you need to override some other method so you can report rows with transient attribute changes only as needing posting. (getPostState(), maybe?)
5) Create a view object definition with entity-derived attributes based on your EO attributes.
6) Override the appropriate methods to call your data assembly procedure rather than execute a query (this is also in the doc).
Still kind of kludgy, but it keeps your business components pretty clean, especially if you use framework classes to do most of the work for you. (I have a partial example of how to do that here.) Of course, it keeps your business components clean by moving the real work to the DB, but some people find that more maintainable that a kazillion business components.
Hope this helps,
Avrom