On the last meeting , we have discussed how the CDK should be improved
and agreed to create CDK Wish List wiki page.
Everyone involed have now chance to express what are the priorities he feel it would be nice to have in CDK.
Later I will take this discussion and prepare wiki page with links to issue tracker.
I will start:
- test base for testing features of CDK from high-level view (input/output)
- incremental build
- fix scanning for interfaces (XML-free inheritance of attributes using Java interfaces)
- full support for iterative/dynamic components
Brian Leathem has pointed out:
- allow casting in templates
Bernard Labno has pointed to:
- generating listener tags
I need more ! Here is a few ideas I had by using the CDK.
Improve scope of <cdk:object> tag : https://issues.jboss.org/browse/RF-12195
Regex or wildcar on "cdk:passThrough" : https://issues.jboss.org/browse/RF-12200
Common and usefull methods automatically generated : https://issues.jboss.org/browse/RF-12201
Great thoughts, Paul.
I'm thinking if RF-12195 is actually something which Brian ran into:
Wildcard support seems pretty reasonable.
Even if you need to leave some on* attribute not taken, you can use onmouse* onkey*.
There is one option already for:
you can import a static method from any class: <cdk:import>:
I think it could be then used with EL, not only with <cdk:call expression="..." />.
RF-12195 is different from RF-11668. The latter deals with perfomeing a cast, whereas the former deals with the distinct functions (encodeBegin and encodeEnd) generated by the parts of the CDK template before and after the <cdk:bogy/> tag. Any cdk:object used in both sections has to be defined in both sections. This repetition looks odd in the template.
+1, wildcard support for imports would be great!
Added feature request to support for cdk:fragment tag as discussed on IRC:
Support for CDK fragments to allow recursion and abstraction of code