Re: [jira] Resolved: (TRINIDAD-731) xOffset/yOffset don't get correctly processed by plugins, switch to horzOffset/vertOffset for simplicity and clarity.

2007-09-25 Thread Danny Robinson
Both. If you grab the trunk and tweak the CorePanelPopup.xml attributes back to using xOffset/yOffset, then also tweak findTypeConstants() in the renderer, then... In JSP, you get /components/panelPopup.jspx(39,102) Unable to find setter method for attribute: yOffset In Facelets, you get

Re: [jira] Resolved: (TRINIDAD-731) xOffset/yOffset don't get correctly processed by plugins, switch to horzOffset/vertOffset for simplicity and clarity.

2007-09-25 Thread Adam Winer
It's probably the case that the component and JSP tag methods need to be setxOffset instead of setXOffset() - or you need to supply a BeanInfo. But the best and simplest option, I think, is just to rename the properties to xoffset and yoffset, no caps - like halign and valign. -- Adam On

[jira] Resolved: (TRINIDAD-731) xOffset/yOffset don't get correctly processed by plugins, switch to horzOffset/vertOffset for simplicity and clarity.

2007-09-25 Thread Danny Robinson (JIRA)
[ https://issues.apache.org/jira/browse/TRINIDAD-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Robinson resolved TRINIDAD-731. - Resolution: Fixed Reverted back to xoffset/yoffset (lower-case). Release notes have

Re: [jira] Resolved: (TRINIDAD-731) xOffset/yOffset don't get correctly processed by plugins, switch to horzOffset/vertOffset for simplicity and clarity.

2007-09-24 Thread Adam Winer
Remind me what the issue is? Is it JSP tags, Facelets, both, something else? -- Adam On 9/24/07, Danny Robinson [EMAIL PROTECTED] wrote: I know. When I made the name changes, I knew the plugins should really get fixed ;-). Any hints on where to look in the plugins would really help

Re: [jira] Resolved: (TRINIDAD-731) xOffset/yOffset don't get correctly processed by plugins, switch to horzOffset/vertOffset for simplicity and clarity.

2007-09-21 Thread Danny Robinson
Hard to say that they are breaking, because I'm not certain they ever worked ;-) I'll update the release notes to cover this though. D. On 9/21/07, Andrew Robinson [EMAIL PROTECTED] wrote: Is this a compatibility breaking change (meaning that the old attributes were removed)? If so, were

[jira] Resolved: (TRINIDAD-731) xOffset/yOffset don't get correctly processed by plugins, switch to horzOffset/vertOffset for simplicity and clarity.

2007-09-21 Thread Danny Robinson (JIRA)
[ https://issues.apache.org/jira/browse/TRINIDAD-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Robinson resolved TRINIDAD-731. - Resolution: Fixed Fix Version/s: 1.0.3-core Switched attribute names to

Re: [jira] Resolved: (TRINIDAD-731) xOffset/yOffset don't get correctly processed by plugins, switch to horzOffset/vertOffset for simplicity and clarity.

2007-09-21 Thread Adam Winer
Yech, why don't we just fix the plugins??? -- Adam On 9/21/07, Danny Robinson [EMAIL PROTECTED] wrote: Hard to say that they are breaking, because I'm not certain they ever worked ;-) I'll update the release notes to cover this though. D. On 9/21/07, Andrew Robinson [EMAIL PROTECTED]