|
Boost : |
From: John Torjo (john.lists_at_[hidden])
Date: 2004-11-16 12:19:26
>>Even reflected property types should be of trivial types:
>>1. build in types
>>2. std::string
>>3. types that can simply be read from /written to strings.
>>
>>For case 3., you might also have a validation function which will be
>>used in design-mode to validate user input.
>>
>>At least that's what I want.
>
>
> I'm not sure that is valid.
>
> Take a TreeList as an example. The items in a treelist are almost always sub-classes,
based on some type of generic 'TreeItem' class. I'm not sure that a
TreeItem can always be represented as a string.
Each node can be identified by a unique ID (which can be an integer,
which can be then converted as a string).
Thus, besides all IDs, you need to persist all parent-child relationship
- which I think is about it.
Best,
John
-- John Torjo, Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -- v1.5 - tooltips at your fingertips (work for menus too!) + bitmap buttons (work for MessageBox too!) + tab dialogs, hyper links, lite html
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk