The context there is interesting: appears to be the ability to virtually reallocate memory between virtual machines. That sounds like a growth area but current niche case. Chances are you're one of those who'd like the capability to do that... :)

I thought that was "Peanuts" Linus and I was excited.

Well, the pope also hears voices in his head (you know, conversations with God and all), and he seems to act on them accordingly. So he can hardly be a critic of someone who hears a voice that tells him to kill the pope. That would be hypocritical!

What are you talking about?

An optional callback on a dialog box object for when users click the inactive region outside a modal dialog is a totally sane request, given that most callers will want to somehow indicate to the user that they can't click out there.

That's the most generic case, having a callback. No policy in the library!

But then the border flashing is one of the most common callbacks people would provide, so I'd provide that callback as a static class members, so people can do:

dialogInstance.setOnModalClick(DialogClass.BorderFlash);

And then BorderFlash is a function which just adds/removes a CSS classname to the dialog every 200 ms, which they can then style themselves. Again, very little policy... just the 200 ms and perhaps how long to flash.

But you could even make those configurable:

dialogInstance.setOnModalClick(DialogClass.borderFlash({ speed: 300, flashes: 20, className: "borderFlash" });

Where borderFlash is a class function returning a customized callback function.