All good to me - test results on tracker

Rebased vs the latest master

What's happening with the merge of this one that was on the approved list of JUX features ? making it into beta 2 so that we can get larger feedbacks ?

It makes a lot of sense together with the recently merged search tools simplifications...

Speaking for myself, I slowed down on the feature tracker after the first beta release as bug reports started coming in about issues with some of our larger patches we merged just before beta, many of them being either JUX or JForm related. Throughout the week, we've obviously gotten things taken care of with that and only over the last couple of days started working on the outstanding feature patches to merge.

Thanks Michael!

I've seen phenomenal progress in the last weeks, Thanks all committers and PR submitters!

I was just trying to make sure we get a consistent overhaul of the admin simplifications that got designed at the JUX codesprint and that got approved, and this is part of them.

So actually, appart of a few smaller parts that got forgotten in the split-up into smaller PRs, this one is the only JUX FR PR which is still open. Not a big one code-wise, but a nice simplification UX-wise.

Rest of forgotten minor items are small details that we can fix as small PRs with issue trackers.

Keep up the great work

The tracker is the place to discuss implementing this or not, and there is a proposal for a "disabled" toolbar which looks very clever and much more user friendly. See Tracker.

@infograf768 Let's just say that it is an alternate proposed screenshot. It might sound clever, but when the jux team tried that other implementation before deciding and committing, even though it looked good, it didn't feel right nor user-friendly to both expert and novice users.

For UX, a screen-shot is only half of the story, real use (preferably by non-developers) is the real test.

Suggestion: We try this PR in beta 2, see real users feedbacks (not that we in here are not real users, but i guess we are all a bit biaised), then depending on feedbacks, we can fix/improve for beta 3 or RC whatever comes after beta 2. It's a very simple change and ieasy to revert or change too.

Reading the above and having thought quite a bit of all feedbacks, I have following proposal:

• Inactive Buttons appear dimmed when the toolbar is hovered with the mouse
• When mouse is not over those buttons, they are hidden.

Thoughts ?

That would be best of both worlds and very easy to imlpement with jQuery.

Status-Quo remains imho worst solution of all 4.

How do you hover over an invisible button

when the toolbar is hovered with the mouse.

So when mouse is in that toolbars area, all invisible buttons become visible and dimmed (with a nice appearing effect)

When you are in the toolbar zone, the inactive buttons become visible but dimmed. That way you can still click on them and see the message to select items.

It solves the "discovery of features and UI" issue raised, and still shows a clean interface concentrating on content when the toolbar area is not hovered.

Thoughts?

Should we start to look into this again? I think the idea is quite good

PLEASE

On 29 August 2014 21:48, Peter Lose notifications@github.com wrote:

Should we start to look into this again? I think the idea is quite good

—
Reply to this email directly or view it on GitHub
#2111 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

@brianteeman just went through the entire debate on the tracker, there are some valid points. But I still believe that it's best to hide the buttons.

This PR in combination with #4197 really improves the clarity of the views:

You wont find anything but approval from me

On 29 August 2014 22:08, Peter Lose notifications@github.com wrote:

@brianteeman https://github.com/brianteeman just went through the
entire debate on the tracker, there are some valid points. But I still
believe that it's best to hide the buttons.

This PR in combination with #4197
#4197 really improves the
clarity of the views:

[image: skaermbillede 2014-08-29 kl 23 04 40]
https://cloud.githubusercontent.com/assets/1738811/4096329/2ad1bd70-2fc0-11e4-8ffb-7000b7a76228.png

—
Reply to this email directly or view it on GitHub
#2111 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

Perhaps @phproberto could stage against the current staging branch or 3.4.-dev? Then we could have a renewed discussion

@phproberto Can we have this in 3.5?

@phproberto On a list with just one checkmarked item the edit-button doesn't appear, is this behavior intended? If the list has more than one item, and one is checked, the button appears correctly.

@dgt41 I'll update it to try to get it into v3.5 :)

@peterpeter testing it now doesn't make sense. Closing it for now