> I experimented with source changes a little. Say you make a change in the
> source and then go back to the Builder and change a label or add another
> control. The Builder is pretty intelligent about only changing what it needs
> to and not losing your source changes. However, I did notice that changing
> control names is a bit more destructive. So it's a good idea to have your
> control names picked before editing sections related to those controls.
>
> I haven't experimented with repeats. I imagine you won't see your controls
> within the repeat in the builder but will see them when you render the
> xform.
>
> A guide on best practices for editing xforms source while still using the
> builder would be nice. I haven't seen any documentation on how the Builder
> does xform updates and what dangers there are in editing the source and then
> using the Builder again.
>
> On 12/16/2010 04:32 PM, Frank wrote:
>>
>> Hi all,
>> I have been using orbeon xforms for a while but have only just started
>> looking at form builder/runner.
>>
>> I see that form builder seems good at developing simple forms but does not
>> have ability to include repeating items.
>> The bookshelf example has repeats. How is this done? Can forms developed
>> within form builder be modified outside of form builder
>> to include repeated data and then published to form runner? Is there any
>> doco for this?
>>
>> Thanks,
>> Franco
>>
>>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing
> list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>