Hello,
I'm evaluating the Metakit and have a few questions
involving on-the-fly data structures and nested views.
I am wondering what the best way to represent the data
in Metakit would be. I have tried nested views, but I'm not
sure they will be the most
efficient. Plus, the on-the-fly data structures do not seem to be
working -- at least for
me.
I have a number of items. Each item can have zero to thousands of data
records. The properties for the data records can differ for
each item. For example,
one item may have data
like Date, Time, Style, Size,
etc. while another item may have data
like Date, Type, Length, Color,
etc.
To make things worse,
I need the ability to add/remove properties from the item data on a per item basis at run
time. The item data could include one or more of hundreds
of properties.
ItemView
Item[Name:S,Description:S,Number:I...]
ItemDataView
ItemData[Date:I,Time:I,Style:I,Size:I...]
...
ItemData[Date:I,Time:I,Style:I,Size:I...]
Item[Name:S,Description:S,Number:I...]
ItemDataView
ItemData[Date:I,Type:I,Length:I,Color:I...]
...
ItemData[Date:I,Type:I,Length:I,Color:I...]
1. Is this possible in Metakit?
2. Any ideas on how
to structure the data in
Metakit?
Thank you,
Kim
Bachman
