[Pharo-project] Suggestions about Nautilus Look
Hi all, I have a couple of propositions about the Nautilus look: 1 - If the Nautilus browser is a package browser why an infinity stack of grey packages is shown? I think it is possible to safely remove all the grey package icons since they are not really useful nor meaningful. This will make the visual impact of nautilus lighter. 2- I think would be nicer to have smaller icons for tests like the one from omnibrowser. I understand the icons are like buttons but the active area to trigger the event "run the test" is not the icon itself, isn't it? It is more in the area around the icon (also these icons appear in strange places in the code, e.g. MooseModel>>add: which is weird). 3- The text in the message that appear in bottom-left corner that notify about the test results it is not really visible if the background is yellow or green so what about to make it black. Or better, what about to make it black if the background color is green or yellow and leave it white if the background is red? 4- the buttons to see the bytecode and the decompile code I immagine they can became useful for some particular development but for normal development I never had the needed to check the decompiled version of a method or the bytecode. Different matter are the buttons for the instance and class variables. It would be cool to make these functionalists less "visible" making them available in a different way, for example in the contextual menu that appear in the method editor panel. What do you think? Cheers, Fabrizio
Fabrizio Perin-3 wrote
I have a couple of propositions about the Nautilus look:
Great feedback! Thanks for taking the time to start the discussion... Fabrizio Perin-3 wrote
1 - If the Nautilus browser is a package browser why an infinity stack of grey packages is shown? I think it is possible to safely remove all the grey package icons since they are not really useful nor meaningful. This will make the visual impact of nautilus lighter.
The gray icons indicate that the package is clean. When there are unsaved changes, the color goes to red Fabrizio Perin-3 wrote
3- The text in the message that appear in bottom-left corner that notify about the test results it is not really visible if the background is yellow or green so what about to make it black. Or better, what about to make it black if the background color is green or yellow and leave it white if the background is red?
Whatever color we make them, they will be less visible with *some* color background ;-) I *really* like that the visual color feedback is part of the testing domain. I know the test passed without moving my eyes to the corner to read the text. Your point about checking the background color and altering for some contrast is valid, but seems like a long-shot (how many people have those bold green/yellow colors as backgrounds?!). I would guess if you're passionate about it, you should implement it yourself and submit the code :) Sean -- View this message in context: http://forum.world.st/Suggestions-about-Nautilus-Look-tp4631723p4631728.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Hi,
Fabrizio Perin-3 wrote
1 - If the Nautilus browser is a package browser why an infinity stack of grey packages is shown? I think it is possible to safely remove all the grey package icons since they are not really useful nor meaningful. This will make the visual impact of nautilus lighter.
The gray icons indicate that the package is clean. When there are unsaved changes, the color goes to red
I have noticed that but what I'm saying is that we know those are packages because that is a package browser. The gray icons are a redundant information and so not useful and also visually disturbing. I think, if you don't have to tell me something in particular like that there are unsaved changes, there should be no icon on the packages.
Fabrizio Perin-3 wrote
3- The text in the message that appear in bottom-left corner that notify about the test results it is not really visible if the background is yellow or green so what about to make it black. Or better, what about to make it black if the background color is green or yellow and leave it white if
the
background is red?
Whatever color we make them, they will be less visible with *some* color background ;-) I *really* like that the visual color feedback is part of the testing domain. I know the test passed without moving my eyes to the corner to read the text. Your point about checking the background color and altering for some contrast is valid, but seems like a long-shot (how many people have those bold green/yellow colors as backgrounds?!). I would guess if you're passionate about it, you should implement it yourself and submit the code :)
I also like that notification. What I'm saying here is that the color of
the text into the feedback is white (or transparent and so white since I have white background) and so it is not really readable in case the feedback is green or yellow accordingly to the tests result. But this is a really tiny point. Regards, Fabrizio
participants (2)
-
Fabrizio Perin -
Sean P. DeNigris