Jump to content

Search the Community

Showing results for tags 'markup'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • HTML5 Game Coding
    • News
    • Game Showcase
    • Facebook Instant Games
    • Web Gaming Standards
    • Coding and Game Design
    • Paid Promotion (Buy Banner)
  • Frameworks
    • Pixi.js
    • Phaser 3
    • Phaser 2
    • Babylon.js
    • Panda 2
    • melonJS
    • Haxe JS
    • Kiwi.js
  • General
    • General Talk
    • GameMonetize
  • Business
    • Collaborations (un-paid)
    • Jobs (Hiring and Freelance)
    • Services Offered
    • Marketplace (Sell Apps, Websites, Games)

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 2 results

  1. Yo @Deltakosh I see your samples now using this new BABYLON.GUI stuff. What is the main reasons for using this babylon gui vs using regular html markup for NON-3D guis, like huds etc. I can see when you need to attach some 2D gui to a 3D Object in the scene. But if is just SCREEN OVERLAY stuff like sliders and buttons and text... What advantage does BABYLON.Gui have over regular HTML markup ???
  2. Hello Guys! at Grey Rook we had the need to have non-code descriptions of the PIXI stage and animations, you know, like HTML. So we created POM - PIXI Object Model. It is JSON and if you know PIXI you know POM: { "type":"sprite", "values": { "position": { "x":100, "y":100 }, "source":"image.png" } } We built all our tooling around this, one of our clients has nearly 3k animations using it, with over 99% of them sharing the exact same JavaScript and are pure JSON! We want to share some of the internal tools and helpers we wrote with the PIXI community. We are starting with POM - the most central piece. So please let us know if there is interest! The documentation is a bare minimum and we are going to improve it - let us know what you are looking for! http://greyrook.github.io/POM/ Details Our scene is composed of elements, like Containers, Sprites, Graphics, or any other custom element you come up with. What attributes these elements have is represented as JSON data, like the example above. All you have to do is pass the data representation to the manager and let it create the scene for you. It works like a factory, where you can register any custom Element you want, as long as it has the methods for processing the JSON data. We extracted POM out of our internal source tree and open sourced it. If there is interest more is to follow, for example our tweenJS-based AnimationManager, that takes JSON data of timelines and creates all the tweens for you, aswell as synchronize animations that use our custom tweens for controlling videos, and checking their buffering status. We hope this is useful for others too, so we can build it and make it awesome together. For a start we have created a minimal project page where you can find the information we have collected so far, we are currently mostly looking into improving our documentation, test coverage and examples. Why We built an online animation editor where users can create (and animate) scenes direcly in the browser and view them again anywhere else in a player. For this we mostly use PIXI (and TweenJS), the backbone of the project is our PIXI Object Model (POM) and its' manager. About us We are Grey Rook Entertainment, a software development and graphic design company from Mülheim an der Ruhr in Germany, designing and manufacturing interactive HTML5 expieriences, and connecting them with the real world.
×
×
  • Create New...