Search the Community

Showing results for tags 'blink'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • HTML5 Game Coding
    • News
    • Game Showcase
    • Facebook Instant Games
    • Coding and Game Design
  • Frameworks
    • Phaser 3
    • Phaser 2
    • Pixi.js
    • Babylon.js
    • Panda 2
    • melonJS
    • Haxe JS
    • Kiwi.js
  • General
    • General Talk
  • Business
    • Collaborations (un-paid)
    • Jobs (Hiring and Freelance)
    • Services Offered

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Skype


Location


Interests

Found 5 results

  1. fubeca6

    Blinking Tile

    Good Evening, I'm trying to create a blinking tile. Here's what I have so far: function create() { this.timer = game.time.create(false); this.timer.loop(1000, updateCounter, this); this.timer.start();}function updateCounter() { if (this.burn) { this.burn.kill(); } else { createBurn(); }}function createBurn() { this.burn = game.add.sprite(224, 352, 'burn'); game.physics.enable(this.burn, Phaser.Physics.ARCADE); this.burn.body.immovable = true;}However, when I run this, it simply creates the tile over and over without ever killing it -____- I've toyed around a lot with the Phaser Timer examples, etc. but haven't been able to get it quite right. Any help would be greatly appreciated! Thanks
  2. https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/KsJCjyWwVkU/CdaO2W6NaIkJ Lots of slides from the conference. Definitely look at the Render Tree, mobile performance and Graphics ones.
  3. A very interesting read about what the Google engineers are doing to enhance rendering in blink: https://docs.google.com/document/d/1wYNK2q_8vQuhVSWyUHZMVPGELzI0CYJ07gTPWP1V1us/pub
  4. One of the topics that was suggested when I recently took a poll on Twitter/G+ of potential blogging topics was what kind of impact the switch to Blink has had on Chrome's WebGL implementation. I thought this would be a great area to talk about, because it allows me to dig into the guts of how WebGL works a bit more than most of you are used to. If you're not familiar with the situation already, Chrome recently switched rendering engines from WebKit to Blink, which is based off the WebKit source. The fact that we're so early in the life of Blink means that the two rendering engines haven't diverged too much yet, aside from dead-code cleanup on both ends, but even this early there are a few changes in how Chrome handles WebGL. http://blog.tojicode.com/2013/05/how-blink-has-affected-webgl.html
  5. WebKit is a lightweight yet powerful rendering engine that emerged out of KHTML in 2001. Its flexibility, performance and thoughtful design made it the obvious choice for Chromium's rendering engine back when we started. Thanks to the hard work by all in the community, WebKit has thrived and kept pace with the web platform’s growing capabilities since then. However, Chromium uses a different multi-process architecture than other WebKit-based browsers, and supporting multiple architectures over the years has led to increasing complexity for both the WebKit and Chromium projects. This has slowed down the collective pace of innovation - so today, we are introducing Blink, a new open source rendering engine based on WebKit. http://blog.chromium.org/2013/04/blink-rendering-engine-for-chromium.html