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

Re: [Pharo-dev] Method recategorization - call for help

by stepharo

Pavel I have a nearly working (just need to look at the rules) to autorecategorize the methods so may be we could do a pass to make it really better. Then as soon as 40 is out I want to recategorize the packages in Morphic aas we discussed when I visited you at Prague. Stef On 16/5/14 11:10, Pavel Krivanek wrote: > Hi, > > if you would like to contribute to better Pharo modularization and you > do not know how, I have a tip for you. > > Following methods are extension methods of various packages that > extend classes in Morphic-Core package. We need to move them directly > to Morphic-Core package so we have to place them in different categories. > > Example: > > Morph organization classify: #handleMouseWheel: under: > 'events-processing'. > Morph organization classify: #handlesMouseWheel: under: > 'events-processing' > > Methods: > > Morph organization classify: #layoutChanged under: 'recategorized'. > PasteUpMorph organization classify: #resizeBackgroundMorph under: > 'recategorized'. > PasteUpMorph organization classify: #backgroundMorph under: > 'recategorized'. > Color organization classify: #fillRectangle:on: under: 'recategorized'. > Morph organization classify: #rejectsEvent: under: 'recategorized'. > Morph organization classify: #privateMoveBy: under: 'recategorized'. > Morph organization classify: #rejectsEvent: under: 'recategorized'. > Morph organization classify: #changed under: 'recategorized'. > Morph organization classify: #handlesDropShadowInHand under: > 'recategorized'. > Morph organization classify: #layoutChanged under: 'recategorized'. > Morph organization classify: #morphicLayerNumberWithin: under: > 'recategorized'. > Morph organization classify: #morphicLayerNumberWithin: under: > 'recategorized'. > Morph organization classify: #handlesMouseOver: under: 'recategorized'. > Morph organization classify: #privateMoveBy: under: 'recategorized'. > Morph organization classify: #rejectsEvent: under: 'recategorized'. > Morph organization classify: #changed under: 'recategorized'. > Morph organization classify: #handlesDropShadowInHand under: > 'recategorized'. > Morph organization classify: #ayoutChanged under: 'recategorized'. > Morph organization classify: #morphicLayerNumberWithin: under: > 'recategorized'. > Morph organization classify: #handlesMouseOver: under: 'recategorized'. > HandMorph organization classify: #fullDrawOn: under: 'recategorized'. > HandMorph organization classify: #fullDrawOn: under: 'recategorized'. > PasteUpMorph organization classify: #resizeBackgroundMorph under: > 'recategorized'. > PasteUpMorph organization classify: #handlerForMouseDown: under: > 'recategorized'. > PasteUpMorph organization classify: #backgroundMorph under: > 'recategorized'. > PasteUpMorph organization classify: #resizeBackgroundMorph under: > 'recategorized'. > PasteUpMorph organization classify: #handlerForMouseDown: under: > 'recategorized'. > PasteUpMorph organization classify: #backgroundMorph under: > 'recategorized'. > Color organization classify: #fillRectangle:on: under: 'recategorized'. > > That is not all. There is a lot of methods that do not need to be in > Morphic-Core package. Most of them will be moved to Morphic-Base > package but it is not good to place them directly to '*Morphic-Base' > category. We should create categories like '*Morphic-Base-something' > or place this methods to some more fitting packages. > > WorldMorph class organization classify: #installNewWorld under: > '*Morphic-Base'. > BorderStyle class organization classify: #raised under: '*Morphic-Base'. > BorderStyle class organization classify: #complexAltRaised under: > '*Morphic-Base'. > BorderStyle class organization classify: #complexAltFramed under: > '*Morphic-Base'. > BorderStyle class organization classify: #complexAltInset under: > '*Morphic-Base'. > BorderStyle class organization classify: #inset under: '*Morphic-Base'. > BorderStyle class organization classify: #simple under: '*Morphic-Base'. > BorderStyle class organization classify: #complexInset under: > '*Morphic-Base'. > BorderStyle class organization classify: #width:color: under: > '*Morphic-Base'. > BorderStyle class organization classify: #complexRaised under: > '*Morphic-Base'. > BorderStyle class organization classify: #complexFramed under: > '*Morphic-Base'. > BorderedMorph class organization classify: #exampleGradient under: > '*Morphic-Base'. > WorldState class organization classify: #startThenBrowseMessageTally > under: '*Morphic-Base'. > WorldState class organization classify: #startMessageTally under: > '*Morphic-Base'. > WorldState class organization classify: #windowsOn: under: > '*Morphic-Base'. > WorldState class organization classify: #systemOn: under: '*Morphic-Base'. > GrafPort organization classify: > #displayScannerFor:foreground:background:ignoreColorChanges: under: > '*Morphic-Base'. > Canvas organization classify: #asAlphaBlendingCanvas: under: > '*Morphic-Base'. > Canvas organization classify: #copyClipRect: under: '*Morphic-Base'. > WorldMorph organization classify: #acceptDroppingMorph:event: under: > '*Morphic-Base'. > WorldMorph organization classify: #install under: '*Morphic-Base'. > WorldMorph organization classify: #installForUIProcessReinstall under: > '*Morphic-Base'. > WorldMorph organization classify: #dispatchKeystroke: under: > '*Morphic-Base'. > BorderedMorph organization classify: #changeBorderWidth: under: > '*Morphic-Base'. > BorderedMorph organization classify: #splitters under: '*Morphic-Base'. > BorderedMorph organization classify: #addPaneVSplitterBetween:and: > under: '*Morphic-Base'. > BorderedMorph organization classify: #removeCornerGrips under: > '*Morphic-Base'. > BorderedMorph organization classify: #addCornerGrips under: > '*Morphic-Base'. > BorderedMorph organization classify: #addPaneSplitters under: > '*Morphic-Base'. > Morph organization classify: #newTransformationMorph under: > '*Morphic-Base'. > Morph organization classify: #exportAsGIF under: '*Morphic-Base'. > Morph organization classify: #embeddedInMorphicWindowLabeled: under: > '*Morphic-Base'. > Morph organization classify: #addWorldHandlesTo:box: under: > '*Morphic-Base'. > Morph organization classify: #useGradientFill under: '*Morphic-Base'. > Morph organization classify: #assureTableProperties under: > '*Morphic-Base'. > Morph organization classify: #resizeMorph: under: '*Morphic-Base'. > Morph organization classify: #justDroppedInto:event: under: > '*Morphic-Base'. > Morph organization classify: #fillWithRamp:oriented: under: > '*Morphic-Base'. > Morph organization classify: #borderColor: under: '*Morphic-Base'. > Morph organization classify: #on:send:to:withValue: under: > '*Morphic-Base'. > Morph organization classify: #assureLayoutProperties under: > '*Morphic-Base'. > Morph organization classify: #exportAsPNG under: '*Morphic-Base'. > Morph organization classify: #embedInWindow under: '*Morphic-Base'. > Morph organization classify: #defaultBalloonFont under: '*Morphic-Base'. > Morph organization classify: #addHandlesTo:box: under: '*Morphic-Base'. > Morph organization classify: #containingWindow under: '*Morphic-Base'. > Morph organization classify: #collapse under: '*Morphic-Base'. > Morph organization classify: #borderWidth: under: '*Morphic-Base'. > Morph organization classify: #on:send:to: under: '*Morphic-Base'. > Morph organization classify: #rowMorphForNode:inColumn: under: > '*Morphic-Base'. > Morph organization classify: #useBitmapFill under: '*Morphic-Base'. > Morph organization classify: #changeColor under: '*Morphic-Base'. > Morph organization classify: #changeProportionalLayout under: > '*Morphic-Base'. > Morph organization classify: #setShadowOffset: under: '*Morphic-Base'. > Morph organization classify: #changeTableLayout under: '*Morphic-Base'. > Morph organization classify: #changeCellInset: under: '*Morphic-Base'. > Morph organization classify: #changeMinCellSize: under: '*Morphic-Base'. > Morph organization classify: #defaultBalloonColor under: '*Morphic-Base'. > Morph organization classify: #changeMaxCellSize: under: '*Morphic-Base'. > Morph organization classify: #defaultBitmapFillForm under: > '*Morphic-Base'. > Morph organization classify: #changeLayoutInset: under: '*Morphic-Base'. > Morph organization classify: #addHalo: under: '*Morphic-Base'. > Morph organization classify: #setArrowheads under: '*Morphic-Base'. > FormCanvas organization classify: > #drawString:from:to:autoBoundAt:font:color: under: '*Morphic-Base'. > FormCanvas organization classify: #asBalloonCanvas under: '*Morphic-Base'. > FormCanvas organization classify: #roundCornersOf:in:during: under: > '*Morphic-Base'. > FormCanvas organization classify: #roundShadowCornersOf:in:during: > under: '*Morphic-Base'. > PasteUpMorph organization classify: #windowsSatisfying: under: > '*Morphic-Base'. > PasteUpMorph organization classify: #keystrokeInWorld: under: > '*Morphic-Base'. > PasteUpMorph organization classify: #modelWakeUp under: '*Morphic-Base'. > PasteUpMorph organization classify: #grabRubberBandFromScreen: under: > '*Morphic-Base'. > PasteUpMorph organization classify: #grabLassoFromScreen: under: > '*Morphic-Base'. > PasteUpMorph organization classify: #drawingClass under: '*Morphic-Base'. > PasteUpMorph organization classify: #createTaskbarIfNecessary under: > '*Morphic-Base'. > PasteUpMorph organization classify: #mouseDown: under: '*Morphic-Base'. > PasteUpMorph organization classify: #makeAScreenshot under: > '*Morphic-Base'. > PasteUpMorph organization classify: #acceptDroppingMorph:event: under: > '*Morphic-Base'. > PasteUpMorph organization classify: #dragThroughOnDesktop: under: > '*Morphic-Base'. > PasteUpMorph organization classify: #fitAll under: '*Morphic-Base'. > HandMorph organization classify: #generateDropFilesEvent: under: > '*Morphic-Base'. > HandMorph organization classify: > #waitForClicksOrDrag:event:selectors:threshold: under: '*Morphic-Base'. > WorldState organization classify: > #startStepping:at:selector:arguments:stepTime: under: '*Morphic-Base'. > WorldState organization classify: #menuBuilder under: '*Morphic-Base'. > WorldState organization classify: #convertStepList under: '*Morphic-Base'. > WorldState organization classify: #addAlarm:withArguments:for:at: > under: '*Morphic-Base'. > > Please try to take care for at least one of the classes and write the > recategorization code here as a response or directly to the issue report > https://pharo.fogbugz.com/f/cases/13263/Morphic-Core-methods-recategorizati… > > Cheers, > -- Pavel > > >

May 17, 2014

Re: [Pharo-dev] Pharo 3.0 / Roassal2 / Ubuntu

by volkert＠nivoba.de

Am 01.05.2014 13:07, schrieb Alexandre Bergel: >> Yes yes yes ... it works. I quickly jumped through some examples. Roassal2 looks so nice. Thank you. > Let me know how it goes. Documentation is missing, but we have many many examplesâ¦ > The chapter in Deep into Pharo (www.deepintopharo.com) contains a documentation about Roassal1 and the Mondrian builder, written on top of the core of Roassal. > > Roassal2 is largely compatible with Roassal1. When it is not, then small changes have to be made. > > Alexandre > today i started with a fresh pharo 3.0 image (#30848) und loaded roassal2 (following the video tutorial). But when selecting the example and evalution menu i got a "MessageNotUnderstood: ByteString>>replaceAllRegex:with:". Something is broken here. BW, Volkert

May 17, 2014

[ANN]: Tiny Gmail Contact Importer

by Sean DeNigris

I wrote a tiny utility to work with Gmail contacts. It is very basic and just maps an export file in the Outlook format to GmailContact objects. It doesn't support the Google CSV format - the field order and names are different, and the file is UTF16-encoded. Enjoy! Gofer it smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; package: 'GmailContact'; load. #GmailContact asClass importAllFromOutlookExport: â/path/to/contacts.csv' asFileReference.

May 16, 2014

Re: [Pharo-dev] Gmail Contact Export and #readStream

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > That is weird indeed, I would say they mixed up Latin1 and UTF8 Yes! Changing to Latin1TextConverter did the trick. I assumed UTF8 because they did not specify and mention UTF8 elsewhere in gmail settings Sven Van Caekenberghe-2 wrote > But if the file starts with the Unicode BOM, that is really confusing... > since in UTF8 it would be different, and from your byte sequence it can't > be UTF16 either. It was UTF16. The byte sequence was from a different output format. Changing to UTF16TextConverter successfully parsed the file. I wonder... can all this be handled automatically? When I open either file in OS X, it seems to just "do the right thing". I also wonder why gmail doesn't clearly display the encoding when you're exporting... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Gmail-Contact-Export-and-readStream-tp4759306p4759320… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 16, 2014

Re: [Pharo-dev] Gmail Contact Export and #readStream

by Sven Van Caekenberghe

That is weird indeed, I would say they mixed up Latin1 and UTF8. BTW, if you do #[40 57 49 52 41 160 52 54 57 45] inspect. in Pharo 3, you'll see that it is actually a Latin1 encoded ByteArray, not a UTF8 one. In Latin1 (http://en.wikipedia.org/wiki/Latin1) 160 is NBSP (Non breaking space). In UTF8, this would be encoded differently ZnUTF8Encoder new encodeString: 160 asCharacter asString. #[194 160] But if the file starts with the Unicode BOM, that is really confusing (http://en.wikipedia.org/wiki/Unicode_Byte-Order_Mark#Usage) since in UTF8 it would be different, and from your byte sequence it can't be UTF16 either. On 16 May 2014, at 22:06, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Two issues: > > 1. Exports for Outlook > ============ > Gmail seems to have inserted "160 asCharacter" in a few places in a gmail > contact csv export, so for example this partial phone number: > '(914) 469-' > is written to file as: > #[40 57 49 52 41 160 52 54 57 45] > And then "aFile readStream contents" signals "ZnInvalidUTF8: Invalid utf8 > input detected" when it encounters the 160 > > 2. Google csv Exports > ============ > The file starts with the BOM #[255 254], which generates the same exception > > ============= > > Are these problems with gmail or Pharo? > Thanks > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Gmail-Contact-Export-and-readStream-tp4759306.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

May 16, 2014

Gmail Contact Export and #readStream

by Sean P. DeNigris

Two issues: 1. Exports for Outlook ============ Gmail seems to have inserted "160 asCharacter" in a few places in a gmail contact csv export, so for example this partial phone number: '(914)Â 469-' is written to file as: #[40 57 49 52 41 160 52 54 57 45] And then "aFile readStream contents" signals "ZnInvalidUTF8: Invalid utf8 input detected" when it encounters the 160 2. Google csv Exports ============ The file starts with the BOM #[255 254], which generates the same exception ============= Are these problems with gmail or Pharo? Thanks ----- Cheers, Sean -- View this message in context: http://forum.world.st/Gmail-Contact-Export-and-readStream-tp4759306.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 16, 2014

Re: [Pharo-dev] a Pharo talk from a ruby conference

by David Astels

To me, âSmalltalkâ is everything. Take anything away (language, tools, image, or library) and itâs not nearly as interesting. On May 16, 2014, at 12:04 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Esteban A. Maringolo wrote >> All the previous dialects were advertised as "a new Smalltalk dialect" >> ... >> This time we could, at least, try to advertise it differently. > > +1. I think that delaying the Smalltalk conversation a bit a la Clojure > might be the sweet spot. A good time to mention it might be in describing > the language, since it's obviously Smalltalk. I'll reiterate that I strongly > feel that the language - which has always been the least interesting thing - > should be introduced /last/, after the environment - which is the real blue > plane idea here - and the libraries, which are of practical importance. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/a-Pharo-talk-from-a-ruby-conference-tp4756805p4759290… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

May 16, 2014

Re: [Pharo-dev] 32 bits and 64 bits VM

by David T. Lewis

On Fri, May 16, 2014 at 10:20:47AM +0200, Esteban Lorenzano wrote: > > On 15 May 2014, at 18:46, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > > > Great. > > > > As we are discussing about build, is it possible to compile CogVM on 64 > > bits architecture as it is already the case for the interpreted SqueakVM > > (https://packages.debian.org/sid/squeak-vm)? > > I do not understand. To compile a regular vm in a 64bits platform is trivial. You just need to have the 32bits library installed. > But to have a 64bits vm that runs on 64bits? that?s another very different history: > > - you need a 64bits image (so trace, export, etc.) > - you need to be 64bits word size aware (not so complicated, but a lot of work). > - you need 64bits plugins (a lot of them) > - you need 64bits JIT (or no JIT at all) > > Some time ago there was an experimental 64bits interpreter vm (not even stack). Who worked with a special traced image. > What squeak guys are doing in the link you provide is still building a 32bits vm. It's experimental 64 bit image is not really all that experimental any more, although Ian still labels it as such on squeakvm.org/unix. A compiled VM is available there. Building it from source is just a matter of specifying --image64 in the configure step, then doing a make. Up to date Squeak trunk images in 64-bit format are traced daily at http://build.squeak.org/job/Squeak%2064-bit%20image/ Dave

May 16, 2014

Re: [Pharo-dev] a Pharo talk from a ruby conference

by phil＠highoctane.be

On Fri, May 16, 2014 at 7:23 PM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > Once, when I told an old friend I was doing Smalltalk, he asked me "Are > you doing computer archeology?" It is difficult to fight this. > Back to the future after 30 years of spinning your wheels ------------------------------------------------------------------- Wanting to code at the speed of tought? Wishing the machine was your friend and not a roadblock? Want to burn cash as slow as possible while maximizing your output? If so, get a copy of Pharo! It is not your (grand) daddy's Smalltalk! ;-) Phil > > Hilaire > > Le 15/05/2014 22:09, Sergi Reyner a Ã©crit : > > "Pharo is a Smalltalk for the 21st century." - Sergi Reyner. > > > > Cheers, > > Sergi > > -- > Dr. Geo http://drgeo.eu > > >

May 16, 2014

Re: [Pharo-dev] 32 bits and 64 bits VM

by Hilaire Fernandes

I know for years[1], only solve partially, on some Linux distribution, not really user friendly, support of this solution may change over making installation of 32bits libs even more complicated for average user. Now my question was related to 64bits, and I am really curious about this 64bits squeakvm compiled for Debian AMD64 Le 16/05/2014 18:17, Damien Cassou a Ã©crit : > On Wed, May 14, 2014 at 9:08 PM, Hilaire Fernandes > <hilaire.fernandes(a)gmail.com> wrote: >> Yesterday my boss asked me to see DrGeo on his Ununtu 14.04LTS 64 bits >> machine. I could not get it working > > Following these simple instructions would have fixed the problem in 2 minutes: > http://www.pharo-project.org/pharo-download/ubuntu > > I run the exact same OS and Pharo works perfectly. > [1] http://www.drgeo.eu/community/faq#TOC-Can-I-run-it-in-my-Linux-64-bits-host- -- Dr. Geo http://drgeo.eu

May 16, 2014