December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Thank you for Pharo

by Marcus Denker

On 27 Dec 2013, at 11:17, Volkert Barr <volkert(a)nivoba.de> wrote: > Thank you for Pharo â¦. > > I am following the development of Pharo since its fork from Squeak, and i am really impressed what you crazy guys all have archived the last years. It all evolved to really nice language, a fantastic nice looking live programming environment, cool packages and a growing ecosystems. I have so much fun using Pharo. Thank you. > > 2011 i gave me a push to learn Pharo and last year i decided to do a small research prototype with it. The goal is a tool to analyze and visualize application landscapes. I have implemented a small repository model for the different architecture levels, some data analytic rules on top the model, and some model visualizations. For visualization i use Roassal/Mondrian. For Data-In/-Export i use simply NeoCSV. Next year i plan to add more data analytic rules, to add model transformation operations to "simulate" landscape transformations (projects), and to use 3D visualizations with Roassal3D (City Metaphor). If all works fine, we see what 2015 brings ... > > Pharo is really a productivity boost for me. If you are able to play around with the objects in an interactive environment life is getting so much easier. Thanks a lot for this mail :-) Marcus

Dec. 30, 2013

Re: [Pharo-dev] Are #explorerContents and #hasContentsInExplorer obsolete ?

by Marcus Denker

On 28 Dec 2013, at 13:36, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thanks for raising this :). > > I now added a simple implementation in the GTInspector to have Pointers available for all objects. Perhaps it is overdoing it to have it by default on all objects, but it was cheap to implement in a crude way. I still do not eliminate all inspector related objects that point to the current object, but it's a start (see attached the pointers to Smalltalk). > If the inspector that is in Pharo gets a solution for pointers, then we can directly clean up a lot of old code. With this being done for tools that are just loadable optionally â> we still have to keep the old code of the Explorer around. Marcus

Dec. 30, 2013

Re: [Pharo-dev] pharo 3.0 image

by Johan Brichau

On 30 Dec 2013, at 09:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> imho, it seems more appropriate to keep them with the image since itâs the image that determines the Pharo version and not the vm. > > Keeping them with the VM makes for easier sharing (just one copy, never think of it again, run images from everywhere). These are different styles I guess. I guess it does not hurt to look at both places. In 10 years from now, you might no longer have the V10.sources anymore with your vm but you might want to dive into a 2011 image of Zinc on Pharo1.4 for good âol times sake ;-) cheers Johan

Dec. 30, 2013

Re: [Pharo-dev] pharo 3.0 image

by Sven Van Caekenberghe

On 30 Dec 2013, at 08:29, Johan Brichau <johan(a)inceptive.be> wrote: > On 29 Dec 2013, at 22:16, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> yeah, but I also remember a discussion of ânow, sources should be always (and just there) with vmâ¦ or the oppositeââ¦ > > imho, it seems more appropriate to keep them with the image since itâs the image that determines the Pharo version and not the vm. Keeping them with the VM makes for easier sharing (just one copy, never think of it again, run images from everywhere). These are different styles I guess. > I made a bug report for it. But what you saw was a bug indeed. > cheers, > Johan

Dec. 30, 2013

Re: [Pharo-dev] pharo 3.0 image

by Johan Brichau

On 29 Dec 2013, at 22:16, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > yeah, but I also remember a discussion of ânow, sources should be always (and just there) with vmâ¦ or the oppositeââ¦ imho, it seems more appropriate to keep them with the image since itâs the image that determines the Pharo version and not the vm. I made a bug report for it. cheers, Johan

Dec. 30, 2013

towards moose in the pharo ide (gtinspector / gtdebugger)

by Tudor Girba

Hi, Some of you asked how the GTInspector and GTDebugger are different from the existing infrastructure. They are quite different from the norm in that: they are tiny, and they are highly extensible. Here are some posts that describe what makes them different: http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructe… http://www.humane-assessment.com/blog/dissecting-the-gtinspector/ http://www.humane-assessment.com/blog/extending-variables-shown-in-gtinspec… http://www.humane-assessment.com/blog/moldable-gtdebugger These tools are already the default development tools in the Moose image. As you can see, Moose is reshaping the Pharo IDE. I think this is exciting. This should be just the beginning. To make it better, we need your energy: - Apply and extend these tools for your context (this is what makes them unique). - Tell us what works and what does not work. - Ideally, start working with us on this topic. In particular, I am looking for people that would like to spend some time working on Morphic widgets. It's your turn now. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Dec. 30, 2013

Re: [Pharo-dev] Nautilus: Selection and Drag & Drop Redux

by Benjamin

There is a bug entry. With a slice. I asked the guy few questions about the code. He nevers answered. It was 2 month agoâ¦ They are used in the proto of Nautilus made with Spec :P Ben On 30 Dec 2013, at 01:55, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Benjamin Van Ryseghem-2 wrote >> NewList fixes this by triggering drag on mousedown, and select on mouseup > > Yes, that seems like the correct behavior. I'm not familiar with NewList. > Will that be used for Nautilus eventually? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Nautilus-Selection-and-Drag-Drop-Redux-tp4732930p4733… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Dec. 30, 2013

Re: [Pharo-dev] Nautilus: Selection and Drag & Drop Redux

by Sean P. DeNigris

Benjamin Van Ryseghem-2 wrote > NewList fixes this by triggering drag on mousedown, and select on mouseup Yes, that seems like the correct behavior. I'm not familiar with NewList. Will that be used for Nautilus eventually? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Nautilus-Selection-and-Drag-Drop-Redux-tp4732930p4733… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 30, 2013

Re: [Pharo-dev] FogBugz status change

by btc＠openinworld.com

Dec. 29, 2013

Re: [Pharo-dev] Commit rights to Pharo repositories

by Esteban Lorenzano

done :) Esteban On 29 Dec 2013, at 22:36, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi, > > I want to publish configurations for Pharo 3.0 > > http://www.smalltalkhub.com/#!/~Pharo/MetaRepoForPharo30 > > Can you grant me commit rights? Could I be added to the Pharo team? > > username: hernan > > Cheers, > > HernÃ¡n >

Dec. 29, 2013