[xwiki-devs] [PROPOSAL] Introduce XClass property reference
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. 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. WDYT ? -- Thomas Mortagne
On Mon, May 30, 2011 at 21:11, Thomas Mortagne <thomas.mortagne@xwiki.com> 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.
WDYT ?
-- Thomas Mortagne
-- Thomas Mortagne
On 05/30/2011 09:25 PM, Thomas Mortagne wrote:
On Mon, May 30, 2011 at 21:11, Thomas Mortagne <thomas.mortagne@xwiki.com> 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? 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. -- Sergiu Dumitriu http://purl.org/net/sergiu/
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 <thomas.mortagne@xwiki.com> 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. 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.
On Tue, May 31, 2011 at 00:29, Vincent Massol <vincent@massol.net> 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 <thomas.mortagne@xwiki.com> 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".
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 devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Tue, May 31, 2011 at 08:45, Thomas Mortagne <thomas.mortagne@xwiki.com> wrote:
On Tue, May 31, 2011 at 00:29, Vincent Massol <vincent@massol.net> 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 <thomas.mortagne@xwiki.com> 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 devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne
On Tue, May 31, 2011 at 08:59, Thomas Mortagne <thomas.mortagne@xwiki.com> wrote: > On Tue, May 31, 2011 at 08:45, Thomas Mortagne > <thomas.mortagne@xwiki.com> wrote: >> On Tue, May 31, 2011 at 00:29, Vincent Massol <vincent@massol.net> 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 >>>>> <thomas.mortagne@xwiki.com> 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 * s/like a/like a hack/ > 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 >>> devs@xwiki.org >>> http://lists.xwiki.org/mailman/listinfo/devs >>> >> >> >> >> -- >> Thomas Mortagne >> > > > > -- > Thomas Mortagne > -- Thomas Mortagne
On Tue, May 31, 2011 at 00:29, Vincent Massol <vincent@massol.net> 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 <thomas.mortagne@xwiki.com> 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.
I agree that we should not limit ourselves, but I really do not see the limit here. What would be the advantage of having several class defined in the same document ? Denis
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 devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
Here is a "new" proposal: * introduce now class property references with "wiki:space.page^property" in which we escape "^" and "." when serializing the "property" * that way if later we really need to have several classes by document (which does not actually bring anything I agree with Denis) we support wiki:space.page^property as a shortcut of wiki:space.page^firstclass.property. It would be a first but it's not hard to do technically. If we don't for sure we can always remove the "." escaping which is just a useless escaping which is supported properly by reference parser and otherwise we don't really break the syntax by adding the classname part to the reference since the separator is already protected. WDYT ? I really need to move on on this and I'm -1 to introduce right now a wiki:space.page^classname.property syntax where you never know what to put as classname. On Wed, Jun 1, 2011 at 14:24, Denis Gervalle <dgl@softec.lu> wrote:
On Tue, May 31, 2011 at 00:29, Vincent Massol <vincent@massol.net> 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 <thomas.mortagne@xwiki.com> 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.
I agree that we should not limit ourselves, but I really do not see the limit here. What would be the advantage of having several class defined in the same document ?
Denis
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 devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Mon, Jun 6, 2011 at 09:57, Thomas Mortagne <thomas.mortagne@xwiki.com>wrote:
Here is a "new" proposal: * introduce now class property references with "wiki:space.page^property" in which we escape "^" and "." when serializing the "property" * that way if later we really need to have several classes by document (which does not actually bring anything I agree with Denis) we support wiki:space.page^property as a shortcut of wiki:space.page^firstclass.property. It would be a first but it's not hard to do technically. If we don't for sure we can always remove the "." escaping which is just a useless escaping which is supported properly by reference parser and otherwise we don't really break the syntax by adding the classname part to the reference since the separator is already protected.
WDYT ?
+1
I really need to move on on this and I'm -1 to introduce right now a wiki:space.page^classname.property syntax where you never know what to put as classname.
On Wed, Jun 1, 2011 at 14:24, Denis Gervalle <dgl@softec.lu> wrote:
On Tue, May 31, 2011 at 00:29, Vincent Massol <vincent@massol.net> 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 <thomas.mortagne@xwiki.com> 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.
I agree that we should not limit ourselves, but I really do not see the limit here. What would be the advantage of having several class defined in the same document ?
Denis
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 devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
On 06/06/2011 09:57 AM, Thomas Mortagne wrote:
Here is a "new" proposal: * introduce now class property references with "wiki:space.page^property" in which we escape "^" and "." when serializing the "property" * that way if later we really need to have several classes by document (which does not actually bring anything I agree with Denis) we support wiki:space.page^property as a shortcut of wiki:space.page^firstclass.property. It would be a first but it's not hard to do technically. If we don't for sure we can always remove the "." escaping which is just a useless escaping which is supported properly by reference parser and otherwise we don't really break the syntax by adding the classname part to the reference since the separator is already protected.
WDYT ?
+1. Not sure if "first" is correct, since this is supposed to be a set of classes, not a list, but yes, without specifying a class name, the main class in that document will be used.
I really need to move on on this and I'm -1 to introduce right now a wiki:space.page^classname.property syntax where you never know what to put as classname.
On Wed, Jun 1, 2011 at 14:24, Denis Gervalle<dgl@softec.lu> wrote:
On Tue, May 31, 2011 at 00:29, Vincent Massol<vincent@massol.net> 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 <thomas.mortagne@xwiki.com> 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.
I agree that we should not limit ourselves, but I really do not see the limit here. What would be the advantage of having several class defined in the same document ?
Denis
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.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On 06/06/2011 10:57 AM, Thomas Mortagne wrote:
Here is a "new" proposal: * introduce now class property references with "wiki:space.page^property" in which we escape "^" and "." when serializing the "property" * that way if later we really need to have several classes by document (which does not actually bring anything I agree with Denis) we support wiki:space.page^property as a shortcut of wiki:space.page^firstclass.property. It would be a first but it's not hard to do technically. If we don't for sure we can always remove the "." escaping which is just a useless escaping which is supported properly by reference parser and otherwise we don't really break the syntax by adding the classname part to the reference since the separator is already protected.
WDYT ?
+1 Thanks, Marius
I really need to move on on this and I'm -1 to introduce right now a wiki:space.page^classname.property syntax where you never know what to put as classname.
On Wed, Jun 1, 2011 at 14:24, Denis Gervalle<dgl@softec.lu> wrote:
On Tue, May 31, 2011 at 00:29, Vincent Massol<vincent@massol.net> 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 <thomas.mortagne@xwiki.com> 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.
I agree that we should not limit ourselves, but I really do not see the limit here. What would be the advantage of having several class defined in the same document ?
Denis
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 devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
On Jun 6, 2011, at 9:57 AM, Thomas Mortagne wrote:
Here is a "new" proposal: * introduce now class property references with "wiki:space.page^property" in which we escape "^" and "." when serializing the "property" * that way if later we really need to have several classes by document (which does not actually bring anything I agree with Denis)
It's about classification. You may want to have a single page that's completely contained and that has 2 class definitions. I actually find it nice to be able to put all your class definitions in a single page (for some small apps for ex). I don't see why we would have an arbitrary limitation of one document == one class definition. Personally I see classes as metadata of a document as exactly the same notion as objects. Everything is a document metadata to me and a document can have as many metadata that it wants, be them class objects or class definitions. MetaData entry = set of properties (key/values).
we support wiki:space.page^property as a shortcut of wiki:space.page^firstclass.property. It would be a first but it's not hard to do technically.
Hmmm so that would mean that each document can have only 1 main class and then ancillary classes. Personally I'd find a way to address any piece of metadata: wiki:space.page^[metadata id].[metadata property] The hard part is defining "metadata id". For a class it could be a class name that the user has to enter. For objects it could be classname[number] (or some other generated id or id entered by the user). Now what I mention is future IMO. Since you have this need now I'm +1 with your proposal for now. Thanks -Vincent
If we don't for sure we can always remove the "." escaping which is just a useless escaping which is supported properly by reference parser and otherwise we don't really break the syntax by adding the classname part to the reference since the separator is already protected.
WDYT ?
I really need to move on on this and I'm -1 to introduce right now a wiki:space.page^classname.property syntax where you never know what to put as classname.
On Wed, Jun 1, 2011 at 14:24, Denis Gervalle <dgl@softec.lu> wrote:
On Tue, May 31, 2011 at 00:29, Vincent Massol <vincent@massol.net> 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 <thomas.mortagne@xwiki.com> 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.
I agree that we should not limit ourselves, but I really do not see the limit here. What would be the advantage of having several class defined in the same document ?
Denis
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 devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
participants (5)
-
Denis Gervalle -
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol