Re: 2 csets were pushed to core/stable: qa fix...

Johnny Robeson wrote:
> mikespub wrote:
> 
>> In article <[email protected]>, 
>> mikespub-111RdWWlOxkOkXtL6OYfHgC/[email protected] (Michel Dalle) wrote:
>>
>>> ...      ChangeSet
>>>     1.2100 05/01/25 01:45:55 [email protected] +4 -0
>>>     add dynamic subform property
>>>  
>>
>>
>> A little something for form freaks and parent/child junkies :-)
>>
>> Mike.
> 
> ok.. wtf is a subform?

Does that mean you're one of those form freaks ? :-)

Anyway, if you have an input form (for a DD object), you can now
have a sub-form (for another DD object) inside it - or several
sub-forms if you want.

The content of the sub-form can either be :

- stored locally in the original DD object (e.g. a details field)

   In that case, the other object is only used to define the different
   fields, their type, default, validation rule etc. It doesn't store
   any content by itself - the original object will store the content
   in serialized format in the subform property.

- linked to an item of that other DD object (e.g. a parent item)

   In that case, the other object has items of its own - you just
   reference one of those items in the form (and can create/update
   this parent item at the same time). The original object will
   store the referenced item id in the subform property.

- the parent value for a list of items of that other DD object (e.g.
   a list of children, or some filter on those items)

   In that case, the other object has items of its own too - but the
   relationship with the original object is reversed : instead of
   pointing to a parent item, it now points to several child items.
   The original object will store the parent/filter value in the
   subform property.

Does that clear things up a bit ? :-)

Mike.