• Table
• Chart

Adjust design on the elements (Kernel, Activity, Statistics) of the Right Sidebar to match the design of the neuron section (maybe use an expansion panel for the Statistics view).

Questions: @bweyers

Investigate the possibilities to unify the structure of the panels and scenes. It would be desirable to have a modular structure, which is identical (or at least similar) for both panels and scenes, so that new panels and scenes can be added with low effort.
Add Panel should give the possibility to select 2D- and 3D-panels (or at least to toggle the selection instead of the toggle on the Explorer button).
Further information: @bweyers

• Menu for simulation

• The left sidebar should be not pinned by default, but the option for pinning it should be accessible in the options.
• The left sidebar should contain the buttons Help and About below Settings (linking to help and about).
• The left side of the Editor icon should be flush with the left bar, the brain icon might be removed.

Questions:@bweyers

The behavior of the navigation bar could be optimized: Currently, switching between the Models and the Project view requires at least two clicks. This might be a bit cumbersome, if one needs to go back and forth more than one time.

Investigate the possibilities to give users the options for sending a bug report.
It needs to address some problems:

• Spam should be prevented.
• The reports should be helpful and reproducible.
• It should be easy (e.g. possible without a Github account, not every neuroscientist has one).
• ... (to be continued)

There are multiple issues regarding the context menus.

• In the NetworkNodeMenu, the style of the view for selecting parameters cuts the letters of the items.
• Same holds for the NetworkConnectionMenu.
• In the NetworkConnectionMenu, selecting ALL or NONE parameters has no effect.

The button to close the sidebar on the right side should be removed, the right sidebar will be pinned by default. Questions: @bweyers

In NEST Desktop the default port number for NEST Simulator is 5000.
However, there was a request that they have to manually change the port number in the settings.

Every setting values are integrated in js file in the production.
Thus, it was not possible to set default value before starting NEST Desktop.

An idea would be to outsource the settings of NEST Simulator to JSON file in public folder.

We will discuss this issue whether it generates sha-128 or sha-256.

src/core/network/network.ts and src/core/project/project.ts Do you think SHA-128 is sufficient for these purposes? Or will we run into trouble with hash collisions? We also have to keep in mind that the hash values generated by this module differ from the ones generated by OpenSSL (as used in the sha1sum or in the Crypto module of Node), so the computed SHA-128 sums with the object-hash package can not be compared with SHA-128 sums generated by other programs.

Add unit, etc. (feedback from the Hackathon)

The font in the outer sidebars is too small and barely readable, leading to blurred rendering in the browser.

Stefan reports that student mostly crashed the nest-server when the sim resolution is smaller than 0.1.
Maybe we should consider a smaller range for simulation time resolution, e.g. 0.1, 1.0, 10.0.

Dragging a node throws an error when leaving the window.

Auto-centering the network graph does not work anymore in the current dev version. It is not a big issue, since manual centering still works (e.g. when toggling the auto centering).

(mentioned by @jougs)

Currently, the mouse pointer does not indicate if a user trying to drag the background or just selected mistakenly a connection. It would be helpful if

• ... the cursor changed to move when the background is held and
• (if possible) to grabbing when a node is moved.

Inspect the possibilities to clone multiple selected nodes at once. This requires bigger efforts, since our selection currently works only for single elements and we would need to synchronize all other display elements with this selection (resp. give them some sort of useful content).
It should be helpful to add switching manually to a "multi-select mode", e.g. with a key combination or a separate button. When this mode is active, the selected nodes are marked in some other style than the "singe select"-node, but do not need to be synchronized with the other UI elements.

Plotly needs to be upgraded to version 2.0.0. The following problem needs to be addressed for this:

• The exported images contain artifacts: In column charts, the text "auto" is contained for every column.

The connector should be removed while nodes are moved around to improve the visibility. For questions: @bweyers

We should have a closer look at the performance of NEST Desktop in Vue to make sure we haven't introduced any undiscovered bottlenecks. This should be done in production mode, not in development mode.

• Performance testing
• Fix bottlenecks, if any
• Performance testing of the fixes

Concrete issues:

• #114

The key used to create multiple connections at once should be switched to ALT. For questions: @bweyers

• Menu for all projects
• Menu for each project

• Lab book interface
• Print to pdf

When searching the NEST Server, sometimes state 0 is returned while the ready state is displayed as 4 (READY).

An upgrade of the package @vue/eslint-config-typescript should be considered: It is currently on version 4.0.0 (2019 or before), the current version would be 7.0.0. A warning of possible problems is given at every compilation.

The color scheme should be checked. Optimally, a user can choose between color schemes.

Points to consider:

• Find a color scheme which has only few restrictions for people with common eye issues (https://en.wikipedia.org/wiki/Color_blindness#Red%E2%80%93green_color_blindness, etc.). Check https://davidmathlogic.com/colorblind/#%23D81B60-%231E88E5-%23FFC107-%23004D40-%2355B3FF.
• Colors from https://vuetifyjs.com/en/styles/colors/#material-colors would be helpful.
• Ask Sebastian Lehmann for ideas.

There seems to be an issue with the Vue watchers, especially if a component is used multiple times. Then multiple executions occur - but interestingly not in every case.

There should be a confirmation dialog when trying to delete a project.

The bin icon for deleting a whole network should be working with the Vue version.

Should appear in ToDo

• The typing of some variables is currently done by setting these types to any. It might be worth to have a closer look at these cases and try to find a solution for them.
• General strategies for typing like
  https://stackoverflow.com/questions/37263357/how-to-declare-and-import-typescript-interfaces-in-a-separate-file#37274839 (a global types.ts file)
  or
  https://stackoverflow.com/questions/36633033/how-to-organize-typescript-interfaces#36636368 (.d.ts files)
  could lead to some universal approaches here. It should be discussed which types these global file(s) should contain (and which should be kept local for performance reasons).

Examples:

• activityData, data, event (multiple and different occurrences)
• layer, trail : src/core/activity/animationScenes/activityAnimationSceneBox.ts, etc.
• scene: src/core/activity/activityAnimationGraph.ts
• route src/components/navigation/NavigationTemporary.vue
• ... (to be continued)

Regression: It should be possible to show more than one display like in the recent versions. (Stefan)

Controller interface for network activity

• Panels for chart
• Controller for animation

The documentation needs to cover the new changes introduced with NEST Desktop 3.0 (especially visual content).

When creating a node, all parameters are shown, which is a bit unintuitive.

In some usecases, the Same Origin Policy of Firefox prevents the access to NEST Server. However, the model information are loaded and the NEST Server is also found, but not all resources can be accessed (e.g. the favicon).
We will need some information about the differences within the SOPs of Firefox and Chrome/Chromium, since in Chrome, this is not a problem.

When new content is detected (upgrade, patched), then it reloads but it did not download new content.
Then it reloads again and it ends with endless reloading.

To stop it, I pressed CTRL + ALT + R.

It might be a good idea to change to a solid code documentation framework. This would pose the option to generate a webpage containing all our documentation and give easy hints for documentation.

A good list can be found at https://vue-community.org/guide/ecosystem/documentation.html. Vue Styleguidist (https://vue-styleguidist.github.io/docs/Documenting.html#code-comments) and Vuese (c.f https://dev.to/berniwittmann/quick--easy-documentation-generation-for-vuejs-components-7k6) looked interesting, Vue Styleguidist has the major advantage to use plain JSDoc comments we are already using, so this should be not a breaking change.

I tested Vue Styleguidist and jsdoc-vuejs, but both seem to struggle with the Composition API. Therefore, I would suggest to address this at earliest in summer, rather autumn (-> task for version >=3.1).

There is a small visibility problem with the right sidebar, as shown below (scroll bar not completely shown):

Additionally, the width of the sidebar differs when selecting the 'Statistics' or 'Code' section. Since there is not a sensible limit for line lengths, it is not possible to avoid line breaks in every case (for both sections), so this is a goal which we will never achieve anyway. All in all, I think we should envisage a compromise in terms of width which is unique for all sections of the right sidebar.

Several unclassified bugs

• Inverse synapse weight
• Inverse all weights of a node
• delete node with connections
• tooltip for elements in panel
• connection in graph clickable
• reset network graph
• update network graph
• gradient color for connection card

Small issue: The spacing of the 'Connection Rule' label is too small (see below).

The upload is not implemented yet.

• Local upload (from file)
• Upload from web