dhmmasson / rezbuild-emperor-tamarin Goto Github PK

Log when a criterion change

• Timestamp
• Aspect ( weight, blurIntensity )
• new value

Is your feature request related to a problem? Please describe.
some criteria should be sorted in ascending order ( greater is better, rpm, capacity... ) some should be sorted in descending order ( lower is better comsumption, noise level ).

Describe the solution you'd like
Criteria in the database should indicate the order they should be sorted.

TODO :

• Add in the criteria_type 2 types ascending and descending
• Change criteria_get_all.sql to get type_name as type
• Change Criterion.mjs constructor to add a param by name ( add type in the bracket l.35 ) and property type ( l.41 )
• Change in Technology updateDominance l.67 so that the > is > when criteria is ascending < when criteria is descending

Describe alternatives you've considered
Normalizing data in the db, not flexible and should be done everytime new values are to be added...

Is your feature request related to a problem? Please describe.
Implement the sorting algorithm found in baboon

Describe the solution you'd like
Algorithm presented in the research paper

Describe alternatives you've considered
none

Additional context
none

import from the db the description

change src/databaseConnector/sql/criteria_get_all.sql

Instead of generating the template.mjs on app start, have a similar process than the sass middleware. Provide a mjs on demand for each pug. Plus a template with all the runtime function

Create a basic User Interface :

• Display the list of technologies sorted
• Allows to modify weight and blur/granularity for every criteria

Implement the 2-dimensional interactor presented in Baboon.

NODE_ENV=development
PORT=3005
mysqlHost=localhost
mysqlUser=user
mysqlPassword=password
mysqlDatabase=dbname

Is your feature request related to a problem? Please describe.
The drag mouse icon is not always visible

Describe the solution you'd like
Having always the cursors

Improve the technology and criterion map in the sorter, so that there use is transparent to the dev.

•  Array access : mainly for of loop
•  Map access : through the name of the technologie/Criteria
•  Proxy the functions call to the right target ( sort to the array, add to the map/array )

When computing the dominance, the lower bound was used in all cases. On descending criteria that meant that criteria was even more accepting..

Describe the solution you'd like
use upper bound on descending criteria

there is no process.env.PWD in windows

backup the current state of all criteria locally ( linked to #10 )

It's possible to set a negative value to a criteria

Describe the solution you'd like
Prevent the criteria from accepting negative values

Describe alternatives you've considered
Always check for positive value when using criteria (which was done at most place...)

Keep sql requests out of the connector.mjs file

Generate the user interface through Pug templating.

Change the UI to reflect a given state ( local or server based )