Hello,

on 04/21/2008 08:12 AM Sergey Klenin said the following:
> I feel like I'm inventing a wheel because it seems I'm trying to do the thing
that is always done.
> I see that it will be meta meta system, but how to handle my needs in more
effective way?
> Maybe the way I'm trying to solve this problem now is fundamentaly mistaken
and I have to use native metastorage capabilities to achieve end user
fuctionality?
> In short, I'm stuck.

This is a bit confusing, not because of your definitions, but rather
because you do not tell me what exactly what you want to do and you are
not able to do it.

Anyway, if you want a meta type system, first you need to have classes
that describe your types. Then you to have classes that store the type
values.

You separated each thing in two components but that is inconvenient
because the factory of one component will not be able to fetch objects
of the other component. You can pass OID back and forth but that may be
a drag.

Anyway, I think first you should design a class model with some UML tool
like Umbrello or others, than you move on to the model implementation
using Metastorage.

Once you have your model diagram ready it is easier to see what do you
want to do and what your model is not allowing, so I can advise. So,
just design your model and show your diagram when you get stuck.


--

Regards,
Manuel Lemos

PHP professionals looking for PHP jobs
http://www.phpclasses.org/professionals/

PHP Classes - Free ready to use OOP components written in PHP
http://www.phpclasses.org/