Hi all,
I've spent some time diving into the tapestry's sources (particulary
BeanEditor and all code which is linked to it).
I use Tapestry 5.2.2.
I found some interesting things, that I can't explain:
1)in PropertyEditor.java there is some code, but it is not used anywhere (I
did't find any usages). Am I missing something?
@Inject
@Core
private BeanBlockSource defaultBeanBlockSource;
BeanBlockSource defaultBeanBlockSource()
{
return defaultBeanBlockSource;
}
2)Why form component doesn't have informal parameters support? There is no
according annotation above the class definition (hovewer it works well with
informal parameters, except IDE errors)
3)There is one inconvenience in the loop component - it has a parameter called
'value' which clashes with different html elements attributes of the same
name,
for example I can't write this simple construction because I can't specify
a value attribute of 'option' tag, so I need to nest option tag inside loop
component:
<option t:type="loop" source="myList"
value="myValue">${myValue.label}</option>
Even if I specify current value of the loop like t:value="myValue" and
client value as just value="myValue.id", then client value (value="myValue.id")
is not rendered. Of course, it does not matter much, but creates some
inconvenience.
As I understand, it's now impossible to change name of the current loop
value parameter, due to backward compatibility reason, but maybe it is
possible to define it deprecated and provide also new parameter named, for
example
'currentValue' or 'var' with the same functionality.
Thanks a lot. It's just my thoughts about how to make great framework even
better.
Anton
