Jump to content

Inquiry about future functionality


Bob H
 Share

Recommended Posts

Define "native to pixi.js" :)

Most of the things you mentioned sound like great plugins. v3 is all about keeping the core lightweight and agile, and putting most features into plugins. That way you can mix-match what you want and need, and the community can come up with great pixi content without it having to be int he core library.

There has been some movement on making Graphics better to support some of those features:

https://github.com/pixijs/pixi.js/pull/1587

Hopefully with changes like this, we can make the core more robust and easier to extend. Tweening will almost certainly never been in the core because it is not related to rendering, and we are a rendering engine. I've been trying to use the motto "If it doesn't need to be in core, it isn't".

Link to comment
Share on other sites

I appreciate an explanation of the design philosophy. When I used the term 'native', I meant functionality that is part of the pixi.js package.

 

I did extend and modifiy CreateJS a bit to achieve the functionality listed above -- see http://www.koolmoves.com/paintball/paintball.html

 

I am not an expert javascript programmer so I would prefer not having to write much code myself.

 

I will look into plugins compatible with pixi.js.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...