- Pharo-dev - lists.pharo.org

Thank you for Pharo
by Volkert Barr Jan. 3, 2014

Jan. 3, 2014

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. My wishes for Pharo: - Some kind of "Pharo Capability Map". It is really hard to understand for a newbie what Pharo is all supporting, what is planed for the future, what the library names are, .... - Stable Pharo 3.0 - Roassal3D (Roassal is so coooool, one of the killer frameworks for Pharo). - More User Interface programming examples - 64 Bit VM and MultiCore Support Thank you guys, and best wishes for 2014 Volkert

9 17

Re: [Pharo-dev] Pharo3 issues
by Stephan Eggermont Jan. 3, 2014

Jan. 3, 2014

If anyone wants the solution for https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-add… before Jan 26, please remember Camillo is working on his PhD till then. (needs reviewing) Stephan

2 1

Re: [Pharo-dev] Don't make me think (the one thing you shouldn't ignore about user interfaces)
by Stephan Eggermont Jan. 3, 2014

Jan. 3, 2014

Sebastian wrote >Cheap idea for us: Good idea for a bit later, and for the new parts. We already have a number of well-known problems for new users. If we donât eliminate them first, weâre not going to find much new issues. They will be hidden behind: - no discoverable way of creating classes & methods; - buttons in the system browser without a visible relationship to the pane they operate on; - context menus that donât operate on the selected item but on a whole group; - menu size - modal editing - keyboard navigation of the ui There are quite some Pharoâers teaching introductions to smalltalk. I think they are aware of these issues. A few of them are on my slides, at least. And a few I always have to explain. Stephan

2 1

Don't make me think (the one thing you shouldn't ignore about user interfaces)
by Sebastian Sastre Jan. 3, 2014

Jan. 3, 2014

Guys is no mystery that we have some issues with UI. It's not so bad either, we have many things that are light years ahead of other but we consistently miss some really basic stuff from the Human-Computer-Interactcion point of view. The community is biased towards engineering and unbalanced regarding to design so this is no surprise (why this happens is another interesting conversation). UI is not that hard when you know what to pay attention to but we need first to decide if we care about usability and the developer experience at all. This fantastic talk from Steve Krug exposes what's the least you can do for the usability of any software. http://blip.tv/business-of-software/steve-krug-on-the-least-you-can-do-abou… sebastian o/

4 7

guiding code changes with gtinspector
by Tudor Girba Jan. 3, 2014

Jan. 3, 2014

Hi, I think the inspector should become more prominent in the life of a Pharo developer. For example, the Inspector is perhaps the last tool you might see as useful for code manipulation, but if you see code as objects, it makes perfect sense to have some support in the inspector. To show how it can be different, I described two recent scenarios in which the GTInspector was essentially the only tool readily available to support editing of a custom set of methods: http://www.humane-assessment.com/blog/guiding-custom-changes-with-gtinspect… I would be happy to hear any feedback. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

1 0

[pharo-project/pharo-core]
by GitHub Jan. 3, 2014

Jan. 3, 2014

Branch: refs/tags/30669 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 441a2e: 30669
by GitHub Jan. 3, 2014

Jan. 3, 2014

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 441a2ef1edbf4a433d65aeb7a26e24ea9a21c3a0 https://github.com/pharo-project/pharo-core/commit/441a2ef1edbf4a433d65aeb7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-03 (Fri, 03 Jan 2014) Changed paths: A Morphic-Base.package/PolygonMorph.class/class/examples/example1.st A Morphic-Base.package/PolygonMorph.class/class/examples/example2.st A Morphic-Base.package/PolygonMorph.class/class/examples/example3.st A Morphic-Base.package/PolygonMorph.class/class/examples/example4.st A Morphic-Base.package/PolygonMorph.class/class/examples/example5.st M Morphic-Base.package/PolygonMorph.class/class/instance creation/arrowPrototype.st R Morphic-Base.package/PolygonMorph.class/instance/access/borderColor_.st A Morphic-Base.package/PolygonMorph.class/instance/accessing/borderColor_.st M Morphic-Base.package/PolygonMorph.class/instance/accessing/borderWidth_.st M Morphic-Base.package/PolygonMorph.class/instance/accessing/fillStyle.st M Morphic-Base.package/PolygonMorph.class/instance/accessing/fillStyle_.st R Morphic-Base.package/PolygonMorph.class/instance/accessing/makeOpenOrClosed.st M Morphic-Base.package/PolygonMorph.class/instance/accessing/midVertices.st M Morphic-Base.package/PolygonMorph.class/instance/accessing/smoothOrSegmentedPhrase.st M Morphic-Base.package/PolygonMorph.class/instance/accessing/step.st A Morphic-Base.package/PolygonMorph.class/instance/accessing/toggleOpenOrClosed.st R Morphic-Base.package/PolygonMorph.class/instance/attachments/boundsSignatureHash.st M Morphic-Base.package/PolygonMorph.class/instance/attachments/defaultAttachmentPointSpecs.st M Morphic-Base.package/PolygonMorph.class/instance/attachments/nudgeForLabel_.st M Morphic-Base.package/PolygonMorph.class/instance/attachments/totalLength.st M Morphic-Base.package/PolygonMorph.class/instance/caching/releaseCachedState.st M Morphic-Base.package/PolygonMorph.class/instance/cubic support/changeInSlopes_of_.st M Morphic-Base.package/PolygonMorph.class/instance/cubic support/closedCubicSlopesOf_.st M Morphic-Base.package/PolygonMorph.class/instance/dashes/borderDashOffset.st M Morphic-Base.package/PolygonMorph.class/instance/drawing/drawOnFormCanvas_.st M Morphic-Base.package/PolygonMorph.class/instance/editing/deleteVertexAt_.st M Morphic-Base.package/PolygonMorph.class/instance/editing/dropVertex_event_fromHandle_.st M Morphic-Base.package/PolygonMorph.class/instance/editing/handleColorAt_.st M Morphic-Base.package/PolygonMorph.class/instance/editing/insertVertexAt_put_.st R Morphic-Base.package/PolygonMorph.class/instance/event handling/justDroppedInto_event_.st M Morphic-Base.package/PolygonMorph.class/instance/geometry/arrowsContainPoint_.st M Morphic-Base.package/PolygonMorph.class/instance/geometry/flipHAroundX_.st M Morphic-Base.package/PolygonMorph.class/instance/geometry/flipVAroundY_.st M Morphic-Base.package/PolygonMorph.class/instance/geometry/rotationCenter.st M Morphic-Base.package/PolygonMorph.class/instance/geometry/rotationCenter_.st M Morphic-Base.package/PolygonMorph.class/instance/geometry/scale_.st M Morphic-Base.package/PolygonMorph.class/instance/initialization/initialize.st M Morphic-Base.package/PolygonMorph.class/instance/initialization/vertices_color_borderWidth_borderColor_.st M Morphic-Base.package/PolygonMorph.class/instance/menu/addPolyLIneCurveMenuItems_hand_.st M Morphic-Base.package/PolygonMorph.class/instance/menu/addPolyShapingMenuItems_hand_.st R Morphic-Base.package/PolygonMorph.class/instance/menu/quickFill_.st M Morphic-Base.package/PolygonMorph.class/instance/shaping/diamondOval.st R Morphic-Base.package/PolygonMorph.class/instance/shaping/rectOval.st A Morphic-Base.package/PolygonMorph.class/instance/shaping/rectangleOval.st M Morphic-Base.package/PolygonMorph.class/instance/smoothing/coefficients.st M Morphic-Base.package/PolygonMorph.class/instance/smoothing/coefficientsForMoreThanThreePoints.st M Morphic-Base.package/PolygonMorph.class/instance/smoothing/slopes_.st M Morphic-Base.package/PolygonMorph.class/instance/testing/hasArrows.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/restrictedBrowseGroups_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/private/isSelectedPackage_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script322.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30669.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30669 12550 MNU on Browse scoped from a Group https://pharo.fogbugz.com/f/cases/12550 12526 Change Groups/packages in Nautilus can freeze the UI https://pharo.fogbugz.com/f/cases/12526 12495 Cleaning PolygonMorph https://pharo.fogbugz.com/f/cases/12495 http://files.pharo.org/image/30/30669.zip

1 0

Re: [Pharo-dev] Anyone noticed or tried Gravel?
by Stephan Eggermont Jan. 3, 2014

Jan. 3, 2014

Iâve asked the author of Gravel to show it to us at Fosdem2014. He wants to, but might not be able to make it due to expected family expansion. Stephan

1 0

Configuration trouble
by Diego Lont Jan. 3, 2014

Jan. 3, 2014

Hi all, Due to the release of Seaside 3.1 some projects have fallen over. I thought I give a heads up. The error message I got was from the CI-server for my project (QCMagritte) was: *** Warning: Warning: This package depends on the following classes: GRDelegatingStream You must resolve these dependencies before you will be able to load these definitions: GRCountingStream count greaseNext:putAll:startingAt: initialize next next: nextPut: nextPutAll: reset greaseNext:putAll:startingAt: Basically, this means that you try to load 2 different versions of Seaside in your configuration: 3.0.9 and/or 3.1 into Pharo. This problem may have occurred in the past as well when we moved the configuration to its own place. So if people get this error: please fix your configuration. Most of the projects I can access the configuration (Magritte3, Pier3, TwitterBootstrap, QCMagritte) have different version for loading 3.1 or 3.0.9. If people have trouble fixing this: we can take a look at your configuration. For instance: I see on the CI-server that the smalltalkhub project has this problem, but I can imagine this is the case for private projects as well, as the "#stable" symbolic version now points to a different numbered version. Note: for gemstone the stable version is changed into 3.0.10 â¦ for people who use seaside on gemstone: it might be needed that a different version for gemstone should be added. Cheers, Diego

1 0

Anyone noticed or tried Gravel?
by vfclists . Jan. 3, 2014

Jan. 3, 2014

Anyone noticed or tried Gravel? https://github.com/gravel-st/gravel -- Frank Church ======================= http://devblog.brahmancreations.com

4 6