In the BeanEditForm, every t:Parameter I provide replaces the entire row ...
there are not two columns. No key or label is present. Whatever I put in
t:Parameter takes up the entire row.
Whereas in BeanDisplay, every t:Parameter I provide gets forced into the
second column. No matter what I do, the label or name of that field always
get's printed on the left hand side.
<t:BeanDisplay t:id="topic" add="edit">
<t:Parameter name="edit"><t:PageLink page="topic/EditTopic"
context="topic.id">edit</t:PageLink></t:Parameter>
</t:BeanDisplay>
<t:BeanEditForm t:id="topic" add="delete">
<t:Parameter name="delete"><t:ActionLink t:Id="Delete" context="
topic.id">Delete</t:ActionLink></t:Parameter>
</t:BeanEditForm>
What that means to me is that when I jump back and forth between Edit and
Show screens in my crud(dy) application, the data lays out differently if I
use these two components.
I think they should render consistently ... but I'm not sure maybe they
really are unrelated and I need to write this myself.
For what its worth, the same thing happens when I provide any type of
AppPropertyBlock. If it is used on the BeanDisplay page, then the 'key' or
'label' automatically show up and the custom block is placed in the second
or right hand column. Again, for the BeanEditForm, no key or label shows up
and the block value simply takes the entire row.
Thoughts?
-Luther
