[
https://issues.apache.org/jira/browse/PIVOT-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875513#action_12875513
]
Appddevvv commented on PIVOT-514:
---------------------------------
I'll work up a patch with DefaultProperty and try to figure out how you are
implementing testing to add some tests.
As a thought, I don't bind being a little specific compared to any other
systems. I think you'll eventually need similar capabilities that other similar
frameworks have implemented as pivot is built out especially around working
across the logical component tree, managing a property system that is robust,
improving compiler/tool checking so everything is not completely string based
or decoupling from the listener pattern and decoupling styles/triggers in a
tool friendly way or using more interfaces versus concrete classes. All of
these things can become quite burdensome to manage without some type of
support: e4, wpf, etc. I hit many of the same framework issues when I was
sketching out a similar system and started implementation. But one step at a
time based on need.
> create an annotation to specify the default "child" property of a component
> used by the serializer to attach children objects
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: PIVOT-514
> URL: https://issues.apache.org/jira/browse/PIVOT-514
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Reporter: Appddevvv
> Priority: Minor
> Fix For: 1.6
>
>
> Add an annotation called @ContentProperty that specifies the default property
> to attach children to in the serializer. I found that I was making mistakes
> when creating WTKX that this annotation and a default "child attachment"
> approach could help. Benefits include:
> a) The client does not need to know which property to attach the children to.
> b) To add objects to a collection the parent object does not need to extend
> from sequence. The sequence can be contained in the object instead of
> implementing the interface. Containment can be another approach to getting
> content into the parent objects versus inheritance.
> c) You can change some of the properties in the class where attachment occurs
> and your WTKX files do not have to change.
> The default mechanism would be similar to what exists today. It's a simple
> extension of it. The "attach child" search would be:
> a) If the content property is specified, use that property to add the child
> to. If the content property is a collection, add it to the collection.
> b) If the content property is not specified,
> b.1) If the parent object is a collection (this is how it is handled today)
> then add it to the collection using the List.add(Object) method.
> b.2) Add it to the property specified in the XML. This is also how it is
> handled today.
> I wrote this for a small modeled framework similar to pivot and could work up
> a couple of patches for this. This is very similar to how wpf handles child
> content specifications in XML. Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
