- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo Trick: #0001] - Simple TODO list

by Torsten Bergmann

Did you check the number of senders of #flag: in a recent Pharo image? You will be surprised that not all come from Squeak ;) By sharing I want to just show what is possible and others may find it valuable for their own work in the given or in a customized form. It is not a "best practice", more a "these things helped me" and as a source of inspiration. Bye T. Gesendet:Â Donnerstag, 12. Dezember 2013 um 11:20 Uhr Von:Â "Nicolas Cellier" <nicolas.cellier.aka.nice(a)gmail.com> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] [Pharo Trick: #0001] - Simple TODO list I don't much like this nice idea.Why? see all the (self flags: #toRemove) and such kind of annotations in Squeak.Then tend to last much longer than due.A todo list should have a (short) expiration date.Maybe a method with expired todo should be purely and simply erased ;) Â 2013/12/12 Serge Stinckwich <serge.stinckwich(a)gmail.com>Nice idea Torsten, this kind of tricks ;-) Maybe we can save them online somewhere ? gists.github.com[http://gists.github.com] ? On Wed, Dec 11, 2013 at 12:16 PM, Torsten Bergmann <astares@gmx.de[astares@gmx.de]> wrote: > Hi, > > the mailinglist, stackoverflow and other Pharo related medias are typically used > in the "here is a question to problem" followed by an "answer from community" style. > > But lets also think the other way around: if we already have a solution for a > problem that others may have too or may have in the future we should share the > answer/solution as well. > > I'm sure many of you have some tricks that make developing with Pharo much easier > and others can profit from these tricks if we share them here on the list. > > Be it > Â - a simple and useful script > Â - a simple key combination other may not yet know of > Â - a package one can use or how you use it > Â - a link to a nice description on the web related on how to use Pharo > Â - a custom tool that makes development easier > Â - an algorithm or something that you think was solved very elegant > Â - a way you solved a common problem easily in your app > Â - ... > > Then just describe it in a few lines and post it. Also write in which Pharo > version you tried it - this makes it easier for others to see in which > version the trick/solution is known to work. > > The idea goes like this: if you have a trick to share then send a mail with > subject "Pharo Trick: #xxxx] - Short Description" to the Pharo dev AND Pharo user > list (see http://lists.pharo.org[http://lists.pharo.org]) Make sure to increase the trick counter xxxx. > > Using this special subject one can later easily get the tricks from the > mailinglist archive. Also others can refer to the trick if it solves a common > problem other may ask for on the list. > > Lets see if we are able to reach the goals of 100, 1000 or more Pharo tricks ;) > > Bye > T. > > > I will start with something easy but useful: > > ----------------------------------------------------------------------------------- > [Pharo Trick: #0001] - Simple TODO > ----------------------------------------------------------------------------------- > Works in: Pharo3.0 Latest update: #30635 but should work in other versions too > ----------------------------------------------------------------------------------- > > If you develop an app with Pharo you may not yet fully implement all features. > Some kind of marker for future "ToDo's" is often needed. Using a pragma on a method is > the easiest solution here: > > Â Â foo > Â Â Â <todo: 'Add world later'> > Â Â Â "That method is not yet fully implemented" > > Â Â Â Transcript show: 'Hello' > > > Using a simple expression in the workspace you can browse all the TODOs for your > project afterwards in a window: > > Â Â SystemNavigation default browseAllSendersOf: #todo: > > You can even query the system for the todo descriptions if you need the full > list of things to work on: > > Â (PragmaCollector filter: [:prg | prg keyword = 'todo:']) > Â Â Â Â reset; > Â Â Â Â collect: [:each| each arguments first ] > > As the pragma keyword #todo: is very common and may be used by others too > it may be wise to use a custom one like "myappplicationTodo:" or similar. > ----------------------------------------------------------------------------------- > Â -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/[http://www.doesnotunderstand.org/] Â

Dec. 12, 2013

Re: [Pharo-dev] could we stop to create spaghetti code?

by Esteban Lorenzano

so far icons are all packed together into an icon pack. for example, Pharo3Icons and FamFamIcons. all tools should register their icons there, as extensions of a theme. then, a method: MyClass clas>>#icon ^ Smalltalk ui icons iconNamed: #myIcon can provide enough decoupling. then... is in tool developers the responsibility of follow the pattern (a pattern that is already there, no need of new stuff). Esteban On Thu, Dec 12, 2013 at 12:25 PM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > >> > > > > I think the idea here is that maybe a class should have an icon. > Independend of Nautilus.\ > > (either just icon or toolIcon). > > > > Marcus > > > > > > In a great environment you have icons and icon-sets defined by UX/UI > designers. > > If we couple too much to code we'll create a barrier for that. > > If Nautilus (or whatever other browser) wants to display icons in classes > and packages (which I found great) it should itself provide the code for > that without system intrusion/pollution for the sake of being lazy > > Idea: > > Classes: > > NautilusIconSet > HottishIcons > CoolishIcons > > > WhoeverDisplaysTheClassListItems>>iconFor: aClass > "Returns the icon for aClass or a default icon" > > ^ aNautilusIconSet > at: Integer > ifAbsent:[self defaultIcon] > >

Dec. 12, 2013

Re: [Pharo-dev] [Pharo Trick: #0008] - If appropriate use the memory file system

by Marcus Denker

Related to that: For Pharo4 I want to experiment to have the following: 1) one Memory FileSystem per RPackage (just an ivar there). 2) File Browser support to show all these so one can put files in the package filesystem 3) in Monticello, save all the files as part of the .zip (directory âresourcesâ) 4) When loading with MC, load all files from the resources dir into the package filesystem (at first the file support will be very simple, e.g. no support for diffs). ==> then store e.g. all the icons there instead of a MIME-Encode string. Marcus On 12 Dec 2013, at 12:39, Torsten Bergmann <astares(a)gmx.de> wrote: > ----------------------------------------------------------------------------------- > [Pharo Trick: #0008] - If appropriate use the memory file system > ----------------------------------------------------------------------------------- > Works in: Pharo 2.0, 3.0, ... > ----------------------------------------------------------------------------------- > > It may be possible that your application has to export some > data into an external file in a specific format. Pharo allows writing into > a file using Streams as any other Smalltalk. > > But sometimes you want to check the result right from the Pharo image > without having to look into the external file using external tools. > > So the trick here is to use the memory file system instead > of the real disk file system during development since also no > cleanup on the hard disk is required afterwards: > > |fs| > fs := FileSystem memory. > (fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Exported data' ]. > (fs / 'hello.txt') readStream contents. > > The memory filesystem is also nice if you need to work with files > within a unit test. So when the test runs nothing remains left on the > hard disk. > > If you need a real copy of the file on the hard disk you can also copy > from the memory file system to the disk file system using #copyTo: > > |fs| > fs := FileSystem memory. > (fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Memory first and then disk' ]. > (fs / 'hello.txt') copyTo: (FileSystem disk / 'exactCopy.txt') > >

Dec. 12, 2013

[Pharo Trick: #0008] - If appropriate use the memory file system

by Torsten Bergmann

----------------------------------------------------------------------------------- [Pharo Trick: #0008] - If appropriate use the memory file system ----------------------------------------------------------------------------------- Works in: Pharo 2.0, 3.0, ... ----------------------------------------------------------------------------------- It may be possible that your application has to export some data into an external file in a specific format. Pharo allows writing into a file using Streams as any other Smalltalk. But sometimes you want to check the result right from the Pharo image without having to look into the external file using external tools. So the trick here is to use the memory file system instead of the real disk file system during development since also no cleanup on the hard disk is required afterwards: |fs| fs := FileSystem memory. (fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Exported data' ]. (fs / 'hello.txt') readStream contents. The memory filesystem is also nice if you need to work with files within a unit test. So when the test runs nothing remains left on the hard disk. If you need a real copy of the file on the hard disk you can also copy from the memory file system to the disk file system using #copyTo: |fs| fs := FileSystem memory. (fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Memory first and then disk' ]. (fs / 'hello.txt') copyTo: (FileSystem disk / 'exactCopy.txt')

Dec. 12, 2013

Re: [Pharo-dev] could we stop to create spaghetti code?

by Sebastian Sastre

>> > > I think the idea here is that maybe a class should have an icon. Independend of Nautilus.\ > (either just icon or toolIcon). > > Marcus > > In a great environment you have icons and icon-sets defined by UX/UI designers. If we couple too much to code we'll create a barrier for that. If Nautilus (or whatever other browser) wants to display icons in classes and packages (which I found great) it should itself provide the code for that without system intrusion/pollution for the sake of being lazy Idea: Classes: NautilusIconSet HottishIcons CoolishIcons WhoeverDisplaysTheClassListItems>>iconFor: aClass "Returns the icon for aClass or a default icon" ^ aNautilusIconSet at: Integer ifAbsent:[self defaultIcon]

Dec. 12, 2013

Re: [Pharo-dev] Tell me about your workflow

by Sebastian Sastre

gee the big code package is airflowing which I have, quite conservatively, running on #14438 images I load filetree like this: Gofer new url: 'http://ss3.gemstone.com/ss/FileTree'; package: 'ConfigurationOfFileTree'; load. ((Smalltalk at: #ConfigurationOfFileTree) project version: #'stable') load. and it never complained let me know On Dec 12, 2013, at 3:53 AM, GOUBIER Thierry <thierry.goubier(a)cea.fr> wrote: > If you would be ready to profile a package save on your repository, it would be great. In the mean time, I'll make available a special gitfiletree package to test. Which version of Pharo you are using? 2.0 or 3.0? > > Regards, > > Thierry > > > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Sebastian Sastre [sebastian(a)flowingconcept.com] > Date d'envoi : mercredi 11 dÃ©cembre 2013 17:09 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] Tell me about your workflow > > ok, if saving is dumping all, then 3 is confirmed? After the first commit, I'd say so. > > about 2, I don't know. I'm available to make tests and measure results > > have a nice trip, keep us tuned about any progress > > > > > > > > On Dec 11, 2013, at 2:09 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Yes, you're right in the general case. >> >> But a solution to that general problem will take time to be implemented (time I lack at the moment, sadly) and if the main gain is a few % because it's writing the version file and the metadata for methods which are the "slow" factors, then we'll have worked hard for nothing. >> >> If you want to help, I'd really like to see either 2- or 3- confirmed. I can produce a special gitfiletree to remove writing the metadata, that you can try on a large project temporary copy; if the slow writing (and reading) is confirmed, then this is 3- >> >> (But I'm leaving on a trip tomorrow early, so I have no idea of when I'll have the time to do that :( ). >> >> Thierry >> >> Le 11/12/2013 16:44, Sebastian Sastre a Ã©crit : >>> Without entering in details, a cause for slow package write is dumping >>> all every time. >>> >>> For that strategy, we already have the image save which is magically fast. >>> >>> So, if we make something to scan the code and write only when it's >>> different from what's on disk, then we would be preventing tons of >>> redundant writes >>> >>> sebastian <https://about.me/sebastianconcept> >>> >>> o/ >>> >>> >>> >>> >>> >>> On Dec 11, 2013, at 1:43 PM, Goubier Thierry <thierry.goubier(a)cea.fr >>> <mailto:thierry.goubier@cea.fr>> wrote: >>> >>>> >>>> >>>> Le 11/12/2013 16:27, Esteban Lorenzano a Ã©crit : >>>>> ah, and IMHO the problem is not about reading... is about writing (if it >>>>> has to write the metadata each time...). >>>> >>>> But, personnaly, I don't know if this is the reason for the lack of >>>> performance... >>>> >>>> I have three hypothesis for Sebastian problem: >>>> 1 - Slow read time for version metadata >>>> - Confirmed because of the 16 seconds wait time for reading the >>>> package metadata in the repository browser. >>>> 2 - Slow metadata write >>>> 3 - Slow package write >>>> >>>> I have an implemented solution for 1-, a very easy to implement for >>>> 2-, and none yet for 3- >>>> >>>> So I'd really like to check if 3- is confirmed ;) >>>> >>>> Thierry >>>> >>>>> >>>>> Esteban >>>>> >>>>> >>>>> On Wed, Dec 11, 2013 at 4:24 PM, Esteban Lorenzano >>>>> <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com> >>>>> <mailto:estebanlm@gmail.com>> wrote: >>>>> >>>>> Thierry, I know there is a working version... let me search... >>>>> >>>>> (5 mins later) >>>>> >>>>> >>>>> here: >>>>> >>>>> https://github.com/rjsargent/CypressReferenceImplementation >>>>> >>>>> Dale says Richard made a metadata-less version. >>>>> >>>>> We should take a look at that. >>>>> >>>>> Esteban >>>>> >>>>> >>>>> On Wed, Dec 11, 2013 at 4:28 PM, Goubier Thierry >>>>> <thierry.goubier(a)cea.fr >>>>> <mailto:thierry.goubier@cea.fr><mailto:thierry.goubier@cea.fr>> wrote: >>>>> >>>>> Esteban, Sebastian, >>>>> >>>>> In the filetree code, you will find a format without metadata, >>>>> but it's not in use anymore. >>>>> >>>>> If you use gitfiletree, it will write the metadata for >>>>> compatibility reasons with filetree, but it will never read it >>>>> back. >>>>> >>>>> I'm pushing code to make filetree robust to absence of metadata, >>>>> but I haven't worked on it for a while. >>>>> >>>>> gitfiletree has solved the problem of a slow metadata read. It >>>>> does not solve any performance problem associated with >>>>> writing, yet. >>>>> >>>>> Thierry >>>>> >>>>> Le 11/12/2013 16:12, Esteban Lorenzano a Ã©crit : >>>>> >>>>> I know there is a version of filetree without metadata (more >>>>> compelling >>>>> for projects that will never use other formats). >>>>> Dale told me that there was a preview somewhere, but I >>>>> didn't tested yet >>>>> (lack of time) and now I cannot find the mail... >>>>> Dale, can you re-send the link? >>>>> >>>>> cheers, >>>>> Esteban >>>>> >>>>> >>>>> On Wed, Dec 11, 2013 at 4:08 PM, Sebastian Sastre >>>>> <sebastian(a)flowingconcept.com >>>>> <mailto:sebastian@flowingconcept.com> >>>>> <mailto:sebastian@flowingconcept.com> >>>>> <mailto:sebastian@__flowingconcept.com >>>>> <mailto:sebastian@flowingconcept.com>>> wrote: >>>>> >>>>> I should breath before I type, but you probably already >>>>> got that I >>>>> meant /redundant writes/ (not reads)... >>>>> >>>>> >>>>> Anyway.. I was talking with Esteban and he mentions >>>>> some kind of >>>>> compatibility metadata. >>>>> >>>>> If I'm going to give a leap of faith to filetree repos >>>>> to save code >>>>> why should I care about mcz compatibility? Paying a >>>>> toll for no >>>>> reason is evil. >>>>> >>>>> Maybe we could make that optional so those who don't >>>>> extract value >>>>> from that feature can opt-out? >>>>> >>>>> sebastian <https://about.me/__sebastianconcept >>>>> <https://about.me/sebastianconcept>> >>>>> >>>>> >>>>> o/ >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Dec 11, 2013, at 12:44 PM, Sebastian Sastre >>>>> <sebastian(a)flowingconcept.com >>>>> <mailto:sebastian@flowingconcept.com> >>>>> <mailto:sebastian@flowingconcept.com> >>>>> <mailto:sebastian@__flowingconcept.com >>>>> <mailto:sebastian@flowingconcept.com>>> >>>>> wrote: >>>>> >>>>> Hi Thierry >>>>> >>>>> On Dec 11, 2013, at 12:43 PM, Goubier Thierry >>>>> <thierry.goubier(a)cea.fr >>>>> <mailto:thierry.goubier@cea.fr> >>>>> <mailto:thierry.goubier@cea.fr> >>>>> <mailto:thierry.goubier@cea.fr >>>>> <mailto:thierry.goubier@cea.fr>__>> wrote: >>>>> >>>>> >>>>> I have packages (in the order of hundreds >>>>> of classes) and save >>>>> delays >>>>> and package click delays are starting to >>>>> demand patience in a >>>>> way that >>>>> doesn't feel like the right path >>>>> >>>>> >>>>> Which operations ? I didn't remember noticing >>>>> much with 179 >>>>> classes on a laptop without a SSD. >>>>> >>>>> >>>>> choose one. Just for clicking the package that will >>>>> should you >>>>> UUID, version and author I need to wait ~16 >>>>> seconds. Sounds like a >>>>> lot of overhead for reading a small .json file. >>>>> >>>>> But the write is the most worrisome >>>>> >>>>> >>>>> All that is with a SSD disk, otherwise save >>>>> delays would be >>>>> /way/ beyond >>>>> unacceptable >>>>> >>>>> >>>>> I'd like to know more, and understand the >>>>> reason, for sure. As >>>>> far as I know, filetree will rewrite the whole >>>>> package to disk >>>>> everytime... and maybe optimising that could be >>>>> the solution. >>>>> >>>>> >>>>> Well, that explains a lot. Writing all every time >>>>> is the lazy >>>>> thing that's okay for a prototype and temporary >>>>> code in a proof of >>>>> concept but that massive redundant reads certainly >>>>> doesn't sounds >>>>> like pro software. Specially for SSD's which has a >>>>> limited >>>>> quantity of writes >>>>> >>>>> >>>>> Thierry >>>>> >>>>> sebastian >>>>> <https://about.me/__sebastianconcept >>>>> <https://about.me/sebastianconcept>> >>>>> >>>>> o/ >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> 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 >>>>> <tel:%2B33%20%280%29%201%2069%2008%2032%2092> >>>>> <tel:%2B33%20%280%29%201%2069%__2008%2032%2092> >>>>> / 83 95 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> 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 >>>>> <tel:%2B33%20%280%29%201%2069%2008%2032%2092> / 83 95 >>>>> >>>>> >>>>> >>>> >>>> -- >>>> 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 >>> >> >> -- >> 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

Dec. 12, 2013

Re: [Pharo-dev] [Pharo Trick: #0004] - Run code using a key command to speedup development

by Benjamin

Then maybe Komitter should use this mechanism instead of registering to World. But I am not sure if letting the possibilities to someone to override it locally is bad or not Ben On 12 Dec 2013, at 11:50, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Yes regarding the bindKeymapping:toAction: > > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… > > - the bubbling explanation needs more love > - the global categories are not yet there > > How do I add figures with the pier sintax? :) > > > On Thu, Dec 12, 2013 at 11:27 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > guille > > is the keymapping chapter up to date to that regards. > It would be good to explain better the bubble and the global binding. > If you have one hour it would be good. > > Stef > > On Dec 12, 2013, at 11:11 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > >> The world morph was initially intended to handle the global system shortcuts, taking advantage of the event bubbling. However, that posed the fact that the global shortcuts have less priority than other shortcuts. The bubbling will activate a global shortcut only if it they key event did not activated a shortcut of its childs first. >> >> So we changed that, and there is another mechanism to install global shortcuts in the system. An example of it is installed in the system: SpotlightShortcuts >> >> >> On Thu, Dec 12, 2013 at 10:59 AM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> BTW, no world binding has yet been initialized yet in Pharo 3.0 (but CMD+K) >> Is it intentional? >> see http://stackoverflow.com/questions/17886061/switch-between-open-windows-in-… >> >> >> 2013/12/12 phil(a)highoctane.be <phil(a)highoctane.be> >> >> Very sweet indeed. >> >> Phil >> >> >> >> On Thu, Dec 12, 2013 at 9:42 AM, Max Leske <maxleske(a)gmail.com> wrote: >> Nice! Didnât know about that one. >> >> >> On 12.12.2013, at 09:35, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> > ----------------------------------------------------------------------------------- >> > [Pharo Trick: #0004] - Run code using a key command to speedup development >> > ----------------------------------------------------------------------------------- >> > Works in: Pharo3.0 Latest update: #30637 but should work in other 2.0/3.0 versions >> > ----------------------------------------------------------------------------------- >> > >> > If you have to run some code very often you typically have to evaluate it >> > from a workspace over and over again. >> > But to speed up you can assign a global keymapping which allows to run it with >> > a simple keyboard shortcut: >> > >> > World >> > on: $a shift command >> > do: [ Object browse ]. >> > >> > Evaluate this once in a workspace. After that anytime you press SHIFT, the >> > command button (on Windows this is ALT) and A together the block gets evaluated >> > and your code runs easily. >> > >> > Background: >> > =========== >> > In Pharo there is a global morph called "World" representing the desktop. >> > One can assign a key combination to any morph including this world. >> > If you are interested on the Keymappings then read http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… >> > for more >> > >> >> >> >> >> > >

Dec. 12, 2013

Re: [Pharo-dev] [Pharo Trick: #0004] - Run code using a key command to speedup development

by Benjamin

https://github.com/DamienCassou/pier-cl/blob/master/CheatSheet.pier.md +caption>file://figures/image.png+ Ben On 12 Dec 2013, at 11:50, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Yes regarding the bindKeymapping:toAction: > > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… > > - the bubbling explanation needs more love > - the global categories are not yet there > > How do I add figures with the pier sintax? :) > > > On Thu, Dec 12, 2013 at 11:27 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > guille > > is the keymapping chapter up to date to that regards. > It would be good to explain better the bubble and the global binding. > If you have one hour it would be good. > > Stef > > On Dec 12, 2013, at 11:11 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > >> The world morph was initially intended to handle the global system shortcuts, taking advantage of the event bubbling. However, that posed the fact that the global shortcuts have less priority than other shortcuts. The bubbling will activate a global shortcut only if it they key event did not activated a shortcut of its childs first. >> >> So we changed that, and there is another mechanism to install global shortcuts in the system. An example of it is installed in the system: SpotlightShortcuts >> >> >> On Thu, Dec 12, 2013 at 10:59 AM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> BTW, no world binding has yet been initialized yet in Pharo 3.0 (but CMD+K) >> Is it intentional? >> see http://stackoverflow.com/questions/17886061/switch-between-open-windows-in-… >> >> >> 2013/12/12 phil(a)highoctane.be <phil(a)highoctane.be> >> >> Very sweet indeed. >> >> Phil >> >> >> >> On Thu, Dec 12, 2013 at 9:42 AM, Max Leske <maxleske(a)gmail.com> wrote: >> Nice! Didnât know about that one. >> >> >> On 12.12.2013, at 09:35, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> > ----------------------------------------------------------------------------------- >> > [Pharo Trick: #0004] - Run code using a key command to speedup development >> > ----------------------------------------------------------------------------------- >> > Works in: Pharo3.0 Latest update: #30637 but should work in other 2.0/3.0 versions >> > ----------------------------------------------------------------------------------- >> > >> > If you have to run some code very often you typically have to evaluate it >> > from a workspace over and over again. >> > But to speed up you can assign a global keymapping which allows to run it with >> > a simple keyboard shortcut: >> > >> > World >> > on: $a shift command >> > do: [ Object browse ]. >> > >> > Evaluate this once in a workspace. After that anytime you press SHIFT, the >> > command button (on Windows this is ALT) and A together the block gets evaluated >> > and your code runs easily. >> > >> > Background: >> > =========== >> > In Pharo there is a global morph called "World" representing the desktop. >> > One can assign a key combination to any morph including this world. >> > If you are interested on the Keymappings then read http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… >> > for more >> > >> >> >> >> >> > >

Dec. 12, 2013

Re: [Pharo-dev] [Pharo Trick: #0004] - Run code using a key command to speedup development

by Guillermo Polito

Yes regarding the bindKeymapping:toAction: https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… - the bubbling explanation needs more love - the global categories are not yet there How do I add figures with the pier sintax? :) On Thu, Dec 12, 2013 at 11:27 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > guille > > is the keymapping chapter up to date to that regards. > It would be good to explain better the bubble and the global binding. > If you have one hour it would be good. > > Stef > > On Dec 12, 2013, at 11:11 AM, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > The world morph was initially intended to handle the global system > shortcuts, taking advantage of the event bubbling. However, that posed the > fact that the global shortcuts have less priority than other shortcuts. The > bubbling will activate a global shortcut only if it they key event did not > activated a shortcut of its childs first. > > So we changed that, and there is another mechanism to install global > shortcuts in the system. An example of it is installed in the > system: SpotlightShortcuts > > > On Thu, Dec 12, 2013 at 10:59 AM, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> BTW, no world binding has yet been initialized yet in Pharo 3.0 (but >> CMD+K) >> Is it intentional? >> see >> http://stackoverflow.com/questions/17886061/switch-between-open-windows-in-… >> >> >> 2013/12/12 phil(a)highoctane.be <phil(a)highoctane.be> >> >> Very sweet indeed. >>> >>> Phil >>> >>> >>> >>> On Thu, Dec 12, 2013 at 9:42 AM, Max Leske <maxleske(a)gmail.com> wrote: >>> >>>> Nice! Didnât know about that one. >>>> >>>> >>>> On 12.12.2013, at 09:35, Torsten Bergmann <astares(a)gmx.de> wrote: >>>> >>>> > >>>> ----------------------------------------------------------------------------------- >>>> > [Pharo Trick: #0004] - Run code using a key command to speedup >>>> development >>>> > >>>> ----------------------------------------------------------------------------------- >>>> > Works in: Pharo3.0 Latest update: #30637 but should work in other >>>> 2.0/3.0 versions >>>> > >>>> ----------------------------------------------------------------------------------- >>>> > >>>> > If you have to run some code very often you typically have to >>>> evaluate it >>>> > from a workspace over and over again. >>>> > But to speed up you can assign a global keymapping which allows to >>>> run it with >>>> > a simple keyboard shortcut: >>>> > >>>> > World >>>> > on: $a shift command >>>> > do: [ Object browse ]. >>>> > >>>> > Evaluate this once in a workspace. After that anytime you press >>>> SHIFT, the >>>> > command button (on Windows this is ALT) and A together the block gets >>>> evaluated >>>> > and your code runs easily. >>>> > >>>> > Background: >>>> > =========== >>>> > In Pharo there is a global morph called "World" representing the >>>> desktop. >>>> > One can assign a key combination to any morph including this world. >>>> > If you are interested on the Keymappings then read >>>> http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… >>>> > for more >>>> > >>>> >>>> >>>> >>> >> > >

Dec. 12, 2013

Re: [Pharo-dev] [Pharo Trick: #0004] - Run code using a key command to speedup development

by StÃ©phane Ducasse

guille is the keymapping chapter up to date to that regards. It would be good to explain better the bubble and the global binding. If you have one hour it would be good. Stef On Dec 12, 2013, at 11:11 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > The world morph was initially intended to handle the global system shortcuts, taking advantage of the event bubbling. However, that posed the fact that the global shortcuts have less priority than other shortcuts. The bubbling will activate a global shortcut only if it they key event did not activated a shortcut of its childs first. > > So we changed that, and there is another mechanism to install global shortcuts in the system. An example of it is installed in the system: SpotlightShortcuts > > > On Thu, Dec 12, 2013 at 10:59 AM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > BTW, no world binding has yet been initialized yet in Pharo 3.0 (but CMD+K) > Is it intentional? > see http://stackoverflow.com/questions/17886061/switch-between-open-windows-in-… > > > 2013/12/12 phil(a)highoctane.be <phil(a)highoctane.be> > > Very sweet indeed. > > Phil > > > > On Thu, Dec 12, 2013 at 9:42 AM, Max Leske <maxleske(a)gmail.com> wrote: > Nice! Didnât know about that one. > > > On 12.12.2013, at 09:35, Torsten Bergmann <astares(a)gmx.de> wrote: > > > ----------------------------------------------------------------------------------- > > [Pharo Trick: #0004] - Run code using a key command to speedup development > > ----------------------------------------------------------------------------------- > > Works in: Pharo3.0 Latest update: #30637 but should work in other 2.0/3.0 versions > > ----------------------------------------------------------------------------------- > > > > If you have to run some code very often you typically have to evaluate it > > from a workspace over and over again. > > But to speed up you can assign a global keymapping which allows to run it with > > a simple keyboard shortcut: > > > > World > > on: $a shift command > > do: [ Object browse ]. > > > > Evaluate this once in a workspace. After that anytime you press SHIFT, the > > command button (on Windows this is ALT) and A together the block gets evaluated > > and your code runs easily. > > > > Background: > > =========== > > In Pharo there is a global morph called "World" representing the desktop. > > One can assign a key combination to any morph including this world. > > If you are interested on the Keymappings then read http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… > > for more > > > > > > >

Dec. 12, 2013