February 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3659 in pharo: Task bar appearance does not make sense

by pharo＠googlecode.com

Updates: Status: Fixed Comment #10 on issue 3659 by stephane...(a)gmail.com: Task bar appearance does not make sense http://code.google.com/p/pharo/issues/detail?id=3659 so what should I do? Is is specific to glamour?

Feb. 9, 2011

Re: [Pharo-project] Issue 3659 in pharo: Task bar appearance does not make sense

by pharo＠googlecode.com

Updates: Labels: Milestone-1.2 Comment #9 on issue 3659 by tudor.gi...(a)gmail.com: Task bar appearance does not make sense http://code.google.com/p/pharo/issues/detail?id=3659 I tried it now. It looks like I would have wanted it from the beginning :)

Feb. 9, 2011

Re: [Pharo-project] Issue 3687 in pharo: Browse senders/implementors in Omnibrowser/OB pops up menu that doesn't respond to enter/CR

by pharo＠googlecode.com

Updates: Status: Fixed Cc: guillermopolito Labels: Type-OB Comment #2 on issue 3687 by stephane...(a)gmail.com: Browse senders/implementors in Omnibrowser/OB pops up menu that doesn't respond to enter/CR http://code.google.com/p/pharo/issues/detail?id=3687 Thanks nick!!! Did you sign the license agreement? OB maintainers can you integrate this fix?

Feb. 9, 2011

Re: [Pharo-project] [COTDC] 5 - PseudoFileStream

by Nicolas Cellier

Oh, sorry, the name is worse than I could remember: RWBinaryOrTextStream What else ? Nicolas 2011/2/9 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > Whether used or not, anything under ReadWriteTextStream hierarchy > should be refactored then deprecated. > The name already tells : I could be a read stream a write stream, a > text stream, what else ? > I suggest to first rename it ReadWriteTextStreamWhatElse. > Then to provide a good comment: > This class was detected, selected, infected, neglected, deprecated > then rejected. > > ;) > > cheers > > 2011/2/9 Guillermo Polito <guillermopolito(a)gmail.com>: >> Okok >> http://code.google.com/p/pharo/issues/detail?id=3686 >> Open issue to *deprecate* it :P. >> >> On Tue, Feb 8, 2011 at 8:06 PM, <csrabak(a)bol.com.br> wrote: >>> >>> Â "If you can't comment and can't find references to it in {core,dev}? >>> image, then remove it!" >>> >>> >>> >>> Em 08/02/2011 19:11, laurent laffont < laurent.laffont(a)gmail.com > >>> escreveu: >>> Time to add >>> >>> COTDC rule #2: If you can't comment it, remove it. >>> >>> Indeed it's compatible with the goal: each day, one less not commented >>> class ! >>> >>> Laurent >>> >>> >>> >>> On Tue, Feb 8, 2011 at 10:01 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>> >>> PseudoFileStream ... >>> Â may be we could remove it :) >>> >>> Â Stef >>> >>> >>> >>> >>> Â On Feb 8, 2011, at 5:39 PM, laurent laffont wrote: >>> >>> Â > Today: PseudoFileStream >>> Â > >>> Â > Comment Of The Day Contest - One Day One Comment >>> Â > Rules: Each day a not commented class is elected. Each day the best >>> comment will be integrated with name of the author(s). >>> Â > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >>> Â > >>> Â > Laurent >>> Â > >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >> >

Feb. 9, 2011

Re: [Pharo-project] [COTDC] 5 - PseudoFileStream

by Nicolas Cellier

Whether used or not, anything under ReadWriteTextStream hierarchy should be refactored then deprecated. The name already tells : I could be a read stream a write stream, a text stream, what else ? I suggest to first rename it ReadWriteTextStreamWhatElse. Then to provide a good comment: This class was detected, selected, infected, neglected, deprecated then rejected. ;) cheers 2011/2/9 Guillermo Polito <guillermopolito(a)gmail.com>: > Okok > http://code.google.com/p/pharo/issues/detail?id=3686 > Open issue to *deprecate* it :P. > > On Tue, Feb 8, 2011 at 8:06 PM, <csrabak(a)bol.com.br> wrote: >> >> Â "If you can't comment and can't find references to it in {core,dev}? >> image, then remove it!" >> >> >> >> Em 08/02/2011 19:11, laurent laffont < laurent.laffont(a)gmail.com > >> escreveu: >> Time to add >> >> COTDC rule #2: If you can't comment it, remove it. >> >> Indeed it's compatible with the goal: each day, one less not commented >> class ! >> >> Laurent >> >> >> >> On Tue, Feb 8, 2011 at 10:01 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >> >> PseudoFileStream ... >> Â may be we could remove it :) >> >> Â Stef >> >> >> >> >> Â On Feb 8, 2011, at 5:39 PM, laurent laffont wrote: >> >> Â > Today: PseudoFileStream >> Â > >> Â > Comment Of The Day Contest - One Day One Comment >> Â > Rules: Each day a not commented class is elected. Each day the best >> comment will be integrated with name of the author(s). >> Â > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >> Â > >> Â > Laurent >> Â > >> >> >> >> >> >> >> >> >> >> >> > >

Feb. 9, 2011

Re: [Pharo-project] Issue 3687 in pharo: Browse senders/implementors in Omnibrowser/OB pops up menu that doesn't respond to enter/CR

by pharo＠googlecode.com

Comment #1 on issue 3687 by ncalexan...(a)gmail.com: Browse senders/implementors in Omnibrowser/OB pops up menu that doesn't respond to enter/CR http://code.google.com/p/pharo/issues/detail?id=3687 In PharoInbox: SLICE-Issue-3687-Browse-senders-implementors-in-Omnibrowser-OB-pops-up-menu-that-doesnt-respond-to-enter-CR-NickAlexander.2 Hopefully I cut the slice correctly this time.

Feb. 9, 2011

[Pharo-project] Issue 3687 in pharo: Browse senders/implementors in Omnibrowser/OB pops up menu that doesn't respond to enter/CR

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3687 by ncalexan...(a)gmail.com: Browse senders/implementors in Omnibrowser/OB pops up menu that doesn't respond to enter/CR http://code.google.com/p/pharo/issues/detail?id=3687 Pharo image: Pharo Pharo core version: <12327> Class browser used (if applicable): <OBSystemBrowserAdaptor> Steps to reproduce: 1. open OB 2. select method in right-most pane 3. type Cmd-N for senders or Cmd-M for implementors 4. try to accept default in menu by hitting enter This is pretty bad for keyboard navigation.

Feb. 9, 2011

Re: [Pharo-project] Status of Alien

by Eliot Miranda

On Tue, Feb 8, 2011 at 7:01 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Eliot, > > I'm impressed :) To say that I truly understand would be dishonest, but I > think I more or less get it. How is the binding of a Process to a thread > done - I guess I am really asking what it looks like in code? One choice > would be class side messages to ProcessScheduler or similar that return > handles to or wrappers for the threads (#gui and #newThread come to mind), > and those could be provided to a new process to bind it. Am I close? > There's an instance variable in Process, threadId, that is nil (unbound) or holds the threadId of the thread it can run on. There is one primitive to bind it to the current thread and one to unbind. It is unsafe to manipulate the threadId inst var directly. > It sounds like a really nice solution to the problem. > The overall scheme or the thread-to-process mapping? best, Eliot > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [ > pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Eliot Miranda [ > eliot.miranda(a)gmail.com] > Sent: Tuesday, February 08, 2011 8:57 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Status of Alien > > On Tue, Feb 8, 2011 at 5:45 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu > <mailto:bschwab@anest.ufl.edu>> wrote: > Eliot, > > No lack of patience implied: just mentioning some things that I have picked > up as off in the future and that would make us all stronger. > > Re the calls on OS threads, that is GREAT news. What strategy are you > using to assign calls to the threads? I ask because there is a tradeoff > between using a pool and taking what is ready to go, and coping with thread > affinity. Example: OpenSSL is "easy" to call if one uses blocking calls and > simply moves them out of the main thread (at least it worked for me on > Dolphin). When I did this, I had to write a wrapper DLL to combined calls > (connect, read, send, etc.) and checks for error status because otherwise, > Dolphin would typically use different threads for the calls and the error > test call was meaningless. IIRC, now they always use the same OS thread for > any given Smalltalk Process - I think. > > There is no pool. Instead, arbitrary threads can run the VM, but only one > at a time. So the strategy to control calls is to decide which processes > are bound to which threads. A new Smalltalk process can be executed by any > thread. There is a well-known thread id for "the GUI thread" and it may be > necessary to have more. So to arrange that a call is made on the GUI thread > one arranges that the cal is made from a Smalltalk process that is bound to > the GUI thread. To arrange that calls are made form some specific thread > once again one binds one or more processes to that thread and makes calls > from those processes. The VM's Smalltalk scheduler is modified to do a > thread switch when a process switch is made to a process bound to other than > the current thread (i.e. it is now a classic two-level scheduler). Hence > scheduling semantics don't change; it is still a real-time scheduler that > always runs the highest-priority runnable Smalltalk process. Its just that > under the covers an implicit thread switch might also occur when a process > switch occurs. Make sense? > > best > Eliot > > > > I fixed a few more things that have been pinning me to my hacked vms, so I > will hopefully be able to more easily experiment. I will look around for > Alien on Linux and give it a try if I find it. I am also looking forward to > running my "real" images through Cog. > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto: > pharo-project-bounces(a)lists.gforge.inria.fr> [ > pharo-project-bounces(a)lists.gforge.inria.fr<mailto: > pharo-project-bounces(a)lists.gforge.inria.fr>] On Behalf Of Eliot Miranda [ > eliot.miranda(a)gmail.com<mailto:eliot.miranda@gmail.com>] > Sent: Tuesday, February 08, 2011 11:19 AM > To: Pharo-project(a)lists.gforge.inria.fr<mailto: > Pharo-project(a)lists.gforge.inria.fr> > Cc: Squeak Virtual Machine Development Discussion > Subject: Re: [Pharo-project] Status of Alien > > On Tue, Feb 8, 2011 at 4:16 AM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu > <mailto:bschwab@anest.ufl.edu><mailto:bschwab@anest.ufl.edu<mailto: > bschwab(a)anest.ufl.edu>>> wrote: > Torsten, > > I have been under the impression that it has never worked on Linux - it > would be great to be wrong on that. Does anyone have Alien on Linux waiting > for someone to try it? > > I would be very surprised if it didn't work. We at least use the data > manipulation side of things routinely at Teleplace. > > > One thing slowing my search for FFI/Alien improvements has been that I was > initially dependent on some vm modifications that I made. Some off-line > correspondence with Dave Lewis and the benefit of some time might have > yielded a solution that will let me return to stock vms. > > I need to integrate my new callback support and the ReentrantFFIPlugin into > the standard interpreter as soon as possible. The ReentrantFFIPlugin > provides compatibility with the old squeak FFI plugin but also allows > aliens to be passed as arguments, at least to the extent of passing Alien > Callbacks. This means its possible to discard the Alien callout support and > use the FFI instead (but just to reiterate to keep the Alien data > representation and callback facilities). The project for the next few > weekends has to be harmonising the primitive set and functionality of Cog > and the standard interpreter now that the StackToRegisterMappingCogit looks > complete. > > > FFI has generally worked for me. I am doing a horrible job of handling > double arrays, but I am at least able to use them. My "solution" makes > assumptions about byte order and I have declare double* as void*. > > There was mention of extending FFI with callbacks. Given that capability, > the only thing missing would then to be make calls on OS threads to avoid > blocking the image (but blocking the calling Smalltalk Process for the > duration of the call). > > I have this in prototype and want to release soon. But there is too much > else going on right now. Patience please. > > best > Eliot > > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr<mailto: > pharo-project-bounces(a)lists.gforge.inria.fr><mailto: > pharo-project-bounces(a)lists.gforge.inria.fr<mailto: > pharo-project-bounces(a)lists.gforge.inria.fr>> [ > pharo-project-bounces(a)lists.gforge.inria.fr<mailto: > pharo-project-bounces(a)lists.gforge.inria.fr><mailto: > pharo-project-bounces(a)lists.gforge.inria.fr<mailto: > pharo-project-bounces(a)lists.gforge.inria.fr>>] On Behalf Of Torsten > Bergmann [astares(a)gmx.de<mailto:astares@gmx.de><mailto:astares@gmx.de > <mailto:astares@gmx.de>>] > Sent: Tuesday, February 08, 2011 4:04 AM > To: pharo-project(a)lists.gforge.inria.fr<mailto: > pharo-project(a)lists.gforge.inria.fr><mailto: > pharo-project(a)lists.gforge.inria.fr<mailto: > pharo-project(a)lists.gforge.inria.fr>> > Subject: [Pharo-project] Status of Alien > > What is the status of Alien. > According to > > http://bugs.squeak.org/view.php?id=7475 > > there is no one who confirmed it working on Linux. > > Any news here? Any ideas on FFI/Alien successor? > > Thanks > T. > -- > GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit > gratis Handy-Flat! http://portal.gmx.net/de/go/dsl > > > > > > >

Feb. 9, 2011

[Pharo-project] smalltalk color-print-style on a web page

by HwaJong Oh

I want to put smalltalk code with syntax coloring as it is http://code.google.com/p/pharo/wiki/CommentOfTheDayContest on my web page http://appdal.com/groups/36442/wiki/bbd28/Pharo_comment_of_the_day_contest.… Best Regards -- View this message in context: http://forum.world.st/smalltalk-color-print-style-on-a-web-page-tp3296588p3… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 9, 2011

Re: [Pharo-project] [COTDC] 5 - PseudoFileStream

by Guillermo Polito

Okok http://code.google.com/p/pharo/issues/detail?id=3686 <http://code.google.com/p/pharo/issues/detail?id=3686>Open issue to *deprecate* it :P. On Tue, Feb 8, 2011 at 8:06 PM, <csrabak(a)bol.com.br> wrote: > > "If you can't comment and can't find references to it in {core,dev}? > image, then remove it!" > > > > Em 08/02/2011 19:11, laurent laffont < laurent.laffont(a)gmail.com > > escreveu: > Time to add > > COTDC rule #2: If you can't comment it, remove it. > > Indeed it's compatible with the goal: each day, one less not commented > class ! > > Laurent > > > > On Tue, Feb 8, 2011 at 10:01 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > PseudoFileStream ... > may be we could remove it :) > > Stef > > > > > On Feb 8, 2011, at 5:39 PM, laurent laffont wrote: > > > Today: PseudoFileStream > > > > Comment Of The Day Contest - One Day One Comment > > Rules: Each day a not commented class is elected. Each day the best > comment will be integrated with name of the author(s). > > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > > > Laurent > > > > > > > > > > > > > >

Feb. 9, 2011