-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unify effects skins around Deere #8424
Comments
Commented by: Pegasus-RPG Excellent idea, but isn't this too much work to be done for 2.1? |
Commented by: ywwg We can always push it back, but we might be able to at least make some headway. Not sure what our planned branch date is for 2.1 |
Commented by: daschuer The idea is good, but the implementation will be hard. Deere exposes the We have also a usability issue since it targets the minority of advanced I have tried to target that issue in Shade by reducing the gui elements to .. but it does not meet advanced requirements.
|
Commented by: ywwg deere and latenight have similar size requirements so we could at least unify those two |
Commented by: Be-ing IMO this should be a release blocker for 2.1. |
Commented by: Be-ing I think the best strategy to handle all use cases, from making use of all engine features to using effects on a netbook screen, is to design multiple modes that display different levels of detail. |
Commented by: Pegasus-RPG Like responsive CSS Web site design? Can we do that in Qt? |
Commented by: Be-ing I have no comment about the technical implementation of it because I don't know the skin system very well. I think the various modes should be easily toggled similar to other skin options, like 2/4 decks and hide/show samplers. |
Commented by: sblaisot maybe we can also think of an "advanced" pane for effect editing (something like the sandwich menu in deere) with the most advanced effects options we don't need/want on the interface directly and only keep most used controls on the main interface. most of the time, DJ setup their effects before the show and only adjust the strength of the effect and the channel they are applied to during the gig. |
Commented by: ywwg This bug is strictly limited to the near-term goal of taking the existing Deere effects UI and generalizing it so LateNight can use it. Please keep more general discussion about the UI in the mailing list. |
Commented by: esbrandt Adapting this to Latenight should not be too hard , since the Deere uses mostly templates. Begs the question why we maintain multiple skins at all, rather then allowing loading of CSS at runtime. Also see lp:1402236 |
Commented by: daschuer A css feature similar to colour schemas solves the visual beauty taste. So I like the idea to improve the situation here. On other aspects of a skin we should keep in mind is that it support one or more special use case like beginner, advanced, radio DJ scratching DJ vinyl control DJ and so on. |
Commented by: sblaisot shouldn't this one be kept open until Latenight is updated ? |
Commented by: daschuer and Shade .. |
Issue closed with status Fix Released. |
Reported by: ywwg
Date: 2016-01-06T15:06:27Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp1531519
Tags: effects, polish, skin, usability
It looks like Deere has the best interface for working with effects. Let's unify around that interface by factoring the effects bar into an xml template that can be used by all of the skins. The other skins should be able to apply CSS to make the panel blend in. Then we only have one place to change the effects interface rather than 3.
The text was updated successfully, but these errors were encountered: