- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Smart Suggestion Version 1

by Goubier Thierry

Le 24/04/2013 09:22, Marcus Denker a Ã©crit : > > On Apr 24, 2013, at 1:18 AM, Gisela Decuzzi <giseladecuzzi(a)gmail.com > <mailto:giseladecuzzi@gmail.com>> wrote: > >> Hello! After some work I think that Smart Suggestions it's ready to >> have some real feedback to continue growing up :) >> >> What is it? >> The idea it's to have suggestions based in the text selected or the >> cursor position. >> Actually there are suggestions for: >> - Temporary/Instance/Class Variable >> - Class >> - Method (when you are in the selector) >> - Source (multiple lines) >> - Message >> > > Nice! > >> >> If you have some comments I will be very happy to heard about, I have >> removed the actions form nautilus menu, because it was to much visual >> noise (at least for me) if you want to add it, only uncoment the >> pragma in: #SugsMenuBuilder>>addSuggestionToSourceCodeMenu: >> > > Maybe we can make a destination between two cases: > > 1) cursor is placed somewhere. Here people are interested in > suggestions. The context menu like it is now makes sense > (I would add one entry for the suggestions, in addition to the > shortcut) > > 2) The user *selected* something explicitly. Here I think we should show > a modified context menu that only has those things > the make sense on the selection. Nobody want to "Debug it" a > variable, or "print it" a syntactically invalid selection... Hum, this one looks cool. The default action menu is quite long (debugIt, exploreIt, etc...) and making it shorter is a nice touch. > > Marcus > Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

April 24, 2013

Re: [Pharo-project] Smart Suggestion Version 1

by stephane ducasse

+ 1 Interfaces are a cool concept and we should use them and adhere to them conceptually > I am tempted to deprecate #definesMethod: and just rename it to canUnderstand: (and fix all senders) > This way the RB model for code would be one step closer to normal classes and methods.

April 24, 2013

Re: [Pharo-project] Smart Suggestion Version 1

by Marcus Denker

On Apr 24, 2013, at 1:18 AM, Gisela Decuzzi <giseladecuzzi(a)gmail.com> wrote: > Hello! After some work I think that Smart Suggestions it's ready to have some real feedback to continue growing up :) > > What is it? > The idea it's to have suggestions based in the text selected or the cursor position. > Actually there are suggestions for: > - Temporary/Instance/Class Variable > - Class > - Method (when you are in the selector) > - Source (multiple lines) > - Message > Nice! > > If you have some comments I will be very happy to heard about, I have removed the actions form nautilus menu, because it was to much visual noise (at least for me) if you want to add it, only uncoment the pragma in: #SugsMenuBuilder>>addSuggestionToSourceCodeMenu: > Maybe we can make a destination between two cases: 1) cursor is placed somewhere. Here people are interested in suggestions. The context menu like it is now makes sense (I would add one entry for the suggestions, in addition to the shortcut) 2) The user *selected* something explicitly. Here I think we should show a modified context menu that only has those things the make sense on the selection. Nobody want to "Debug it" a variable, or "print it" a syntactically invalid selection... > ps: It could appear a DNU when fetching the suggestions for a class variable the description and solution are in https://pharo.fogbugz.com/default.asp?10380#75204 I am tempted to deprecate #definesMethod: and just rename it to canUnderstand: (and fix all senders) This way the RB model for code would be one step closer to normal classes and methods. The real plan of course is to unify *all* meta models for code and just use Ring. The RBMethod/RBClass hierarchy is one of the candidates for that, PseudoClass and PseudoMethod the other. (I am sure there are eve more). Marcus

April 24, 2013

Re: [Pharo-project] A Pharo launcher

by Damien Cassou

On Wed, Apr 24, 2013 at 8:53 AM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > Nice initiative ! There was already something similar done by > a korean guy: HwaJong Oh (https://twitter.com/Daliot ) > called Pharo Launcher that works only for mac os x. yes, there has been many initiatives around that. But I think we should make something more powerful and cross-platform. I want people to click the 'Pharo' icon and get the full power. People should stop thinking about the vm + the image + the changes + the sources... That's too much -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 24, 2013

Re: [Pharo-project] A Pharo launcher

by Erwan Douaille

Same with Fernando : http://forum.world.st/Pharo-Launcher-app-td4238576.html 2013/4/24 Serge Stinckwich <serge.stinckwich(a)gmail.com> > Nice initiative ! There was already something similar done by > a korean guy: HwaJong Oh (https://twitter.com/Daliot ) > called Pharo Launcher that works only for mac os x. > > Regards, > > On Mon, Apr 22, 2013 at 11:14 PM, Damien Cassou <damien.cassou(a)gmail.com> > wrote: > > I think the idea to have a Pharo launcher that lets the user pick a > > Pharo template (either bare pharo 2.0, pharo+seaside, > > pharo+seaside+mongodb+ > > magritte+voyage, pharo+pier, ...) and then create > > a new image the user must save somewhere is important. I want people > > to have one Pharo icon on their desk and just click it (like in > > Eclipse, word processors, virtual box...). Here is a set of > > requirements for such an application, please comment. > > > > - must be implemented in Pharo 2.0 with maintained technology (spec or > glamour) > > - must be cross-platform (we want 1 application for all Pharo users) > > - must download the list of templates from internet (so that we don't > > have to update the application all the time) > > - must propose different kinds of template (stable/unstable, desktop/web) > > - must rapidly create an image out of the selected template (either by > > downloading Fueled packages, or by downloading ready-made images) > > - must cache the created images so that they do not have to be > > recreated all the time (except when a newer version is available) > > - must force the user to copy the created image so he can freely > > change it and crash it without impacting the cache of created images. > > - must present a list of recently launched images so that the user can > > just pick a recent image instead of creating a new one > > > > > > Please comment (and implement this idea) > > > > -- > > Damien Cassou > > http://damiencassou.seasidehosting.st > > > > "Success is the ability to go from one failure to another without > > losing enthusiasm." > > Winston Churchill > > > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > > -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

April 24, 2013

Re: [Pharo-project] A Pharo launcher

by Serge Stinckwich

Nice initiative ! There was already something similar done by a korean guy: HwaJong Oh (https://twitter.com/Daliot ) called Pharo Launcher that works only for mac os x. Regards, On Mon, Apr 22, 2013 at 11:14 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > I think the idea to have a Pharo launcher that lets the user pick a > Pharo template (either bare pharo 2.0, pharo+seaside, > pharo+seaside+mongodb+ > magritte+voyage, pharo+pier, ...) and then create > a new image the user must save somewhere is important. I want people > to have one Pharo icon on their desk and just click it (like in > Eclipse, word processors, virtual box...). Here is a set of > requirements for such an application, please comment. > > - must be implemented in Pharo 2.0 with maintained technology (spec or glamour) > - must be cross-platform (we want 1 application for all Pharo users) > - must download the list of templates from internet (so that we don't > have to update the application all the time) > - must propose different kinds of template (stable/unstable, desktop/web) > - must rapidly create an image out of the selected template (either by > downloading Fueled packages, or by downloading ready-made images) > - must cache the created images so that they do not have to be > recreated all the time (except when a newer version is available) > - must force the user to copy the created image so he can freely > change it and crash it without impacting the cache of created images. > - must present a list of recently launched images so that the user can > just pick a recent image instead of creating a new one > > > Please comment (and implement this idea) > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

April 24, 2013

[Pharo-project] [ANN] Pharo VM for Ubuntu moved!

by Damien Cassou

After a request from Esteban, I changed the Pharo VM PPA location from ppa:cassou/pharo to ppa:pharo/stable. Please issue the following commands to update your system: $ sudo rm -f /etc/apt/sources.list.d/cassou-emacs-quantal.list $ sudo add-apt-repository ppa:pharo/stable $ sudo apt-get update Sorry for the additional effort -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 24, 2013

Re: [Pharo-project] Metacello Preview

by Ben Coman

DeNigris Sean wrote: > [cross posted to pharo-project and squeak-dev] > > Dale has done some really cool work on Metacello! From the original announcement at http://forum.world.st/Metacello-Preview-release-1-0-beta-32-2-td4642064.html : > >> The Metacello Preview release provides the following features: >> >> - Metacello Scripting API (user guide[1] and reference[2]) >> - Metacello-Base package for inclusion in Squeak/Pharo base images >> - support for git and GitHub (filetree:// and github:// repository loaded) >> > > In typical Dale fashion, he wants to provide our community with as much value as possible, so he's been tentative to release his "preview" version until he gets feedback from users and can tailor it to our real-world needs. > > I feel, after checking with Dale, that integrating the preview into Pharo and Squeak trunk now will provide a balance between exposure and malleability, to make sure we have an API we'll all love by the next respective releases. > > Cheers, > Sean > It natural to want to minimise harm to others by releasing something Clean And Shiny, but the other side of the coin is "Release Early Release Often" [1]. Although having said that, I notice my own behaviour is more CAS than RERO at the moment. I'll have to work on that. cheers -ben [1] http://www.catb.org/esr/writings/homesteading/cathedral-bazaar/ar01s04.html

April 24, 2013

Re: [Pharo-project] Processes, what are they doing?

by Michael van der Gulik

On Wed, Apr 24, 2013 at 11:58 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > In practice it means that one should not write: > [ ... ] fork > > but > > [ ... ] forkWithDescription: 'i doing this that and there' > > Was BlockContext>>forkNamed: removed from the image? Gulik -- http://gulik.pbwiki.com/

April 24, 2013

Re: [Pharo-project] Processes, what are they doing?

by Chris Muller

On Tue, Apr 23, 2013 at 6:58 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Have you ever seen the list of processes running under your OS? > There's many, isn't? > The operating systems may be different, but i'd like to tell, what is > common between all of them: > - by looking at list of processes you have no idea what each of them > there for, nor what are they doing. > > For instance, my home windows machine has strange peaks of disk > activity (when it supposed to be idle, since it is not touched > more than a hour)... > now this is annoying that i cannot ask system in easy way, what is > going on and why such heavy disk activity is needed, > and disable such "very important feature".. Under Linux you can. > Today's systems grown too large and too clever, where user more and > more feels like a passenger (which request to stop the train can be > silently ignored), rather than driver of the train who can stop it at > any moment. > > ...snip... > > Sure thing, i am not proposing to change the world and fix today's > operating systems, but what i thought that at least in Pharo we have a > good > opportunity to fix that. > > I think it would be beneficial to establish a quality standard (or at > least make an attempt to move closer to it): > - each running process should have a description what its purpose and > who/what running it, as well as how to terminate it in non-abrupt way. > > In practice it means that one should not write: > [ ... ] fork > > but > > [ ... ] forkWithDescription: 'i doing this that and there' > > or even: > > [ ... ] forkWithDescription: 'i doing this that and there' > toTerminateDo: [.. block for graciously terminating this process > regardless in which state it currently is ] When I want to name my process I simply avoid the fork shortcut: [ ... ] newProcess name: 'processing items' ; resume I think this is elegant enough to not need forkWithDescription:. > So, my question are you with me or not? :) > And how far? > > 0 - keep things as they are > ... > 1 - deprecate all protocols which allow anonymous process creation, > and force developers to always put a description for every #fork in > their code. > (or simply refuse to #resume the process unless its description is not nil ;) > > There is already field in Process - name. But it is not enforced by > system that it should be never nil. I am not sure if we need both name > and description > or we need just one field (which will serve for both). What i am sure > about is that anonymous processes are BAD. I think all caps overstates it a bit. Forcing the user into an unnecessary API will not help achieve your goal of more lucidity in the system. Maybe a user just wants to open up a workspace and start playing around with Smalltalk processes and show a stranger sitting next to on a plane as a demo how easy it is. He makes some processes in some workspace code and "naming" them via temp variables. So if he is forced to type in a full descriptive name just to satisfy the API, it is distracting so what is he gonna do? "xxx" will be the name of his processes because he didn't want to be bothered with that. No computer can force a human to be clean and organized. I think this type of idea belongs more at an "App-Studio" level than in the general-purpose programming kit (Pharo). That's why MaClientProcess is part of the core-extensions package of the "Ma" application suite. MaClientProcess provides app developers a nice wrapper of a Process that handles name+description, current item being worked, progress, pause, resume and graceful terminate. The only requirement of the app is that it send #advance to the MaClientProcess occasionally to support graceful pause/resume/cancel. Based on the frequency the app sends #advance, MaClientProcess automatically calculates the "rate" of processing items and, if its #taskSize: has been specified, the calculated #timeRemaining.

April 24, 2013