enbock / time-tracker Goto Github PK

The router config seems at moment not really pratically.

I have follow idea:

• We could write the Root-Node code, as example <Settings.... /> into a special template file *.html.tpl.
• Then is it possible to configure the route in a json:

{
  settings: {
    url: '/settings',
    root: '/Templates/Settings/root.html.tpl'
  }
}

Target:

• Some test running ;)
• Auto deploy to gh-pasges (for beginning, each commit)

On MDC should it possible to create custom color schema.

Target:

• Inject Custom CSS direct to document
• Removing of injected Rules

Currently is using the Axois library to XHR. The fetch API may save some compiling code.

Target

Get application testable, before implementing business functions.

Description

While the break of last year, I found very nice pattern and ideas in Uncle Bob Martin Books. That we should upgrade here, to see how it looks and work.

Story

As user I want create and use my own color theme.

See: https://github.com/enbock/Time-Tracker/wiki/2018.01.21-Languages

The module loader should get an own repository.

Target: The option page visible.

Investigate/experiment to use https://svelte.dev/

How we can handle the language data, to be able to change them in runtime?

Target:

• Find library
  • Fallback: Plan own component
• Figure out, how to inform conatiners about library changes
  • Event of React?
  • Redux?

The idea to do an "refresh" of language via the onChange on the language manager leads into a parallelism refresh system of the components.
Also is hold indirect the instance of remove visual components.
As third its couple the domain to the components.

To solve all 3 problems, lets remove the onChange function from the adapter and use Rect-state system to let refresh the components.

After we introduced the settings page, we need also a way to store the configurations.

At beginning is it enough to store it in any local browser storage.
But later on we want to synchronize with remote storage systems, like Google Drive, or AWS S3.

Be aware that we need different parts stored in different locations. So access keys will still store in local storage, other than language and color setup data.