July 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Does anyone use menuMorph in dockingbar?

by Peter UhnÃ¡k

Isn't DockingBar a Squeak thing? The little tabs things that would live around the edges of the screen and you could grab morphs onto a canvas. On Fri, Jul 25, 2014 at 2:06 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > No idea what this could be. > go go go! > > Alexandre > > > On Jul 24, 2014, at 4:39 PM, stepharo <stepharo(a)free.fr> wrote: > > > Hi guys > > > > the code of MenuMorph is crippled of isInDockingBar and the logic is > much more complex. > > I have the impression that it is decades since we got a menu in a > docking bar. I do not even remember > > what it mean. I would like to clean this part because we should really > be a bit more radical else we will die under > > the mass of complex, old.... code. > > > > Stef > > > > looks like a dockingbar is this > > > > DockingBarMorph new > > addMorph: (SimpleButtonMorph new > > label: 'Say hello'; > > target: [UIManager inform: > 'Hello']; > > actionSelector: #value); > > addMorph: (SimpleButtonMorph new > > label: 'Say bonjour'; > > target: [UIManager inform: > 'Bonjour']; > > actionSelector: #value); > > addMorph: (SimpleButtonMorph new > > label: 'Close'; > > target: [DockingBarMorph > allInstances last delete]; > > actionSelector: #value); > > adhereToBottom; > > openInWorld. > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

July 25, 2014

Re: [Pharo-dev] Does anyone use menuMorph in dockingbar?

by Alexandre Bergel

No idea what this could be. go go go! Alexandre On Jul 24, 2014, at 4:39 PM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > the code of MenuMorph is crippled of isInDockingBar and the logic is much more complex. > I have the impression that it is decades since we got a menu in a docking bar. I do not even remember > what it mean. I would like to clean this part because we should really be a bit more radical else we will die under > the mass of complex, old.... code. > > Stef > > looks like a dockingbar is this > > DockingBarMorph new > addMorph: (SimpleButtonMorph new > label: 'Say hello'; > target: [UIManager inform: 'Hello']; > actionSelector: #value); > addMorph: (SimpleButtonMorph new > label: 'Say bonjour'; > target: [UIManager inform: 'Bonjour']; > actionSelector: #value); > addMorph: (SimpleButtonMorph new > label: 'Close'; > target: [DockingBarMorph allInstances last delete]; > actionSelector: #value); > adhereToBottom; > openInWorld. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 25, 2014

Does anyone use menuMorph in dockingbar?

by stepharo

Hi guys the code of MenuMorph is crippled of isInDockingBar and the logic is much more complex. I have the impression that it is decades since we got a menu in a docking bar. I do not even remember what it mean. I would like to clean this part because we should really be a bit more radical else we will die under the mass of complex, old.... code. Stef looks like a dockingbar is this DockingBarMorph new addMorph: (SimpleButtonMorph new label: 'Say hello'; target: [UIManager inform: 'Hello']; actionSelector: #value); addMorph: (SimpleButtonMorph new label: 'Say bonjour'; target: [UIManager inform: 'Bonjour']; actionSelector: #value); addMorph: (SimpleButtonMorph new label: 'Close'; target: [DockingBarMorph allInstances last delete]; actionSelector: #value); adhereToBottom; openInWorld.

July 24, 2014

New CogVMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3056/. CogVM binaries as per VMMaker.oscog-eem.832/r3056 Add the time zone to the version info on Mac OS X and Win32. Fix bug in assigning parameter 55 (growth ratio at which to do a global GC). Add vmParameter 52 to answer the capacity of the root table (in Spur a.k.a. the rememberedSet). In the wake of the inlining change below (see Slang:), split lookupInMethodCacheSel:classTag: into inlineLookupInMethodCacheSel:classTag:, and use the inline version in internalFindNewMethod. Fix printStringOf: (used in e.g. frame print) to not print crs that would cause previous info to be overwritten. Spur: Fix bug with class table management and two-way become. Because two-way become may do an in-place swap obj1 & obj2 in SpurMemoryManager>>doBecome:and:copyHash: may not be forwarded after the inner become. Hence they should not be followed if not forwarded. The bug manifested as Object's identityHash changing: superclass is the first slot in a class. Following an unforwarded subclass of object yields Object. Setting the hash bits of the followed object smashes Object's identityHash. Thanks to Stephane Rollandin for finding the bug. More rationalization of the class table management post become. Now no post become scan of the class table is necessary at all. Add vm parameter 53 to answer the number of segments. Move the rememberedSet into a pinned object in oldSpace. Allow it to grow on demand, starting at 1k entries, doubling on each grow. Make sure to abort if the attempt to grow the remembered set fails. Try to grow by another 1k slots if doubling fails, then abort. Revise markAndTrace: given that markAndShouldScan: is inlined within it (see Slang changes below). Move the ephemeron processing into markAndShouldScan: out of the now unused numStringSlotsOf:ephemeronInactiveIf: circumlocution. Add activeAndDeferredScan: and numStrongSlotsOfInephemeral: in place of the double negative inactiveOrFailedToDeferScan: and hence inline numStrongSlotsOfInephemeral:. Increase the traceImmediatelySlotLimit. These changes plus the 2 repeats for compaction speed up global GC by at least x2. Change the defaultEdenBytes to 4Mb. Allow the number of compaction passes to vary, 2 on GC, 3 on GC for snapshot. Slang: Add support for inlining into the condition of ifTrue:/ifFalse: when it is marked as inline. Transform expr1 ifTrue:/ifFalse: [^expr2] by inlining ^expr2 into expr1. Transform expr ifTrue:/ifFalse: [statements] by replacing ^boolean occurrences in expr with gotos. -- Aloha, Eliot

July 24, 2014

Re: [Pharo-dev] File Outs: Can We Have Unix Line Endings?

by Damien Cassou

Agree. Mac switched to Unix line endings long ago Le 24 juil. 2014 07:18, "Sean P. DeNigris" <sean(a)clipperadams.com> a Ã©crit : > Any reason not to? Tedious to continually do "%s/\r/\r/g"s on Mac to fix: > TextStream subclass:^M#UCTextStream^MinstanceVariableNames: > ''^MclassVariableNames: ''^MpoolDictionaries: ''^Mcategory: 'UFFA-Core'!^M! > > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/File-Outs-Can-We-Have-Unix-Line-Endings-tp4769721.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

July 24, 2014

Re: [Pharo-dev] Deprecator

by Dale Henrichs

haha! On Thu, Jul 24, 2014 at 10:01 AM, Ben Coman <btc(a)openinworld.com> wrote: > Dale Henrichs wrote: > > ohoh:) > > Deprair > Deprecair > > > Deprecare = Depreca(tion), care (of) > > > > DeDeprecate > > > On Thu, Jul 24, 2014 at 9:11 AM, Ben Coman <btc(a)openinworld.com> wrote: > >> Camille Teruel wrote: >> >> >> On 24 juil. 2014, at 17:05, stepharo <stepharo(a)free.fr> wrote: >> >> Camille >> >> Ammonite is not that sezzy :) >> >> >> Because it has tentacles? :-D >> >> May be >> autoRepair >> selfRepair :) >> >> >> Yes for example ;) >> >> >> How about 'Reprecator' because you are Rep(airing)(Dep)recations. >> >> >> >> >> Stef >> On 24/7/14 14:34, Camille Teruel wrote: >> >> Hello Pharo users, >> >> I'm pleased to announce the release of Deprecator. >> It's a prototype of a small tool that permits you to deprecate method by >> annotating them with a <deprecated: ...> pragma. >> This pragma takes a rewrite expression as argument that specifies how to >> rewrite the message send to the deprecated method. >> If such a deprecated method is executed, a warning is thrown and a >> debugger opens. >> This debugger has a little 'Rewrite' button that permits to rewrite the >> sending method according to the rewrite expression and then resume the >> execution with the new rewritten sending method :) >> The implementation is a proof-of-concept and is a bit hacky here and >> there, but it works. >> >> Example: >> >> You have a class C with a method that you deprecate. >> Its rewrite expression tells that if it's executed as the result of a >> message send of the form: >> *<receiver>* deprecatedMethodArg1: *<arg1>* arg2: *<arg2>*, >> this message send should be rewritten to: >> *<receiver>* replacementMethodArg1: *<arg2>* arg2: *<arg1>*. >> Note you can change the order of arguments or even the receiver. >> >> C>>deprecatedMethodArg1: o1 arg2: o2 >> <deprecated: '`@receiver replacementMethodArg1: `@arg2 arg2: `@arg1'> >> ^ #deprecated >> >> C>>replacementMethodArg1: o1 arg2: o2 >> ^ #replacement >> >> C>>senderMethod >> ^ self deprecatedMethodArg1: 1 + 1 arg2: 2 + 2. >> >> Then if you execute C new senderMethod, and then click on the "Rewrite" >> button of the debugger, then sending method is rewritten to: >> >> C>>senderMethod >> ^ self replacementMethodArg1: 2 + 2 arg2: 1 + 1. >> >> and the result is #replacement. >> >> The repo is on sSmalltalkHub: >> MCHttpRepository >> location: 'http://smalltalkhub.com/mc/CamilleTeruel/Deprecator/main' >> user: '' >> password: '' >> >> I hope for comments, feature suggestions, code reviews, contributors, >> etc :) >> BTW, if you have a better name for this project let me know! >> For example, I thought about Ammonite because it's an extinct animal >> (analogy with deprecated) and it fits the sea naming theme. >> >> Cheers, >> Camille >> >> >> >> >> > >

July 24, 2014

Re: [Pharo-dev] DO NOT COMMIT TO PHARO TEAM IN SMALLTALKHUB

by nicolas petton

Hi guys, I will fix it together with Esteban later tonight. I do not have my machine right now so I can't put it down, but please follow esteban's advice and do not commit to any project of the pharo team :) Cheers, Nico Le 24 juil. 2014 18:43, "Esteban Lorenzano" <estebanlm(a)gmail.com> a Ã©crit : > the subject says it all :) > (it is broken, Iâm working on fixing it) > > Esteban > > >

July 24, 2014

Re: [Pharo-dev] Deprecator

by Ben Coman

July 24, 2014

Re: [Pharo-dev] Deprecator

by Dale Henrichs

ohoh:) Deprair Deprecair DeDeprecate On Thu, Jul 24, 2014 at 9:11 AM, Ben Coman <btc(a)openinworld.com> wrote: > Camille Teruel wrote: > > > On 24 juil. 2014, at 17:05, stepharo <stepharo(a)free.fr> wrote: > > Camille > > Ammonite is not that sezzy :) > > > Because it has tentacles? :-D > > May be > autoRepair > selfRepair :) > > > Yes for example ;) > > > How about 'Reprecator' because you are Rep(airing)(Dep)recations. > > > > > Stef > On 24/7/14 14:34, Camille Teruel wrote: > > Hello Pharo users, > > I'm pleased to announce the release of Deprecator. > It's a prototype of a small tool that permits you to deprecate method by > annotating them with a <deprecated: ...> pragma. > This pragma takes a rewrite expression as argument that specifies how to > rewrite the message send to the deprecated method. > If such a deprecated method is executed, a warning is thrown and a > debugger opens. > This debugger has a little 'Rewrite' button that permits to rewrite the > sending method according to the rewrite expression and then resume the > execution with the new rewritten sending method :) > The implementation is a proof-of-concept and is a bit hacky here and > there, but it works. > > Example: > > You have a class C with a method that you deprecate. > Its rewrite expression tells that if it's executed as the result of a > message send of the form: > *<receiver>* deprecatedMethodArg1: *<arg1>* arg2: *<arg2>*, > this message send should be rewritten to: > *<receiver>* replacementMethodArg1: *<arg2>* arg2: *<arg1>*. > Note you can change the order of arguments or even the receiver. > > C>>deprecatedMethodArg1: o1 arg2: o2 > <deprecated: '`@receiver replacementMethodArg1: `@arg2 arg2: `@arg1'> > ^ #deprecated > > C>>replacementMethodArg1: o1 arg2: o2 > ^ #replacement > > C>>senderMethod > ^ self deprecatedMethodArg1: 1 + 1 arg2: 2 + 2. > > Then if you execute C new senderMethod, and then click on the "Rewrite" > button of the debugger, then sending method is rewritten to: > > C>>senderMethod > ^ self replacementMethodArg1: 2 + 2 arg2: 1 + 1. > > and the result is #replacement. > > The repo is on sSmalltalkHub: > MCHttpRepository > location: 'http://smalltalkhub.com/mc/CamilleTeruel/Deprecator/main' > user: '' > password: '' > > I hope for comments, feature suggestions, code reviews, contributors, > etc :) > BTW, if you have a better name for this project let me know! > For example, I thought about Ammonite because it's an extinct animal > (analogy with deprecated) and it fits the sea naming theme. > > Cheers, > Camille > > > > >

July 24, 2014

Re: [Pharo-dev] Context merge and external frameworks

by Stephan Eggermont

ClÃ©ment wrote: >If there is something clever we can do in the Pharo image to help for this migration, let us know. The first thing to do is to walk smalltalkhub, squeak source and ss3 packages to check which ones have those extensions. I assume a MooseMonticelloHTTPImporter can be used for that Stephan

July 24, 2014