Yes. Have read that. I have a hunch we are thinking similarly but using different ways of describing it. My chunky responses don't help.
-----Original Message----- From: Greg Brown (JIRA) [mailto:j...@apache.org] Sent: Wednesday, June 09, 2010 8:46 AM To: dev@pivot.apache.org Subject: [jira] Commented: (PIVOT-520) add a name property to Component [ https://issues.apache.org/jira/browse/PIVOT-520?page=com.atlassian.jira.plug in.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877063#action_1 2877063 ] Greg Brown commented on PIVOT-520: ---------------------------------- If IDs in XAML get translated to variable names, then they work exactly like WTKX IDs. WTKX isn't compiled into a class like XAML, but WTKX IDs still become variable names. They are accessible by script code, and by Java code if the root element implements Bindable. Have you used the @WTKX annotation or any <wtkx:script> tags yet? If not, it might help to review the WTKX Primer - this may shed some light on how IDs work. The Stock Tracker tutorial in Pivot 1.5 and the Scripting tutorial may also be of interest. > add a name property to Component > -------------------------------- > > Key: PIVOT-520 > URL: https://issues.apache.org/jira/browse/PIVOT-520 > Project: Pivot > Issue Type: Improvement > Components: wtk > Reporter: Appddevvv > Priority: Minor > Fix For: 1.6 > > > Add a name property to Component > a) A getter/setter > b) A method to Container for Component getNamedComponent(String componentName) > The name should default to an the wtkx:id if one is specified for that component or if the name is not specified, null. If a name is specified and no wtkx:id is specified , it should become the wtkx:id of that component. The name must be a valid java identifier, otherwise an serialization exception should be thrown. The name used in the component should be left and right whitespace trimmed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
