Hi, >>> - The selection state of a ListView or TableView is represented as a >>> collection of integers, whereas in TreeView it is a collection of lists of >>> integers. So you could probably share selection management code pretty >>> easily between ListView and TableView, but maybe not TreeView. >> Yes I know that Tree has a different way to handle data inside > > The public API is different, not just the implementation details. List/table > selection is via index, whereas tree selection is via path. Yes I know ... so the real question here is that makes sense to try to make a common api for them ...
>>> FYI, you can already do something like this by passing a Bean type to the >>> JSONSerializer constructor. When given such a type, JSONSerializer will >>> read and write data from and to the Bean's properties rather than from and >>> to untyped objects like Map and List. >> But even for not directly supported data types in JSON (like Date, >> Calendar, BigInteger, BigDecimal, etc) ? > > I believe the Number types are supported already. BeanAdapter supports them, I have to look better at JSONSerializer and related stuff ... > The JSON spec does define date or calendar types, so JSONSerializer does not > support them. That's the real question for this, because usually beans used as a data model (for example for business applications) many times have data directly not supported, so the idea to provide something extendable (in application-specific code) instead of throwing exception ... but just as idea. Thank you again for now. Bye
