- Pharo-dev - lists.pharo.org

Re: [Pharo-project] implementors and senders when there is only one result

by Henrik Johansen

Working mostly in VisualWorks, I too sometimes miss those when doing stuff in Pharo. What would be even cooler imho, would be using RoelTyper to find (potential) results only for the specific method you asked for senders of :) Cheers, Henry On Nov 3, 2009, at 8:30 16AM, Torsten Bergmann wrote: > > It also provides a "local senders" and "local implementors" > functionality (searching only within the class (hierarchy) itself) as > you will find in most Smalltalks. > > This browser provides a nice way to go through the system and follow > message chains. > > Bye > Torsten > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > <stmt.png>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 3, 2009

Re: [Pharo-project] implementors and senders when there is only one result

by Lukas Renggli

This is what the Chasing Browser in OmniBrowser does. Instead of using a tree it uses a Apple Finder like structure. I know that various people don't like the way this is presented in OmniBrowser. Personally I like it very much and use it all the time. Lukas 2009/11/3 Torsten Bergmann <astares(a)gmx.de>: > I always liked the sender/implementor/messages browser from > Smalltalk MT. Attached is a screenshot. > > When one searches for sender in the normal browser this browser opens > with a tree node "senders" and all the senders. > > If you click on one of the messages you can select > "senders" again, or "implementors" or "messages" and > go deeper. > > For instance you want to see the senders of #timeStamp > and from the second hit you want to see all the > other messages within this method and from there all implementors, ... > > It also provides a "local senders" and "local implementors" > functionality (searching only within the class (hierarchy) itself) as > you will find in most Smalltalks. > > This browser provides a nice way to go through the system and follow > message chains. > > Bye > Torsten > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Nov. 3, 2009

[Pharo-project] implementors and senders when there is only one result

by Torsten Bergmann

I always liked the sender/implementor/messages browser from Smalltalk MT. Attached is a screenshot. When one searches for sender in the normal browser this browser opens with a tree node "senders" and all the senders. If you click on one of the messages you can select "senders" again, or "implementors" or "messages" and go deeper. For instance you want to see the senders of #timeStamp and from the second hit you want to see all the other messages within this method and from there all implementors, ... It also provides a "local senders" and "local implementors" functionality (searching only within the class (hierarchy) itself) as you will find in most Smalltalks. This browser provides a nice way to go through the system and follow message chains. Bye Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Nov. 3, 2009

Re: [Pharo-project] Server sockets, ephermal ports, and a Linux VM crash

by Schwab,Wilhelm K

Mariano, Understood. I have not had time to run it down, but I am not being a complete slug today (not that you implied I was being such). I added to my stream protocol, wrote a nice test of in-image socket server and client, and am now tweaking my "load script" to look for code that I wrote and is not properly packaged. My image is ancient, and I don't know when Stef might make good on his threat to hunt us down for that :) Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Monday, November 02, 2009 10:25 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Server sockets, ephermal ports, and a Linux VM crash Bill: As always, it would help if you can give us/them more information. For example, running Pharo from command line and send the output of the command line. Or the PharoDebug.log or whatever other thing that may help. Best mariano 2009/11/3 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> John, By crash, I mean pretty much the standard thing: one instant, Pharo is running, click something on the inspector, and suddenly Pharo is gone. Not good. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr> [mailto:pharo-project-bounces@lists.gforge.inria.fr<mailto:pharo-project-bounces@lists.gforge.inria.fr>] On Behalf Of John McIntosh Sent: Monday, November 02, 2009 9:43 PM To: Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> Subject: Re: [Pharo-project] Server sockets, ephermal ports, and a Linux VM crash On Mon, Nov 2, 2009 at 5:52 PM, Igor Stasenko <siguctua(a)gmail.com<mailto:siguctua@gmail.com>> wrote: 2009/11/2 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>>: > A nice trick is to use "ephmeral" ports, which is a fancy way of saying to pass zero for the listening port and let the OS assign a port. OS-X assigns you the range 49152-65535 As for the getOption, the values for the key and the results is platform specific, and likely operating system version specific too. However for platforms that use BSD sockets, ala (Unix/Linux/OS-X) then the keys are in this table. Obviously if you fiddle with them then you know what you are doing? { "SO_DEBUG", SOL_SOCKET, SO_DEBUG }, { "SO_REUSEADDR", SOL_SOCKET, SO_REUSEADDR }, { "SO_DONTROUTE", SOL_SOCKET, SO_DONTROUTE }, { "SO_BROADCAST", SOL_SOCKET, SO_BROADCAST }, { "SO_SNDBUF", SOL_SOCKET, SO_SNDBUF }, { "SO_RCVBUF", SOL_SOCKET, SO_RCVBUF }, { "SO_KEEPALIVE", SOL_SOCKET, SO_KEEPALIVE }, { "SO_OOBINLINE", SOL_SOCKET, SO_OOBINLINE }, { "SO_LINGER", SOL_SOCKET, SO_LINGER }, { "IP_TTL", SOL_IP, IP_TTL }, { "IP_HDRINCL", SOL_IP, IP_HDRINCL }, { "IP_MULTICAST_IF", SOL_IP, IP_MULTICAST_IF }, { "IP_MULTICAST_TTL", SOL_IP, IP_MULTICAST_TTL }, { "IP_MULTICAST_LOOP", SOL_IP, IP_MULTICAST_LOOP }, #ifdef IP_ADD_MEMBERSHIP { "IP_ADD_MEMBERSHIP", SOL_IP, IP_ADD_MEMBERSHIP }, { "IP_DROP_MEMBERSHIP", SOL_IP, IP_DROP_MEMBERSHIP }, #endif { "TCP_MAXSEG", SOL_TCP, TCP_MAXSEG }, { "TCP_NODELAY", SOL_TCP, TCP_NODELAY }, #ifdef SO_REUSEPORT { "SO_REUSEPORT", SOL_SOCKET, SO_REUSEPORT }, #endif I created a TcpService on port zero, the listening socket gets a port and all seems reasonably well until I later inspect a few aspects of the TcpService, at which point the vm crashes. > > Bill More details required about the crashes? Whatever crashes mean. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com<mailto:johnmci@smalltalkconsulting.com>> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com =========================================================================== _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 3, 2009

Re: [Pharo-project] Server sockets, ephermal ports, and a Linux VM crash

by Mariano Martinez Peck

Bill: As always, it would help if you can give us/them more information. For example, running Pharo from command line and send the output of the command line. Or the PharoDebug.log or whatever other thing that may help. Best mariano 2009/11/3 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> > John, > > By crash, I mean pretty much the standard thing: one instant, Pharo is > running, click something on the inspector, and suddenly Pharo is gone. Not > good. > > Bill > > > > ------------------------------ > *From:* pharo-project-bounces(a)lists.gforge.inria.fr [mailto: > pharo-project-bounces(a)lists.gforge.inria.fr] *On Behalf Of *John McIntosh > *Sent:* Monday, November 02, 2009 9:43 PM > *To:* Pharo-project(a)lists.gforge.inria.fr > *Subject:* Re: [Pharo-project] Server sockets, ephermal ports, and a Linux > VM crash > > > > On Mon, Nov 2, 2009 at 5:52 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> 2009/11/2 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: >> >> > A nice trick is to use "ephmeral" ports, which is a fancy way of saying >> to pass zero for the listening port and let the OS assign a port. >> > > OS-X assigns you the range 49152-65535 > > As for the getOption, the values for the key and the results is platform > specific, and likely operating system version specific too. However for > platforms that use BSD sockets, ala (Unix/Linux/OS-X) then the keys are in > this table. Obviously if you fiddle with them then you know what you are > doing? > > > { "SO_DEBUG", SOL_SOCKET, SO_DEBUG }, > > { "SO_REUSEADDR", SOL_SOCKET, SO_REUSEADDR }, > > { "SO_DONTROUTE", SOL_SOCKET, SO_DONTROUTE }, > > { "SO_BROADCAST", SOL_SOCKET, SO_BROADCAST }, > > { "SO_SNDBUF", SOL_SOCKET, SO_SNDBUF }, > > { "SO_RCVBUF", SOL_SOCKET, SO_RCVBUF }, > > { "SO_KEEPALIVE", SOL_SOCKET, SO_KEEPALIVE }, > > { "SO_OOBINLINE", SOL_SOCKET, SO_OOBINLINE }, > > { "SO_LINGER", SOL_SOCKET, SO_LINGER }, > > { "IP_TTL", SOL_IP, IP_TTL }, > > { "IP_HDRINCL", SOL_IP, IP_HDRINCL }, > > { "IP_MULTICAST_IF", SOL_IP, IP_MULTICAST_IF }, > > { "IP_MULTICAST_TTL", SOL_IP, IP_MULTICAST_TTL }, > > { "IP_MULTICAST_LOOP", SOL_IP, IP_MULTICAST_LOOP }, > > #ifdef IP_ADD_MEMBERSHIP > > { "IP_ADD_MEMBERSHIP", SOL_IP, IP_ADD_MEMBERSHIP }, > > { "IP_DROP_MEMBERSHIP", SOL_IP, IP_DROP_MEMBERSHIP }, > > #endif > > { "TCP_MAXSEG", SOL_TCP, TCP_MAXSEG }, > > { "TCP_NODELAY", SOL_TCP, TCP_NODELAY }, > > #ifdef SO_REUSEPORT > > { "SO_REUSEPORT", SOL_SOCKET, SO_REUSEPORT }, > > #endif > > > I created a TcpService on port zero, the listening socket gets a port >> and all seems reasonably well until I later inspect a few aspects of the >> TcpService, at which point the vm crashes. >> > >> > Bill >> >> More details required about the crashes? Whatever crashes mean. > > > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 3, 2009

Re: [Pharo-project] Server sockets, ephermal ports, and a Linux VM crash

by Schwab,Wilhelm K

John, By crash, I mean pretty much the standard thing: one instant, Pharo is running, click something on the inspector, and suddenly Pharo is gone. Not good. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of John McIntosh Sent: Monday, November 02, 2009 9:43 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Server sockets, ephermal ports, and a Linux VM crash On Mon, Nov 2, 2009 at 5:52 PM, Igor Stasenko <siguctua(a)gmail.com<mailto:siguctua@gmail.com>> wrote: 2009/11/2 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu<mailto:bschwab@anest.ufl.edu>>: > A nice trick is to use "ephmeral" ports, which is a fancy way of saying to pass zero for the listening port and let the OS assign a port. OS-X assigns you the range 49152-65535 As for the getOption, the values for the key and the results is platform specific, and likely operating system version specific too. However for platforms that use BSD sockets, ala (Unix/Linux/OS-X) then the keys are in this table. Obviously if you fiddle with them then you know what you are doing? { "SO_DEBUG", SOL_SOCKET, SO_DEBUG }, { "SO_REUSEADDR", SOL_SOCKET, SO_REUSEADDR }, { "SO_DONTROUTE", SOL_SOCKET, SO_DONTROUTE }, { "SO_BROADCAST", SOL_SOCKET, SO_BROADCAST }, { "SO_SNDBUF", SOL_SOCKET, SO_SNDBUF }, { "SO_RCVBUF", SOL_SOCKET, SO_RCVBUF }, { "SO_KEEPALIVE", SOL_SOCKET, SO_KEEPALIVE }, { "SO_OOBINLINE", SOL_SOCKET, SO_OOBINLINE }, { "SO_LINGER", SOL_SOCKET, SO_LINGER }, { "IP_TTL", SOL_IP, IP_TTL }, { "IP_HDRINCL", SOL_IP, IP_HDRINCL }, { "IP_MULTICAST_IF", SOL_IP, IP_MULTICAST_IF }, { "IP_MULTICAST_TTL", SOL_IP, IP_MULTICAST_TTL }, { "IP_MULTICAST_LOOP", SOL_IP, IP_MULTICAST_LOOP }, #ifdef IP_ADD_MEMBERSHIP { "IP_ADD_MEMBERSHIP", SOL_IP, IP_ADD_MEMBERSHIP }, { "IP_DROP_MEMBERSHIP", SOL_IP, IP_DROP_MEMBERSHIP }, #endif { "TCP_MAXSEG", SOL_TCP, TCP_MAXSEG }, { "TCP_NODELAY", SOL_TCP, TCP_NODELAY }, #ifdef SO_REUSEPORT { "SO_REUSEPORT", SOL_SOCKET, SO_REUSEPORT }, #endif I created a TcpService on port zero, the listening socket gets a port and all seems reasonably well until I later inspect a few aspects of the TcpService, at which point the vm crashes. > > Bill More details required about the crashes? Whatever crashes mean. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com<mailto:johnmci@smalltalkconsulting.com>> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Nov. 3, 2009

Re: [Pharo-project] implementors and senders when there is only one result

by Mariano Martinez Peck

On Tue, Nov 3, 2009 at 12:14 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Mariano, > > I think that is not a good user interface choice, because I never know > what I will get before asking for it. > > What's more, the senders/implementors have a different functionality > than the browser (unfortunately), so I sometimes do want to search for > the senders of the sender, and if I get to a browser, I cannot do that. > > But in a broader context I do think that we badly need a cohesive > effort to rethink and rebuild the tool chain :). > Ok....I see your point. That's why I asked ;) Can we agree then, at least, this: Suppose I look for implementors of something. There is only ONE results. I click on the "browse" button and the class browsed is OBSelectorNode. I would like it to be the only one result. I mean, I would love no having to select the only one result in order to browse it. What do you think? > > Cheers, > Doru > > > On 3 Nov 2009, at 04:05, Mariano Martinez Peck wrote: > > > Hi folks, > > > > I would love that when I look for senders, implementors, senders, > > etc for something, if there is ONLY ONE result, the system browser > > is opened directly with the class/method I am searching, instead of > > the implementor, senders or reference windows with one only raw. > > > > What do you think? If you are agree I can open a ticket and mark it > > as milestone-1.1 > > > > Best > > > > Mariano > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 3, 2009

Re: [Pharo-project] implementors and senders when there is only one result

by Tudor Girba

Hi Mariano, I think that is not a good user interface choice, because I never know what I will get before asking for it. What's more, the senders/implementors have a different functionality than the browser (unfortunately), so I sometimes do want to search for the senders of the sender, and if I get to a browser, I cannot do that. But in a broader context I do think that we badly need a cohesive effort to rethink and rebuild the tool chain :). Cheers, Doru On 3 Nov 2009, at 04:05, Mariano Martinez Peck wrote: > Hi folks, > > I would love that when I look for senders, implementors, senders, > etc for something, if there is ONLY ONE result, the system browser > is opened directly with the class/method I am searching, instead of > the implementor, senders or reference windows with one only raw. > > What do you think? If you are agree I can open a ticket and mark it > as milestone-1.1 > > Best > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."

Nov. 3, 2009

[Pharo-project] implementors and senders when there is only one result

by Mariano Martinez Peck

Hi folks, I would love that when I look for senders, implementors, senders, etc for something, if there is ONLY ONE result, the system browser is opened directly with the class/method I am searching, instead of the implementor, senders or reference windows with one only raw. What do you think? If you are agree I can open a ticket and mark it as milestone-1.1 Best Mariano

Nov. 3, 2009

Re: [Pharo-project] Server sockets, ephermal ports, and a Linux VM crash

by John McIntosh

On Mon, Nov 2, 2009 at 5:52 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > 2009/11/2 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > > > A nice trick is to use "ephmeral" ports, which is a fancy way of saying > to pass zero for the listening port and let the OS assign a port. > OS-X assigns you the range 49152-65535 As for the getOption, the values for the key and the results is platform specific, and likely operating system version specific too. However for platforms that use BSD sockets, ala (Unix/Linux/OS-X) then the keys are in this table. Obviously if you fiddle with them then you know what you are doing? { "SO_DEBUG", SOL_SOCKET, SO_DEBUG }, { "SO_REUSEADDR", SOL_SOCKET, SO_REUSEADDR }, { "SO_DONTROUTE", SOL_SOCKET, SO_DONTROUTE }, { "SO_BROADCAST", SOL_SOCKET, SO_BROADCAST }, { "SO_SNDBUF", SOL_SOCKET, SO_SNDBUF }, { "SO_RCVBUF", SOL_SOCKET, SO_RCVBUF }, { "SO_KEEPALIVE", SOL_SOCKET, SO_KEEPALIVE }, { "SO_OOBINLINE", SOL_SOCKET, SO_OOBINLINE }, { "SO_LINGER", SOL_SOCKET, SO_LINGER }, { "IP_TTL", SOL_IP, IP_TTL }, { "IP_HDRINCL", SOL_IP, IP_HDRINCL }, { "IP_MULTICAST_IF", SOL_IP, IP_MULTICAST_IF }, { "IP_MULTICAST_TTL", SOL_IP, IP_MULTICAST_TTL }, { "IP_MULTICAST_LOOP", SOL_IP, IP_MULTICAST_LOOP }, #ifdef IP_ADD_MEMBERSHIP { "IP_ADD_MEMBERSHIP", SOL_IP, IP_ADD_MEMBERSHIP }, { "IP_DROP_MEMBERSHIP", SOL_IP, IP_DROP_MEMBERSHIP }, #endif { "TCP_MAXSEG", SOL_TCP, TCP_MAXSEG }, { "TCP_NODELAY", SOL_TCP, TCP_NODELAY }, #ifdef SO_REUSEPORT { "SO_REUSEPORT", SOL_SOCKET, SO_REUSEPORT }, #endif I created a TcpService on port zero, the listening socket gets a port and > all seems reasonably well until I later inspect a few aspects of the > TcpService, at which point the vm crashes. > > > > Bill > > More details required about the crashes? Whatever crashes mean. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Nov. 3, 2009