From: Jocelyn <li...@dj...> - 2007-02-22 15:15:11
|
May be we can not define a proper RND "define" for this "group" but use it whenever needed with <element name="group" /> <element name="target"> ... <zeroOrMore> <ref name="tasks" /> <element name="group"> <zeroOrMore> <ref name="tasks" /> </zeroOrMore> </element> </zeroOrMore> </element> Except the RNG point, I guess we could try to have a notion of group in geant .. and then do not have a specific "group" task. In my (test) code, the group task and command were almost empty ... so we could create a GEANT_GROUP and handle this for tasks, or even group of options, group of .. whatever Jocelyn On 2/22/2007 15:16 PM, Eric Bezault wrote: > Jocelyn wrote: >> For now, I made the GEANT_GROUP_TASK and GEANT_GROUP_COMMAND. >> So this is a basic geant task, which can be used as any task. >> It doesn't have any extra semantic appart from being a tasks containing >> a sequential group of tasks. >> >> The schema should looks like >> <define name="group"> >> <element name="group"> >> <ref name="dir_if_unless"/> >> <optional> >> <attribute name="name"/> >> </optional> >> <ref name="tasks"/> >> </element> >> </define> >> >> so a group can include another group and so on, as the example in my >> previous post. >> Does it answer the question ? > > Yes, but it's more restrictive than I thought. It would > be great if there was a mean to use groups as a kind of > parentheses to group any kind of elements. Now that <group> > is used to group tasks, will it be possible to use it > later on to group other kinds of elements? Or will we be > out of luck because <group> is already used for tasks? > |