May 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Understanding Workspace

by stepharo

better use the Tx package of Athens. Stef On 21/5/14 14:10, Tudor Girba wrote: > The first suggestion is to not invest in the PluggableTextMorph :) > > Ideally, we should get the new text widget soon, but in the meantime, > you would be better with using Rubric. It is a pragmatic solution > developed by Alain Plantec and that works now. This is where we are > going with the Glamorous Toolkit at the moment. You find it already in > the Moose image, or you can download it from here: > http://smalltalkhub.com/#!/~AlainPlantec/Rubric > <http://smalltalkhub.com/#%21/%7EAlainPlantec/Rubric> > > Cheers, > Doru > > > On Wed, May 21, 2014 at 12:44 PM, kilon alios <kilon.alios(a)gmail.com > <mailto:kilon.alios@gmail.com>> wrote: > > Hello guys, I have started a new experiment of mine, a tool I call > "Talos". I want Talos to become workspace on steroids. > > The first thing I want to implement is emacs like navigation. With > that I mean keyboard shortcuts for moving inside the text like you > can do with arrow keys already and the ability to move to the next > word , the first character of next word, the last character of > next word , previous world, quickly rename variables and all the > great things one can do with emacs and vim. > > Of course I don't want to do all that at once, one step at a time. > > Now I have take a look at Workspace and it seems that it uses > PlaggableTextMorph , it also looks like I can get the contents via > PluggableTextMorph>>text instance side. The source code returned > is also send to RBParser using the parseBlock method , I think for > syntax highlighting. > > However because the PluggableTextMorph is very big and it does not > even have a class comment, though quite a lot of methods are > commented, I am really open to advice and suggestions on to how to > parse the contents and manipulate the cursor position. > > I know I could use PettitParser but I dont know if there are > better options out there, or maybe I am doing the whole thing wrong. > > So any advice and suggestion is more than welcomed. > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

May 22, 2014

Re: [Pharo-dev] Pharo in Rasbian ?

by phil＠highoctane.be

I'd say that Phratch is another kind of beast. As it has deeper abilities to go down the system, the pragmas blocks things etc. In that, this can be usable by engineers and not kids. I am seeing Phratch as "Scratch for grown ups". >From I saw from the code and plugins etc, there has indeed been a ton of cleanups. One very cool place where we would see it are in fablabs. e.g. Close to where I live - http://makilab.org (this thing is getting its wings ready) - and where I'll introduce Phratch at one point. Jannik, you have given us a powertool. Let's use it as such! Phil On Thu, May 22, 2014 at 9:50 AM, stepharo <stepharo(a)free.fr> wrote: > I think that Jannik started to clean to code long before tim and he is not > payed for that > so at least we should respect that and do not start to blame him about > redundancy. > > And cleaning Scratch is really a MUST because it is full of *&%^&%. > To the point that the people from Scat dropped the maintenance because it > was a NIGHTMARE. > > So can we respect the work of people? > > Stef > > On 21/5/14 18:11, Chris Muller wrote: > >> One reason might be that Phratch is kind of redundant isn't it? >> Smalltalk already has a foothold on the Pi in the form of Squeak, and >> Tim Rowledge is being paid by that organization right now to improve >> Scratch. So if you're interested in helping kids learn programming >> with Scratch, why not check with Tim see if you can find a way help >> with what he's doing..? >> >> On Tue, May 20, 2014 at 10:41 AM, Alexandre Bergel >> <alexandre.bergel(a)me.com> wrote: >> >>> Hi! >>> >>> My point was the following: why Phratch is not included in the default >>> setting of Rasbian? >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> On May 20, 2014, at 9:36 AM, jannik laval <jannik.laval(a)gmail.com> >>> wrote: >>> >>> Hi, >>>> >>>> Probably he does not know phratch for Rasberry-Pi: >>>> https://ci.inria.fr/pharo-contribution/view/Phratch/job/ >>>> Phratch-OneClick-RPi/ >>>> >>>> Cheers :) >>>> >>>> >>>> 2014-05-20 15:32 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >>>> Hi! >>>> >>>> A friend of mine recently bought a Raspberry pi and installed Rasbian, >>>> a Debian-like OS for Raspberry. Squeak and Scratch are installed per >>>> default. There is room to fill here... >>>> >>>> <image001.png> >>>> >>>> Cheers, >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> ~~Jannik Laval~~ >>>> Ãcole des Mines de Douai >>>> Enseignant-chercheur >>>> http://www.jannik-laval.eu >>>> http://www.phratch.com >>>> http://car.mines-douai.fr/ >>>> >>>> >>> >> > >

May 22, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by phil＠highoctane.be

On Thu, May 22, 2014 at 1:18 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > Hi All, > > > On Wed, May 21, 2014 at 3:11 AM, stepharo <stepharo(a)free.fr> wrote: > >> We would love to have a real update but I'm sure that you realize that >> something we >> are modifying the system that modify the methods modifying the system. >> > > but we've been doing that for years. It used to be tricky using change > sets, but Monticello's update scheme means it is very simple. > > >> >> So we should probably remove the software update button. >> Now if somebody wants to work on an infrastructure supporting real atomic >> load. >> > > I don't think one needs atomic load to do this. It is very nice to have > but Monticello's update scheme is sufficient. > > >> Stef >> PS: the last time I updated my iPhone it blocked and I had to fully >> reinstall everything. >> And once when I updated my mac my mouse got blocked forever on the left >> top corner. >> >> But I can't remember the last time an update for Squeak failed and the > updates are of the cool kind you mention. Personally I think having an > update system is a *really important* facility in a development > environment. It means I can keep my personal working environment > up-to-date. That means I'm more likely to be able to contribute my own > improvements to the system. > > I worked for a long time with VisualWorks which has a closed development > cycle, and doesn't support anything like update. Keeping up to date was > always slightly tedious (one had to do things like export one's own stuff > and import it into the latest image, etc). Since I've been using Squeak > I've understood how superior the Monticello scheme is. So I would urge you > to /not/ remove the update button, and instead educate people in the > process so that potentially dangerous changes are done properly (by > defining baselines, a.k.a. updates in Monticello) and hence preserve the > valuable ability to keep one's own image up-to-date. > Mmh, it depends on how one considers images I guess. If the project can be loaded based on a fresh image an packages (and configurations etc), images are throwaway things. Using that approach (with the CI), one can recreate images easily. Okay, it may mean a couple of minutes to rebuild but there are weird behaviors when one messes with an image too much during development (as Ron commented with change sets). Also, when does one updates? Updates on a fresh Pharo30 interest me. But not on my dev image as there are a ton of packages loaded, some slices packed on top to deal with some extra stuff. No wonder that updates on top of that aren,'t going to fly. And Monticello is indeed super cool. Not always that cool with filtree:// based repos but that is maybe because I do not grasp it all properly right now (facing trouble with the metadata style files on merge with Git - yes,filetree here, not gitfiletree - looking scary). Phil > > -- > best, > Eliot >

May 22, 2014

Re: [Pharo-dev] Improving Pharo By Example

by kilon alios

oh yes I completely missed the "examples" option. Great ! One thing less to worry about , thanks Ben :) On Thu, May 22, 2014 at 1:42 AM, Ben Coman <btc(a)openinworld.com> wrote: > kilon alios wrote: > > In section 1.9 page 18 there is this text > > "At other times you may have a good idea that a method exists, but > will have no idea what it might be called. The method finder can still > help! For example, suppose that you would like to find a method that turns > a string into upper case, for example, it would translate 'eureka' into > 'EUREKA'. > > The method finder will suggest a method that does what you want.8 > > An asterisk at the beginning of a line in the right pane of the method > finder indicates that this method is the one that was actually used to > obtain the requested result. So, the asterisk in front of String > asUppercase lets us know that the method asUppercase defined on the class String > was executed and returned the result we wanted. The methods that do not > have an asterisk are just the other methods that have the same name as the > ones that returned the expected result. So CharacterÂ»asUppercase was not > executed on our example, because 'eureka' is not a Character object. > > You can also use the method finder for methods with arguments; for > example, if you are looking for a method that will find the greatest common > factor of two integers, you might try 25. 35. 5 as an example. You can > also give the method finder multiple examples to narrow the search space; > the help text in the bottom pane explains how. " > > I tried " 'eureka' . 'EUREKA '" and the other suggestion it does not seem > to work , should I remove this section ? > > It works for me... > * World > Tools > Finder > * Type... 'eureka' . 'EUREKA' > * Change [Selectors] to [Examples] > > >

May 22, 2014

Re: [Pharo-dev] Pharo in Rasbian ?

by stepharo

I think that Jannik started to clean to code long before tim and he is not payed for that so at least we should respect that and do not start to blame him about redundancy. And cleaning Scratch is really a MUST because it is full of *&%^&%. To the point that the people from Scat dropped the maintenance because it was a NIGHTMARE. So can we respect the work of people? Stef On 21/5/14 18:11, Chris Muller wrote: > One reason might be that Phratch is kind of redundant isn't it? > Smalltalk already has a foothold on the Pi in the form of Squeak, and > Tim Rowledge is being paid by that organization right now to improve > Scratch. So if you're interested in helping kids learn programming > with Scratch, why not check with Tim see if you can find a way help > with what he's doing..? > > On Tue, May 20, 2014 at 10:41 AM, Alexandre Bergel > <alexandre.bergel(a)me.com> wrote: >> Hi! >> >> My point was the following: why Phratch is not included in the default setting of Rasbian? >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> On May 20, 2014, at 9:36 AM, jannik laval <jannik.laval(a)gmail.com> wrote: >> >>> Hi, >>> >>> Probably he does not know phratch for Rasberry-Pi: https://ci.inria.fr/pharo-contribution/view/Phratch/job/Phratch-OneClick-RP… >>> >>> Cheers :) >>> >>> >>> 2014-05-20 15:32 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >>> Hi! >>> >>> A friend of mine recently bought a Raspberry pi and installed Rasbian, a Debian-like OS for Raspberry. Squeak and Scratch are installed per default. There is room to fill here... >>> >>> <image001.png> >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> -- >>> ~~Jannik Laval~~ >>> Ãcole des Mines de Douai >>> Enseignant-chercheur >>> http://www.jannik-laval.eu >>> http://www.phratch.com >>> http://car.mines-douai.fr/ >>> >> >

May 22, 2014

Re: [Pharo-dev] GetText deleting Pharo classes

by Hilaire Fernandes

As long as we keep it external to Pharo I will say it is good practice. But, I am so short in time now, I hope to have more time in a few weeks. Hilaire Le 20/05/2014 10:10, Usman Bhatti a Ã©crit : > My suggestion: > - not to throw away pharo package > - merge pharo package with GetText and name the merged package as > system-localization in Pharo (for default multi-lingual functionality > inside the image). > - write some tests (because currently there are none). > > What do you say? > -- Dr. Geo http://drgeo.eu

May 22, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Freemail

On Thu May 22 01:18:51 2014 Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi All, > > > On Wed, May 21, 2014 at 3:11 AM, stepharo <stepharo(a)free.fr> wrote: > > > We would love to have a real update but I'm sure that you realize that > > something we > > are modifying the system that modify the methods modifying the system. > > > > but we've been doing that for years.Â It used to be tricky using change > sets, but Monticello's update scheme means it is very simple. > > > > > > So we should probably remove the software update button. > > Now if somebody wants to work on an infrastructure supporting real > > atomic load. > > > > I don't think one needs atomic load to do this.Â It is very nice to have > but Monticello's update scheme is sufficient. > > > > Stef > > PS: the last time I updated my iPhone it blocked and I had to fully > > reinstall everything. > > And once when I updated my mac my mouse got blocked forever on the left > > top corner. > > > > But I can't remember the last time an update for Squeak failed and the > updates are of the cool kind you mention.Â Personally I think having an > update system is a *really important* facility in a development > environment.Â It means I can keep my personal working environment > up-to-date.Â That means I'm more likely to be able to contribute my own > improvements to the system. > > I worked for a long time with VisualWorks which has a closed development > cycle, and doesn't support anything like update.Â Keeping up to date was > always slightly tedious (one had to do things like export one's own stuff > and import it into the latest image, etc).Â Since I've been using Squeak > I've understood how superior the Monticello scheme is.Â So I would urge > you to /not/ remove the update button, and instead educate people in the > process so that potentially dangerous changes are done properly (by > defining baselines, a.k.a. updates in Monticello) and hence preserve the > valuable ability to keep one's own image up-to-date. > > -- > best, > Eliot Are we talking about the update menu item in the system menu? I don't understand this discussion, I always use this menu item for updating the image. I thought this is the nomal way. And I never had any problems with that (maybe it works because I use it regulary) How do you keep the image up to date? Nicolai

May 22, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Eliot Miranda

Hi All, On Wed, May 21, 2014 at 3:11 AM, stepharo <stepharo(a)free.fr> wrote: > We would love to have a real update but I'm sure that you realize that > something we > are modifying the system that modify the methods modifying the system. > but we've been doing that for years. It used to be tricky using change sets, but Monticello's update scheme means it is very simple. > > So we should probably remove the software update button. > Now if somebody wants to work on an infrastructure supporting real atomic > load. > I don't think one needs atomic load to do this. It is very nice to have but Monticello's update scheme is sufficient. > Stef > PS: the last time I updated my iPhone it blocked and I had to fully > reinstall everything. > And once when I updated my mac my mouse got blocked forever on the left > top corner. > > But I can't remember the last time an update for Squeak failed and the updates are of the cool kind you mention. Personally I think having an update system is a *really important* facility in a development environment. It means I can keep my personal working environment up-to-date. That means I'm more likely to be able to contribute my own improvements to the system. I worked for a long time with VisualWorks which has a closed development cycle, and doesn't support anything like update. Keeping up to date was always slightly tedious (one had to do things like export one's own stuff and import it into the latest image, etc). Since I've been using Squeak I've understood how superior the Monticello scheme is. So I would urge you to /not/ remove the update button, and instead educate people in the process so that potentially dangerous changes are done properly (by defining baselines, a.k.a. updates in Monticello) and hence preserve the valuable ability to keep one's own image up-to-date. -- best, Eliot

May 21, 2014

Re: [Pharo-dev] JQueryWidgetBox build is green

by Ben Coman

Stephan Eggermont wrote: > ConfigurationOfJQueryWidgetBox > version28 now uses release3.1 of Seaside, which > currently refers to 3.1.0.2. It used to be 3.1.0 > > That makes the Pharo 2 builds green. > > Please note that this configuration should be in two places: > http://www.smalltalkhub.com/mc/Seaside/JQueryWidgetBox/main > http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main' > If you change it, please make sure to copy it to the other location. > > Stephan > > > I don't use these (yet), but its great to see your result. Thanks for your efforts. cheers -ben

May 21, 2014

Re: [Pharo-dev] Improving Pharo By Example

by Ben Coman

May 21, 2014