But seriously,
this is nice.
1) so we know a grid can redraw based on a process running, etc.
But I bet this is something in the render/init script that must be "listening" for something... but what?
2) And, since there are some who don't like "losing their place" when a screen redraws (like if you scroll down a big list, edit/save a rec, Aware redraws and puts you back at the top of a form), I wonder if this has that same drawback? Because when the "losing their place" issue is resolved, then it will be even more nice here to not have you dragged away from where you are on a screen.
3) If you have active filters, does it retain them when it redraws?
4) OK, here's how this can be really useful. IMHO. John might have missed this discussion at the R.I. conference... I have thought there is a need to alert someone based on an INBOUND EVENT/NOTIFICATION.
If you have callbacks/messages being processed by Aware, then there is a need to alert an current LIRU that something has happened that needs his attention (ie. a text message was replied to; an email came in; An email was opened by recipient, etc.). Based on the "old" CRM, it uses a badge to let you know that a msg. is waiting - but it does that by running a process every "x" seconds - which means [potentially] lots of users baning away on the database every 10,20,30 seconds unnecessarily. Sure would be nice for John's "listener" code to be installed in several "key" Queries/Forms, and the Rules that process these inbound events would have an easy way to let LIRU know something has happened.
just my $.03
jaymer...
