do we need handleDisabledKey:

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

do we need handleDisabledKey:

Stéphane Ducasse
hi gary

do we need handleDisabledKey: because this is not defined on the new editorHierarchy?

http://code.google.com/p/pharo/issues/detail?id=3003

Stef
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: do we need handleDisabledKey:

Guillermo Polito
I had a look at CUIS, and it doesn't use it neither.

On Fri, Sep 24, 2010 at 3:01 PM, Stéphane Ducasse <[hidden email]> wrote:
hi gary

do we need handleDisabledKey: because this is not defined on the new editorHierarchy?

http://code.google.com/p/pharo/issues/detail?id=3003

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


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: do we need handleDisabledKey:

Stéphane Ducasse
In reply to this post by Stéphane Ducasse
Yes it is a polymorph features.
I ask gary to have a look when he has time.

Stef

On Sep 25, 2010, at 10:52 PM, Guillermo Polito wrote:

> I had a look at CUIS, and it doesn't use it neither.
>
> On Fri, Sep 24, 2010 at 3:01 PM, Stéphane Ducasse <[hidden email]> wrote:
> hi gary
>
> do we need handleDisabledKey: because this is not defined on the new editorHierarchy?
>
> http://code.google.com/p/pharo/issues/detail?id=3003
>
> Stef
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: do we need handleDisabledKey:

Gary Chambers-4
In reply to this post by Stéphane Ducasse
Catching up on emails after being away... will check once software update
completes...

Regards, Gary

----- Original Message -----
From: "Stéphane Ducasse" <[hidden email]>
To: "Pharo Development" <[hidden email]>
Sent: Friday, September 24, 2010 7:01 PM
Subject: [Pharo-project] do we need handleDisabledKey:


> hi gary
>
> do we need handleDisabledKey: because this is not defined on the new
> editorHierarchy?
>
> http://code.google.com/p/pharo/issues/detail?id=3003
>
> Stef
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project 


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: do we need handleDisabledKey:

Gary Chambers-4
Well, the short answer is "yes" if we want the (previously requested long
ago) features of being able to copy text, browse classes etc. from
selections in disabled text.

Regards, Gary

----- Original Message -----
From: "Gary Chambers" <[hidden email]>
To: <[hidden email]>
Sent: Monday, October 04, 2010 11:17 AM
Subject: Re: [Pharo-project] do we need handleDisabledKey:


Catching up on emails after being away... will check once software update
completes...

Regards, Gary

----- Original Message -----
From: "Stéphane Ducasse" <[hidden email]>
To: "Pharo Development" <[hidden email]>
Sent: Friday, September 24, 2010 7:01 PM
Subject: [Pharo-project] do we need handleDisabledKey:


> hi gary
>
> do we need handleDisabledKey: because this is not defined on the new
> editorHierarchy?
>
> http://code.google.com/p/pharo/issues/detail?id=3003
>
> Stef
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


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


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: do we need handleDisabledKey:

Guillermo Polito
So as a first approach, we should use the ParagraphEditor  #handleDisabledKey: behavior.  Should we?

Cheers,
Guille

On Mon, Oct 4, 2010 at 7:29 AM, Gary Chambers <[hidden email]> wrote:
Well, the short answer is "yes" if we want the (previously requested long ago) features of being able to copy text, browse classes etc. from selections in disabled text.

Regards, Gary

----- Original Message ----- From: "Gary Chambers" <[hidden email]>
To: <[hidden email]>
Sent: Monday, October 04, 2010 11:17 AM
Subject: Re: [Pharo-project] do we need handleDisabledKey:



Catching up on emails after being away... will check once software update
completes...

Regards, Gary

----- Original Message ----- From: "Stéphane Ducasse" <[hidden email]>
To: "Pharo Development" <[hidden email]>
Sent: Friday, September 24, 2010 7:01 PM
Subject: [Pharo-project] do we need handleDisabledKey:


hi gary

do we need handleDisabledKey: because this is not defined on the new editorHierarchy?

http://code.google.com/p/pharo/issues/detail?id=3003

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


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

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


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: do we need handleDisabledKey:

Gary Chambers-4
Similar, but reworked to fit in with TextEditor>>disptachOn: style of handling.

Regards, Gary
----- Original Message -----
Sent: Monday, October 04, 2010 1:26 PM
Subject: Re: [Pharo-project] do we need handleDisabledKey:

So as a first approach, we should use the ParagraphEditor  #handleDisabledKey: behavior.  Should we?

Cheers,
Guille

On Mon, Oct 4, 2010 at 7:29 AM, Gary Chambers <[hidden email]> wrote:
Well, the short answer is "yes" if we want the (previously requested long ago) features of being able to copy text, browse classes etc. from selections in disabled text.

Regards, Gary

----- Original Message ----- From: "Gary Chambers" <[hidden email]>
To: <[hidden email]>
Sent: Monday, October 04, 2010 11:17 AM
Subject: Re: [Pharo-project] do we need handleDisabledKey:



Catching up on emails after being away... will check once software update
completes...

Regards, Gary

----- Original Message ----- From: "Stéphane Ducasse" <[hidden email]>
To: "Pharo Development" <[hidden email]>
Sent: Friday, September 24, 2010 7:01 PM
Subject: [Pharo-project] do we need handleDisabledKey:


hi gary

do we need handleDisabledKey: because this is not defined on the new editorHierarchy?

http://code.google.com/p/pharo/issues/detail?id=3003

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


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

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


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

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