One more thing regarding the UI I'd like to ask is to avoid using pure white.<br>A slightly darker shade, like 245, 245, 245 or 240, 240, 240 is easier on the eyes and still provides good contrast.<br><br>Thanks for listening!<br>
Gabriel<br><br><br><div class="gmail_quote">2011/3/6 Gabriel Gazzán <span dir="ltr"><<a href="mailto:gabcorreo@gmail.com">gabcorreo@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I think we should make sure than users with, say, 1024 x 768 could be able to use kdenlive without big shortcommings.<br>Then, of course, the more room the user has the better.<br>But when designing the default layout I think we should put in there just the basic elements needed for comfortable and simple video editing, and leave the more sofisticated scopes and control panels for alternative layouts aimed at more specific tasks, such as color correction, audio editing and the like.<br>
<br>Fom my experience I tend to work using the default layout in a big part of my editing sessions. I suppose that could be indicative of a well designed default layout in PremierePro.<br>Another thing that I like having at hand is the possibility of saving my own layouts, for very specific tasks.<br>
<br>And last, the possibility of "reseting" a changed layout back to its original form (but I suppose that's useful because of the way Premiere layouts work: when you're using a specific layout and change something in it, this changes are automatically incorporated into this layout, and from this point on, everytime you activate this layout the changes are still there. If you latter change your mind and want the original layout back, you reset the layout to its original form with a Reset Layout option).<br>
<br>Speaking of useful layouts, I think one where the Project Tree, Clip and Timeline Monitors are put side by side is very useful during heavy clip selecting and trimming sessions. This one would allow for quickly moving original clips from the Project Tree to the Clip Monitor for trimming and then, after overlaying or inserting them in the Timeline, the Timeline Monitor would allow to instantly see how's the editing going so far.<br>
<br>Greetings,<br>Gabriel<br><br><br><br><div class="gmail_quote">2011/3/6 Simon Eugster <span dir="ltr"><<a href="http://simon.eu" target="_blank">simon.eu</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>></span><div>
<div></div><div class="h5"><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Combined them with the Colour widgets dock now.<br>
<br>
Somebody (I forgot who and where, sorry) suggested to ship some<br>
default layouts. I think this is a good idea, then we could hide all<br>
my scopes (Audio and Colour) in the standard layout — not only because<br>
of the waste in space, but also for better performance (no expensive<br>
calculations for all colour scopes). Is this possible @jb? Perhaps<br>
something similar to the ones I proposed here?<br>
<a href="http://kdenlive.org/users/granjow/widget-layouts-kdenlive" target="_blank">http://kdenlive.org/users/granjow/widget-layouts-kdenlive</a><br>
<br>
@Gabriel Based on your experience, could you maybe give some hints how<br>
to improve them?<br>
<br>
Simon<br>
<br>
PS: Uh. When loading kdenlive now with the default<br>
.kde/share/config/kdenliverc, it does not fit on my 1680x1050 screen<br>
:D<br>
<br>
2011/3/5 Dan Dennedy <<a href="mailto:dan@dennedy.org" target="_blank">dan@dennedy.org</a>>:<br>
<div><div></div><div>> Currently, the default layout has AudioSpectrum and Spectrogram in<br>
> separately docked panels. IMO, that makes the layout too wide for a<br>
> suitable default. Audio Signal is also, but that is more commonplace<br>
> and probably justifiable. Also, with all of the scopes enabled by<br>
> default and placed onto the panel together with Effect List and Undo<br>
> History, it can be argued it forces that panel to be too wide.<br>
><br>
> --<br>
> +-DRD-+<br>
><br>
> ------------------------------------------------------------------------------<br>
> What You Don't Know About Data Connectivity CAN Hurt You<br>
> This paper provides an overview of data connectivity, details<br>
> its effect on application quality, and explores various alternative<br>
> solutions. <a href="http://p.sf.net/sfu/progress-d2d" target="_blank">http://p.sf.net/sfu/progress-d2d</a><br>
> _______________________________________________<br>
> Kdenlive-devel mailing list<br>
> <a href="mailto:Kdenlive-devel@lists.sourceforge.net" target="_blank">Kdenlive-devel@lists.sourceforge.net</a><br>
> <a href="https://lists.sourceforge.net/lists/listinfo/kdenlive-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/kdenlive-devel</a><br>
><br>
<br>
------------------------------------------------------------------------------<br>
What You Don't Know About Data Connectivity CAN Hurt You<br>
This paper provides an overview of data connectivity, details<br>
its effect on application quality, and explores various alternative<br>
solutions. <a href="http://p.sf.net/sfu/progress-d2d" target="_blank">http://p.sf.net/sfu/progress-d2d</a><br>
_______________________________________________<br>
Kdenlive-devel mailing list<br>
<a href="mailto:Kdenlive-devel@lists.sourceforge.net" target="_blank">Kdenlive-devel@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/kdenlive-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/kdenlive-devel</a><br>
</div></div></blockquote></div></div></div><br>
</blockquote></div><br>