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

Re: [Pharo-dev] Spotlight

by Sven Van Caekenberghe

Cool ! I haven't loaded your change set yet, but your ideas are good - I agree with all of them. Maybe it would be better to make the placement a setting (a bit like for the growl widget). What I find annoying is that the shortest match is not always chosen, for example when you type String, the String class is not in the top matches, and you have to type a space before hitting return. On 16 May 2014, at 11:02, phil(a)highoctane.be wrote: > Hello, > > There are a couple of things that do get on my nerves with Spotlight, namely that it lists all kinds of symbols that have nothing to do in the search list, > > e.g. Globals (Display), old classes that aren't there anymore etc. > > that it is on the top right,making me look away from the code etc. > I want this in the middle of the screen, like in Eclipse for example. > > Also, if I type in Display, I'd like to inspect it right away (I know I can do that with :<expr> but still> as I forget it all the time, I've put a reminder in the box). > > Next, I do not want to search, I want to find, so, ghosttext changed accordingly. > > So, I had a look and changed it to be the way I wanted. > > It is much more usable that way as far as I am concerned. > > If you want to try this, just file in the attached change set or get https://gist.github.com/philippeback/f43447ec2bddcd3f9b84 > > What would also nice it to be able to have the autocompletion list wider. Any idea on how to do just that? (yes, I have long class names...) > > Feedback welcome. > > Phil > > <Screenshot-13.png><Spotlight.st>

May 16, 2014

Re: [Pharo-dev] Auto-documenting your Pharo-projects

by kilon alios

ah nice this is very cool :) are there any other features or thats about it ? On Fri, May 16, 2014 at 12:00 PM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > It is like JavaDoc, based on class and method comments. > > On 16 May 2014, at 10:53, kilon alios <kilon.alios(a)gmail.com> wrote: > > > how exactly it works ? it documents class and method comments ? Or you > can add also additional text to it ? > > > > > > On Fri, May 16, 2014 at 10:49 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > > Hi everyone. > > > > Following yesterdayâs discussion about WebDoc, Iâm pleased to share with > you my new blog post with a tutorial how to generate documentation on CI: > http://sleepycoders.blogspot.com/2014/05/auto-documenting-your-pharo-projec… > > > > Cheers. > > Uko > > > > >

May 16, 2014

Method recategorization - call for help

by Pavel Krivanek

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 16, 2014

Spotlight

by phil＠highoctane.be

Hello, There are a couple of things that do get on my nerves with Spotlight, namely that it lists all kinds of symbols that have nothing to do in the search list, e.g. Globals (Display), old classes that aren't there anymore etc. that it is on the top right,making me look away from the code etc. I want this in the middle of the screen, like in Eclipse for example. Also, if I type in Display, I'd like to inspect it right away (I know I can do that with :<expr> but still> as I forget it all the time, I've put a reminder in the box). Next, I do not want to search, I want to find, so, ghosttext changed accordingly. So, I had a look and changed it to be the way I wanted. It is much more usable that way as far as I am concerned. If you want to try this, just file in the attached change set or get https://gist.github.com/philippeback/f43447ec2bddcd3f9b84 What would also nice it to be able to have the autocompletion list wider. Any idea on how to do just that? (yes, I have long class names...) Feedback welcome. Phil

May 16, 2014

Re: [Pharo-dev] Auto-documenting your Pharo-projects

by Sven Van Caekenberghe

It is like JavaDoc, based on class and method comments. On 16 May 2014, at 10:53, kilon alios <kilon.alios(a)gmail.com> wrote: > how exactly it works ? it documents class and method comments ? Or you can add also additional text to it ? > > > On Fri, May 16, 2014 at 10:49 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi everyone. > > Following yesterdayâs discussion about WebDoc, Iâm pleased to share with you my new blog post with a tutorial how to generate documentation on CI: http://sleepycoders.blogspot.com/2014/05/auto-documenting-your-pharo-projec… > > Cheers. > Uko >

May 16, 2014

Re: [Pharo-dev] Auto-documenting your Pharo-projects

by kilon alios

how exactly it works ? it documents class and method comments ? Or you can add also additional text to it ? On Fri, May 16, 2014 at 10:49 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>wrote: > Hi everyone. > > Following yesterdayâs discussion about WebDoc, Iâm pleased to share with > you my new blog post with a tutorial how to generate documentation on CI: > http://sleepycoders.blogspot.com/2014/05/auto-documenting-your-pharo-projec… > > Cheers. > Uko >

May 16, 2014

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

by Esteban Lorenzano

On 16 May 2014, at 10:27, phil(a)highoctane.be wrote: > On Fri, May 16, 2014 at 10:20 AM, Esteban Lorenzano <estebanlm(a)gmail.com> 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.) > > ImageTracers are intriguing to me :-) Is this in some way relatable to Oz? What's that project doing now? It was very interesting/useful. Guille? > > - 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) > > > And... > > * 64-bit aware hashing functions as the current ones are 32-bit centric. So, not so trivial I'd say. (what's the plan?) > > * special care of the Float which will be directly in a 64 bit "oop" - I guess we'll face some fun here. Especially with the float plugin. yes, the plan is to introduce SmallFloat, etc. So, in summary: a lot of work :) > > As a side note, I see that http://www.mpfr.org/ is supported by INRIA. WTF aren't we considering this ? LGPL and INRIA may help getting some special thing for Pharo. > > Phil > > 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. > > Now. In the agenda for this year is to work on a 64bits spur version. If everything is fine and the stars align properly, it will be ready around christmas. > > Esteban > > > > > > Hilaire > > > > Le 15/05/2014 18:24, Esteban Lorenzano a Ã©crit : > >> so yesâ¦ I integrated the fix, created a pull request, waited until validationâ¦ and then I forget to merge :S > >> it should be in process to build now. > > > > -- > > Dr. Geo http://drgeo.eu > > > > > > >

May 16, 2014

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

by phil＠highoctane.be

On Fri, May 16, 2014 at 10:20 AM, Esteban Lorenzano <estebanlm(a)gmail.com>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.) > ImageTracers are intriguing to me :-) Is this in some way relatable to Oz? What's that project doing now? It was very interesting/useful. Guille? > - 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) > > And... * 64-bit aware hashing functions as the current ones are 32-bit centric. So, not so trivial I'd say. (what's the plan?) * special care of the Float which will be directly in a 64 bit "oop" - I guess we'll face some fun here. Especially with the float plugin. As a side note, I see that http://www.mpfr.org/ is supported by INRIA. WTF aren't we considering this ? LGPL and INRIA may help getting some special thing for Pharo. Phil > 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. > > Now. In the agenda for this year is to work on a 64bits spur version. If > everything is fine and the stars align properly, it will be ready around > christmas. > > Esteban > > > > > > Hilaire > > > > Le 15/05/2014 18:24, Esteban Lorenzano a Ã©crit : > >> so yesâ¦ I integrated the fix, created a pull request, waited until > validationâ¦ and then I forget to merge :S > >> it should be in process to build now. > > > > -- > > Dr. Geo http://drgeo.eu > > > > > > >

May 16, 2014

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

by Esteban Lorenzano

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. Now. In the agenda for this year is to work on a 64bits spur version. If everything is fine and the stars align properly, it will be ready around christmas. Esteban > > Hilaire > > Le 15/05/2014 18:24, Esteban Lorenzano a Ã©crit : >> so yesâ¦ I integrated the fix, created a pull request, waited until validationâ¦ and then I forget to merge :S >> it should be in process to build now. > > -- > Dr. Geo http://drgeo.eu > >

May 16, 2014

Auto-documenting your Pharo-projects

by Yuriy Tymchuk

Hi everyone. Following yesterdayâs discussion about WebDoc, Iâm pleased to share with you my new blog post with a tutorial how to generate documentation on CI: http://sleepycoders.blogspot.com/2014/05/auto-documenting-your-pharo-projec… Cheers. Uko

May 16, 2014