Re: conf problem
Jean-Christophe Michel <jc.michel-/aRvmaKoZxNWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.lib.binarycloud.devel |
|---|---|
| Message-ID | <[email protected]> |
[email protected] wrote: > the bad: to me it seems you hit an inconsistency in the design of > simpleentity. No, simply that the way to extend it was not defined :-) > Entities are defined from an .edf , right ? No. edf belonged to storage package, which is in his third rewrite, never ended, and maybe will never end. > First Impression: the conf: should not be in SimpleEntity's conf path. > Second Impression: you shouldn't use conf but some definition file (like > node does). > Third impression: if include_entity('item') is a function, it would be > better to have include_entity('item', 'path_2_class'). No ;-) wouldn't work. The idea is: I release a package, like store, that can be used and extended. This package uses simpleentities as data objects. I want to change/extend only one of these objects but not copy the whole package I reuse. So I need a way to tell to the package: each time you want to create an Item object, don't use your own class but mine instead. I thought to overriding conf values, but the simple solution is: in my own app I make a list of all data objects and their paths. (the package can have a default similar map too of course). So no overriding magic, simply a list of all simpleentities used in the project. Simple, solved ;-) PS: Please all change the list address when answering. -- Jean-Christophe Michel _______________________________________________ dev mailing list dev-PnctHDZWAvB/Cz2I37pSEPZ4XP/[email protected] http://lists.binarycloud.com/mailman/listinfo/dev