webaxol / pluglightjs

A light-weight JavaScript framework designed to create flexible and maintainable projects with a modular and hierarchical approach

• 🔭 I’m currently working on Mirroware


• 🌱 I’m currently learning WordPress, AngularJS


• 💬 Ask me about TypeScript, JavaScript, NodeJS


• 📫 How to reach me [email protected]


• ⚡ Fun fact I am left-handed (That ain't funny though)

---

Languages and Tools:

---

My Online Certificates

My Hackerrank Profile

---

pluglightjs's Issues

Missing built-in initializer

Setting up an application with CASES implies registering components such as: services, collections, events, agent types, etc. Therefore, it would be of great benefit to have a module responsible for initializing the things previously mentioned, so that the initialization process becomes more abstracted from the consumer of the framework. Not only having a built-in initializer would ease this task; there would be more security, as we will be able to check for errors before setting up everything.

AgentPool doesn't respect Objects' classes when assigning fields to new Agents

Agents-types are registered correctly; the prototype is correctly stored at AgentPool.#types, respecting the classes of objects defined at its attributes, for example:

class Example {
    constructor(){
        this.field = 'dummy';
    }
}

// Attribute A is stored with its class (Example)

typeA: {  attributeA : (instance of Example) }

However, when a new agent is created, its attributes (defined as objects) will be set as generic javascript objects, instead of keeping their original class.

// Notice that 'attributeA' is not defined as an instance of Example; it is a JavaScript vanilla Object

agent = {  #type : 'typeA', attributeA : { field : 'dummy' } }

This occurs because each agent attribute is assigned by creating a deep copy of the prototype's attributes; it doesn't recognize classes, only vanilla empty objects:

AgentPool.js - line 34

 this[field] = Object.assign({},_field); 

Missing delta-time at execution loop

The execution loop of does not provide information about execution time; it could be a problem when clients with different computer resources attempt to run a program, for example: a video game. Not implementing delta-time functions could vary how the same program executes at different clients; it is an issue especially for online interactive applications, where synchronization is a requirement.
Therefore, it is important to implement the delta-time feature as soon as possible.

Inheritance doesn't work properly when the framework is integrated with typescript modules

First of all, I imported the JavaScript vanilla World class to another project, which utilizes TypeScript; the intention was making a subclass as an extra layer to implement new functionalities on top of the framework's World class. However, Typescript sub-classes only inherit those fields and methods from their super class which are explicitly defined as "public." ECMAScript does not support the reserved word public for classes, therefore, there is not a simple way of letting typescript to inherit those attributes from JavaScript vanilla classes.

Possible solution:

• Making a version of the framework using Typescript: It could be expensive, but those applications using Typescript could benefit from it.