thaisrobba / ox Goto Github PK

I need to fix the frame rate - it is getting sped up and down when returning to a scene.

EDIT: I think I will have to refactor the sprite entity.

It should be possible to load data files like json and maybe txt with ease, simply by adding them to the assets manifest.

It should be possible to:

• reset timers
• call a function when they end (with bound this)
• pause/resume timers
• remove/add timers

What is says on the tin

Installing should be as easy as npm install ox2d or something like that.

This should make it dead easy to create things like fighting games clocks and whatnot.

Think Love's baby inspector.

Simple CSS should do the trick.

Maybe expose the keyboard the same way that ox.mouse is exposed? Perhaps expose ox.mouse further?

Perhaps think in terms of pointers (mouse + touch)? Hmmm.

It should greatly simplify things and helps with: #6

I know this is abandoned but do you have the docs available anywhere?

The link from the readme is broken:
http://ox2d.com/docs

Should be done sometime in the future.

There should one, even if it is quite simple.

Right now it bugs out when loading things from outside the regular folders. Gotta fix that.

Also, loading bar looks weird and we probably shouldn't say "loading", looks meh.

Entities are not currently removed when the scene changes. Oops.

What it says on the tin

The engine probably has a few corners that need sanding.

Perhaps an options file would be a good idea. People would be able to set up:

• Plugins
• Canvas size
• Cursor
• Debug (boolean)
• ???

Useful as heck.

One single object is nice but offering multiple costs very little and offers a lot.

Allow input from mouse, keyboard and touch.

Some of the build scripts return errors.

npm run assets
npm run entities
npm run scenes

$ npm run assets

> [email protected] assets c:\Users\aerze\projects\ox
> ./src/tools/assetsWatcher.js

'.' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "c:\\Program Files\\nodejs\\node.exe" "c:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "assets"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE
npm ERR! [email protected] assets: `./src/tools/assetsWatcher.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] assets script './src/tools/assetsWatcher.js'.
npm ERR! This is most likely a problem with the ox2d package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ./src/tools/assetsWatcher.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls ox2d
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\Users\aerze\projects\ox\npm-debug.log

Simple solution, I think, is to just but node in front of the string. windows doesn't read the hash bang and the top of the files.

{
        "assets": "node ./src/tools/assetsWatcher.js",
        "entities": "node ./src/tools/entitiesWatcher.js",
        "scenes": "node ./src/tools/scenesWatcher.js"
}

Should it sit in a json file within the data folder? Or an assets.js file within the src folder?

Want to have it sooner rather than later.

We don't want the garbage collector firing up all the time so, lets pool entities.

Ideally, a sprite should offer the following options:

• Anchor/Pivot
• Masking
• Crop
• Scale
• Rotation
• Transform
• Animation
• Event listeners.

Sometimes the game requires a refresh before it loads.

Bug happens in chrome. Ox sprite only shows afyer reloading the page.

I should have used the window offset instead of the weird present solution.

By default, the context is acessible through ox.ctx. It should and could be better though.
Perhaps this?

ox.Shape('rectangle', {
  x: 100, y: 100, w: 100, h: 100, fill: "lightblue"
});

or this?

ox.fillStyle('lightblue').fillRect(100,100,100,100);

It should have:

• Cursor png
• Animated sprite
• Probably something with a timer
• Something with keyboard/mouse???

There should be basic support for tweening properties.

Right now, if someone doesn't want the sprite entity, they are hosed. This should not be the case.

I should get started on preparing it for others to be able to use it and redistribute it.

Right now it is just stubbed - need to actually implement it.

It should highlight ox features by showcasing a simple demo of the engine. Doesn't need many pages. API docs should be hugely simple if at all available.

UH OH.

Right now it looks weird - there has to be a cleaner, better way to do it.

Right now things don't seem too clear. I've been devising a new API that should make the developer's intention crystal clear and allow for a certain level of "self documenting code".

• Scenes (Create, Set)
  ox.createScene
  ox.setScene
• Entities
  ox.createEntity
  ox.removeEntity
  ox.spawnEntity

...

I think the main engine should be kept as small as possible - some games don't need camera systems, some don't need particles, some don't need physics and so on.

ox should offer a clean and easy api to hook in plugins.

Official plugins should be developed and offered in a special repo, along with community made plugins.