- Pharo-dev - lists.pharo.org

[Pharo-project] Hot keys in Pharo

by roberto.minelli＠usi.ch

Hi, When I attended PharoConf last week, I've seen that there are many keyboard shortcuts embedded in Pharo that I wasn't aware of (e.g., creating a default initialize message). IMHO it would be cool to collect all such hot keys in a webpage or Wiki since those are really a killer features for developers. Cheers, Roby

April 8, 2013

Re: [Pharo-project] [ANN] Pharo VM packages and PPA for Ubuntu

by Max Leske

Damien, We're looking into building the PharoVM on our own build server for our systems (Debian). Did you just build the VM once on your machine or do you have a more general approach for building it? Ideally we'd like jenkins to do something like 1) pull sources 2) run script Cheers, Max On 07.04.2013, at 21:12, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Dear Pharo and Ubuntu users, > > Nicolas Petton and I are proud to announce Ubuntu packages for the > Pharo VM. Installing the pharo vm is now just a matter of: > > sudo add-apt-repository ppa:cassou/pharo > sudo apt-get update > sudo apt-get install pharo-vm > > With this package, you get: > > - the latest pharo vm as a 'pharo' binary in the PATH > - all plugins and libraries (native boost, freetype, ssl, ...) > - file association so you can just double-click on pharo images > - pharo icons visible everywhere (on image files, on ALT+TAB...) > - PharoV10.sources and PharoV20.sources > > Please fill bug reports on https://pharo.fogbugz.com. > > This package is currently only available for Ubuntu 12.10 Quantal. > Fill a bug report if you want me to package it for another version of > Ubuntu. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

April 8, 2013

Re: [Pharo-project] [Pharo-users] [ANN] Fuel Release Version 1.9

by Martin Dias

On Sun, Mar 31, 2013 at 11:06 AM, stephane ducasse <stephane.ducasse(a)free.fr > wrote: > Thanks guys > > this is great. I'm really happy to see that the effort we started two > years ago is paying off. > Stef: thanks to you, INRIA and ESUG for the financial support during the first years. That is important to remark.

April 8, 2013

Re: [Pharo-project] Improving the programmer experience with Pharo (ideas)

by Max Leske

Cool! On 08.04.2013, at 13:08, Gisela Decuzzi <giseladecuzzi(a)gmail.com> wrote: > Hi, I'm just starting an internship for 3 months and we were talking about the scope for my time here. This is a summary of what we have discussed: > The main objective it's to improve the AST and use it to implement as many improvements and refactors/transformations as we can to help the programmer. Some ideas: > - distinguish the code scope (for example, when you have lot of blocks all together when you pass over with the mouse that it get special something to understand where you are) +1. The same for the keyboard would be cool (maybe highlight brackets like it's done in some popular text editors) > - make suggestions depending on what you have selected. Example if it's a variable rename it, or find accesses (â¦) You should take a look at Pavels work Periscope (http://smalltalkhub.com/#!/~PavelKrivanek/Periscope) which is his take on LightTable and does some of these things already. > - highlight selectors > - implements some rules to help code improvement, for example if you select some part of the code and it's repeated you can do an: extract method, or extract to variable transformation. > - improve the navigation between static code > - review the refactoring API and evaluate a change for admitting AST nodes and avoid the use of strings... > > Please let me know your thoughts about it and if you have more ideas, they are always welcome. > > > >

April 8, 2013

Re: [Pharo-project] [ANN] Pharo VM packages and PPA for Ubuntu

by Norbert Hartl

Am 08.04.2013 um 13:05 schrieb Damien Cassou <damien.cassou(a)gmail.com>: > On Mon, Apr 8, 2013 at 11:35 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> sudo apt-get download pharo-vm >> sudo dpkg -i --ignore-depends openssl:i386 pharo-* > > > thank you. I wrote that on the PPA web page > I don't even think that it is work-around. It would be a work-around if you don't need any ssl support. Treating it like this you should face complaints of users why Zinc SSL isn't working. I'm not sure if the automatic installation of a broken package is a benefit for anyone. Let's just fix the multiarch build. Norbert > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

April 8, 2013

Re: [Pharo-project] Collect all references to AnObsoleteFoo

by Martin Dias

pffff thank you. The word 'awesome' is too much, but well, I can put the snippet somewhere in the doc. I don't know if this should be the default behaviour in Fuel, since it will add the dependency to Ring. Also we can discuss about removing the "defensive" error during serialization: as you could see, technically there is no problem to serialize the obsolete class. We decided to raise an error just because as users we found that almost always when you are serializing the obsolete, it was due to some mistake, and you discover that the obsolete was in the .fuel file later when you materialize. Alternatively, we could just raise a "class not found" error during materialization. cheers, Martin ps: I'd like to see the video of Max's presentation in PharoConf! On Sun, Apr 7, 2013 at 2:47 PM, roberto.minelli(a)usi.ch < roberto.minelli(a)usi.ch> wrote: > I'd say that handling obsolete reference this way is very good! I'd put > this behavior in Fuel! > > Cheers, > R > > On Apr 6, 2013, at 2:27 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > Martin, should be manage obsolete always that way (meaning to put such > behavior directly inside Fuel)? > > If not, could be write your awesome code in the Fuel website? > > > > Thanks!!! :) > > > > > > > > > > On Sat, Apr 6, 2013 at 8:26 AM, roberto.minelli(a)usi.ch < > roberto.minelli(a)usi.ch> wrote: > > Martin, your solution is awesome. > > > > I've seen the presentation at Pharoconf about setting an analyzer to the > serializer and I was thinking in that direction. > > > > Thanks a lot, > > R > > > > On Apr 5, 2013, at 4:59 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > > > > > As Fernando said, probably is better for you to substitute the > obsolete class by a ring definition. Look here: > > > > > > http://ws.stfx.eu/OAVG8IXKWOYA > > > > > > Don't need to filein the workaround of my previous email. > > > > > > Martin > > > > > > > > > On Fri, Apr 5, 2013 at 4:47 PM, Martin Dias <tinchodias(a)gmail.com> > wrote: > > > Hi, > > > I'm sorry for my delay. I didn't stop to think a good solution. There > were interesting answers before mine. But if it's a prototype... maybe this > workaround helps you. I played with this code: > > > > > > http://ws.stfx.eu/HYWM1ZB9R45K > > > > > > (the first time I use the shared workspace :-) > > > > > > if you file in the attached file, it materializes the new A class. > > > > > > But this will be not useful for you, if either: > > > - you don't have the "original class" at materialization time > > > - you don't want to know if the class was obsolete at serialization > time > > > > > > HTH > > > Martin > > > > > > > > > > > > On Tue, Apr 2, 2013 at 7:33 AM, Yanni Chiu <yanni(a)rogers.com> wrote: > > > On 02/04/13 12:50 AM, roberto.minelli-BHDiRLqP7qo(a)public.gmane.orgwrote: > > > > > > Is there any way to "browse" through such references to understand > where are they? > > > > > > From an inspector, choose the "Explore pointers", making sure you've > selected the object that you're trying to understand what is referencing it. > > > > > > It takes trial & error, and intuition on which pointers to follow. > This method has often been unsuccessful for me. > > > > > > Another approach (my memory is fuzzy), was to put a halt at a suitable > place during the Fuel serialization. Then explore the intermediate > structures used by Fuel, to try to find out why Fuel thinks it needs to > serialize that object. > > > > > > Yet another approach is to put a halt in the Fuel materialization, and > explore the intermediate structures used by Fuel. You might even set up a > mapping of the obsolete class to some temporary class, which allows Fuel to > fully materialize the saved objects. You can then explore the Fuel > intermediate structures, as well as the final de-serialized object > structure. > > > > > > > > > > > > > > > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > >

April 8, 2013

[Pharo-project] Photos from Pharoconf and Moose day on G+

by Yuriy Tymchuk

Hi, https://plus.google.com/events/crhg5httv7iserrrqv5tulaevhc https://plus.google.com/events/cbi42b525e96tp1gj2bjr9bolns Uko

April 8, 2013

[Pharo-project] [update 3.0] #30025

by Marcus Denker

30025 ----- 7518 ShortPointArray and ShortRunArray not used https://pharo.fogbugz.com/f/cases/7518 6938 Create Collection>>#reject:thenCollect: https://pharo.fogbugz.com/f/cases/6938 10245 Run #cleanUpForRelease on every update https://pharo.fogbugz.com/f/cases/10245 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/UpdateStreamer-Core-MarcusDe… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/CollectionsTests-MarcusDenke… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Collections-Sequenceable-Mar… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Collections-Abstract-MarcusD… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/BalloonTests-MarcusDenker.3 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Balloon-MarcusDenker.93

April 8, 2013

Re: [Pharo-project] Improving the programmer experience with Pharo (ideas)

by Damien Cassou

On Mon, Apr 8, 2013 at 1:08 PM, Gisela Decuzzi <giseladecuzzi(a)gmail.com> wrote: > Please let me know your thoughts about it and if you have more ideas, they > are always welcome. 1) when you have a selector with multiple keywords, I would like to navigate easily between the arguments. For example : self doSomething: (1) with: (2) andThen: (3) I would like to be able to easily go in one of the 3 positions (for example typing TAB could go from one to the next). Dolphin had something equivalent. 2) The pretty printer (ALT+SHIFT+u) should keep all comments where they are and be a bit smarter and more configurable 3) I want AST-based text seletion. Lukas has a screencast where he demonstrates the use of CTRL+SHIFT+Up and CTRL+SHIFT+Down to select larger and larger (respectively smaller and smaller) AST nodes in the source code. Something like https://www.youtube.com/watch?v=fTMX1f8Lu5w and http://youtu.be/_RvHz3vJ3kA?t=52s -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 8, 2013

[Pharo-project] Improving the programmer experience with Pharo (ideas)

by Gisela Decuzzi

Hi, I'm just starting an internship for 3 months and we were talking about the scope for my time here. This is a summary of what we have discussed: The main objective it's to improve the AST and use it to implement as many improvements and refactors/transformations as we can to help the programmer. Some ideas: - distinguish the code scope (for example, when you have lot of blocks all together when you pass over with the mouse that it get special something to understand where you are) - make suggestions depending on what you have selected. Example if it's a variable rename it, or find accesses (...) - highlight selectors - implements some rules to help code improvement, for example if you select some part of the code and it's repeated you can do an: extract method, or extract to variable transformation. - improve the navigation between static code - review the refactoring API and evaluate a change for admitting AST nodes and avoid the use of strings... Please let me know your thoughts about it and if you have more ideas, they are always welcome.

April 8, 2013