Comments on: The invisible model http://canoo.com/blog/2008/03/27/the-invisible-model/ Web 2.0 Technology Blog on Java, AJAX and Flex Thu, 20 Nov 2008 11:57:59 +0000 http://wordpress.org/?v=2.5.1 By: Daniel http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11706 Daniel Wed, 09 Apr 2008 06:47:08 +0000 http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11706 Hi Chris, Binding of subbean data is possible for table binding as well as for the form model. The binding for subbeans is done exactly how you describe it, e.g. "address.street", "address.country.name". Regards Dany Hi Chris,

Binding of subbean data is possible for table binding as well as for the form model. The binding for subbeans is done exactly how you describe it, e.g. “address.street”, “address.country.name”.

Regards Dany

]]> By: Chris http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11675 Chris Tue, 08 Apr 2008 13:43:55 +0000 http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11675 Looks good - how about binding of subbean data ? The person class might have a property address of type Address with properties street (String), city (String), country (Country) and Country itself might have properties name (String), code(string). The binding for these additional table fields could then be defined as follows (xpath syntax): - tableBinding.addColumnBinding("firstName").setColumnHeaderValue("First Name") - tableBinding.addColumnBinding("address.street").setColumnHeaderValue("Street") - tableBinding.addColumnBinding("address.city").setColumnHeaderValue("City") - ableBinding.addColumnBinding("address.country.name").setColumnHeaderValue("CountryName") - tableBinding.addColumnBinding("address.country.code").setColumnHeaderValue("CountryCode") Is this kind of data binding supported ? Regards Chris Looks good - how about binding of subbean data ? The person class might have a property address of type Address with properties street (String), city (String), country (Country) and Country itself might have properties name (String), code(string). The binding for these additional table fields could then be defined as follows (xpath syntax):
- tableBinding.addColumnBinding(”firstName”).setColumnHeaderValue(”First Name”)
- tableBinding.addColumnBinding(”address.street”).setColumnHeaderValue(”Street”)
- tableBinding.addColumnBinding(”address.city”).setColumnHeaderValue(”City”)
- ableBinding.addColumnBinding(”address.country.name”).setColumnHeaderValue(”CountryName”)
- tableBinding.addColumnBinding(”address.country.code”).setColumnHeaderValue(”CountryCode”)
Is this kind of data binding supported ? Regards Chris

]]> By: Daniel http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11278 Daniel Tue, 01 Apr 2008 07:11:39 +0000 http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11278 Hi Andrea, I can think of two kinds for paging. The first one is in the user interface. This is known from HTML applications where you can see only one page at a time and you can browse through the pages with help of forward and backward buttons. An example for this kind of paging is the result list of a Google search. This kind of paging is uncommon for rich internet applications. A RIA usually displays all rows and provides a scrollbar to browse the rows. So there will be no support for this kind of paging. The second kind of paging is while the applications loads data from the backend, e.g. a database. Usually is is advised to not load all data at once but to load the data as needed in pages. Currently it is not planned to add this kind of support, i.e. this should be self-coded. Regards Dany Hi Andrea,

I can think of two kinds for paging.

The first one is in the user interface. This is known from HTML applications where you can see only one page at a time and you can browse through the pages with help of forward and backward buttons. An example for this kind of paging is the result list of a Google search. This kind of paging is uncommon for rich internet applications. A RIA usually displays all rows and provides a scrollbar to browse the rows. So there will be no support for this kind of paging.

The second kind of paging is while the applications loads data from the backend, e.g. a database. Usually is is advised to not load all data at once but to load the data as needed in pages. Currently it is not planned to add this kind of support, i.e. this should be self-coded.

Regards Dany

]]> By: Daniel http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11277 Daniel Tue, 01 Apr 2008 07:00:33 +0000 http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11277 Hi Etienne, You are right, talking in terms of beans is more precise than talking in terms of business objects. I will use the beans term in the future. Maps are not supported in our initial implementation. After milestone 1 we decide upon how to extend our initial implementation. My feeling is that support for maps is a good candidate for the final release. Regards Dany Hi Etienne,

You are right, talking in terms of beans is more precise than talking in terms of business objects. I will use the beans term in the future.

Maps are not supported in our initial implementation. After milestone 1 we decide upon how to extend our initial implementation. My feeling is that support for maps is a good candidate for the final release.

Regards Dany

]]> By: Andrea http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11223 Andrea Mon, 31 Mar 2008 12:29:04 +0000 http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11223 Sounds great, but what about paging ? Is it planned to add paging for tables or should this be self-coded? Thanks Andrea Sounds great, but what about paging ? Is it planned to add paging for tables or should this be self-coded?

Thanks
Andrea

]]> By: Etienne http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11215 Etienne Mon, 31 Mar 2008 05:18:10 +0000 http://canoo.com/blog/2008/03/27/the-invisible-model/#comment-11215 Looks good, but I would not talk in terms of business objects, rather just in terms of beans or something like that. Not every application exposes its biz objects on the ULC tier, but might still use your form model. Suggestion: it would be great if your models could also operate on a Map rather than a bean (or biz object). Maybe that can all be abstracted out into its on aspect, such that custom mappings from any key to any value is possible, no matter what type the key and no matter what type the biz object is. Looks good, but I would not talk in terms of business objects, rather just in terms of beans or something like that. Not every application exposes its biz objects on the ULC tier, but might still use your form model.

Suggestion: it would be great if your models could also operate on a Map rather than a bean (or biz object). Maybe that can all be abstracted out into its on aspect, such that custom mappings from any key to any value is possible, no matter what type the key and no matter what type the biz object is.

]]>