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

[Pharo-project] Bug Report: 3 of 6; Image freeze

by S Krish

3. Image Freeze: Anything that hits #fullBounds with a byteString instead of a Morph does not simply handle it... but freezes. This occurs with an external Table Morph Package that permits constructing a grid of morphs, but if you pass the 'string' instead of 'string' asMorph.. it takes it.. but when opening freezes similar to if we put a break point on Morph>>fullBounds/ processEvent:using: ... Alt . with an image that has Sound package loaded, causes a dialog for choosing a Sound Package that is all disabled and freezes the image

Jan. 3, 2012

[Pharo-project] Bug reports: 2 of 6:

by S Krish

2. bug with mouseUp not passing through for event handling with on:send:to: target... click all over the World and you will keep getting the dialog though you are not clicking the morph. #clickClient in MouseClickState holds the morph as the recipient morph for clicks.. rather than the modal dialog.. ( SimpleButtonMorph new extent: 80@60 ; label: 'test' ; on:#click send: #value to:[ UIManager default inform: 'test']; color: Color red) openInWorld.

Jan. 3, 2012

[Pharo-project] Bug reports: 1 of 6: Damaged Window/ rectangles on Screen

by S Krish

1. Damaged Window rectangle painting all over.. as you drag the window over the World.. * This is just the repeatable test, but occurs very annoyingly with an image if we have debugged through some piece of Morphic UI code.. Infact this damaged rectangles/ lost refresh of World occurs very frequently with ordinary non forked UI stuff also. of other variants viz: SystemWindow etc.. * Transcript if used on / or STranscript.. the World repaint many a times starts popping up its TextMorph through other top windows.. while it sends the transcript text to it. [ | dialog builder | builder := UITheme exampleBuilder. dialog := builder newPluggableDialogWindow: 'BasicTestDamagedWindows'. dialog contentMorph: (dialog newRow: {dialog newColumn: {dialog newColumn: {dialog newTextEntryFor: (ValueHolder new contents: 'text') getText: #contents setText: #contents: help: 'hostName'}}}); model: self. World openModal: dialog ] fork.

Jan. 3, 2012

Re: [Pharo-project] roadmap

by StÃ©phane Ducasse

>>> >>> Then my question is: How can anybody use Pharo that does not want to >>> use your changes of AST and FS? >> >> Normally we talk and we reach a consensus. > > The issue here is that FS was a separately maintained package that was (and apparently still is) loaded into different places. Adding the FS packages to Pharo amounts to a fork of FS. In hindsight, there should have been a discussion at that point. Apparently you did not browse enough the archive because it was mentioned and mentioned and mentioned and and mentioned again. We even stopped to fork it and published our changes to a common repository. instead of PharoTaskForces. > Is it possible to maintain FS as a separate package, yes now what would be the key reason? Did you ever see a smalltalk without its own file system? The same question goes for the compiler. Can OPAL work without its own AST? Now if you read carefully my emails you will see that the door is always open but so far I did not hear anything about possible collaboration and as its latin root probably indicate to collaborate we should be two willing to do it. Let us take a concrete example: Pinocchio for example developed a large set of registry allocation for assembly generation and other analysis. Pinocchio people released the code under MIT and camillo spent time to make sure that their analyses work on our system. So should we throw away this effort because we cannot add nodes to AST? Frankly? What I asked is a discussion and so far I did not get anything concrete. > and use it for Pharo core? I think the answer is yes, because it is possible to run without .sources and .changes files. Do you think that the system works without files? > IMHO, the right way forward is to make it a priority to build the "core" from PharoKernel, and the modularity everyone wants will be a natural outcome. Did you check the FS repository recently to see the changes we are talking about? May be this is not 100% published in fs but this is easy to do it :) Why somebody does not merge in both way? We spent time commenting the code that we do not know because they was no serious comments. damien improved some part, camillo spent some time to fix some other problems. Now the code is there so what? Stef

Jan. 3, 2012

Re: [Pharo-project] roadmap

by Yanni Chiu

On 02/01/12 2:58 PM, StÃ©phane Ducasse wrote: > > On Jan 2, 2012, at 8:42 PM, Lukas Renggli wrote: > >>> How can the core of pharo work with FS if FS is not loaded in Pharo? >> >> Then my question is: How can anybody use Pharo that does not want to >> use your changes of AST and FS? > > Normally we talk and we reach a consensus. The issue here is that FS was a separately maintained package that was (and apparently still is) loaded into different places. Adding the FS packages to Pharo amounts to a fork of FS. In hindsight, there should have been a discussion at that point. Is it possible to maintain FS as a separate package, and use it for Pharo core? I think the answer is yes, because it is possible to run without .sources and .changes files. IMHO, the right way forward is to make it a priority to build the "core" from PharoKernel, and the modularity everyone wants will be a natural outcome.

Jan. 3, 2012

Re: [Pharo-project] [ VM ]Smalltalk getSystemAttribute:

by Esteban Lorenzano

El 02/01/2012, a las 4:39p.m., David T. Lewis escribiÃ³: >> Real problem then is: >> >> we don't have a way to get the executable name >> >> or >> >> getSystemAttribute: comment is wrong :) >> > > On a unix VM, it answers the full path to the executable, which is > in agreement with the comment. For example: > > Smalltalk getSystemAttribute: 0 ==> '/usr/local/lib/squeak/4.7.18-2505/squeakvm' > > Maybe is is more complicated for Mac, but wasn't there some discussion > about it on vm-dev a while back? I don't remember :) so, how can we solve this? of course, it is not a problem to make getSystemAttribute: 0 answer argv[0], but that's not the expected behavior... we can be making a mistake, because it should answer vm path, no vm fullName. I can add a 10XX number to answer vm full name, but that will lead to consistency problems inside the image... I really don't know how to proceed :( Esteban

Jan. 2, 2012

Re: [Pharo-project] TWM bug when deleting a snapshot

by laurent laffont

Hi Sean, for my last day of vacation (sniff sniff) I've played with an idea of snapshot browser. From here you can browse and delete snapshot - with thumbnails ! Demo in this video (I've promised to not speak such bad english anymore but fail :( ) http://vimeo.com/34478511 It's an early prototype, available in last TWM, feel free to hack. Happy new year ! Laurent On Fri, Dec 30, 2011 at 4:15 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Most of it feels very natural to me. > > > laurent laffont wrote > > > > - go to S3. Then move some windows and delete. If automatically TWM > > restore > > last snapshot, we loose current state..... > > > If I delete a snapshot, I'm saying that the state is no longer interesting, > so that's what I would expect. > > > laurent laffont wrote > > > > Another idea is to have TWMWorldRecorder plugged to announcements so each > > time a window move / appear / disappear it creates automatically a > > snapshot.... > > > This could be interesting, but I think it would be another feature - "world > history" vs. "particular points I find interesting"; like browser history > vs. bookmarks > > -- > View this message in context: > http://forum.world.st/TWM-bug-when-deleting-a-snapshot-tp4243197p4245948.ht… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Jan. 2, 2012

[Pharo-project] [update 1.4] #14277

by stephane ducasse

14277 ----- - Issue 5143: Replacing Monitor with Semaphore in Announcer. Thanks Igor Stasenko and StÃ©phane Ducasse. http://code.google.com/p/pharo/issues/detail?id=5143 - Issue 5140: Some cleanup of unused (but defined) stuff. Thanks Igor Stasenko and StÃ©phane Ducasse. http://code.google.com/p/pharo/issues/detail?id=5140 - Issue 5138: Remove TextConstants from Array. Thanks Igor Stasenko and StÃ©phane Ducasse. http://code.google.com/p/pharo/issues/detail?id=5138 - Issue 5134: Comment of Collection>>#reduce: http://code.google.com/p/pharo/issues/detail?id=5134 - Issue 5098: Settings browser wants to repeatedly safe changes. Thanks Alain Plantec http://code.google.com/p/pharo/issues/detail?id=5098 - Issue 5098: Settings browser wants to repeatedly safe changes. Thanks Alain Plantec http://code.google.com/p/pharo/issues/detail?id=5098 - Issue 5099: Regexp button in settings browser is slow. Thanks Alain Plantec http://code.google.com/p/pharo/issues/detail?id=5099 Stef

Jan. 2, 2012

Re: [Pharo-project] roadmap

by StÃ©phane Ducasse

>> >> >>> - Announcements-*: A big problem, but simple enough to work around. >>> - FileSystem-*: A big problem, the method renaming make it impossible >>> to use it with any code that depends on the official version. >> >> How can the core of pharo work with FS if FS is not loaded in Pharo? > > Then my question is: How can anybody use Pharo that does not want to > use your changes of AST and FS? For your information we will use FS in the core and AST is used by OPAL. And OPAL should be our new compiler. Now I will stop replying to such emails because I should work too.

Jan. 2, 2012

Re: [Pharo-project] About announcements

by Lukas Renggli

>> Now for me you don't need to change the semantics of the Pharo >> Announcements again. Now for my code I will just use my own >> implementation that has exactly the behavior and performance >> characteristics I need. > > Lukas our state of mind is that we want the infrastructure gets better so we like to change > for a better one if this better one is better. Seems that the understanding of what is better/worse and what is progress/regress is rather different among people. > If everybody has its own version then we do not improve the infrastructure. Performance issues aside, the current implementation forces me to use a different implementation because Pharo's announcements have a different implementation of selecting the handler (point 7). However, the really weird thing is that Pharo's announcements are now suddenly inconsistent with the Pharo exceptions and how they select the handler. Do you think this is better or worse? Lukas -- Lukas Renggli www.lukas-renggli.ch

Jan. 2, 2012