Closed GoogleCodeExporter closed 9 years ago
My chief concern with this is it would be jarring if you had extensions and the
clock was left-aligned, and then no extensions were visible so the clock jumped
to the center.
Currently my UX decision was to center the clock only if no extensions are
added at all. I'll explore further if other folks feel the same way.
Thanks!
Original comment by roman.nurik
on 12 Feb 2013 at 12:05
Agreed, consistency is important. It just looks a little off.
Original comment by ldjugg...@gmail.com
on 12 Feb 2013 at 12:08
Yeah, tradeoffs and all that :-( I'll see if something clever comes to mind.
Original comment by roman.nurik
on 12 Feb 2013 at 12:09
Isn't there space to have to option to have a centred clock and have the
extensions to the side?
Original comment by james.94...@gmail.com
on 12 Feb 2013 at 6:40
Seems like there's plenty of empty space off to the right of the widget...maybe
some slight adjustments are possible...?
Original comment by uansa...@gmail.com
on 13 Feb 2013 at 11:01
Take a look at the screenshot in Issue 9.
Original comment by ldjugg...@gmail.com
on 13 Feb 2013 at 11:32
Issue 70 has been merged into this issue.
Original comment by roman.nurik
on 13 Feb 2013 at 9:15
Would really love for it to be centered than left-aligned on the screen,
Original comment by kumud.ne...@gmail.com
on 14 Feb 2013 at 2:38
In fact, another suggestion came to mind about the positioning on the screen.
Rather than fully center it, I think the widget would look sexy if it were
aligned with the left column of the pattern lock dots. I think this would allow
space for extensions to still appear on the right of the clock. Not sure if
this is even possible
Original comment by kumud.ne...@gmail.com
on 14 Feb 2013 at 2:43
I have no knowledge in coding but wouldn't it be possible to have the clock
centered and have the notification icons below the clock?
Original comment by pranavpr...@gmail.com
on 14 Feb 2013 at 6:53
This will become an available 'Advanced' config option in the next version.
Original comment by roman.nurik
on 14 Feb 2013 at 6:59
Oh, and fixed by revision 009b9e195240
Original comment by roman.nurik
on 14 Feb 2013 at 6:59
Issue 96 has been merged into this issue.
Original comment by roman.nurik
on 14 Feb 2013 at 1:38
Issue 131 has been merged into this issue.
Original comment by roman.nurik
on 15 Feb 2013 at 11:07
Issue 135 has been merged into this issue.
Original comment by roman.nurik
on 16 Feb 2013 at 4:28
Original comment by roman.nurik
on 17 Feb 2013 at 6:48
Original issue reported on code.google.com by
ldjugg...@gmail.com
on 12 Feb 2013 at 11:25