asls-org / studio Goto Github PK

Togglelable lists empty states do not fit UI. A rework would be appreciated.

hello
I am unable to move objects/fixtures to desired location. I dont see any functions to move the components to the place i want.

Draggable list item UI/UX could be improved. Maybe add a drag handle to draggable list items to let the user know that these specific items are draggable ? Also drop container could be improved. WHile it does work great, it doesn't feel right UI-wise.

Fixtures implementing RGBW are supported but only RGB channels are currently being used by the software's color picker and visualizer.

Create the following automation workflows to ensure CI/CD:

• Release workflow
• Deployment workflow(s)

Deleting all groups in project crashes everything. A check should be made in order to either prevent the user from doing this or regenerate an empty group if all have been destroyed.

Lint the whole project according to ASLS's linter rules.

Reactivity/watch issues with list component. The list component behaves weirdly. it seems like changes to many irrelevant and out of the component's scope show variables are able to trigger re-parsing of the list items. I knew setting up watchers there would eventually fire back. Now is the day to find fixes!

Either delete the cuepool searchbox or implement a way to filter grid items effectively.

Chases can inclue cue items that go out of the chase's user-set duration boundaries. This happens when creating a 2 bar chase and resizing it to 1 bar for example.
The chase cue items or pieces of cue items that go outqide of tha set boundaries shouldn't be cropped out of tje timeline but they should be grayed out instead.

Use object.freeze to make fixture configurations (and every other objects that should be immutable) immutable. This should prevent may problems from happening during fixture creation process, mode selection and universe patching. This is a much better way to accomplish immutability rather than deeply copying the objects before processing to any modifications.

Some elements seem to be overlapping on the timeline when it is scrolled horizontaly. This could be patched but a full refactor of the component's UI might be for the better.

Migrate ui-kit & vue fragments from vue2 to vue3

Local WebRTC communication seems to be causing issues.

Group fixture popup is not deinitialised on close/reopen. This causes the list content to be corrupted and unusable.

Popup horizontal dragging is independent of mouse position on popup header.

Chase playback doesn't behave correctly in loop mode. This might be due to experimental code left in the update routine somewhere (my bad).
The chase module could go with a refactor too.

Numeral inputs with bounds are a pain to work with. It would make more sense to forward input validation on click outside and clamp the provided value afterwards.

Add an ability to spread pan/tilt positions over groups. Either by creating a new group widget or by extending the pan/tilt widget's capabilities. This would be incredibly useful in order to generate position presets.

Visualizer's default background, floor and scene eel a bit bland. Some changes could be made to better fit the visualizer into the UI. Some kind of volumetric fog effect ? A blender-like infinite grid that expands to the horizon ? Feel free to leave comments over here if you have an ideas.

Errcode system implemented in models is inconsistent and meaningless. A real error code system would be a gamechanger for error handling.

Implement spotlight gobos using THREE's new SpotLight Map feature!

Patch bay ressources cannot be deleted. The user has to delete the fixtures within the universe modifier. Implementing resources deletion within patchbay shouldn't be too hard to make.

Colorpicker widget started as an experimental feature. It was patched over and over following growing feature list and could be massively improved.

Expected behavior:

The playing chase keeps on playing until the next quantization step is reached.

Observed behavior:

Quantized chase hangs for a little while (time for next quantization step to be reached) when switched within a same fixture group.

Steps to reproduce:

• define two or more chases within a single fixture group
• manually play them one after another

Implement a setCapture-like polyfill in order to prevent unintentional clicks to be troggered when releasing mouse button on a drag operation.

Switching fixture mode over universe modifier breaks everything.

See #10.

Show model isn't well documented yet.

Group selection (UI/UX) could be greatly improved. It is hard for users to understand how to select groups. Also, once a group is selected the selection styling applied does not truly convey the information that the group is currently beeing selected.

Some elements (eg. Patch button) are just placeholders. These should either be removed or implemented for beta release.

Since complex fixtures are not yet available for visualization, only moving-head fixtures are patchable. Such complex fixtures should be made patchable and setup with a placeholder 3D model signifying the user that the visualization process for that kind of equipment is still under development. Please refer to https://open-fixture-library.org/categories for a list of fixture categories that are/should be implemented.

Default cue duration is still absolutely set to 1000(ms). It should be updated to be defaulted to 1(bar) following the cue time management system update (see 71a86bf).

Timeline cue items container scroll position not reset on change. This means that when displaying a chase with less cues than the previous one might display a blank space where the previous cue items used to be.