You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Greg Brown (JIRA)" <ji...@apache.org> on 2010/06/23 14:50:50 UTC
[jira] Resolved: (PIVOT-541) Remove "name" properties in Menu.Item
and Menu.Section
[ https://issues.apache.org/jira/browse/PIVOT-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Brown resolved PIVOT-541.
------------------------------
Resolution: Fixed
> Remove "name" properties in Menu.Item and Menu.Section
> ------------------------------------------------------
>
> Key: PIVOT-541
> URL: https://issues.apache.org/jira/browse/PIVOT-541
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Reporter: Greg Brown
> Priority: Minor
> Fix For: 2.0
>
>
> These properties were meant to facilitate section and item lookup but thus far have not been used in practice. Additionally, Menu.Item's "name" property now conflicts with the "name" property defined by Component.
> This support can be easily re-added later by overriding Component#setName() if the functionality is deemed valuable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Resolved: (PIVOT-541) Remove "name" properties in Menu.Item
and Menu.Section
Posted by Greg Brown <gk...@mac.com>.
Menu.Item still has the name property it inherits from Component.
On Jun 23, 2010, at 9:09 AM, aappddeevv wrote:
> Is an id or name still on the menu item? I use a property like that to do
> menu management.
>
> -----Original Message-----
> From: Greg Brown (JIRA) [mailto:jira@apache.org]
> Sent: Wednesday, June 23, 2010 8:51 AM
> To: dev@pivot.apache.org
> Subject: [jira] Resolved: (PIVOT-541) Remove "name" properties in Menu.Item
> and Menu.Section
>
>
> [
> https://issues.apache.org/jira/browse/PIVOT-541?page=com.atlassian.jira.plug
> in.system.issuetabpanels:all-tabpanel ]
>
> Greg Brown resolved PIVOT-541.
> ------------------------------
>
> Resolution: Fixed
>
>> Remove "name" properties in Menu.Item and Menu.Section
>> ------------------------------------------------------
>>
>> Key: PIVOT-541
>> URL: https://issues.apache.org/jira/browse/PIVOT-541
>> Project: Pivot
>> Issue Type: Improvement
>> Components: wtk
>> Reporter: Greg Brown
>> Priority: Minor
>> Fix For: 2.0
>>
>>
>> These properties were meant to facilitate section and item lookup but thus
> far have not been used in practice. Additionally, Menu.Item's "name"
> property now conflicts with the "name" property defined by Component.
>> This support can be easily re-added later by overriding
> Component#setName() if the functionality is deemed valuable.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
RE: [jira] Resolved: (PIVOT-541) Remove "name" properties in Menu.Item
and Menu.Section
Posted by aappddeevv <aa...@verizon.net>.
Is an id or name still on the menu item? I use a property like that to do
menu management.
-----Original Message-----
From: Greg Brown (JIRA) [mailto:jira@apache.org]
Sent: Wednesday, June 23, 2010 8:51 AM
To: dev@pivot.apache.org
Subject: [jira] Resolved: (PIVOT-541) Remove "name" properties in Menu.Item
and Menu.Section
[
https://issues.apache.org/jira/browse/PIVOT-541?page=com.atlassian.jira.plug
in.system.issuetabpanels:all-tabpanel ]
Greg Brown resolved PIVOT-541.
------------------------------
Resolution: Fixed
> Remove "name" properties in Menu.Item and Menu.Section
> ------------------------------------------------------
>
> Key: PIVOT-541
> URL: https://issues.apache.org/jira/browse/PIVOT-541
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Reporter: Greg Brown
> Priority: Minor
> Fix For: 2.0
>
>
> These properties were meant to facilitate section and item lookup but thus
far have not been used in practice. Additionally, Menu.Item's "name"
property now conflicts with the "name" property defined by Component.
> This support can be easily re-added later by overriding
Component#setName() if the functionality is deemed valuable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.