Just my 2 cents.
I don't have a lot of troubles with white theme usage. Maybe I just got used, I
don't know. But it hits my eyes really hard. On the retina display it's better but
on an older cinema display that I'm using it really makes my eyes suffer.
So maybe if everything was completely black, I'd be ok with it.
Also please note that I don't like iOS7 design :)
Cheers.
Uko
Sent from my iPhone
On 08 Apr 2014, at 06:47, Tudor Girba
<tudor(a)tudorgirba.com> wrote:
Hi,
Thanks for the detailed remarks. This is an excellent step.
As I figured, people have a problem with handling Nautilus. In my opinion, making
Nautilus work properly is a class of problems of its own because currently it uses widgets
in unfortunate ways. See my comments below.
Are you using other tools where you see problems? Perhaps some GT tools or something
Glamour related?
On Mon, Apr 7, 2014 at 1:40 AM, Johan Fabry
<jfabry(a)dcc.uchile.cl> wrote:
In other configurations/other tools it can of course look differently. This is why I said
system browser ;-) Example is the image below
<AB.tiff>
> On Apr 6, 2014, at 8:23 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>
> Hi!
>
> I do not follow the problem with text field. On the test runner, it is obvious to me
that there are two text fields.
>
> <Screen Shot 2014-04-06 at 8.21.28 PM.png>
>
>
> or do you mean something else? Just wondering
>
> Alexandre
>
>
>> On Apr 6, 2014, at 8:16 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote:
>>
>> Sorry for the delay, I’ve been needing to concentrate on some other things …
>>
>> Here is a list of concrete things which annoy me in the white theme (today’s
download of 5.0). This is all restricted to what I see in the system browser
>> - text fields for searching and history navigator drop down are without an
outline that indicate that these are text fields
It's true. I am not happy at
all with how the drop downs look. I could not make it to work properly because it
hardcodes too many things and I did not have the time to look at it.
That being said, both text fields are actually clearly indicated due to the text that
goes with them. I doubt that people will not be able to find where the field is.
I am actually torn with drawing borders around the text fields. Adding a border around
text areas would imply adding borders around lists as well and this will add significant
noise. On very few occasions I see problems with having two text fields next to each
other. This can happen in the GTInspector when browsing the code in both panes. However,
this situation will be solved with a new widget.
>> - for drop down opening button it's
is not clear it’s a button.
Agreed. This is a problem induced by the implementation
of the drop down widget. I will try to solve it somehow.
>> - background of the class toggle is
different from the buttons.
Well, that is because it is not a button. It's a
checkbox morph. I would not optimize a whole theme just to make this unfortunate choice
more fortunate.
>> - it’s not clear that buttons are buttons
because the conventional borders around buttons are absent (holds for both the traditional
ones as the show source code / show byte code / etc…)
When you place those button
on a white space, it is actually quite clear. The buttons you mention did not receive a
particularly happy design:
- the first two represent states that would be better modeled as tabs. I guess this will
not happen.
- the last three require some space in between. Just doing this would make things
simpler.
>> Also, I don’t like that the borders of
text fields are gone. I could live with that however. It’s just that when you have a
scroll bar in the text field but the content of the text is less than a page, there is
white space to the right of the text that is not used and it’s not clear why. This because
you don’t see the border of the text field so you don’ t know this is the space of the
scroll bar. So it’s like: why does it reflow there, when there are 30 pixels more of white
?
Hmm, in what situation did you see this? The scrollbar typically appears when
we the text is larger than the area. In that case, the scrolling bar appears as well and
it should indicate its presence.
Cheers,
Doru
2014-04-04 22:13 GMT+02:00 Tudor Girba
<tudor(a)tudorgirba.com>om>:
> Thanks for the input.
>
> If you say it like that there are little chances of changing anything. The only way
we can improve is to know why something does not work. Only when we know the reasons can
we start to react properly. So, please do let us know what does not work.
---> Save our in-boxes!
http://emailcharter.org <---
Johan Fabry -
http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---> Save our in-boxes!
http://emailcharter.org <---
Johan Fabry -
http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev