On Tue, May 31, 2011 at 08:45, Thomas Mortagne <[email protected]> wrote: > On Tue, May 31, 2011 at 00:29, Vincent Massol <[email protected]> wrote: >> >> On May 30, 2011, at 9:57 PM, Sergiu Dumitriu wrote: >> >>> On 05/30/2011 09:25 PM, Thomas Mortagne wrote: >>>> On Mon, May 30, 2011 at 21:11, Thomas Mortagne >>>> <[email protected]> wrote: >>>>> Hi dev, >>>>> >>>>> I would like to introduce class property entity type and related >>>>> reference and syntax separator. >>>>> >>>>> For the separator syntax I propose to use the same thing as object >>>>> separator since you can't have both in the same reference and it's >>>>> always a pain to find a new separator. >>>> >>>> FYI it means wiki:space.page^property >>>> >>>>> >>>>> Note that I'm inly talking about class property and not class since >>>>> class reference is exactly the same thing as document reference I >>>>> don't think we really need to have a specific one. >>> >>> Currently there can be only one class in a document, but for a while the >>> question whether this is going to be valid in the future as well has >>> been floating around. >>> >>> So, a prerequisite vote is: >>> >>> In the new model, can a document contain more than one class? >> >> I don't think we should limit ourselves (I don't see any reason, do you see >> one?). BTW the new model I started has the ability to have several classes >> per document. > > Well why dot but then what does it mean in term of reference ? > > wiki:space.page^classname.property ? > > The issue is what to put as "classname" element currently since this > part is useless and for a long time given the place of the new model > in the priority list. It could be possible to support a shortcut > version as wiki:space.page^property but then it would be a first and > would be a special case in serializer/resolver. But I can't see how to > support such a shortcut for class reference unless by using an even > more special case where "if hitting a dot it mean there is no class > name and so we are actually looking at a document name".
We could allow anything, even empty classname and just not taking it into account but wiki:space.page^.property looks like to a user who knows there is no such thing as class in the current implementation. And still what do we get as class name when asking a PropertyClass reference ? > >> >> Thanks >> -Vincent >> >>> One thing I believe we're definitely going to need is a special data >>> structure to explicitly represent XClasses, holding XClass metadata such >>> as "is the class supposed to be stand-alone, one instance per document, >>> like BlogPosts, or is it an aggregated class, with several instances >>> attached to a document, like the Comments"; "what is the sheet used to >>> display the object in view mode"; "what is the parent class (if we want >>> to do inheritance)". With this meta-class in place, we could, in theory, >>> have two meta-classes in a document, with each class property mapped to >>> one of the meta-classes. >>> >>>>> WDYT ? >>> >>> +1, if we decide that we only want at most one class per document. >> >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs >> > > > > -- > Thomas Mortagne > -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
