|
2010-08-04 10:34
|
A3-editor-mockup.png (41,509 bytes) |
|
|
Thanks oo! |
|
|
An important point to note of this design adjustment is that the introduction of the Nudge Up/Down arrows to the primary clock should be deducting a small amount of horizontal space from the primary clock's width rather than adding that many pixels to the width of that horizontal segment of the main menu strips (the one containing primary and secondary clocks etc.)- every horizontal pixel counts! |
|
|
I also neglected to mention that the snap mode menu (and hence the editor) doesn't quite fit on a 1280 wide screen when the editor mixer is enabled. However, I always have the editor mixer enabled and I would imagine most people using Ardour with just a single display (ie nearly all laptop users) will work the same way and seeing as we could have everything (inc. Editor mixer strip) fitting into the width of a 1280 display with only this one adjustment with no functionality lost it would seem strange not to. Of course, it would be even better if Ardour would fit onto a 1024 wide display but thats not going to happen without a significant shake up of the GUI so 1280 seems to be a do-able minimum required horizontal res for a full-featured editor display. |
|
|
I installed A3 on my netbook today- took just over 2hrs to compile. I thought I was wasting my time but instead I feel the need to take back what I said about A3 potentially running on a 1024 pixel wide display as, once this tweak has been implemented you would be able to see nearly the entire width of the A3 gui sans editor mixer @ 1024x ... Another idea for freeing up horizontal space would be to rename a few of the items in the Snap/Grid Units drop-down: the Timecode options could be renamed to TC ... and the Region options renamed to RG ... ? The Snap/Grid drop-down being one of the widest widgets we have. Yeah but who wants to run A3 on a netbook? I do and I could see many others wanting to do the same. Of course, the lack of Firewire, CPU/RAM etc and the limited display does mean you can't do any serious audio recording or mixing but you can realistically put a song together entirely with MIDI tracks- only needing to escape the confines of the netbook when serious audio stuff comes into play. To summarise I think it would be great if a few little tweaks were made to the GUI so that A3 could fit into 1024 pixels without editor mixer and 1280 with- it would certainly maximise its reach. |
|
|
Personally I'm not sure about this change; the resulting clock (with the nudge clock integrated) seems a little counter-intuitive to me. There is already support for a "small screen" profile, which removes some stuff from the toolbars (e.g. the secondary clock). This currently happens if the screen width is less than 1200 pixels; perhaps this should be modified? Alternatively it could be made possible to explicitly choose "small screen mode". More generally, perhaps we need system whereby we one can configure the elements of the toolbars which should be visible. Any thoughts, anyone? |
|
|
I fail to see how this integration in counter-intuitive. The nudge clock controls the primary clock and, so long as they user has entered a non-zero value into the nudge clock they would see how it affects the primary clock as soon as they click one of the up/down arrows- same as it does now. Doesn't really require documentation. "Small Screen" mode (which I didn't realise existed until you mentioned it) obviously isn't quite effective enough in getting rid of stuff to free up horizontal space as it stands- there seems to be quite a lot of unnecessary 'whitespace' in the menu such as the gaps to the right of the snap-off arrows to detach the toolbars which could free up a little more room along with the tweaks I've already suggested. Being able to configure which elements are visible would likely solve all such screen issues but is that overkill? Thats my 2p on Ardour real-estate issues so lets here what others have to say now. |
|
|
I run Ardour 2 and 3 on a 1280x800 screen and I have no issues with the screen not fitting here. I cannot really understand if this is really an Ardour issue or something related to your WM or distribution. |
|
|
If the fonts are scaled down in size, with the control in the preferences, do things not start to fit ? |
|
|
Hi lincoln! I just compiled the latest svn then deleted ~/.config/ardour3 on my 1280 wide Debian laptop to check this and I dunno what has changed or was wrong before but now I can see the full width of the menus @ 1280 so long as I don't enable the editor mixer which pushes the clock and MIDI panic button off the side of the screen still. If the nudge clock got integrated this wouldn't happen. This is no showstopper really as I never had to use the MIDI panic button and I've got clocks elsewhere I can reference instead- I'm just thinking about presentation and how it may make people perceive Ardour as well as ensuring A3 can be used on the widest selection of displays. I'm using fluxbox btw and Debian seems to default to a different default GTK theme than Ubuntu uses and I suspect this makes a (small) difference to the size of the elements. |
|
|
Oofus: If I have editor mixer enabled and fonts set to about 70 I can fit it all on @ 1280 but the text is a bit small for my liking at that size. Good temp solution at least. |
|
|
the nudge clock doesn't ONLY control the primary clock (playhead position). if you have objects selected (e.g. regions) and you nudge, it is them that move, not the playhead (and thus not the primary clock). nice idea superficially, but the wrong change to make. also, we have spare pixels in the toolbar row, so ... |
|
|
Hi Paul! Just got back off holiday hence the delay. I had no idea you could move selected regions with the nudge clock until you mentioned it now but even so, my adjustmemt still makes perfect space-saving sense to me. However, if you and Carl think its impractical, at least for 3.0, then feel free to clear this one down. |
|
|
this is not going to be a solution to any general "too wide" issue, so i am therefore marking it resolved. there is another issue open for the "too wide" case (possibly more than one). |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
- Anonymous
