pmeas / pmeas-frontend Goto Github PK
View Code? Open in Web Editor NEWpmeas-frontend is a frontend application to the pmeas-backend
License: GNU General Public License v3.0
pmeas-frontend is a frontend application to the pmeas-backend
License: GNU General Public License v3.0
'Enabled' area should scroll when 4 or more effects are added
The current README.md file is almost completely blank, aside from a title.
For effects that have 5 or more parameters the area should become scrollable
The settings page should have an update button when new options are set to inform the backend.
This can be properly debugged once the S3 outage issues with TravisCI and most of the web is fixed. You cannot see the build log because of the outage.
The current theme is what I like to call a hot dog theme, because it uses extremely bright colors that are random, similar to what you'd find on a hot dog.
The GUI needs to have a sleek theme.
The user should have the option to select from a drop down menu to choose how many signals to harmonize or frequency shift. This will dynamically change the number of parameters listed for the user to set. These specific parameters should be contained in a list for the back-end to use properly.
Add an effect or a text that shows the current effect. After you click on an effect there is no way to tell which tab you are on right now.
You can simply change the color of the sidebar for that particular effect.
This is the license that Qt is under.
Currently the TcpServer class is just a barebones class and does not perform and reading of messages. This needs to be accomplished by prototype 2
Window decorations display incorrectly and have no close button. There's no other way to close the settings popup, so the user is trapped there until they kill the application.
Dragging items in the 'Enabled' area should allow the user to rearrange the effects order
This corresponds to the ParametersColumnArea and the EffectsColumnArea. Drag and dropped effects and changed out parameter values should have really slick and smooth transition animations. QML has a types for this.
The parameters of the same effect being enabled multiple times should retain separate parameter values
Just investigating for now. Enabled effects list might need more space/special resize policy accomodations
That is, if there are 2 enabled Delays, we should be able to have one with a delay of 0.5 and another with a delay of 0.25, and they should be independently adjustable
When there are 2 or more effects in the 'Enabled' effect list and an effect is deleted that has one listed below it they overlap while the deletion animation plays.
There will be a slider that gives the user the option to change the global volume of the system. It should pass to the back-end the same as an effect does and in the same JSON file.
Add the different stages before loading the main effects page. I.E -> Open App -> Show Splash Screen -> Pick Connection Medium -> Pick Ports -> Load Main Page
In the enabled effects list the remove button, which looks something like "x", should only show when the user's mouse hovers over the button.
Settings button should so a visual interaction when clicked like a color change
The effects buttons need their z index higher than the every GUI widget when they are being dragged. We could just use the constant 100, so something like 'z: 100'.
Submit button should so a visual interaction when clicked like a color change
Adjust the sidebar to the text. e.g. Frequency Shift doesn't fit.
Section in the Effects list for Phaser when clicked show its parameters.
Flanger button allows for adjustment of parameters before sending to modulating application.
When the user opens the application, the GUI will connect to the backend device and query data from it. While this data is being queried, we should present the user with a splash screen / loading screen.
Just look over the code and refactor if needed and comment each and every class, along with every function call, describing what the return value means, if any, and what the function parameters are used for, and what sort of data manipulation is expected to happen.
I don't know and it is mostly up to the client and you guys, but the colors of the UI is not pleasing to the audience. e.g. I wouldn't use a white text on a red background with a blue border.
Introduce the users to the UI of the interface to what each section does.
I am not sure if it is intended or not and maybe ask your client this:
After switching the effect does he want the sliders to also reset to its original states?
Stretch goal!
The parameters in 'Enabled' area should retain values when selecting any other effects
To ensure users understand how the GUI functions there should be a 'help' icon that pops up a window with detailed instructions on how to connect ports, set effects and submit to the back end.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.