[Pharo-project] Please comment on a bug fix for Nautilus
We need you to give your opinion on a bug fix for Nautilus. No need to load any code in your image, just look at the screenshots and comments at: https://pharo.fogbugz.com/default.asp?10139 and give us your opinion -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
On 10 April 2013 13:21, Damien Cassou <damien.cassou@gmail.com> wrote:
We need you to give your opinion on a bug fix for Nautilus. No need to load any code in your image, just look at the screenshots and comments at:
https://pharo.fogbugz.com/default.asp?10139
and give us your opinion //
Often, especially with Morphs i need to go to superclass and i think it would be nicer to keep it one-line above in the list close to selected class i am working with. If it is about extensions or extended classes which not belongs to your package they can be in any order. But if you really want to separate them (gray / black) then i would even go further and put them into separate list widget, so there will be no confusion that those lists are independent (and no need to invent some strange ordering scheme) //
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
-- Best regards, Igor Stasenko.
On Apr 10, 2013, at 8:12 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 10 April 2013 13:21, Damien Cassou <damien.cassou@gmail.com> wrote:
We need you to give your opinion on a bug fix for Nautilus. No need to load any code in your image, just look at the screenshots and comments at:
https://pharo.fogbugz.com/default.asp?10139
and give us your opinion //
Often, especially with Morphs i need to go to superclass and i think it would be nicer to keep it one-line above in the list close to selected class i am working with. If it is about extensions or extended classes which not belongs to your package they can be in any order.
But if you really want to separate them (gray / black) then i would even go further and put them into separate list widget, so there will be no confusion that those lists are independent (and no need to invent some strange ordering scheme)
No We want to see packages extensions with the classes defined in the package. No separated list! Stf
//
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
-- Best regards, Igor Stasenko.
On 10 April 2013 21:42, stephane ducasse <stephane.ducasse@free.fr> wrote:
On Apr 10, 2013, at 8:12 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 10 April 2013 13:21, Damien Cassou <damien.cassou@gmail.com> wrote:
We need you to give your opinion on a bug fix for Nautilus. No need to load any code in your image, just look at the screenshots and comments at:
https://pharo.fogbugz.com/default.asp?10139
and give us your opinion //
Often, especially with Morphs i need to go to superclass and i think it would be nicer to keep it one-line above in the list close to selected class i am working with. If it is about extensions or extended classes which not belongs to your package they can be in any order.
But if you really want to separate them (gray / black) then i would even go further and put them into separate list widget, so there will be no confusion that those lists are independent (and no need to invent some strange ordering scheme)
No We want to see packages extensions with the classes defined in the package. No separated list!
this is what i don't like either.. i just proposed the other side of extreme. to me the list should be sorted in a way how that it follows hierarchy.
Stf
//
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.
n.b. this conversation is half on the issue tracker and half on the mailing list ----- Cheers, Sean -- View this message in context: http://forum.world.st/Please-comment-on-a-bug-fix-for-Nautilus-tp4680595p468... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On 2013-04-10, at 21:42, stephane ducasse <stephane.ducasse@free.fr> wrote:
On Apr 10, 2013, at 8:12 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 10 April 2013 13:21, Damien Cassou <damien.cassou@gmail.com> wrote:
We need you to give your opinion on a bug fix for Nautilus. No need to load any code in your image, just look at the screenshots and comments at:
https://pharo.fogbugz.com/default.asp?10139
and give us your opinion //
Often, especially with Morphs i need to go to superclass and i think it would be nicer to keep it one-line above in the list close to selected class i am working with. If it is about extensions or extended classes which not belongs to your package they can be in any order.
But if you really want to separate them (gray / black) then i would even go further and put them into separate list widget, so there will be no confusion that those lists are independent (and no need to invent some strange ordering scheme)
No We want to see packages extensions with the classes defined in the package. No separated list!
I DO want to have them clearly separated => add an option! once the algorithm works for mixed packages that should be no problem to make it work both ways.
yes, I think is confusing but we can have an option in settings for that :) On Apr 11, 2013, at 8:31 AM, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-04-10, at 21:42, stephane ducasse <stephane.ducasse@free.fr> wrote:
On Apr 10, 2013, at 8:12 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 10 April 2013 13:21, Damien Cassou <damien.cassou@gmail.com> wrote:
We need you to give your opinion on a bug fix for Nautilus. No need to load any code in your image, just look at the screenshots and comments at:
https://pharo.fogbugz.com/default.asp?10139
and give us your opinion //
Often, especially with Morphs i need to go to superclass and i think it would be nicer to keep it one-line above in the list close to selected class i am working with. If it is about extensions or extended classes which not belongs to your package they can be in any order.
But if you really want to separate them (gray / black) then i would even go further and put them into separate list widget, so there will be no confusion that those lists are independent (and no need to invent some strange ordering scheme)
No We want to see packages extensions with the classes defined in the package. No separated list!
I DO want to have them clearly separated => add an option! once the algorithm works for mixed packages that should be no problem to make it work both ways.
On Thu, Apr 11, 2013 at 9:01 AM, Esteban Lorenzano <estebanlm@gmail.com>wrote:
yes, I think is confusing but we can have an option in settings for that :)
I'm only asking you to choose between what we already have, not an hypothetical future. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
participants (6)
-
Camillo Bruni -
Damien Cassou -
Esteban Lorenzano -
Igor Stasenko -
Sean P. DeNigris -
stephane ducasse