On Thu, Mar 19, 2009 at 17:35, Todd Volkert <[email protected]> wrote:
> >>(3) ApplicationContext - setInterval, clearInterval, setTimeout, > >>clearTimeout are not great names. > >>addIntervalTask(), removeIntervalTask(), addTimeoutTask(), > >>removeTimeoutTask() would be much better. > > > > I'm not opposed to changing the names, but I actually don't think they > are too bad - they are consistent with their JavaScript equivalents. If we > were to change it, "Task" is probably not the right terminology, since > you're queueing a Runnable, not a pivot.util.concurrent.Task. "Callback" > might be better. > Hmmm, I've noticed that elsewhere, and perhaps it makes sense for the API's between the applet and the browser, but for Java code, I would have thought that sticking to Java conventions made sense, and setXXX()/getXXX() in Java always means (a) modifying the value of a property and (b) the property in question is singular i.e. not a list
