explorviz-archive / explorviz-frontend Goto Github PK

The double click is an old pc-era based feature. It will (probably) never find its way into mobile devices.

We should discuss, if we want to use

1. The Tap gesture for opening / closing packages
2. The Press gesture for highlighting entities

Have a look at this demo: https://codepen.io/jtangelder/pen/lgELw Again: A short mouse click would open / close packages (double click at the moment). Holding the mouse button for a short time would highlight entities.

What do you say?

The line (representing the communication between two classes) is not visualized correctly in the application level perspective. Right now it ends/starts above the class instances (see picture) , but the class instance should be the source/target point.

Rebuild ExplorViz's navbar in this new frontend (Bootstrap Navbar https://getbootstrap.com/components/#navbar)

At the time of writing, the JSONAPISerializer does not provide a way to save a model with its relationships. You can save the type and ID of a relationships by customizing the serializer with a attrs-property, but this will not include any data of the related model, e.g. properties like names, ip adresses etc.

This feature is necessary for extensions (updating models in the backend-extension) and probably for the core at some time. Unfortunately, it is not considered in version 1.0 of the JSONAPISpec, hence the missing the feature in the Ember serializer.

There is a discussion that notes this feature ("Determine critical features for 1.1."). Thus, the Ember Data team will probably implement it when JSONAPISpec 1.1 arrives.

As workaround we can use the Ember-Data-Save-Relationships-Addon. The JSONAPI-Converter of the backend correctly converts the embedded properties in related models.

When JSONAPISpec 1.1 arrives, we will need to remove possible uses of the workaround and use the native approach of the future serializer.

Add a dialog for choosing a specific landscape and another one for uploading landscapes. (LandscapeRepositoryModel)

We need to provide an exception handling for unavailable timestamps from the backend, i.e., when clicking on a specific timestamp within the timeline.

Related to #34 and #16 (Frontend).

Use three.js to rebuild the 3D application renderer.

The dependency ember-data was updated from 3.4.1 to 3.4.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-data is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency ember-concurrency was updated from 0.8.20 to 0.8.21.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-concurrency is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The landscape-reload service loads all data at the moment. Obviously, it's better to load only data that is necessary for the current visualization.

Possible procedure:
If an application is clicked in the landscape viz -> load all data for this application every ten seconds and pause landscape-reload. If user goes back to landscape viz -> pause the application-reload service (to be developed) and restart landscape-reload of latest-landscape.

A new backend resource (ApplicationResource) is necessary.

Enhance the search within the application perspective.
Ideas: auto-completion instead of first matching.

Optimize the application labeling. The names are too small and the position is not ideal. Names should be shortened and the full name could be provided via a HTML popup on request.

Additionally provide a quick-start guide with controller-mapping images (Vive & Rift) for the upcoming release.

Version 1.2.8 of ember-auto-import was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-auto-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency ember-source was updated from 3.4.1 to 3.4.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-source is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

During runtime the Ember Store is growing and consumes more and more memory.
Idea: Cleanup the store and keep only important data, possibly can be triggered via JS?

I open this issue here, but it affects the explorviz-backend as well. I would like to switch to Jenkins for a full control CI build. For that, remote master branches should be protected. To contribute changes to the master, developers should create a pull request (as shown in https://github.com/kieker-monitoring/kieker/pulls) with changes, which can be auto-merged by git. Then @czirkelbach or I use the Jenkins Github pull request builder plugin to trigger a build that does the following:

• Most of these steps
• Test environment

Static analysis should consist of the following:

Backend:

• Checkstyle
• Findbugs/Spotbugs
• PMD
• Sonarqube
• Code Climate

Frontend:

• ESLint
• Code Climate Example

More sources:

• https://jenkins.io/blog/2017/04/18/continuousdelivery-devops-sonarqube/

The interaction in the frontend is not working anymore when using Firefox.
Hence, we are limited to use Google Chrome at the moment.

Version 3.4.0 of ember-cli was just published.

This version is covered by your current version range and after updating it in your project the build failed.

ember-cli is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Loading previously recorded landscapes into ExplorViz via a dialog.
Might be necessary to make changes in the backend as well.

The current instance-initializer is not sufficent for consistent setting the environment variables. When refreshing the page, the default settings are used. (configuration.json)

We need popups to show relevant information for the user, including communication, classes, and traces.

Showing detailed trace information as proved by ExplorViz Legacy, when clicking on a communication line.

Bootstrap in Ember

Implement a stable version of the new timeline, which also provides the ability to load a specific landscape (as described here)
Should be later improved via panning, zooming and performance-optimization.

Currently, we can only access the frontend from localhost and not from another remote client.

Console.log:

net::ERR_CONNECTION_REFUSED
localhost:8081/users?username=admin Failed to load resource:

UNCAUGHT
"Property set failed: object in path "session.session.messages" could not be found or was destroyed."

We need to fix this issue.

Idea: Provide a Dummy- /Offline Mode, thus no running backend is needed for development

What should we use for authentication?

By clicking on a navbar item, the respective route should trigger a reset action / function.
The action needs to be defined for each route, especially for extensions.

Idea: Implement a parent route BasicRoute, which provides an action reset can be implemented in every route via extend.

Specific routes should not be accessible for every user.
Related to the corresponding backend issue.

Frontend receives backend from backend now but needs more logic to show for example communications.

If you close a system, the ports aren't calculated correctly.

Rebuild plain login page.

Provicding more options in the configuration dialog for the user:

• Different options for normal users und admins
• Option, which landscape should be presented for the 10 sec. tiem frame: latest or dummy
• Change backend URL, if the deployment changes

Use three.js to rebuild the 2D landscape renderer.

Use Ember http-mock to mock the JSON API backend (in development mode and testing).

See: https://www.youtube.com/watch?v=ICQKlgIUymg

ember g http-mock landscape

Use an execution environment on ember startup to toggle backend and mocked backend usage, e.g., ember s --environment=mocked. For that, modify the application adapter's namespace.

Use session storage instead of local storage for token.

Rebuild tutorial mode

The latest ember-data version 2.14.10 results in a buggy application-rendering. Somehow only the foundation and the guard package of our Neo4j dummy app are rendered.

The foundation is not a component of our model (it is added / removed when needed for rendering). Therefore only one actual package (component) is rendered (the Guard package).

I think @thacau showed me this problem in his VR-approach first. This is the related issue in the ember-data-repo. For now we stay with a forced version 2.13.1.

Provide a visually impaired mode via the colorpicker extension

Rebuild experiment mode

Upgrade package.json dependencies to be in line with the frontend.

Idea: Updating the landscape model insted of creating a new one every time. Might be neccessary to provide consistent ids for the landscape to be able to properly update them.

Rebuild timeline with collapsable div

The new Live-Demo seems to be available at http://samoa.informatik.uni-kiel.de:8181/explorviz-frontend

However without knowing username and passwort, it's not possible to login.