PixiJS Day277

Posted on June 14, 2020 by SzRaPnEL

If you have ??? instead of ‘żżż’ on your screen – this is encoding issue.

They come in many colors:

Your file is not UTF-8. You can check this with Notepad++. Some IDEs like Visual Studio 2019 have ANSI as default file save encoding. This needs to be changed.
Your initial HTML is not UTF-8. You need to add meta tag with charset=”utf-8″ attribute in the head section.
Your text in file is already save not in UTF-8 format. Make sure your file is saved as UTF-8 (look 1.) and retype the string.
You are passing raw invalid information. You need to use and pass encoded variable – encodeURI(variable) and use the decoded one – decodeURI(variable).
Your inner loaded JS is not UTF-8. You need to add charset=”utf-8″ attribute in the script src tag.

PixiJS Day76

Polishing what’s left and made game on a glimpse:

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

Nihil novi sub sole.

According to plan:

Game Loop is complete.

Main topics now:

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:

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:

Main issues:

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

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

Main observation:

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: