If we nuked the little map, we could fit about six buttons in landscape mode. We're still stuck with about 4 buttons in portrait mode, unless we get creative. Perhaps 45 degree angle slanting text buttons?
At 06:44 PM 2/15/2011, Tobias Bieniek wrote: >I would suggest, removing the map from beneath the tabs and instead >have the following tabs: > >- Task Edit >- Task Calc >- Task Map >- Task Browse >- Task Declare (with Status information of some kind the we might >have later..) >- Close > >By using the right symbols we could save some space by narrowing the >tabs to make some more room for the content. Simon Taylor already >created a few symbols for this purpose... > >Turbo > > > >Am 16.02.2011 00:27, schrieb Helmut Rohs: >>Hi Rob, >> >>the mockup is really awesome, no better way to present and collect >>feedback! >>Some thoughts of mine, maybe not ordered: >>- The tabbed dialog is smart and gives direct access with only one >>click, good. >>- The tabs grab space on the dialog you may want to have for different >>purpose. >>- For more or less all tab pages it lacks some button space. >>- An alternative could be a process, or assistant like dialog base. The >>drawback are some more clicks if you want to access the last page in the >>chain. >>- I identify three main activities for "Tasks": Task browser, task >>editor, task calculator. If chained I would suggest exactly this >>sequence. >>- For the tabbed approach I would expect those three titles as tab >>pages. >>- "Close" is by default associated with a button function. >>- Ground interaction with XCSoar do not need to save clicks. We may >>differ: Home-, Ground-, and Flight interaction. Whereas I see the home >>interaction is: Planning tasks on the desktop and SD swap them onto the >>preferred gadged afterwards. >>- I like the in-flight preference to the task calculator, required is >>that all features are still reachable. Thats a plus for tabs, and a >>minus for chained pages. >>- Most important: I want to be able to delete the active task. That make >>sense from a user perspective, even if it is a different thing for the >>objective oriented designer and programmer. >>- Buttons should be always visible, even if their function is currently >>not available and they are shown inactive. >>- Instead of "Clear Task" I expected a remove waypoint button in the >>editor. >>- Buttons should stay at the display boarder, if possible (Altair). >> >>Having those things in mind for a while, sorting and prioritizing, I get >>to this: >>http://rohs.volatus.de/xcsoar/TaskDialog/TaskBrowser.jpg >>-> Not sure if the "(New task)" is necessary, could short cut to an >>empty editor. >>-> Double click leads you directly to the editor tab. Same as a task >>select and then switch to the edit tab. >> >>http://rohs.volatus.de/xcsoar/TaskDialog/TaskEditor.jpg >>-> To change one waypoint double click it on the list. >>-> The Properties button swaps the entire editor tab content. >>-> Remove acts only on the selected waypoint. >> >>http://rohs.volatus.de/xcsoar/TaskDialog/TaskProperties.jpg >>-> close to swap back to the waypoint list. >> >>http://rohs.volatus.de/xcsoar/TaskDialog/TaskCalc.jpg >>-> seems straight forward. The tabbed dialog offers to set this as a >>on-flight preselection when opening the dialog. >> >>Thank you, Rob, for kicking this off. >> >>Cheers, >> >>Helmut >> >> >> >>Am Dienstag, den 15.02.2011, 02:21 -0500 schrieb Rob Dunning: >>>Please comment on the proposed 6.1 Task menu structure in the mockups >>>linked below: >>> >>>www.tinyurl.com/xcsoardevrld/TaskManager/TaskMenuMock1/index.html >>> >>>The mock runs in two modes "flying" mode and "on the ground" >>>mode. The idea is that while you are flying, you want the Task menu >>>to go directly to the task calculator. While you' are on the ground, >>>you probably want the Task menu to change or edit your task. >>> >>>Please send comments and suggestions. >>> >>>Thanks, >>> >>>Rob >>> >>> >>>------------------------------------------------------------------------------ >>>The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>>Pinpoint memory and threading errors before they happen. >>>Find and fix more than 250 security defects in the development cycle. >>>Locate bottlenecks in serial and parallel code that limit performance. >>>http://p.sf.net/sfu/intel-dev2devfeb >>>_______________________________________________ >>>Xcsoar-user mailing list >>>[email protected] >>>https://lists.sourceforge.net/lists/listinfo/xcsoar-user >> >> >>------------------------------------------------------------------------------ >>The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>Pinpoint memory and threading errors before they happen. >>Find and fix more than 250 security defects in the development cycle. >>Locate bottlenecks in serial and parallel code that limit performance. >>http://p.sf.net/sfu/intel-dev2devfeb >>_______________________________________________ >>Xcsoar-user mailing list >>[email protected] >>https://lists.sourceforge.net/lists/listinfo/xcsoar-user ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Xcsoar-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcsoar-user
