I have no problem with adding "..." to the appropriate Task Control buttons. But remember that any change to translatable strings, no matter how small, invalidates that string in the localization tables for each language, so that string will no longer be translated until the volunteer translators update it. This means that we should only change strings when there won't be a public release for a while, to give the volunteers time to update their translation.
On Jun 17, 2015, at 3:51 PM, Jacob Klein <[email protected]> wrote: > I'll be honest. I don't feel comfortable splitting up our "boolean-able > buttons" into 2 buttons. The current setup feels good to me, for an Advanced > View. I agree with this. The column of buttons can already get quite long (tall) as it is. > What I'd much rather prefer are columns in the grid, ie: "Suspended", so I > can easily sort/find my Suspended Projects/Tasks. Although the Tasks tab is already too wide to fit on most monitors without using ellipses in some of the columns, the BOINC Manager now offers the ability to optionally show or hide each column, and some of the columns can now be set to be hidden by default. So the additional column(s) proposed by Jacob could be added as hidden by default, and shown only by users who need them. Also, on MS Windows systems only, the user can drag columns around to rearrange their order. Cheers, --Charlie On Jun 17, 2015, at 3:51 PM, Jacob Klein <[email protected]> wrote: > David, > > Here are my thoughts: > - Whatever logical changes you make here in the Task Commands groupbox, would > also need to be applied in the Projects Commands groupbox, and Transfers too. > - I have mixed feelings on splitting the commands group. I might leave it > grouped and labeled the way it is. > - The following is a proposal, an idea, but I encourage you to read my > comments afterward, since my opinion is mixed. > -----Tasks: > - "Show only active tasks" checkbox sounds good to me > - For "Show graphics", "..." sounds good. I also think this should be enabled > when any selected task can show graphics, instead of current functionality > that disables it when any can't. > - For Suspend/Resume, if you have some suspended and some running tasks > selected, then what? Current behavior is to disable the button. I propose we > split into 2 buttons. > - If we split, then Suspend and Resume should be enabled, when ANY selected > task is capable of the operation, even if some aren't. > - Abort should follow suit. If I select 9 aborted tasks and 1 unaborted task, > I should be able to click Abort. > - For "Properties", "..." sounds good. > -----Projects: > - Same logic applies for Suspend, Resume, No New Tasks, Reset Project... if > any one of my selected projects is capable of the operation, then enable the > button. > - I guess we'd have a button for "No New Tasks", and a separate button for > "Allow new tasks"? > -----Transfers: > - Same logic applies for Retry Now and Abort Transfer... if any one of my > selected files is capable of the operation, then enable the button. > > I personally have not had much of a problem with the button structure/layout > as it exists today, but it has for sure at times been uber tedious to cherry > pick certain "Unsuspended" tasks just to make "Suspend" become enabled, or to > cherry pick certain "No New Tasks" projects just to make "Allow New Tasks" > become enabled. > > I'll be honest. I don't feel comfortable splitting up our "boolean-able > buttons" into 2 buttons. The current setup feels good to me, for an Advanced > View. What I'd much rather prefer are columns in the grid, ie: "Suspended", > so I can easily sort/find my Suspended Projects/Tasks. Same for finding the > "No New Tasks" ones, and "Projects controlled by Account Manager". And > "Project Disk Usage", "Tasks completed", "Tasks failed", "Estimated > Computation Size", "Working Set Size", "Directory" ...... Those would be fun > to be able to easily view, and sort by, from an "advanced user's > perspective". :) And they'd help me to select the correctly tasks/projects, > to get the button to become enabled. > > My grids on my main rig: 37 projects, usually running 14 tasks all at the > same time, amidst a mix of ~200 queued tasks. > > Regards, > Jacob > > >> Date: Wed, 17 Jun 2015 15:17:13 -0700 >> From: [email protected] >> To: [email protected] >> CC: [email protected]; [email protected]; >> [email protected] >> Subject: [boinc_dev] suggested changes to Manager GUI >> >> Based on Steven's comments, I propose that we >> >> - replace the "Show active tasks" / "Show all tasks" botton with a checkbox >> "[x] Show only active tasks >> >> - Remove the word "Commands" >> >> - Put "..." after Show graphics and Properties to indicate that they open a >> new window. >> >> - Group Show graphics and Properties (which show info) >> separately from Suspend and Abort (which operate on the task). >> >> - Enable Suspend and Resume if a group of tasks is selected >> where some are suspended and some are not. >> >> Comments? >> >> -- David >> >> On 15-Jun-2015 3:41 PM, Steven Bailey wrote: >>> >>> *Tasks* tab >>> >>> · “Show active tasks” and “Show all tasks” have different contexts from the >>> other >>> buttons in the “Commands” groupbox. >>> >>> · “Show active tasks” and “Show all tasks” are different names for the same >>> binary >>> switch. Some of the buttons in the “Commands” groupbox are switches, and >>> some open >>> a new window, but they all look alike. >>> >>> ·“Commands” is programmer jargon. >>> >>> · “Suspend” and “Resume” are disabled if a group of tasks are selected >>> where at >>> least one task is suspended and at least one task is not suspended. >>> >>> *Tools/Computing preferences* dialog >>> >>> ·“0 means no restriction” means also, “100 means totally restricted”. The >>> only >>> restriction that is predictable is 50; 50.1 and 49.9 are ambiguous. >>> >>> ·“On multiprocessor systems …” could be a list of processors and an >>> election of >>> which ones to use, instead of a percentage where 1%, 2%, and 33% mean the >>> same >>> thing on a machine with 3 CPUs (I’m guessing; I don’t know, and I’m expert, >>> and >>> I’ve looked it up on the message boards). Fixing this also solves an >>> identified >>> task of allowing election of which CPUs are used. >>> >>> >> >> _______________________________________________ >> boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. > > _______________________________________________ > boinc_alpha mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
