Done. See video at http://screencast.com/t/bJbGoswZrc.
Notice that in the comp suite demo, the progress bar starts with a value of 10 instead of 0. That's because the value is incremented in the getter. The getter is not just called by encode(), it is also called by decode() and maybe the framework (e.g. tag handler?). So the value shouldn't be changed in the getter. Ideally in this case it should be changed by a separate thread.
Also in this use case scenario, don't instinctively try to set the value on a change event, or you will end up with an infinite loop forever triggering change events.
Revision: 25917
Modified : /icefaces-ee/scratchpads/grimlock/icefaces/ace/component/resources/icefaces.ace/jquery/ui/jquery-ui.js
Modified : /icefaces-ee/scratchpads/grimlock/icefaces/ace/component/resources/icefaces.ace/progressbar/progressbar.js
Modified : /icefaces-ee/scratchpads/grimlock/icefaces/ace/component/src/org/icefaces/ace/component/progressbar/ProgressBarMeta.java
Modified : /icefaces-ee/scratchpads/grimlock/icefaces/ace/component/src/org/icefaces/ace/component/progressbar/ProgressBarRenderer.java
Added : /icefaces-ee/scratchpads/grimlock/icefaces/ace/component/src/org/icefaces/ace/event/ProgressBarChangeEvent.java
Revision: 29025
Modified : /applications/comp-suite/trunk/comp-suite/src/main/java/org/icefaces/samples/showcase/example/ace/progressbar/ProgressBarBean.java
Modified : /applications/comp-suite/trunk/comp-suite/src/main/resources/org/icefaces/samples/showcase/view/resources/messages.properties
Modified : /applications/comp-suite/trunk/comp-suite/src/main/webapp/resources/examples/ace/progressbar/progressBar.xhtml
Done. See video at http://screencast.com/t/bJbGoswZrc.
Notice that in the comp suite demo, the progress bar starts with a value of 10 instead of 0. That's because the value is incremented in the getter. The getter is not just called by encode(), it is also called by decode() and maybe the framework (e.g. tag handler?). So the value shouldn't be changed in the getter. Ideally in this case it should be changed by a separate thread.
Also in this use case scenario, don't instinctively try to set the value on a change event, or you will end up with an infinite loop forever triggering change events.
Revision: 25917
Modified : /icefaces-ee/scratchpads/grimlock/icefaces/ace/component/resources/icefaces.ace/jquery/ui/jquery-ui.js
Modified : /icefaces-ee/scratchpads/grimlock/icefaces/ace/component/resources/icefaces.ace/progressbar/progressbar.js
Modified : /icefaces-ee/scratchpads/grimlock/icefaces/ace/component/src/org/icefaces/ace/component/progressbar/ProgressBarMeta.java
Modified : /icefaces-ee/scratchpads/grimlock/icefaces/ace/component/src/org/icefaces/ace/component/progressbar/ProgressBarRenderer.java
Added : /icefaces-ee/scratchpads/grimlock/icefaces/ace/component/src/org/icefaces/ace/event/ProgressBarChangeEvent.java
Revision: 29025
Modified : /applications/comp-suite/trunk/comp-suite/src/main/java/org/icefaces/samples/showcase/example/ace/progressbar/ProgressBarBean.java
Modified : /applications/comp-suite/trunk/comp-suite/src/main/resources/org/icefaces/samples/showcase/view/resources/messages.properties
Modified : /applications/comp-suite/trunk/comp-suite/src/main/webapp/resources/examples/ace/progressbar/progressBar.xhtml