Message from JavaScript discussions

June 2017

— That will be calculated primarily by the Collector classes, with the game goal being "get X entity to Y collector"

Message permanent page

— 

FluxAxe serves as the Flux framework with some React-like components built in. I use Differentia as the default diffing algorithm

— That way we can render the Pixi WebGL view as if we were running a page with React

— Do you actually write it like that?

— No, it's a mess at the moment

— Oh man, no const or shorthand function properties

— I just hashed out some constructors to get a feel for what I needed, they will be made into Flux actions

Message permanent page

— I see

— I don't think it even runs at the moment, haha

— Pretty much everything will be in a Flux action, no matter what, it will be very smooth when it's done. I also invented a way for view components to reach into datastore state without running data through the datastore, with what I call Immediate Mode view components. It pulls from the view domain's stored state and also allows for outside parameters to be passed in, breaking some Flux rules but allowing very fast reaction times

Message permanent page

— So for highlighting objects with the mouse, the view component doing the highlighting has to know a few things like what kind of object it is etc... I previously ran that action through the datastore, but the propagation time to the component was too slow to support someone moving their mouse around.

Message permanent page

— So the immediate mode component accepts a parameter of where the mouse is from the event handler, does some conditional based off what object that is in it's own state (not from presentation state) and then highlights or ignores the object based on the result, all without interacting with the datastore but while still using it's state. in "normal" Flux you would pass that parameter all the way through the datastore

Message permanent page