- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 1.3] #13213

by StÃ©phane Ducasse

;) On May 23, 2011, at 11:53 PM, Damien Cassou wrote: > On Mon, May 23, 2011 at 11:20 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> 13213 >> ----- >> >> - Issue 4263: Refactor in DialogWindow to add isResizeable as an instance variable. Thanks Benjamin van ryseghem. >> http://code.google.com/p/pharo/issues/detail?id=4263 >> >> - Issue 4264: Adding Object>>log: to prepare Transcript show: extermination. STef the wild butcher. >> http://code.google.com/p/pharo/issues/detail?id=4264 >> >> - Issue 4262: Fixed checksForSlips manipulating strings and pretending they are methodReferences... >> http://code.google.com/p/pharo/issues/detail?id=4262 > > - Adding issue URL after each resolved issue item in the release > message. Thanks Stef :-) > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry >

May 24, 2011

Re: [Pharo-project] Tiling windows

by GastÃ³n Dall' Oglio

Laurent and corious :) I add some TasklistMorph behavior. With the open list (cmd-rigth or cmd-left): * cmd-up: maximize all windows * cmd-down: minimize all windows * cmd-b: apply SystemBrowser windows's filter * cmd-w: apply Worspace windows's filter * cmd-a: remove windows's filter ** The cmd-b work in 1.2.1, in 1.3 you have to change TasklistMorph>>keyStroke: because I use OBSystemBrowser class by way of example and therefore does not perform properly filtered. 2011/5/23 laurent laffont <laurent.laffont(a)gmail.com> > 2011/5/23 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > >> Laurent, I attached a package I've added some improvements to your work, I >> have found useful. Of course I am not knowledgeable about morph, just added >> some and perhaps can serve as inspiration. >> > > Thanks GastÃ³n, I like the idea. It will be a good step forward in having > better window management. Now we should rewrite this clean + tests (may be > adding the notion of widgets like in KDE / Gnome). > > As windows fill all the space, would be good to have a button to open the > world menu. > > I would love having the possibility of splitting the World + back and > forward configuration like Emacs winner mode, keyboard driven. > > Since several days I use http://most-advantageous.com/optimal-layout/ on > OSX and there's some great ideas too. > > Laurent. > > >> >> 2011/5/23 laurent laffont <laurent.laffont(a)gmail.com> >> >>> On 1.2: >>> >>> Gofer it >>> squeaksource: 'LaurentLSandbox'; >>> version: 'Polymorph-Widgets-LaurentLaffont.388'; >>> load. >>> >>> >>> Then open or move a window so the TaskBar is updated and you have a new >>> "magic" button on bottom left. >>> >>> (note this is hacky actually, I will write a nicer version this week if >>> people like it). >>> >>> Laurent. >>> >>> On Mon, May 23, 2011 at 9:06 AM, StÃ©phane Ducasse < >>> stephane.ducasse(a)inria.fr> wrote: >>> >>>> send a cs that we can play with it :) >>>> >>>> On May 22, 2011, at 8:25 PM, laurent laffont wrote: >>>> >>>> > Hi, >>>> > >>>> > what do you think of adding this in Pharo ? >>>> > >>>> > |taskbar tileWindowsBlock| >>>> > >>>> > tileWindowsBlock := [ >>>> > |windows numberOfColumns numberOfRows windowWidth windowHeight| >>>> > windows := (World submorphs select: [:m| m isSystemWindow and: [m >>>> isNotMinimized]]) asOrderedCollection. >>>> > numberOfColumns := windows size sqrtFloor. >>>> > numberOfRows := (windows size / numberOfColumns) rounded. >>>> > windowWidth := World width // numberOfColumns.. >>>> > windowHeight := World height - taskbar height // numberOfRows. >>>> > >>>> > Matrix >>>> > rows: numberOfRows >>>> > columns: numberOfColumns >>>> > tabulate: [:row :column| |window| >>>> > windows ifNotEmpty: [ >>>> > window := windows remove: windows first. >>>> > window >>>> > bounds: ( >>>> > ((column - 1 * windowWidth) @ (row - 1 * >>>> windowHeight)) >>>> > extent: (windowWidth) @ windowHeight) >>>> > ] >>>> > ] >>>> > ]. >>>> > >>>> > >>>> > taskbar := (World submorphs detect: [:m| m isTaskbar]). >>>> > >>>> > taskbar >>>> > addMorph: (IconicButton new >>>> > target: tileWindowsBlock; >>>> > actionSelector: #value; >>>> > labelGraphic: taskbar theme smallWindowIcon; >>>> > color: Color transparent; >>>> > yourself). >>>> > >>>> > >>>> > Laurent Laffont - @lolgzs >>>> > >>>> > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >>>> > Blog: http://magaloma.blogspot.com/ >>>> > Developer group: http://cara74.seasidehosting.st >>>> > >>>> >>>> >>>> >>> >> >

May 24, 2011

Re: [Pharo-project] [Ann] Ephemerons for Cog

by Eliot Miranda

On Mon, May 23, 2011 at 5:47 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > What is Ephemerons? > Smart associations that can be used to implement per-object finalization. An ephemeron holds onto some object via its key field in a quasi-weak manner such that the garbage collector will only consider the key live if it can be reached from the roots and not reachable by the ephemeron's other inst vars. If the only references to objects referred to by ephemeron keys are through the other fields of ephemerons with otherwise unreachable keys then the these objects are collectable. The garbage collector works in two phases. First it traces all objects from the roots, topping the trace at any ephemeron whose key is unreachable. The second phase then loops until a fixed point is reached; all ephemerons with unreachable keys are added to the finalization queue and the objects reachable from the key and the ephemeron's other fields are traced. Any ephemerons with unreached keys are added to the finalization queue. This phase continues until no more ephemerons are found. Then, if the finalization queue is non-empty, the GC signals the rest of the system that there are finalizable ephemerons. The image then takes over, drain ing the ephemerons in the queue and sending e.g. mourn to each ephemeron which can then send finalize to its key and remove itself from any dictionaries in which it exists, allowing it and its key to be garbage-collected after finalization. What's the rationale? Often one wants to associate state with finalizable objects, such that that state refers back to the finalizable obejcts. The classic examples are views in MVC. RThe views are dependents of some model and we may want want the model to be finalized when no object (including dependents) refer to the model. But we don't want references from the dependents to keep the object alive. But if the dependents are stored in some global dictionary from model to sequence of dependents then the reference from the global dictionary keeps both the model and the dependents alive. If we replace the association with a weak key association then the references from the dependents back to the model keep the model alive. But with ephemerons there is an implicit switch, implemented by the GC, that causes the system to exclude references from the transitive closure of the dependents unless the model is reachable from the roots, excluding references from ephemeron keys. So ephemerons provide a mechanism for providing per-instance finalization and property lists (dependents being a special case of property list). They allow the system to detect when an object is reachable from the roots, excluding an arbitrary set of references (reachable from an ephemeron's other fields) which do not count towards an object being considered live. They allow for finalization to be managed by the system, above the VM, while the VM's job is just to determine reachability and liveness. make sense? clear as mud? best, Eliot > Alexandre > > > > Le 23 mai 2011 Ã 20:43, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : > > > I felt a bit hacky today and decided to implement Ephemerons. > > > > I tried to run it on both StackVM and Cog VMs, > > it seems to work fine (at least all 4 tests, which my brain were > > capable to produce, are green. ;) > > > > > > You can find the VM code on SqS/VMMaker in package: > > VMMaker-oscog-IgorStasenko.67 > > > > Also, i created a separate issue on Cog issue tracker to track it. > > http://code.google.com/p/cog/issues/detail?id=44 > > > > The implementation may contain a bugs. So, it needs review and testing. > > Now i would like all interested parties to give a feedback and help > > integrating it into our production images. > > > > -- > > Best regards, > > Igor Stasenko AKA sig. > > > >

May 24, 2011

Re: [Pharo-project] [Ann] Ephemerons for Cog

by Alexandre Bergel

What is Ephemerons? Alexandre Le 23 mai 2011 Ã 20:43, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : > I felt a bit hacky today and decided to implement Ephemerons. > > I tried to run it on both StackVM and Cog VMs, > it seems to work fine (at least all 4 tests, which my brain were > capable to produce, are green. ;) > > > You can find the VM code on SqS/VMMaker in package: > VMMaker-oscog-IgorStasenko.67 > > Also, i created a separate issue on Cog issue tracker to track it. > http://code.google.com/p/cog/issues/detail?id=44 > > The implementation may contain a bugs. So, it needs review and testing. > Now i would like all interested parties to give a feedback and help > integrating it into our production images. > > -- > Best regards, > Igor Stasenko AKA sig. >

May 24, 2011

[Pharo-project] [Ann] Ephemerons for Cog

by Igor Stasenko

I felt a bit hacky today and decided to implement Ephemerons. I tried to run it on both StackVM and Cog VMs, it seems to work fine (at least all 4 tests, which my brain were capable to produce, are green. ;) You can find the VM code on SqS/VMMaker in package: VMMaker-oscog-IgorStasenko.67 Also, i created a separate issue on Cog issue tracker to track it. http://code.google.com/p/cog/issues/detail?id=44 The implementation may contain a bugs. So, it needs review and testing. Now i would like all interested parties to give a feedback and help integrating it into our production images. -- Best regards, Igor Stasenko AKA sig.

May 24, 2011

Re: [Pharo-project] [update 1.3] #13213

by Damien Cassou

On Mon, May 23, 2011 at 11:20 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 13213 > ----- > > - Issue 4263: Â Refactor in DialogWindow to add isResizeable as an instance variable. Thanks Benjamin van ryseghem. > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4263 > > - Issue 4264: Â Adding Object>>log: to prepare Transcript show: extermination. STef the wild butcher. > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4264 > > - Issue 4262: Â Fixed checksForSlips manipulating strings and pretending they are methodReferences... > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4262 - Adding issue URL after each resolved issue item in the release message. Thanks Stef :-) -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

May 23, 2011

[Pharo-project] [update 1.3] #13213

by StÃ©phane Ducasse

13213 ----- - Issue 4263: Refactor in DialogWindow to add isResizeable as an instance variable. Thanks Benjamin van ryseghem. http://code.google.com/p/pharo/issues/detail?id=4263 - Issue 4264: Adding Object>>log: to prepare Transcript show: extermination. STef the wild butcher. http://code.google.com/p/pharo/issues/detail?id=4264 - Issue 4262: Fixed checksForSlips manipulating strings and pretending they are methodReferences... http://code.google.com/p/pharo/issues/detail?id=4262 Stef

May 23, 2011

Re: [Pharo-project] SqueakDBX and MacOS X

by Mariano Martinez Peck

Thanks Olivier. It as a great apport :) I have just updated the website. On Mon, May 23, 2011 at 9:15 PM, Olivier Auverlot < olivier.auverlot(a)gmail.com> wrote: > Le 23/05/11 21:05, Mariano Martinez Peck a Ã©crit : > > I have created an archive with the libraries for MysqL 5.1 and >> PostgreSQL. You can download it at >> http://www.auverlot.fr/squeakdbx/squeackDBXlibclients.zip >> >> > Thanks. Good idea. But "The system cannot find the file specified. " > > > ooops ! sorry :-( > > http://www.auverlot.fr/squeakdbx/squeakDBXlibclients.zip > > Olivier ;-) > www.auverlot.fr > -- Mariano http://marianopeck.wordpress.com

May 23, 2011

Re: [Pharo-project] paragraph replacement?

by StÃ©phane Ducasse

Yes this would be good because I was always sad to remove it. Now this is not sure that we need the TextURL Stef >> Hi, >> >> Yes, it triggers the hyperlinks, but the method is not implemented and I could not find it in older images either. That is why I asked if someone knows how should the method behave. > > > In older images (1.2), there is an #actOnClickFor: on the TextAction Hierarchy. > > TextDoit does for example: > > actOnClickFor: anObject > "Note: evalString gets evaluated IN THE CONTEXT OF anObject > -- meaning that self and all instVars are accessible" > Compiler evaluate: evalString for: anObject logged: false. > ^ true > > > It seems the interface was extended to send the editor instance and the paragraph to the Link, so that > a link could e.g. change what is displayed. > > What kind of TextAction do you have? > > You could just implement there whatever action makes sense (ignoring the editor and paragraph parameter > and do exactly what #actOnClickFor: did in the old ST80 Paragraph). > > The whole TextAction stuff needs a pass... maybe with Moose as a Client, we can do that pass... > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

May 23, 2011

Re: [Pharo-project] Tiling windows

by Mariano Martinez Peck

Yes Gaston, don't worry ;) I didn't have any useful in the image. I just warned in case some other folks do. 2011/5/23 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > Sorry Mariano, I omitted to say that I tried this on a one-click image > 1.2.1, but still is not the code so try to share with you but the idea of > separating the types of windows, which I found very useful when I have many > windows. > > 2011/5/23 Mariano Martinez Peck <marianopeck(a)gmail.com> > >> Be careful, in 1.3 it hangs my image and I was forced to kill it. >> >> 2011/5/23 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> >> >>> Laurent, I attached a package I've added some improvements to your work, >>> I have found useful. Of course I am not knowledgeable about morph, just >>> added some and perhaps can serve as inspiration. >>> >>> >>> 2011/5/23 laurent laffont <laurent.laffont(a)gmail.com> >>> >>>> On 1.2: >>>> >>>> Gofer it >>>> squeaksource: 'LaurentLSandbox'; >>>> version: 'Polymorph-Widgets-LaurentLaffont.388'; >>>> load. >>>> >>>> >>>> Then open or move a window so the TaskBar is updated and you have a new >>>> "magic" button on bottom left. >>>> >>>> (note this is hacky actually, I will write a nicer version this week if >>>> people like it). >>>> >>>> Laurent. >>>> >>>> On Mon, May 23, 2011 at 9:06 AM, StÃ©phane Ducasse < >>>> stephane.ducasse(a)inria.fr> wrote: >>>> >>>>> send a cs that we can play with it :) >>>>> >>>>> On May 22, 2011, at 8:25 PM, laurent laffont wrote: >>>>> >>>>> > Hi, >>>>> > >>>>> > what do you think of adding this in Pharo ? >>>>> > >>>>> > |taskbar tileWindowsBlock| >>>>> > >>>>> > tileWindowsBlock := [ >>>>> > |windows numberOfColumns numberOfRows windowWidth windowHeight| >>>>> > windows := (World submorphs select: [:m| m isSystemWindow and: [m >>>>> isNotMinimized]]) asOrderedCollection. >>>>> > numberOfColumns := windows size sqrtFloor. >>>>> > numberOfRows := (windows size / numberOfColumns) rounded. >>>>> > windowWidth := World width // numberOfColumns.. >>>>> > windowHeight := World height - taskbar height // numberOfRows. >>>>> > >>>>> > Matrix >>>>> > rows: numberOfRows >>>>> > columns: numberOfColumns >>>>> > tabulate: [:row :column| |window| >>>>> > windows ifNotEmpty: [ >>>>> > window := windows remove: windows first. >>>>> > window >>>>> > bounds: ( >>>>> > ((column - 1 * windowWidth) @ (row - 1 * >>>>> windowHeight)) >>>>> > extent: (windowWidth) @ windowHeight) >>>>> > ] >>>>> > ] >>>>> > ]. >>>>> > >>>>> > >>>>> > taskbar := (World submorphs detect: [:m| m isTaskbar]). >>>>> > >>>>> > taskbar >>>>> > addMorph: (IconicButton new >>>>> > target: tileWindowsBlock; >>>>> > actionSelector: #value; >>>>> > labelGraphic: taskbar theme smallWindowIcon; >>>>> > color: Color transparent; >>>>> > yourself). >>>>> > >>>>> > >>>>> > Laurent Laffont - @lolgzs >>>>> > >>>>> > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >>>>> > Blog: http://magaloma.blogspot.com/ >>>>> > Developer group: http://cara74.seasidehosting.st >>>>> > >>>>> >>>>> >>>>> >>>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > -- Mariano http://marianopeck.wordpress.com

May 23, 2011