Another look at the [First Impression Count] in Pharo 5
AMHO, there are some needed feedbacks on some tools. There are the most visible I can see, where newbies will be contemplating without understanding. I try to propose a tip, please *correct* it when wrong or incomplete. NAUTILUS - 'Scoped'-> not sure what is the extent of the Scoped, but a proposed tip: 'Browse in the context of the selected package/class: all nautilus tools -- including refactoring -- will proceed only within the selected package/class.' - 'Format as you read' -> based on Peter suggestion: 'Autoformat code without editing. Useful when reading some old/unformatted code.' - 'NW/W' -> I don't know - '+L' -> 'Toggle line number for code" SETTINGS BROWSERS - There are about 100 Spotter entries without unhelpful descriptions as: 'Trait>>#spotterReferenceFor: spotterReferenceFor: aStep <spotterOrder: 30> aStep listProcessor title: 'References'; allCandidates: [ (SystemNavigation default allReferencesTo: self binding) collect: #compiledMethod ]; itemName: [ :method | method gtDisplayString ]; filter: GTFilterSubstring' is it a bug or on purpose? However definitely not newbie friendly. If these settings are not relevant, may be hiding it. - GRAPHIC THEME It lacks contrast, (and no there is objective measure, otherwise what is design for) but I guess nothing much can be done. Tooltips lost again the blue contrasting background for a grey unconstrasting one. In the past I already fixed the Water theme from random refactoring, it is sad to see few care on the UI: this is the first thing newbies will notice even before reaching the deep beauty of Pharo, they will be gone because the first impression went wrong. Hilaire PS: Please, don't assume because I post this review I take responsibility on fixing it, I may or not. I really get this irritating feedback from my feedbacks, and I don't think pressure is helpful. We are doing our best according to our personnel life constraints. If not ok, I will shut up for ever. -- Dr. Geo http://drgeo.eu
On May 5, 2016, at 12:32 AM, Hilaire <hilaire@drgeo.eu> wrote:
AMHO, there are some needed feedbacks on some tools. There are the most visible I can see, where newbies will be contemplating without understanding.
I try to propose a tip, please *correct* it when wrong or incomplete.
NAUTILUS - 'Scoped'-> not sure what is the extent of the Scoped, but a proposed tip: 'Browse in the context of the selected package/class: all nautilus tools -- including refactoring -- will proceed only within the selected package/class.' - 'Format as you read' -> based on Peter suggestion: 'Autoformat code without editing. Useful when reading some old/unformatted code.' - 'NW/W' -> I don't know - '+L' -> 'Toggle line number for code"
SETTINGS BROWSERS - There are about 100 Spotter entries without unhelpful descriptions as: 'Trait>>#spotterReferenceFor: spotterReferenceFor: aStep <spotterOrder: 30> aStep listProcessor title: 'References'; allCandidates: [ (SystemNavigation default allReferencesTo: self binding) collect: #compiledMethod ]; itemName: [ :method | method gtDisplayString ]; filter: GTFilterSubstring'
is it a bug or on purpose? However definitely not newbie friendly.
If these settings are not relevant, may be hiding it.
- GRAPHIC THEME It lacks contrast, (and no there is objective measure, otherwise what is design for) but I guess nothing much can be done. Tooltips lost again the blue contrasting background for a grey unconstrasting one. In the past I already fixed the Water theme from random refactoring, it is sad to see few care on the UI: this is the first thing newbies will notice even before reaching the deep beauty of Pharo, they will be gone because the first impression went wrong.
Hilaire
PS: Please, don't assume because I post this review I take responsibility on fixing it, I may or not. I really get this irritating feedback from my feedbacks, and I don't think pressure is helpful. We are doing our best according to our personnel life constraints. If not ok, I will shut up for ever.
Hilaire, please, never shut up.
-- Dr. Geo http://drgeo.eu
On 05/05/16 10:38, Eliot Miranda wrote:
Hilaire, please, never shut up.
+1 Noticing all theses things and not having enough time and energy to be able to fix them all can be tiring. We value what you are able to do. Stephan
Le 05/05/2016 09:32, Hilaire a écrit :
AMHO, there are some needed feedbacks on some tools. There are the most visible I can see, where newbies will be contemplating without understanding.
I try to propose a tip, please *correct* it when wrong or incomplete.
NAUTILUS - 'Scoped'-> not sure what is the extent of the Scoped, but a proposed tip: 'Browse in the context of the selected package/class: all nautilus tools -- including refactoring -- will proceed only within the selected package/class.' - 'Format as you read' -> based on Peter suggestion: 'Autoformat code without editing. Useful when reading some old/unformatted code.' - 'NW/W' -> I don't know - '+L' -> 'Toggle line number for code"
SETTINGS BROWSERS - There are about 100 Spotter entries without unhelpful descriptions as: 'Trait>>#spotterReferenceFor: spotterReferenceFor: aStep <spotterOrder: 30> aStep listProcessor title: 'References'; allCandidates: [ (SystemNavigation default allReferencesTo: self binding) collect: #compiledMethod ]; itemName: [ :method | method gtDisplayString ]; filter: GTFilterSubstring'
is it a bug or on purpose? However definitely not newbie friendly.
If these settings are not relevant, may be hiding it.
- GRAPHIC THEME It lacks contrast, (and no there is objective measure, otherwise what is design for) but I guess nothing much can be done. Tooltips lost again the blue contrasting background for a grey unconstrasting one. In the past I already fixed the Water theme from random refactoring, it is sad to see few care on the UI: this is the first thing newbies will notice even before reaching the deep beauty of Pharo, they will be gone because the first impression went wrong.
Hilaire
PS: Please, don't assume because I post this review I take responsibility on fixing it, I may or not. I really get this irritating feedback from my feedbacks, and I don't think pressure is helpful. We are doing our best according to our personnel life constraints. If not ok, I will shut up for ever.
Hi Hilaire, I just added tooltips on rubric options in Nautilus for Pharo 5 release. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France
Hi Hilaire, Sorry for the delayed response. Please see my reply below.
On May 5, 2016, at 9:32 AM, Hilaire <hilaire@drgeo.eu> wrote:
AMHO, there are some needed feedbacks on some tools. There are the most visible I can see, where newbies will be contemplating without understanding.
I try to propose a tip, please *correct* it when wrong or incomplete.
NAUTILUS - 'Scoped'-> not sure what is the extent of the Scoped, but a proposed tip: 'Browse in the context of the selected package/class: all nautilus tools -- including refactoring -- will proceed only within the selected package/class.' - 'Format as you read' -> based on Peter suggestion: 'Autoformat code without editing. Useful when reading some old/unformatted code.' - 'NW/W' -> I don't know - '+L' -> 'Toggle line number for code"
SETTINGS BROWSERS - There are about 100 Spotter entries without unhelpful descriptions as: 'Trait>>#spotterReferenceFor: spotterReferenceFor: aStep <spotterOrder: 30> aStep listProcessor title: 'References'; allCandidates: [ (SystemNavigation default allReferencesTo: self binding) collect: #compiledMethod ]; itemName: [ :method | method gtDisplayString ]; filter: GTFilterSubstring'
is it a bug or on purpose? However definitely not newbie friendly.
Thanks for the input. These settings are indeed on purpose. Would you mind exchanging some more messages about this with me a bit to see what information would make it easier for a newcomer to comprehend? To get the conversation started, I put together a description of what they mean here: http://www.humane-assessment.com/blog/discovering-and-managing-spotter-exten... What do you think? Does this clarify the problem for you? If yes, what information would be useful to have in the image to better communicate the intent? Cheers, Doru
If these settings are not relevant, may be hiding it.
- GRAPHIC THEME It lacks contrast, (and no there is objective measure, otherwise what is design for) but I guess nothing much can be done. Tooltips lost again the blue contrasting background for a grey unconstrasting one. In the past I already fixed the Water theme from random refactoring, it is sad to see few care on the UI: this is the first thing newbies will notice even before reaching the deep beauty of Pharo, they will be gone because the first impression went wrong.
Hilaire
PS: Please, don't assume because I post this review I take responsibility on fixing it, I may or not. I really get this irritating feedback from my feedbacks, and I don't think pressure is helpful. We are doing our best according to our personnel life constraints. If not ok, I will shut up for ever.
-- Dr. Geo http://drgeo.eu
-- www.tudorgirba.com www.feenk.com "Some battles are better lost than fought."
Documentation always help :) What information will be helpful ? I understand now your intend: you want to encourage people to discover the Spot settings and how to write your own search plugin, so you expose the source code plugin in the settings browser description. It does not strike me, and I find your web page more helpful. But again, only my perception. Now, try to imagine the worst case scenario by playing the role of a student learning Pharo with MOOC. What information will be helpful for your given a few facts? - you already discover Spot, and find the tools pretty cool. - you learn about the Setting browser, there you discover you can toggle Spot's option. What will be useful for you to understand what does the plugings. Then, do you first want to know what does the plugin or how to write your own? May be in the settings browser, GT Spotter Extensions category, you can write a bit more about writing spotter plugin, then in each plugin entry write a human readable sentence explaining what does the plugin. After all, from the Settings browser, each entry is just one shortcut [alt]-b away. One remark, why is there both: Trait>>#spotterSuperClassMethodsFor: and Class>>#spotterSuperClassMethodsFor: The Trait one seems uneffective. Hilaire Le 05/06/2016 08:17, Tudor Girba a écrit :
make it easier for a newcomer to comprehend?
To get the conversation started, I put together a description of what they mean here: http://www.humane-assessment.com/blog/discovering-and-managing-spotter-exten...
What do you think? Does this clarify the problem for you? If yes, what information would be useful to have in the image to better communicate the intent?
-- Dr. Geo http://drgeo.eu
On Sun, Jun 5, 2016 at 4:28 PM, Hilaire <hilaire@drgeo.eu> wrote:
Documentation always help :)
What information will be helpful ? I understand now your intend: you want to encourage people to discover the Spot settings and how to write your own search plugin, so you expose the source code plugin in the settings browser description. It does not strike me, and I find your web page more helpful. But again, only my perception.
Now, try to imagine the worst case scenario by playing the role of a student learning Pharo with MOOC. What information will be helpful for your given a few facts?
- you already discover Spot, and find the tools pretty cool. - you learn about the Setting browser, there you discover you can toggle Spot's option. What will be useful for you to understand what does the plugings. Then, do you first want to know what does the plugin or how to write your own?
May be in the settings browser, GT Spotter Extensions category,
Oh! Not seen that before. That is interesting!
you can write a bit more about writing spotter plugin,
Sounds like a good place for such info. Or a button or link to bring up a help topic.
then in each plugin entry write a human readable sentence explaining what does the plugin.
And a bit of executable code to launch a demo of the GUI effect.
After all, from the Settings browser, each entry is just one shortcut [alt]-b away.
There is such a large number of extensions, its easy to be overwhelmed. Perhaps the could be another level, and/or display so some common/easy to follow ones at the top of the list of settings. cheers -ben
One remark, why is there both: Trait>>#spotterSuperClassMethodsFor: and Class>>#spotterSuperClassMethodsFor:
The Trait one seems uneffective.
Hilaire
Le 05/06/2016 08:17, Tudor Girba a écrit :
make it easier for a newcomer to comprehend?
To get the conversation started, I put together a description of what they mean here: http://www.humane-assessment.com/blog/discovering-and-managing-spotter-exten...
What do you think? Does this clarify the problem for you? If yes, what information would be useful to have in the image to better communicate the intent?
-- Dr. Geo http://drgeo.eu
participants (6)
-
Ben Coman -
Cyril Ferlicot D. -
Eliot Miranda -
Hilaire -
Stephan Eggermont -
Tudor Girba