
Registered since September 28th, 2017
Has a total of 4281 bookmarks.
Showing top Tags within 3 bookmarks
howto information development guide reference administration design website software solution online service product business uk tool company linux code server application system web list video marine create data experience tutorial description explanation learn technology build article blog world project boat download windows lookup security free performance javascript technical london beautiful control network tools support course file research purchase image library programming youtube example php construction install opensource community html quality computer feature profile power browser music platform process mobile work user share manage professional database hardware buy industry advice internet dance developer installation search 3d camera customer access travel material standard money test develop documentation review css engineering photography webdesign engine device digital speed event api source management question program client phone discussion content simple story water marketing yacht app account setup interface package idea fast communication compare cheap script market study easy live google resource operation demonstration contact startup
Tag selected: invalidate.
Looking up invalidate tag. Showing 3 results. Clear
Saved by uncleflo on March 5th, 2013.
Today, we are releasing Kraken, the distributed pub/sub server we wrote to handle the performance and scalability demands of real-time web apps like Asana. What problem does Kraken solve? One of the key promises of real-time web applications is that users will see changes made by other users as they happen, without hitting reload or refresh. Many of the up-and-coming reactive web frameworks initially accomplish this by periodically re-executing queries against the database. When we were building the early prototypes of Asana, our reactive framework (Luna) was no different.
luna pubsub realtime web html data incremental solution database invalidate messaging server query
Saved by uncleflo on January 24th, 2012.
Flex 4 introduced an awesome new skinning architecture. Among other things, the new architecture provides significantly better separation between a component and its skin. Flex 4 also promotes the use of states to the point where they are virtually mandatory in any non-trivial app. And that brings us to the question of the day: How do you communicate state information from the host component down to its skin? As always, we’ll dive into some examples to explore how things work. In our first example, we just want our skin to mirror the states of its host component. So, we begin with a simple component based on SkinnableComponent. And then we add three states: base, happy, sad. Here we discuss the code.
framework information guidelines development invalidate current communication component state spark skinning skin flex Adobe Flex
Saved by uncleflo on November 22nd, 2011.
As mentioned in other answers, the flash player is single threaded, if you don't break up your work into discrete chunks that can executed in separate "frames", you're going to see jumps and stutters in the ui, which is effectively what you're seeing. If you really must see that 12% message, then it's not enough to invalidate the display list, as the display list isn't getting a chance to update until after the 56% work has completed, you must explicitly interrupt the natural event cycle with a call to validateNow() after your message has been set.
invalidate update cycle complete display flex interrupt force refresh draw redraw screen displaylist
No further bookmarks found.