BlockUI / BlockPanel summary
Posted: 31 Aug 2012, 20:04
UP to this point, we have been using custom java code in each a4j:support's on[event] and oncomplete attribute to block events and visually indicate that events are blocked.
So I'm interested in p:blockUI, pe:blockUI, and pe:blockPanel
However, after reading every reference that a search on BlockUI turned up, it's still not 100% clear what the differences are.
It appears that pe:blockUI also blocks keys but not every kind of ajax request, and also allows you to specify blocking only certain kinds of events, although it's unclear whether that means we're blocking everything only when certain events are initiated, or if once we start blocking (on any event), we are only stopping certain events during blocking.
p:blockUI appears to be a much more limited subset of pe:blockUI functionality.
Internally, p:blockUI was written from scratch while pe:blockUI uses JQuery blocking infrastructure.
pe:blockPanel appears to be a convenience component that blocks everything outside of a panel allowing modal panel behavior. Basically a replacement strategy for rich:modalPanel.
Do I have this right?
Code: Select all
event="onclick"
onclick="process();"
oncomplete="processStop();"
However, after reading every reference that a search on BlockUI turned up, it's still not 100% clear what the differences are.
It appears that pe:blockUI also blocks keys but not every kind of ajax request, and also allows you to specify blocking only certain kinds of events, although it's unclear whether that means we're blocking everything only when certain events are initiated, or if once we start blocking (on any event), we are only stopping certain events during blocking.
p:blockUI appears to be a much more limited subset of pe:blockUI functionality.
Internally, p:blockUI was written from scratch while pe:blockUI uses JQuery blocking infrastructure.
pe:blockPanel appears to be a convenience component that blocks everything outside of a panel allowing modal panel behavior. Basically a replacement strategy for rich:modalPanel.
Do I have this right?