I have one small quibble with this. I like symmetry in add/remove methods, so
I'd prefer either:
addValueUpdatedListener/removeValueUpdatedListener
or
addValueUpdatedChangeListener/removeValueUpdatedChangeListener
The former probably makes more sense, since the parameter is a
Cool thx, must have got mixed up w/ the previous patch.
Made the change for addValueUpdatedListener/removeValueUpdatedListener
Thanks!
On 3/19/2014 10:47 AM, Mark Yvanovich wrote:
I have one small quibble with this. I like symmetry in add/remove
methods, so I'd prefer either:
+1
Am 18.03.2014 09:04, schrieb Thomas Andraschko:
+1
2014-03-17 21:38 GMT+01:00 Werner Punz werner.p...@gmail.com
mailto:werner.p...@gmail.com:
+1
Am 17.03.14 08:05, schrieb Leonardo Uribe:
+1
2014-03-17 2:05 GMT-05:00 Leonardo Uribe lu4...@gmail.com
[
https://issues.apache.org/jira/browse/TRINIDAD-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933603#comment-13933603
]
Ji Kim edited comment on TRINIDAD-2459 at 3/19/14 7:36 PM:
---
So as requested I am sending out a separate email to get responses from
the crowd regarding this JIRA
[https://issues.apache.org/jira/browse/TRINIDAD-2459].
The change is to add 2 new APIs to Trinidad's UIXEditableValueTemplate =
public void *addValueUpdatedListener*(ValueUpdatedListener
[
https://issues.apache.org/jira/browse/MYFACES-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13940892#comment-13940892
]
Michael Kurz commented on MYFACES-3868:
---
I opened the spec issue
For note =
This is to allow components and etcetera to listen to this event by
adding a listener in the new
UIXEditableValueTemplate.addValueUpdatedListener API.
The pro of adding this event + listener is that various components can
then listen when the value has been updated in the model.
