Hey Pascal,
First off, thanks a lot for joining this discussion. It's really
beneficial to get as many people as possible in on this discussion so
that we can really understand all the perspectives and use cases
involved. Whatever we decide on for a new skinning system will hopefully
last Mixxx for a long time -- so we need to talk about it a lot to make
sure we cover all the bases.
I read your post to the Mixxx forums and this email and I have one
question. If you group all the widgets into a grouping that is
identified as a Mixer or a Player, then what happens when someone comes
along and wants to make a skin where the EQ section of the mixer is
separate from the crossfader section?
In all the current Mixxx skins, none of them have a clear boundary
between the widgets that you could draw a box around and say 'Here is
the Mixer'. The parallel waveform display concept, for example, is
something that we believe is a major aid to DJ'ing. The waveform
displays are front and center in the outline skins, while the rest of
the player widgets are on the left or right. In terms of commercially
available software, Virtual DJ and Torq agree with us in this respect,
while Traktor does not. In my opinion, a skinning system shouldn't
constrain the organization of widgets on the screen -- rather it should
facilitate it.
I'm for a more general approach that doesn't involve grouping widgets at
all along functional boundaries. Why not allow the skin to specify
groupings which have layouts, but are not necessarily tied to the
grouping's functional purpose? That seems a lot more flexible to me.
Cheers,
RJ
pascal.hue...@bluewin.ch wrote:
> Hello,
>
> i need some feedback on that topic. I thought a lot and reviewed the code.
> And I was thinking about how to make a
> "soft" transition to a new interface.
>
> To change the skinning engine, i think there has to be some modifications to
> the interface itself. Now all
> the widgets are placed by absolute coordinates and like that its not possible
> to get a fluid layout. So I'd like to
> keep the current xml files, but change the positioning in the wwidget.cpp:
>
>
>
> void WWidget::setup(QDomNode node)
>
> {
>
> // Set position
>
> QString pos = selectNodeQString(node, "Pos");
>
> int x = pos.left(pos.indexOf(",")).toInt();
>
> int y = pos.mid(pos.indexOf(",")+1).toInt();
>
> //move(x,y); <- remove that to realize a fluid layout
>
>
>
> // Get tooltip
>
> m_Tooltip = selectNodeQString(node, "Tooltip");
>
>
>
> .....
>
>
>
> Then I think I will write a container class (a QWidget with layout
> abilities), which holds some widgets and allows to
> arrange them by drag and drop. But then I will have to store the positioning
> somewhere. WHERE???
>
>
>
> The container class will align on the mainwindow.
>
>
>
> Second thing: Somehow i have to know, which controls i have to put together
> into a container class. This means: I'll
> have to put all the Mixer controls into one container class and all the
> Player controls into one and so forth... Any
> ideas how i can find out which control elements belong together?
>
>
>
> I'll try to catch some of you on irc later....
>
>
>
>
>
> Thanks!
>
> Pascal
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for Conference
> attendees to learn about information security's most important issues through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
