[jira] Created: (PIVOT-530) Create a doclet for WTKX (BXML)

2010-06-14 Thread Greg Brown (JIRA)
Create a doclet for WTKX (BXML) --- Key: PIVOT-530 URL: https://issues.apache.org/jira/browse/PIVOT-530 Project: Pivot Issue Type: New Feature Components: wtk-wtkx Reporter: Greg Brown

[jira] Commented: (PIVOT-524) Add default properties to components and other classes as appropriate

2010-06-14 Thread Greg Brown (JIRA)
[ https://issues.apache.org/jira/browse/PIVOT-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878817#action_12878817 ] Greg Brown commented on PIVOT-524: -- Be sure to add Javadoc to document the default property

[jira] Resolved: (PIVOT-520) add a name property to Component

2010-06-14 Thread Greg Brown (JIRA)
[ https://issues.apache.org/jira/browse/PIVOT-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Brown resolved PIVOT-520. -- Resolution: Fixed > add a name property to Component > > >

[jira] Resolved: (PIVOT-529) Allow attached properties to be specified using elements in WTKX

2010-06-14 Thread Greg Brown (JIRA)
[ https://issues.apache.org/jira/browse/PIVOT-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Brown resolved PIVOT-529. -- Resolution: Fixed > Allow attached properties to be specified using elements in WTKX > -

[jira] Updated: (PIVOT-527) add getCurrentElement() to WTKXSerializer

2010-06-14 Thread Greg Brown (JIRA)
[ https://issues.apache.org/jira/browse/PIVOT-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Brown updated PIVOT-527: - Summary: add getCurrentElement() to WTKXSerializer (was: add getEnclosingObject() to the serializer to su

Re: [jira] Updated: (PIVOT-514)

2010-06-14 Thread Greg Brown
>> Could you use the Action API here? > >> > Will check. Don't think so for these use-cases. Could you explain why? Based on what you have described, it seems like it might be a natural fit. >>> I am putting a >>> cross-cutting concern into the Component's scope and allowing it to >>> initial

[jira] Commented: (PIVOT-528) Allow Dictionary values to be specified using elements in WTKX

2010-06-14 Thread Greg Brown (JIRA)
[ https://issues.apache.org/jira/browse/PIVOT-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878771#action_12878771 ] Greg Brown commented on PIVOT-528: -- Yes. See the above example, which adds an instance of M

Re: Pivot 1.6->2.0

2010-06-14 Thread Greg Brown
Files with a .wtkx extension will still work fine. However, the "wtkx" namespace prefix will change to "bxml", the annotation will change to @BXML, and the serializer will change to BeanSerializer, so for consistency I think we'd want to recommend changing the file extension as well. Greg On J

Re: Pivot 1.6->2.0

2010-06-14 Thread Noel Grandin
Hi I don't have a problem with the version numbering, but is there any reason why you can't continue to support the WTKX extension for backwards compatibility? -- Noel On Mon, Jun 14, 2010 at 02:13, Greg Brown wrote: > Hi all, > > I'd really like to refactor WTKXSerializer to BeanSerializer and

[jira] Commented: (PIVOT-528) Allow Dictionary values to be specified using elements in WTKX

2010-06-14 Thread Appddevvv (JIRA)
[ https://issues.apache.org/jira/browse/PIVOT-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878655#action_12878655 ] Appddevvv commented on PIVOT-528: - Does this fix allow me to specify the contents of a user

RE: [jira] Updated: (PIVOT-514)

2010-06-14 Thread aappddeevv
Decorator works! At least in the early tests. See my comments with >>> Thanks! I'll test creating a map using elements (for the user data). That would finish all the use cases out. -Original Message- From: Greg Brown [mailto:gkbr...@mac.com] Sent: Monday, June 14, 2010 8:34 AM To: dev@p

Re: [jira] Updated: (PIVOT-514)

2010-06-14 Thread Greg Brown
> - Explain exactly what it is you are trying to do in as few sentences as > possible. > >> >> Create reusable behaviors with minimalistic API and usage requirements. Could you use the Action API here? >> I am putting a >> cross-cutting concern into the Component's scope and allowing it to >> i