Issue 5452 in pharo: Add a single way to lock every Morphs entryPoints

Status: New
Owner: ----

New issue 5452 by [hidden email]: Add a single way to lock every  
Morphs entryPoints
http://code.google.com/p/pharo/issues/detail?id=5452

In a way that
     - halo are not displayed anymore
     - can't right click on text morphs
     - can't use some cmd+ shortcuts on text morphs (maybe should add ctrl  
too)
     - StandardWindow menu is disabled (even if the little triangle is still  
there)
     - World Menu is disabled

Slice is incoming


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 5452 by [hidden email]: Add a single way to lock  
every Morphs entryPoints
http://code.google.com/p/pharo/issues/detail?id=5452

- Lock the drop file into the image mechanism

Slice in the inbox


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixReviewNeeded
        Cc: [hidden email]

Comment #2 on issue 5452 by [hidden email]: Add a single way to lock  
every Morphs entryPoints
http://code.google.com/p/pharo/issues/detail?id=5452

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Workneeded

Comment #4 on issue 5452 by [hidden email]: Add a single way to lock  
every Morphs entryPoints
http://code.google.com/p/pharo/issues/detail?id=5452

hello,

I don't think that this is a good implementation. because we used to be  
able to just disable morphs halos (and enable them for subclasses), while  
keeping everything else working.

The same: I might want to disable the text menu, but not turn of halos.

So merging everything into one mechanism is not the way to go, I think.

What would be better: have all the things that one disable separate, but a  
simple way to turn them all off at once.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #5 on issue 5452 by [hidden email]: Add a single way to lock  
every Morphs entryPoints
http://code.google.com/p/pharo/issues/detail?id=5452

Ok :)

We will split that :)



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #7 on issue 5452 by [hidden email]: Add a single way to lock  
every Morphs entryPoints
http://code.google.com/p/pharo/issues/detail?id=5452

I close this for now.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Accepted

Comment #8 on issue 5452 by [hidden email]: Add a single way to lock  
every Morphs entryPoints
http://code.google.com/p/pharo/issues/detail?id=5452

Why close this? As I understand it, this is still a valid feature, but just  
needs a different implementation. It will now be a script that does all the  
items on the list, which can also be done separately, no?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #9 on issue 5452 by [hidden email]: Add a single way to lock  
every Morphs entryPoints
http://code.google.com/p/pharo/issues/detail?id=5452

Because they can open a new entry as soon they have the [enh] ready.

The code proposed is not good  enough.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker