Paging and vmblast default option placement

(In [11513]) fixes #4843 adds default directory checkbox back in

(In [11514]) fix more issues that went wrong from merge back re #4843

(In [11517]) more fixes re #4843, from the looks of it, this never worked in bs branch... seems ok now

p_lindheimer, the default directory option was moved to somewhere more intuitive, intentionally. What is possibly broken is SAVING the default dir.

(In [11520]) closes #4843 - fix saving the default dir

(In [11521]) re #4843 - no need to revert modules.xml

Reopening:

• intuitive includes:
  • consistency with other modules that do similar
  • consistency with previous operations (sometimes)
  • showing it clearly when inside a directory that it is the default
  • less key strokes and submits to go through to set something up

So, as far as it being more intuitive how you changed it vs. how it was, I would tend to say that both have their merits and drawbacks. However, my current opinion is that consistency with the Paging Default group and the Vmblast Default group are probably more important since the act of dealing with default groups often includes all of the above for an admin. If we are to make changes, I believe they should be consistent.

Also, in the changes you just made you reverted #4711

Sorry about the accidental part of the revert. I agree that we should have constant across the gui - feel free to make the necessary changes to Paging and Vmblast. Closing as #4711 has been reopened

Actually I don't think it is clear which is better. The changes you made require more steps to setup as well as less obvious to someone that the feature exists. Here are some typical steps when setting up a new system:

1. Go do some stuff.
2. Eventually go create a new Directory for the system
3. Now move on to do more stuff

In that typical scenario, one never even notices the option of a Default Directory because it is not presented any where during the natural flow. If you do noticed, now you have to go through the extra step of selecting the default directory after you have created it.

In the current interface, one immediately sees there is an option for a default directory during the initial setup, and it is also what they are used to from setting up existing systems wrt to paging and vmblast groups.

My inclination is to keep it the way it is, and in any event, I will not be going back during 2.9 release to make changes to paging and vmblast. Reopened until resolved and should not be closed until agreed upon, thanks.

Philippe, default: a selection automatically used ... in the absence of a choice made by the user

I've always been bothered by the wording for an option to be called default when there aren't any other obvious choices to select from. Based on feedback I've received, I've moved the Default Directory selector to a place where there is a choice of options.

While in the current setup "one immediately sees there is an option for a default directory" it is unintuitive as there are no other choices that would require THIS choice to be the default. The setting also tends to get lost between the other call flow-related settings and is difficult to find.

With the changes in place, the default option is visible regardless of which Directory screen your on. Being that you can see this option 'globally' its only natural that you should be able to change this option from a 'global' spot (the Directory landing page is 'global' in as much as its neutral vis a vis a specific directory). You should have to dig in to a specfic Directory to make the change.

Like I said, more intuitive! :)

Moshe,

please keep this on task and don't start changing categories. This is a matter of opinions and not facts as well as consistency between other modules. If you felt so strongly when the change was made, it would be upon you to go make the changes to the other modules. For now I will keep this open until resolved and seek input from others to decide which way to leave this in 2.9. I respect your opinion and see merits in both and thus will seek feedback from others. (And wrt to your implementation, you should be making it clear when in the default entry that it is the current default with some sort of additional label/notation indicating such).

I think having the default directory option on the main directory page is where it belongs since it is a global setting and that is where all global settings should be. For once I am in 100% agreement with Moshe and I am the one who asked him to do it that way when we built that module.

I've gotten mixed feedback from a few parties in favor of both and with some concerns of both. Since both Moshe and Tony are very strong on wanting it the new way, we can go ahead and leave it that way but I'll open feature requests for 2.10 to bring vmblast and paging in line since I think consistency is still pretty important. I'll also add some notations in the current form when on a specific directory page indicating if it is the Default directory.

(In [11550]) closes #4711 and closes #4843 and adds some notation within a directory page if current directory

Moving forward, I think the bold menu option stand out on its own.

Which bold option?

The one that show which directory is the default.