Project

General

Profile

Task #4494

Redesign JS portion of the Hawat web interface

Added by Jan Mach over 1 year ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Development - GUI
Target version:
Start date:
01/08/2019
Due date:
% Done:

0%

Estimated time:
To be discussed:
No

Description

The current design of the JS part of the web interface does have few flaws and drawbacks. It recommend to take a step back and reconsider some design choices with future development in mind.

#1

Updated by Pavel Kácha over 1 year ago

Please, be more specific in wording. Design decisions should be based on clear deficiencies and at least sparsely documented at the issue concerned. However this issue mostly sounds like “Something loose in cockpit” ? “Ok, something tightened in the cockpit.” (ref)

What are the flaws and drawbacks, what needs reconsideration?

#2

Updated by Jan Mach over 1 year ago

Pavel Kácha wrote:

Please, be more specific in wording. Design decisions should be based on clear deficiencies and at least sparsely documented at the issue concerned. However this issue mostly sounds like “Something loose in cockpit” ? “Ok, something tightened in the cockpit.” (ref)

What are the flaws and drawbacks, what needs reconsideration?

I preferred discussing this issue at first in person. I have entered it here so that I would not forget to bring it up on the next meeting and I wanted to specify it more after the discussion. Communication solely via these notes is time consuming.

But ok, my issue with the current JS design is that there is no clear JS application structure in place. There is only jQuery, that is being used as well as possible. I have encountered the some problems when localizing the D3 charts and dataset tables in JS. These problems were regarding the order of code execution, some parts of the localization library were not yet initialized (because they were fetching external configuration files) and other parts of the application were already eager to use that functionality. Another problem was a lack of documentation for my use case, these tasks are usually taken care of by the JS framework. I have solved that issue temporarily by using synchronous AJAX get requests to fetch these important configurations, but there certainly is a better solution.

I would like to discuss this tomorrow on our meeting.

#3

Updated by Jan Mach over 1 year ago

  • Target version changed from 2.4 to 2.5
#4

Updated by Pavel Kácha about 1 year ago

  • Target version changed from 2.5 to 2.6
#5

Updated by Jan Mach 7 months ago

  • Target version changed from 2.6 to 2.7
#6

Updated by Pavel Kácha 4 months ago

  • Target version changed from 2.7 to Backlog

Also available in: Atom PDF