Could someone please explain why the Windows version deviates from the rest of the world in that the Tree View is the default? All the instructions show the Linux way, and all the prior stuff I worked with in getting to Windows was Radio as well. What was the precipitant for the tree view becoming the DEFAULT?
This is a “shoot ourselves in the foot” issue - a needless reason to confuse potential users. There is NOTHING about Windows which makes the tree view better. If a single customer desired it, then have that customer fix THEIR copy, not subject everybody else to having to explain why it doesn’t look like the instructions!
If there is not some COMPELLING reason why ALL users should have tree view as default when they first get it for Windows, what must be done to change that globals.php code to the same default as the rest of the user base? We should not wait until some next "fix", since this is a "bug" in my mind, (to say nothing of the other end!)
To add to the confusion, i have noticed that in 3.0.1, in left_nav.php, the
genTreeLink(‘RBot’,‘cod’,‘Charges’);
that creates the ‘Changes’ link has an if (false) around it, causing you to be unable to select that page, so the two interfaces have (in a minor way) drifted.
please can you free a little bit of time to solve this problem? What you did with Language choice, could you solve this "Menu view" as well.
Make a choice of menu view at the login screen that defaults to the last menu choice?
You told me about all other kind of obligation, but this is the same kind of problem. Now we have to change global.php line, but with the new option as seen in CVS Demo login screen for Language it can be just a "hit the button " choice…
Or give the Developers the keys toward change of this global.php issue, while at the loging screen.
I am all too aware THAT it is changed. What I have yet to grasp is WHY?! We have a huge group of users for whom the radio buttons are familiar. We have a developer who has done a masterful job of making a good instruction manual which shows the radio buttons. So this must obviously be a great reason to fix something which ain’t broke?! When did we start thinking like Microsoft?
Certainly these two distributions of the same release should have the same default configuration, to the degree that is reasonable. But let’s focus on future releases and how to make them better - it’s too late to change this one.
After a fresh installation with the tree view as the standard, I propose making the menu/radio/tree a per-user option. When a user is created they would get the system-wide default but could then choose something different later. This also ties back to the creation of a table or addition of fields to store a users preferences such as date-format and calendar-style.
YOU and ME may have no problem with believing the Tree View is intuitive, but I already have examples of people who are tossing in the towel because what they have for instructions does not agree with what they see on the demo screen! And thinking that they will figure it out is self-delusional.
I have no issue with the next release being another view than the CURRENT default (I have only just been informed that Dr Bowen changed the Windows Xampp-OpenEMR 3.0.1 package BACK to Radio Buttons to match the Linux distribution, thankfully) PROVIDED that our demo, and our published instructions, MATCH that default in EVERY version we distribute. Otherwise we look like amateurs, we lose potential users, and we MOST CERTAINLY cannot meet CCHIT regs.
It is obvious that you intend for the Tree View to become the "standard". But until we STOP making unilateral changes to what newbies see as initial presentations, we will continue to lose users. Until we make the effort to view things from the perspective of someone who has NO IDEA how to change a UOR field from required to optional so they can enter their data in a way which is intuitive for THEM, rather than because we think it is better, we will continue to make it harder than it has to be for NEW users. And like it or not, THEY are the key to having EXPERIENCED users.
Not that we should neglect current clients - but THEY have enough experience to know that stuff CAN be modified, and often HOW. NO NEWBIE is so informed. Can we PLEASE make it a policy that we consider the next incremental new user as our MOST important objective? It is like Ben Franklin said; "watch the pennies, and the dollars will take care of themselves". We cannot have dollars until the pennies get to grow. PLEASE!