January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Schwab,Wilhelm K

Gary, If announcements are at all what I am expecting (perhaps a non-trivial assumption??), then I doubt it will be a problem. One would observe the world/window-manager for open events, and then express interest in events from individual windows. That might turn out to be easier on consumers than getting everything from one source. Cleanup should be trivial if the announcement framework uses weak references. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Gary Chambers Sent: Thursday, January 07, 2010 8:10 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Notifications of windows opening/closing/focus That is one option, though it does seem to be burdensome on the announcement consumers to (depending upon requirements) possibly have to track all windows themselves. Regards, Gary ----- Original Message ----- From: "Simon Denier" <Simon.Denier(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, January 07, 2010 12:47 PM Subject: Re: [Pharo-project] Notifications of windows opening/closing/focus > > On 7 janv. 2010, at 12:49, Gary Chambers wrote: > >> I think the annnouncements should be sent by the World (being, >> effectively, >> the window manager). > > One problem is that World is an instance of PasteUpMorph. If we modify > this class, what happens to potential other instances? > By default in my Pharo image, it seems that World is the only instance of > PasteUpMorph. > >> Too many ways to open open a window exist and only the fact of being >> added >> to the World seems consistent. >> I suggest opened, closed, activated (becoming topmost-ish), deactivated, >> expanded, collapsed, restored and maybe repositioned/resized would be >> useful. > > > Do you mean that such announcements should be performed by World? Because > most are already done by windows themselves with the patch of Alex. > As I said, the only one really necessary in World is window opened, so > that listeners subscribed to World are notifited of windows opened in > World and can subscribe to them. > > By the way Alex, is there a squeaksource project with your extensions as > regular methods and classes (not in a changeset)? > > >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Henrik Sperre Johansen" <henrik.s.johansen(a)veloxit.no> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Wednesday, January 06, 2010 9:53 PM >> Subject: Re: [Pharo-project] Notifications of windows >> opening/closing/focus >> >> >>> On 06.01.2010 22:36, Simon Denier wrote: >>>> On 6 janv. 2010, at 18:42, Gary Chambers wrote: >>>> >>>> >>>>> Indeed. Would be nicer if there was a proper announcement protocol for >>>>> such >>>>> things though. >>>>> >>>> I see, updateTasks is called everytime a change in layout happens then. >>>> Indeed, it looks like announcements will greatly simplified the trick. >>>> >>>> I am not sure where to do the announcement though. Does any top window >>>> uses openInWorld to add itself to World? >>>> >>>> >>> My guess would be that at the end of >>> SystemWindow>> openAsIsIn: >>> would be the the simplest place to put it. >>> >>> Cheers, >>> Henry >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 7, 2010

Re: [Pharo-project] Simple question about NewInspector

by Henrik Johansen

In latest version from ss, loaded into PharoCore, it does a MNU ByteString>types. ProtoObject >> niChildrenBlockForFixedFields, in the line: extractedType types do: [:t | s nextPutAll: t printString] separatedBy: [s nextPutAll: ', ']. extractedType is the string you mentioned. Cheers, Henry On Jan 4, 2010, at 9:49 49AM, Frederic Pluquet wrote: > RoelTyper is also used in ProtoObject>>niChildrenBlockForFixedFields (an extension for NewInspector). > > NewInspector can work without RoelTyper. The message "The last version of RoelTyper must be loaded to have this information" is shown when NewInspector tries to calculate types and that RoelTyper is not found. > > > FrÃ©d > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet > > > On Sat, Dec 26, 2009 at 11:29 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi Frederic. I am trying to see if it make sense to create a metacello configuration for NewInspector. The only external (not in PharoCore) dependency I saw using the DependencyBrowser is RoelTyper, which is used in the class NICompiledMethodNode >> configuration you use the class TypeCollector which is from RoelTyper. > > So, the question is, is this dependency correct? I ask because I took a PharoCore image, load NewINspector WITHOUT RoelTyper and it "seemed" to work. > > Thank you very much. > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 7, 2010

Re: [Pharo-project] About my recursive blues :)

by David T. Lewis

On Thu, Jan 07, 2010 at 08:23:02AM +0200, Danie Roux wrote: > 2010/1/7 Miguel Enrique Cob? Martinez: > > > Respect to Squeak, I seriously began to write a reply to the mail from > > Andreas announcing the removal of Etoys > > Are you referring to this message: > http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-January/142974.… > > The one that states "... I finished the first round on making Etoys > package *reloadable* in trunk" (emphasis mine). > > That is not the same as removal to me? Right. Miguel, perhaps you misunderstand. Etoys and other packages are being made reloadable. Clean, reloadable packages are a goal that we all share, and IMO the work in Squeak and Pharo will be complimentary and helpful to all in the long run. In the case of Squeak, one of the goals is to be able to provide better support for Etoys. Making a reloadable Etoys package is an important step in that direction. :) Dave

Jan. 7, 2010

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Henrik Johansen

On Jan 7, 2010, at 2:10 04PM, Gary Chambers wrote: > That is one option, though it does seem to be burdensome on the announcement > consumers to (depending upon requirements) possibly have to track all > windows themselves. > > Regards, GaryI am not talking about Announcers, but where the Announcement is created. I'm not talking about letting the window be the announcer, but where the announcement is made. So you'd do openAsIsIn: aWorld "current implementation" someAnnouncer announce: (WindowOpened for: self in: self world) someAnnouncer could be a global announcer for all window events. Cheers, Henry

Jan. 7, 2010

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Gary Chambers

That is one option, though it does seem to be burdensome on the announcement consumers to (depending upon requirements) possibly have to track all windows themselves. Regards, Gary ----- Original Message ----- From: "Simon Denier" <Simon.Denier(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, January 07, 2010 12:47 PM Subject: Re: [Pharo-project] Notifications of windows opening/closing/focus > > On 7 janv. 2010, at 12:49, Gary Chambers wrote: > >> I think the annnouncements should be sent by the World (being, >> effectively, >> the window manager). > > One problem is that World is an instance of PasteUpMorph. If we modify > this class, what happens to potential other instances? > By default in my Pharo image, it seems that World is the only instance of > PasteUpMorph. > >> Too many ways to open open a window exist and only the fact of being >> added >> to the World seems consistent. >> I suggest opened, closed, activated (becoming topmost-ish), deactivated, >> expanded, collapsed, restored and maybe repositioned/resized would be >> useful. > > > Do you mean that such announcements should be performed by World? Because > most are already done by windows themselves with the patch of Alex. > As I said, the only one really necessary in World is window opened, so > that listeners subscribed to World are notifited of windows opened in > World and can subscribe to them. > > By the way Alex, is there a squeaksource project with your extensions as > regular methods and classes (not in a changeset)? > > >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Henrik Sperre Johansen" <henrik.s.johansen(a)veloxit.no> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Wednesday, January 06, 2010 9:53 PM >> Subject: Re: [Pharo-project] Notifications of windows >> opening/closing/focus >> >> >>> On 06.01.2010 22:36, Simon Denier wrote: >>>> On 6 janv. 2010, at 18:42, Gary Chambers wrote: >>>> >>>> >>>>> Indeed. Would be nicer if there was a proper announcement protocol for >>>>> such >>>>> things though. >>>>> >>>> I see, updateTasks is called everytime a change in layout happens then. >>>> Indeed, it looks like announcements will greatly simplified the trick. >>>> >>>> I am not sure where to do the announcement though. Does any top window >>>> uses openInWorld to add itself to World? >>>> >>>> >>> My guess would be that at the end of >>> SystemWindow>> openAsIsIn: >>> would be the the simplest place to put it. >>> >>> Cheers, >>> Henry >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 7, 2010

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Henrik Johansen

On Jan 7, 2010, at 12:49 57PM, Gary Chambers wrote: > I think the annnouncements should be sent by the World (being, effectively, > the window manager). > Too many ways to open open a window exist and only the fact of being added > to the World seems consistent. > I suggest opened, closed, activated (becoming topmost-ish), deactivated, > expanded, collapsed, restored and maybe repositioned/resized would be > useful. > > Regards, Gary I thought the same, thus my first thought was doing it in PasteupMorph>> addMorph:. Now I think it's a bad idea, because: - Not all PasteUpMorphs are necessarily Worlds. - Not all morphs added to Worlds are windows. If putting it in a SystemWindow method means having to refactor some methods so all ways of opening a window passes through that method, I don't really see that as a bad thing. As far as I can tell though, all open... methods for SystemWindow + subclasses already pass through #openAsIsIn: Cheers, Henry

Jan. 7, 2010

Re: [Pharo-project] cutting dependencies

by StÃ©phane Ducasse

On Jan 6, 2010, at 7:54 PM, Marcus Denker wrote: > > On Jan 6, 2010, at 5:44 PM, Alain Plantec wrote: > >> StÃ©phane Ducasse a Ã©crit : >>> Now the fact that Setting is cool will also >>> reduce some problems we saw before. This will raise the question of the usage of services too. >>> Because Services are a registration mechanism. >>> >> I thought that Services was to be removed and I've started to do so (It >> would allow to fully remove Preferences). >> Have I missed something ? > > No, services (the artefact that is there now, unused) should be removed. But we might need to introduce > something similar (but simpler) later again. Yes we will have > > Marcus > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 7, 2010

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Simon Denier

On 7 janv. 2010, at 12:49, Gary Chambers wrote: > I think the annnouncements should be sent by the World (being, effectively, > the window manager). One problem is that World is an instance of PasteUpMorph. If we modify this class, what happens to potential other instances? By default in my Pharo image, it seems that World is the only instance of PasteUpMorph. > Too many ways to open open a window exist and only the fact of being added > to the World seems consistent. > I suggest opened, closed, activated (becoming topmost-ish), deactivated, > expanded, collapsed, restored and maybe repositioned/resized would be > useful. Do you mean that such announcements should be performed by World? Because most are already done by windows themselves with the patch of Alex. As I said, the only one really necessary in World is window opened, so that listeners subscribed to World are notifited of windows opened in World and can subscribe to them. By the way Alex, is there a squeaksource project with your extensions as regular methods and classes (not in a changeset)? > > Regards, Gary > > ----- Original Message ----- > From: "Henrik Sperre Johansen" <henrik.s.johansen(a)veloxit.no> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, January 06, 2010 9:53 PM > Subject: Re: [Pharo-project] Notifications of windows opening/closing/focus > > >> On 06.01.2010 22:36, Simon Denier wrote: >>> On 6 janv. 2010, at 18:42, Gary Chambers wrote: >>> >>> >>>> Indeed. Would be nicer if there was a proper announcement protocol for >>>> such >>>> things though. >>>> >>> I see, updateTasks is called everytime a change in layout happens then. >>> Indeed, it looks like announcements will greatly simplified the trick. >>> >>> I am not sure where to do the announcement though. Does any top window >>> uses openInWorld to add itself to World? >>> >>> >> My guess would be that at the end of >> SystemWindow>> openAsIsIn: >> would be the the simplest place to put it. >> >> Cheers, >> Henry >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Simon

Jan. 7, 2010

Re: [Pharo-project] Beginner question :) search and rep lace in String

by csrabak＠bol.com.br

Em 06/01/2010 22:06, Levente Uzonyi < leves(a)elte.hu > escreveu: > On Wed, 6 Jan 2010, csrabak(a)bol.com.br wrote: > > > Em 06/01/2010 17:30, Levente Uzonyi < leves(a)elte.hu > escreveu: > > > >> On Wed, 6 Jan 2010, csrabak(a)bol.com.br wrote: [snipped] > >>> As everybody else knows :-P the string concatenation operator is > >>> '+', right!? So #, needs to be explained anyway. . . > >> You're wrong, it's '.'. :) > > You know this polyglot approach to programming ends up with some > > confusion :-) > > [snipped] > > > >>> This may lead to the same problem we already have with #, namely > >>> it is slow and not recommended for repeated operations. > >>> No, it's fast, because it doesn't create copies. Of course to > >> know > >> that you also have to know that List is an alias for > >> OrderedCollection... It's just a C++ism that makes your code > >> slower. :) > >> Levente, > > In a ordinary (sort of, it's a dev image, Pharo 1.0 #10503, there > > is no List class, and: > > > > Collection>>, aCollection ^self copy addAll: aCollection; yourself > > Which creates copies for each #, method send, right? Or do I miss > > something here? > Yes you do, List is one of Adrian's ideas to Huffman code > smalltalk. Details here > http://www.iam.unibe.ch/~akuhn/blog/2009/one-letter-method-names/ > Ok Levente! In this case after reading Adrian's blog post, I would say "List" is not a good choice: VW uses List for a different kind of object (a descendant from OrderedCollection, in fact). As a side note, IMNHO Object>>out (as Travis' idea) seems to me better than Object>>p for the same purpose. Regards, -- Cesar Rabak

Jan. 7, 2010

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Schwab,Wilhelm K

Gary, It would also be nice to know about menus that open, but that is probably a matter to be taken up with the individual tool shell as it is opened. Either way, this sounds like a great start. Thanks to all involved for working on this! Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Gary Chambers Sent: Thursday, January 07, 2010 6:50 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Notifications of windows opening/closing/focus I think the annnouncements should be sent by the World (being, effectively, the window manager). Too many ways to open open a window exist and only the fact of being added to the World seems consistent. I suggest opened, closed, activated (becoming topmost-ish), deactivated, expanded, collapsed, restored and maybe repositioned/resized would be useful. Regards, Gary ----- Original Message ----- From: "Henrik Sperre Johansen" <henrik.s.johansen(a)veloxit.no> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, January 06, 2010 9:53 PM Subject: Re: [Pharo-project] Notifications of windows opening/closing/focus > On 06.01.2010 22:36, Simon Denier wrote: >> On 6 janv. 2010, at 18:42, Gary Chambers wrote: >> >> >>> Indeed. Would be nicer if there was a proper announcement protocol for >>> such >>> things though. >>> >> I see, updateTasks is called everytime a change in layout happens then. >> Indeed, it looks like announcements will greatly simplified the trick. >> >> I am not sure where to do the announcement though. Does any top window >> uses openInWorld to add itself to World? >> >> > My guess would be that at the end of > SystemWindow>> openAsIsIn: > would be the the simplest place to put it. > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 7, 2010