PixiJS Day72

First issue noticed on mobile:

  • mousedown not working as intended on mobile – should use Buttons or Touch Events instead
  • music sounds different
  • need of full screen emerges

PixiJS Day71

Nihil novi sub sole.

  • JS context – always a pain
  • .on .off for handling event (jQuery style)

According to plan:

  • PixiJS text fields [DONE]
  • Points system
  • Add containers to Monster Level [DONE]
  • Timer system
  • Finish Monster Level [IN PROGRESS]

PixiJS Day69 ;)

Dev in progress after heavy weekend.

Observations:

  • JS scope current solution let context=this
  • Mitigate “this” with context refrence since this gets “rebuild” in each concurrent function call scope

Goals:

  • JS Enums

PixiJS Day67

Dev at full speed (during nights) minus family activities (16h+).

 

I finally understood JS scope and it is very annoying to keep the right context.

Self managing it by this.context=this or let context=this is the current approach.

Goals:

  • Complete all views
  • Complete game loop

Main issues:

  • PixiJS event listeners take function name as param therefore cannot call context.funcName(context)

PixiJS Day66

After whole cosmos of gap in development I have started more activities in recent 3 days.

Main observation:

  • create views
  • create methods for view
  • create controlers

Main issues:

  • JS scope is nightmare
    • I am currently using methods that take context parameter to run inner method on that context example:
      • scannerBarShown(context) {
        context.showScannerTxt(context);
        }
    • There must be a better way, but this is how I am making sure calling a function will not generate “not a function” error.
  • GSAP tweens updated to most recent version (3.0.1) – backwards compatible
  • JS dispatch events unuable since they are designed for DOM elements (not custom object)
  • NPM works only on dedicated servers (unless provider will install packages for you)

Current development: