Re: [Ayatana] Rendering Status of Elements when Lens is Active

[Ingo Gerth <ingo@xxxxxxxxxxx>]

I am totally with you on this one. It looks like the original design was intended to be a bit different, check out this beautiful mockup:
https://launchpadlibrarian.net/68218500/unity_dash_01.png (Taken from https://bugs.launchpad.net/ayatana-design/+bug/750374 )

There is a very clear division between launcher, dash, and panel (actually becoming part of the dash), which we do not have right now.

I am not sure what happened to that concept, but it might just be that there was not enough time this cycle to implement the design exactly like that.

Otherwise it would be great to hear from one of the Unity devs what the reasons are why the current dash does not look like the one in that screenshot.

--Ingo

On Mon, Apr 11, 2011 at 3:22 AM, Allan Caeg <allancaeg@xxxxxxxxx> wrote:

There's an inconsistency in rendering status of elements while a Lens is active. As seen here http://img6.imagebanana.com/img/zty9kgns/Workspace1_003.png , the Unity Launcher is grayed out, while the top panel isn't. 

With this identified, how should the top panel be treated? Visually, it needs a differentiation from the normal clickable state.  

On the other hand, we can also consider changing the panel's behavior instead of the visual treatment, like how it's done on GNOME Shell while on Overview http://img6.imagebanana.com/img/8yunbmeb/Workspace2_008.png . Let's keep in mind that Lens and Overview may not be apples to apples in this case, though. Does it really make sense to make the panel inactive while a Lens is active? It may, but this will also depend on future plans for Unity.

--
Regards,
Allan
http://www.google.com/profiles/AllanCaeg#about

+63 918 948 2520

_______________________________________________
Mailing list: https://launchpad.net/~ayatana
Post to     : ayatana@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~ayatana
More help   : https://help.launchpad.net/ListHelp