darlingjs / darlingjs Goto Github PK

concept

var recipe = darling.recipe(function(pipeline, ops) {
  return pipeline
    .pipe(system1(ops.system1))
    .pipe(system2(ops.system2));
});

Tap into the pipeline chain in order to perform operations on intermediate results within the chain

concept

darling.world()
  .pipeline(system1())
  .pipeline({
    tap: function(entities, interval, world) {
      //do some magic in between system1 and system2
    }
  })
  .pipeline(system2());

because update system only needed for realtime games but turn based games require other approach. Make it more like stream of gulp

Example:
request target for entities with ai.

concept

//version A
world
  .require('target')
  .pipe(dosometing())
  .pipe(onemore())
  .live(once())

//version B
entities
  .catch('target')
  .pipe(dosometing())
  .pipe(onemore())
  .live(once())

//version C
world
  .filter('target')
  .pipe(dosometing())
  .pipe(onemore())
  .live(once())

support such use case:

darling.system({
  lazy: true,
  updateAll: function(entities) {
    return new Promise((resolve, reject) => {
      //TODO: do some lazy job
    });
  }
})

make that modules won't require explicit description in deps of a world and connect them to the world automatic.

• update from latest https://github.com/kripken/box2d.js
• add package.json and bower.json
• fix undefined Box2D and Vec2

https://github.com/openopensource/openopensource.github.io

The documention indicates that the fps can be specified when creating the world object.... but from what I can tell the rate is dictated by the window.requestAnimationFrame function.

useful to create common recipes for modules

concept:

var recipe = function(ops) {
  return  {
    ops: ops,
    sequence: [
      system1,
      system2
    ]
  };
};

alternative:

var recipe = darling.recipe(function(pipeline, ops) {
  return pipeline
    .pipe(system1(ops.system1))
    .pipe(system2(ops.system2));
});

alternative 2:

var recipe = darling.recipe.sequence([
  system1(),
  system2()
]);

usage:

darling.world()
  .pipe(recipe({
    system1: 'query',
    system2: 123
  })
  .pipe(doSomething());

inspired by interfaces of https://github.com/rvagg/through2 and https://github.com/phated/undertaker

• https://github.com/darlingai - there will be page (https://darlingai.github.io)
• research existing virtual env for AI agents (which value I could bring with browser based env)
• design modern API
• make plans to support modern js (code style and env)
• get simple example to train AI (for example pingpong)
• heavily relay on node.js (to allow server side/headless simulation) but keep browser support
• what should be MVP
• stop using $
• start using mocha
• get read of grunt and use rollup

https://ci.testling.com/

• put all libs to npm
• organize source in node way with require of deps
• follow that one https://blog.codecentric.de/en/2014/02/cross-platform-javascript/

here is explanation who to fix olivierlacan/keep-a-changelog#71 (comment)

modify/add component trigger event, ever if we have component before

like $e, $update, etc