- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Use Spotlight to quickly evaluate and inspect short expressions

by phil＠highoctane.be

Opening a workspace and typing in it right away is Cmd-o Cmd-w / Alt-o Alt-w So, the Shift-Enter : thing is faster for some things. As a TWM user, well, tiling workspaces helps when trying to find back a given window, but I do a lot of inspect/explore in the workspace, so this comes in handy. Phil On Tue, Mar 25, 2014 at 4:22 PM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > On Mar 25, 2014, at 10:30 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Opening a workspace for a single expression often is overkill. This > feature is totally keyboard driven and very clean. > > > Sounds okay. > > Need to test it for useful feedback. > > What I like about workspaces is that they have (at least) 3 functions from > the UX point of view: > > 1. frictionless input of code to evaluate (single or multiline) > 2. output when doing cmd-P > 3. user orientation because it will remember you that you were doing > something related to that little code pretty much like that post it in your > desktop > > I get the point about shift+enter+: and getting a command evaluated but a > cmd+[something] could open a workspace and you have more features at the > same price and one keystroke cheaper because you won't need the : to get > something evaluated. > > Plus you'll have to added friction to do something multiline (like a Gofer > load for example) > > You may say, hey I don't want pollution on my desktop, fair enough you > have cmd-w to optionally close it right after use. > > That enables a pretty good flow* > > Hey... I have no complains if it's there > > just sharing how I use workspaces > > *which BTW is interrupted (so broken) by not having the "open new > workspace" key combination as many smalltalk IDE have (so your flow forces > mouse-menu-click before unloading the code of your next evaluation) <- it's > only me or that sounds like a quick fix of high return? > > > > > >

March 25, 2014

Re: [Pharo-dev] Use Spotlight to quickly evaluate and inspect short expressions

by Sebastian Sastre

On Mar 25, 2014, at 10:30 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Opening a workspace for a single expression often is overkill. This feature is totally keyboard driven and very clean. Sounds okay. Need to test it for useful feedback. What I like about workspaces is that they have (at least) 3 functions from the UX point of view: 1. frictionless input of code to evaluate (single or multiline) 2. output when doing cmd-P 3. user orientation because it will remember you that you were doing something related to that little code pretty much like that post it in your desktop I get the point about shift+enter+: and getting a command evaluated but a cmd+[something] could open a workspace and you have more features at the same price and one keystroke cheaper because you wonât need the : to get something evaluated. Plus youâll have to added friction to do something multiline (like a Gofer load for example) You may say, hey I donât want pollution on my desktop, fair enough you have cmd-w to optionally close it right after use. That enables a pretty good flow* Heyâ¦ I have no complains if itâs there just sharing how I use workspaces *which BTW is interrupted (so broken) by not having the âopen new workspaceâ key combination as many smalltalk IDE have (so your flow forces mouse-menu-click before unloading the code of your next evaluation) <- itâs only me or that sounds like a quick fix of high return?

March 25, 2014

Re: [Pharo-dev] Use Spotlight to quickly evaluate and inspect short expressions

by phil＠highoctane.be

AWESOME! (oops, overwhelming enthusiasm effect). Alt-O Alt-W usage is going down in flames with this one. Now, making the spotlight larger is the next step so that we can actually read longer expressions. And $: is just the beginning of prefixes I guess. Phil On Tue, Mar 25, 2014 at 2:30 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I had this idea: > > > https://pharo.fogbugz.com/f/cases/13128/Use-Spotlight-to-quickly-evaluate-a… > > now you can do > > <shift-Enter>:42<Enter> > > to inspect the magic number 42 > > <shift-Enter>:1500*1.25<Enter> > > to quickly compute your 25% raise > > <shift-Enter>:Float pi<Enter> > > to see how many decimals you still remember > > <shift-Enter>:ZnClient new get: 'http://zn.stfx.eu/zn/small.html'<Enter> > > and so on. > > The interaction with the completion menu is not 100% perfect, but pressing > <Space> at the end before <Enter> solves that. > > Feedback ? > > Sven > > PS: I know that many Smalltalk greybeards type everywhere to the same > effect, and that is cool to, but it leaves around dirty windows. Opening a > workspace for a single expression often is overkill. This feature is > totally keyboard driven and very clean. > > PS2: Yes it resembles Emacs' M-: (evaluate-expression), but Pharo is much > cooler, right ;-) > > >

March 25, 2014

Re: [Pharo-dev] Use Spotlight to quickly evaluate and inspect short expressions

by Goubier Thierry

What about doing it that way? <Shift-enter>1500*1.25<Alt-i> ? Like that, you keep the same shortcut and behavior everywhere, and you don't have to answer questions such as: Why typing :42<enter> doesn't work in a workspace? Thierry Le 25/03/2014 14:30, Sven Van Caekenberghe a Ã©crit : > I had this idea: > > https://pharo.fogbugz.com/f/cases/13128/Use-Spotlight-to-quickly-evaluate-a… > > now you can do > > <shift-Enter>:42<Enter> > > to inspect the magic number 42 > > <shift-Enter>:1500*1.25<Enter> > > to quickly compute your 25% raise > > <shift-Enter>:Float pi<Enter> > > to see how many decimals you still remember > > <shift-Enter>:ZnClient new get: 'http://zn.stfx.eu/zn/small.html'<Enter> > > and so on. > > The interaction with the completion menu is not 100% perfect, but pressing <Space> at the end before <Enter> solves that. > > Feedback ? > > Sven > > PS: I know that many Smalltalk greybeards type everywhere to the same effect, and that is cool to, but it leaves around dirty windows. Opening a workspace for a single expression often is overkill. This feature is totally keyboard driven and very clean. > > PS2: Yes it resembles Emacs' M-: (evaluate-expression), but Pharo is much cooler, right ;-) > > > > -- 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

March 25, 2014

Re: [Pharo-dev] Use Spotlight to quickly evaluate and inspect short expressions

by Esteban A. Maringolo

I share with you the impression that a workspace is overkill most of the times. I have different feelings with this. At one side I would preserve spotlight for searching ONLY. And have a separate REPL/cmd prompt docked to some edge (like Autocad's Text Window one). On the other hand I'm a vim user, so I'm used to run commands and search through a single command "mode". It's good to have the option as long as it doesn't interfere with previous behavior though. Esteban A. Maringolo 2014-03-25 10:30 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > I had this idea: > > https://pharo.fogbugz.com/f/cases/13128/Use-Spotlight-to-quickly-evaluate-a… > > now you can do > > <shift-Enter>:42<Enter> > > to inspect the magic number 42 > > <shift-Enter>:1500*1.25<Enter> > > to quickly compute your 25% raise > > <shift-Enter>:Float pi<Enter> > > to see how many decimals you still remember > > <shift-Enter>:ZnClient new get: 'http://zn.stfx.eu/zn/small.html'<Enter> > > and so on. > > The interaction with the completion menu is not 100% perfect, but pressing <Space> at the end before <Enter> solves that. > > Feedback ? > > Sven > > PS: I know that many Smalltalk greybeards type everywhere to the same effect, and that is cool to, but it leaves around dirty windows. Opening a workspace for a single expression often is overkill. This feature is totally keyboard driven and very clean. > > PS2: Yes it resembles Emacs' M-: (evaluate-expression), but Pharo is much cooler, right ;-) > >

March 25, 2014

Re: [Pharo-dev] Use Spotlight to quickly evaluate and inspect short expressions

by Benjamin

I would love to have it the other way around: that Alfred can browse a Pharo image :) Ben On 25 Mar 2014, at 14:41, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Excellent! > > This goes in the direction of Alfred or Quicksilver. I worked on a design (no implementation yet) that goes in the same direction. I think we definitely need to get more in this direction, and that we should make it easy for people to hook their own matchers. For example, when I start something with / or ./ I would like to inspect the file with that name. > > Doru > > > On Tue, Mar 25, 2014 at 2:30 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I had this idea: > > https://pharo.fogbugz.com/f/cases/13128/Use-Spotlight-to-quickly-evaluate-a… > > now you can do > > <shift-Enter>:42<Enter> > > to inspect the magic number 42 > > <shift-Enter>:1500*1.25<Enter> > > to quickly compute your 25% raise > > <shift-Enter>:Float pi<Enter> > > to see how many decimals you still remember > > <shift-Enter>:ZnClient new get: 'http://zn.stfx.eu/zn/small.html'<Enter> > > and so on. > > The interaction with the completion menu is not 100% perfect, but pressing <Space> at the end before <Enter> solves that. > > Feedback ? > > Sven > > PS: I know that many Smalltalk greybeards type everywhere to the same effect, and that is cool to, but it leaves around dirty windows. Opening a workspace for a single expression often is overkill. This feature is totally keyboard driven and very clean. > > PS2: Yes it resembles Emacs' M-: (evaluate-expression), but Pharo is much cooler, right ;-) > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 25, 2014

Re: [Pharo-dev] Use Spotlight to quickly evaluate and inspect short expressions

by Tudor Girba

Excellent! This goes in the direction of Alfred or Quicksilver. I worked on a design (no implementation yet) that goes in the same direction. I think we definitely need to get more in this direction, and that we should make it easy for people to hook their own matchers. For example, when I start something with / or ./ I would like to inspect the file with that name. Doru On Tue, Mar 25, 2014 at 2:30 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I had this idea: > > > https://pharo.fogbugz.com/f/cases/13128/Use-Spotlight-to-quickly-evaluate-a… > > now you can do > > <shift-Enter>:42<Enter> > > to inspect the magic number 42 > > <shift-Enter>:1500*1.25<Enter> > > to quickly compute your 25% raise > > <shift-Enter>:Float pi<Enter> > > to see how many decimals you still remember > > <shift-Enter>:ZnClient new get: 'http://zn.stfx.eu/zn/small.html'<Enter> > > and so on. > > The interaction with the completion menu is not 100% perfect, but pressing > <Space> at the end before <Enter> solves that. > > Feedback ? > > Sven > > PS: I know that many Smalltalk greybeards type everywhere to the same > effect, and that is cool to, but it leaves around dirty windows. Opening a > workspace for a single expression often is overkill. This feature is > totally keyboard driven and very clean. > > PS2: Yes it resembles Emacs' M-: (evaluate-expression), but Pharo is much > cooler, right ;-) > > > -- www.tudorgirba.com "Every thing has its own flow"

March 25, 2014

Use Spotlight to quickly evaluate and inspect short expressions

by Sven Van Caekenberghe

I had this idea: https://pharo.fogbugz.com/f/cases/13128/Use-Spotlight-to-quickly-evaluate-a… now you can do <shift-Enter>:42<Enter> to inspect the magic number 42 <shift-Enter>:1500*1.25<Enter> to quickly compute your 25% raise <shift-Enter>:Float pi<Enter> to see how many decimals you still remember <shift-Enter>:ZnClient new get: 'http://zn.stfx.eu/zn/small.html'<Enter> and so on. The interaction with the completion menu is not 100% perfect, but pressing <Space> at the end before <Enter> solves that. Feedback ? Sven PS: I know that many Smalltalk greybeards type everywhere to the same effect, and that is cool to, but it leaves around dirty windows. Opening a workspace for a single expression often is overkill. This feature is totally keyboard driven and very clean. PS2: Yes it resembles Emacs' M-: (evaluate-expression), but Pharo is much cooler, right ;-)

March 25, 2014

pharocloud.com

by S Krish

Great work..! Hope it grows leaps and bounds like Heroku or AWS..!

March 25, 2014

Re: [Pharo-dev] threading in Pharo

by phil＠highoctane.be

On Tue, Mar 25, 2014 at 1:05 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 24 March 2014 22:54, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > >> On Mon, Mar 24, 2014 at 8:23 PM, Alexandre Bergel < >> alexandre.bergel(a)me.com> wrote: >> >>> >> I am working on a memory model for expandable collection in Pharo. >>> Currently, OrderedCollection, Dictionary and other expandable collections >>> use a internal array to store their data. My new collection library recycle >>> these array instead of letting the garbage collector dispose them. I simply >>> insert the arrays in an ordered collection when an array is not necessary >>> anymore. And I remove one when I need one. >>> > >>> > Hm, is that really going to be worth the trouble? >>> >>> This technique reduces the consumption of about 15% of memory. >>> >>> >> At the end, #add: and #remove: are performed on these polls of >>> arrays. I haven't been able to spot any problem regarding concurrency and I >>> made no effort in preventing them. I have a simple global collection and >>> each call site of "OrderedCollection new" can pick an element of my global >>> collection. >>> >> >>> >> I have the impression that I simply need to guard the access to the >>> global poll, which is basically guarding #add: #remove: and #includes: >>> > >>> > One of the AtomicCollections might be the right things for you? >>> >>> I will have a look at it. >>> >>> >> What is funny, is that I did not care at all about multi-threading >>> and concurrency, and I have not spotted any problem so far. >>> > >>> > There isn't any 'multi-threading' like in Java, you got a much more >>> control version: cooperative on the same priority, preemptive between >>> priorities. >>> > So, I am not surprised. And well, these operations are likely not to >>> be problematic when they are racy, except when the underling data structure >>> could get into an inconsistent state itself. The overall operations >>> (adding/removing/searing) are racy on the application level anyway. >>> > >>> > However, much more interesting would be to know what kind of benefit >>> do you see for such reuse? >>> > And especially, with Spur around the corner, will it still pay off >>> then? Or is it an application-specific optimization? >>> >>> I am exploring a new design of the collection library of Pharo. Not all >>> the (academic) ideas will be worth porting into the mainstream of Pharo. >>> But some of them yes. >>> >>> Thanks for all your help guys! You're great! >>> >>> Cheers, >>> Alexandre >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> An interesting method I stumbled upon which may help in understanding how >> these things do work. >> >> BlockClosure>>valueUnpreemptively >> "Evaluate the receiver (block), without the possibility of preemption >> by higher priority processes. Use this facility VERY sparingly!" >> "Think about using Block>>valueUninterruptably first, and think about >> using Semaphore>>critical: before that, and think about redesigning your >> application even before that! >> After you've done all that thinking, go right ahead and use it..." >> | activeProcess oldPriority result semaphore | >> activeProcess := Processor activeProcess. >> oldPriority := activeProcess priority. >> activeProcess priority: Processor highestPriority. >> result := self ensure: [activeProcess priority: oldPriority]. >> >> > I would not recommend you to use this method for anything. > This method heavily relies on how process scheduler works, and in case of > any changes, it may break everything. > For the sake of programming, one shall never assume there is a way to > "stop the world while i busy doing something". > If you reshape the world, it makes sense. I was looking at how classes were migrated, that's why I found it. And all of the new Pharo way of doing these things. Hey, it is becoming really cool down there. Martin and Camille have been hard at work. Kudos! migrateClasses: old to: new using: anInstanceModification instanceModification := anInstanceModification. old ifEmpty: [ ^ self ]. [ 1 to: old size do: [ :index | self updateClass: (old at: index) to: (new at: index)]. old elementsForwardIdentityTo: new. " Garbage collect away the zombie instances left behind in garbage memory in #updateInstancesFrom: " " If we don't clean up this garbage, a second update would revive them with a wrong layout! " " (newClass rather than oldClass, since they are now both newClass) " Smalltalk garbageCollect. ] valueUnpreemptively KR Phil > > > -- > Best regards, > Igor Stasenko. >

March 25, 2014