You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
The *event* loop is built in, but I want to provide some convenient default way in the standard library of invoking a *rendering* loop. So: is this good? What would be better? whenever (graphics.start_render) for each v in (visible_objects) render(v, graphics.renderer);
I think you mostly eliminate the inner loop and say, “Here’s a scene, render what’s visible [under some predicates that affect visibility/opacity/debug flags]) from [point of view].” Making potentially visible sets an application concern doesn’t pay for itself.
Yeah, I was thinking something similar—build a scene graph, tell some standard library function “update & render this as needed”. But at the same time I’m thinking: I’m going to have to build that functionality, and a user should be able to as well, so what’s a good way to do it?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
