MessageType.APPLICATION constant in use?

Hi I can't find a use for the constant MessageType.APPLICATION in the pivot code. Is it intended for something, or can I remove it? -- Noel Grandin

[jira] Resolved: (PIVOT-538) Table is uneditable when opened modally

[ https://issues.apache.org/jira/browse/PIVOT-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Brown resolved PIVOT-538. -- Resolution: Not A Problem OK, great. Since you have it working now, I'm going to resolve this as not a

[jira] Created: (PIVOT-546) Add a context argument to Bindable#initialize()

Add a context argument to Bindable#initialize() --- Key: PIVOT-546 URL: https://issues.apache.org/jira/browse/PIVOT-546 Project: Pivot Issue Type: Improvement Components: core-beans

[jira] Resolved: (PIVOT-546) Add a context argument to Bindable#initialize()

[ https://issues.apache.org/jira/browse/PIVOT-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Brown resolved PIVOT-546. -- Resolution: Fixed Add a context argument to Bindable#initialize()

[jira] Commented: (PIVOT-468) Update tutorials to use Bindable where applicable

[ https://issues.apache.org/jira/browse/PIVOT-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882159#action_12882159 ] Greg Brown commented on PIVOT-468: -- With the introduction of the context argument

[jira] Updated: (PIVOT-239) Create an Eclipse launch configuration for ScriptApplication

[ https://issues.apache.org/jira/browse/PIVOT-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Brown updated PIVOT-239: - Priority: Major (was: Minor) With an increased emphasis on Bindable (see PIVOT-546), this feature will

[jira] Commented: (PIVOT-544) Add a command line argument, --undecorated, to support removing native Frame chrome on a non-fullscreen window

[ https://issues.apache.org/jira/browse/PIVOT-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882229#action_12882229 ] Roger Whitcomb commented on PIVOT-544: -- Just wanted to add to the use case for this

[jira] Commented: (PIVOT-544) Add a command line argument, --undecorated, to support removing native Frame chrome on a non-fullscreen window

[ https://issues.apache.org/jira/browse/PIVOT-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882289#action_12882289 ] Greg Brown commented on PIVOT-544: -- I think the existing full-screen mode might be better

Re: [RFC] Selection change events

The performance impact should be negligible. On Jun 24, 2010, at 5:52 PM, Sandro Martini wrote: Hi Greg, for me the change is right, and maybe with this application selection listeners could see what to do (and when it's the case ignoring the indirect change event, like today) ... and on all

Re: [RFC] Selection change events

The performance impact should be negligible. I was sure of it :-) ...

Re: PIVOT-535

To me some parts are not-so-clear, so maybe showing some minimal classes (for example a minimal and simple usage) could help to clarify and comments ... Bye, Sandro

FindBugs report on trunk

Hi to all, some little things seen by FindBugs on Pivot trunk: Core: BeanSerializer.java:81 Method org.apache.pivot.beans.BeanSerializer$NamedObjectBindings.putAll(Map) makes inefficient use of keySet iterator instead of entrySet iterator Tools: EventLoggerSkin.java:44

Re: FindBugs report on trunk

Core: BeanSerializer.java:81 Method org.apache.pivot.beans.BeanSerializer$NamedObjectBindings.putAll(Map) makes inefficient use of keySet iterator instead of entrySet iterator Ignore this. Tools: EventLoggerSkin.java:44 org.apache.pivot.tools.wtk.EventLoggerSkin$TreeNodeComparator

[jira] Resolved: (PIVOT-468) Update tutorials to use Bindable where applicable

[ https://issues.apache.org/jira/browse/PIVOT-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Brown resolved PIVOT-468. -- Resolution: Fixed Update tutorials to use Bindable where applicable

RE: [RFC] Selection change events

I'm not sure of the current implementation, but if by doing a selection indirectly, you fire an event for each selection, as it is selected in the set being set, then that could be inefficient or at least push the burden of inefficiency into the client. If it fires after all of them have been

RE: [jira] Resolved: (PIVOT-542) enable the serializer to initialize components written in java code

Thoughts with . My mail program did not auto the previous email :-) Thanks for responding to this. I'll close this out. -Original Message- From: Greg Brown [mailto:gkbr...@mac.com] Sent: Wednesday, June 23, 2010 2:41 PM To: dev@pivot.apache.org Subject: Re: [jira] Resolved: (PIVOT-542)

[jira] Created: (PIVOT-547) Bug in JSON.java prevents the use of Element as a destination for data binding

Bug in JSON.java prevents the use of Element as a destination for data binding -- Key: PIVOT-547 URL: https://issues.apache.org/jira/browse/PIVOT-547 Project: Pivot

[jira] Updated: (PIVOT-547) Bug in JSON.java prevents the use of Element as a destination for data binding

[ https://issues.apache.org/jira/browse/PIVOT-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Allman updated PIVOT-547: - Attachment: xml_binding_fix.patch Proposed fix Bug in JSON.java prevents the use of Element as