belevtsoff / earlpipeline Goto Github PK

Any port name longer than 5-10 letters is overlapping or renedered ugly. As a possible solution, one could just allow dynamic unit width

Currently, unit instance names are generated from the corresponding class name + some number. One should be able to specify the name other than the class name

Separate the unit/port rendering code from the other code mechanics, so that the user can easily modify it

Output port caching leads to the problem that when the state of a unit is changed, the thing still outputs old results. Possible solutions:

• remove catching
• implement something like 'wasModified' field

An in port "src" and out port "src" cause graphical glitch in the gui. Fix the create_id functions

Naming conventions for node/port names are now hard coded. This needs to be gotten rid of as soon as possible, i.e. one can implement a separate module with naming functions

Common keys like Enter and Tab do unexpected things

implment something to make units groupable. It will be ab important feature when the number of available components grows

when reloading the page, the graph is sometimes loaded in with errors

This will allow for such an important feature as the distinction between optional and mandatory ports

Maybe via adding an optional method overloadable stop method to base.GenericPipeline

Ember components are fancy html-tags. If the pipeline is a single component, it can be easily embeddable in larger projects

bootstrap-doalogs have white header which indicates that the css is not working properly

This may be implemented via CodeParameter

Take a look at this project: http://yeoman.io/
And this totorial: https://www.openshift.com/blogs/day-24-yeoman-ember-the-missing-tutorial

to that end:

• implement special cleanup handler for processes that exit gracefully

This should allow to outsource setting the default value to the backend

Those are much cooler

Implement comments for unit parameters (i.e. pop-ups on mouse hover)

Tests are crucial for JS stuff