May 2015 - Pharo-users - lists.pharo.org

Lectures in africa :)

by stepharo

Hi guys I m back to europe after one week to senegal. There I gave lectures to Dakar 3 h OO advanced design seaside and met Pr. Alassane Bah an old Smalltalker that is eager to push Pharo. I gave him my lectures and we will see what we will do. Then at Saint-Louis I gave lectures two times 3 h. They want to have an advanced oop lectures. Students loved it. I gave a presentation of Pharo to all the reseach group leader of the LIRIMA a lab join with inria and several countries. People from Yaounde want to do something with Pharo :) So be ready to get newbies soon. Stef

May 24, 2015

Re: [Pharo-users] Alt-tab between windows

by Offray Vladimir Luna CÃ¡rdenas

Hi, Comments below. El 20/05/15 a las 07:03, Ben Coman escribiÃ³: > > > On Wed, May 20, 2015 at 3:04 AM, Avdi Grimm <avdi(a)avdi.org > <mailto:avdi@avdi.org>> wrote: > > I dunno if this is useful to anyone, but I was rolling around concepts in my > mind and this is something I came up with: > > Inline image 1 > > This takes some cues from modern IDEs, but it also differs in that it > doesn't make the assumption that you want to see just one "buffer" at a > time, and that "split window mode" isn't sufficiently powerful to handle the > need for lots of windows open on lots of little methods. > > > Interesting idea. It might be better to use a breadcrumb rather than the three > pulldowns and I think Playground tends to need more room. > > One idea I've contemplated, since often my many open windows result from > following some path investigating senders/implementors of other > senders/implementors, is that it would be useful to have a tree structure docked > to the side that records that hierarchical path of investigation. This would > help in cases when I want to back up a few steps to investigate another path but > usually I've lost the needed window (so I just open another one). This would > also help when it came time to prune an investigation, since windows often hang > around longer than needed since its hard to remember which windows below to > which path of investigation. Ideally you might collapse the middle items of a path. > > cheers -ben > Attached is an screenshot[*] of my mockup for a tree-like explorative computing, which I think is in the same lines of Ben's "tree structure docked to the side that records that hierarchical path of investigation". It's wrote on Smalltalk itself and modelled as a document expressed like a tree, which can contain nested nodes of code playgrounds and documentation wrote light markup language (markdown). Its an attempt to make concrete the ideas in an old blog post[1] and I don't know how well is suited for programmers/coders (I'm not one myself), but is more about people which writes and interchanges code with prose (which is my case). [1] http://mutabit.com/offray/static/blog/output/posts/on-deepness-and-complexi… I remember finding Smalltalk in 2005 and having difficulties to be comfortable there, kind of a bittersweet sensation (still there today but in less proportion). On one hand is was a concretion of older ideas of mine about what computation could be (maleable and cognitive empowering), but on the other it was so difficult to connect with my previous experiences with documentation and scripting: The browser hierarchy and "the everything is an object" imposed to much order/paradigm for me. 10 years later, after Pharo, Moose, Leo[2], IPython[3] and others, I'm finding my place again, trying to mix the emergent nature of the tree/document/script with the more structured browser and class and object paradigm. [2] http://leoeditor.com/ [3] http://ipython.org/ If user interface is about experience, we could try to search in sharing our own experiences and mockups what Pharo could be for growing and diverse number of people, even going beyond programmers as a key about this future experience we would like to have. Cheers, Offray [*] In the screenshot you see the tree and 10 open windows, but mostly I go from playgrounds to the document tree to the class browser, switching/cycling tree windows to most of my experience.

May 23, 2015

Re: [Pharo-users] [OT] Pharo pi machine

by Offray Vladimir Luna CÃ¡rdenas

Really nice! I have shared your pictures in the Twittesphere: https://twitter.com/offrayLC/status/602165698119475200 Thanks for sharing, Offray El 17/05/15 a las 07:26, Torsten Bergmann escribiÃ³: > Got my Raspberry Pi B+ with a TontecÂ® 3.5 touch screen display > to bootstrap into Pharo. > > The Raspberry Pi from CI (https://ci.inria.fr/pharo/view/RaspberryPi/) > worked out of the box on Raspbian. Nice! >

May 23, 2015

Re: [Pharo-users] [Pharo-dev] Pillar 0.56 : New features, new syntax

by Ben Coman

This might be a case where is reasonable for both to be valid: @ for backward compatibility # for compatibility with internet conventions cheers -ben On Sat, May 23, 2015 at 8:36 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > Hi. > We used '@' because Pier used it this way. I'm afraid that if we > change the character that will break Pier. > But if you write *Chapter 1>../Chapter1/chapter1.pillar@cha:chapter1* > and export in HTML you'll get > <a href="../Chapter1/chapter1.html#cha:chapter1"> I. Chapter 1 </a> > > On 23 May 2015 at 08:44, Norbert Hartl <norbert(a)hartl.name> wrote: > > Cyril, > > > > Am 22.05.2015 um 23:12 schrieb Cyril Ferlicot <cyril.ferlicot(a)gmail.com > >: > > > > The second main change is the Internal Links. > > Now when you want to reefer to an anchor, a figure or a script you'll > > need to use *@anchor* instead of *anchor*. > > I'm sorry for that but that's the easiest way to implement the > > inter-files links. > > > > > > why @? It is about links and how to point to a fragment inside a > resource. > > This already exists and is called fragment identifier > > > > http://en.wikipedia.org/wiki/Fragment_identifier > > > > You do it by using # the separate the resource and the fragment in an > URI. > > > > '../chapters/chapter1.pillar#section1' > > > > is complete valid URI and the way to go. Can you change that? > > > > Norbert > > > > > > -- > Cheers > Cyril Ferlicot > >

May 23, 2015

Re: [Pharo-users] [Pharo-dev] Pillar 0.56 : New features, new syntax

by Cyril Ferlicot

Hi. We used '@' because Pier used it this way. I'm afraid that if we change the character that will break Pier. But if you write *Chapter 1>../Chapter1/chapter1.pillar@cha:chapter1* and export in HTML you'll get <a href="../Chapter1/chapter1.html#cha:chapter1"> I. Chapter 1 </a> On 23 May 2015 at 08:44, Norbert Hartl <norbert(a)hartl.name> wrote: > Cyril, > > Am 22.05.2015 um 23:12 schrieb Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > > The second main change is the Internal Links. > Now when you want to reefer to an anchor, a figure or a script you'll > need to use *@anchor* instead of *anchor*. > I'm sorry for that but that's the easiest way to implement the > inter-files links. > > > why @? It is about links and how to point to a fragment inside a resource. > This already exists and is called fragment identifier > > http://en.wikipedia.org/wiki/Fragment_identifier > > You do it by using # the separate the resource and the fragment in an URI. > > '../chapters/chapter1.pillar#section1' > > is complete valid URI and the way to go. Can you change that? > > Norbert > -- Cheers Cyril Ferlicot

May 23, 2015

Re: [Pharo-users] Pillar 0.56 : New features, new syntax

by Norbert Hartl

Cyril, > Am 22.05.2015 um 23:12 schrieb Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > > The second main change is the Internal Links. > Now when you want to reefer to an anchor, a figure or a script you'll > need to use *@anchor* instead of *anchor*. > I'm sorry for that but that's the easiest way to implement the > inter-files links. why @? It is about links and how to point to a fragment inside a resource. This already exists and is called fragment identifier http://en.wikipedia.org/wiki/Fragment_identifier <http://en.wikipedia.org/wiki/Fragment_identifier> You do it by using # the separate the resource and the fragment in an URI. '../chapters/chapter1.pillar#section1' is complete valid URI and the way to go. Can you change that? Norbert

May 23, 2015

PhD at Mons

by stepharo

Hi guys there is a PhD opening at Mons and you may probably use Pharo there :). Stef Begin forwarded message: From: Tom MENS <Tom.MENS(a)umons.ac.be> Subject: poste d'assistant Ã Mons Date: 22 May 2015 09:39:31 GMT To: Kim Mens <Kim.Mens(a)uclouvain.be>, Anthony Cleve <anthony.cleve(a)unamur.be>, Anne Etien <anne.etien(a)inria.fr>, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>, Lionel Seinturier <lionel.seinturier(a)lifl.fr>, Laurence Duchien <laurence.duchien(a)lifl.fr>, Martin Monperrus <martin.monperrus(a)univ-lille1.fr> Cc: Laurent Christophe <lachrist(a)vub.ac.be>, Coen De Roover <cderoove(a)vub.ac.be> Bonjour, Si vous connaissez de bons Ã©tudiants souhaitons de faire un thÃ¨se de doctorat en sciences informatiques Ã Mons, sous la forme dâun mandat dâassistant (50% enseignement, 50% recherche), nâhÃ©sitez pas dâinformer les candidats de lâopportunitÃ© suivante. On attends les dossiers pour le 26 juin au plus tard. Tom Mens Begin forwarded message: From: VÃ©ronique BruyÃ¨re <Veronique.Bruyere(a)umons.ac.be> Subject: poste d'assistant Date: 20 May 2015 12:57:26 GMT+2 OUVERTURE D'UN POSTE D'ASSISTANT DÃ©partement d'Informatique FacultÃ© des Sciences, UMONS Le DÃ©partement d'Informatique de la FacultÃ© des Sciences de l'UMONS souhaite engager un/une assistant(e) Ã partir du 15 septembre 2015. Le contrat d'assistant a une durÃ©e dÃ©terminÃ©e de 2 ans, renouvelable deux fois. Enseignement Le/la candidat(e) sera amenÃ©(e) Ã encadrer les travaux pratiques des cours liÃ©s Ã la programmation, lâalgorithmique et les structures de donnÃ©es. Le/la candidat(e) pourrait Ã©galement Ãªtre amenÃ©(e) Ã encadrer les travaux pratiques et exercices d'autres cours enseignÃ©s au DÃ©partement dâInformatique (Ã Mons et Ã horaire dÃ©calÃ© Ã Charleroi). ThÃ¨mes de recherche Le/la candidat(e) devra s'engager dans une thÃ¨se de doctorat. Le sujet de la thÃ¨se sera choisi dans la thÃ©matique de recherche de l'un des services du DÃ©partement d'Informatique, Ã savoir: Algorithmique, GÃ©nie Logiciel, Informatique ThÃ©orique, RÃ©seaux informatiques, et SystÃ¨mes d'Information (voir http://informatique.umons.ac.be/index.php?p=research) Profil Le/la candidat(a) doit Ãªtre dÃ©tenteur d'un diplÃ´me universitaire: Master en Sciences Informatiques, ou Master en Sciences MathÃ©matiques avec une formation suffisante en informatique. En particulier, le/la candidat(e) doit maÃ®triser les langages de programmation Python et Java, et avoir suivi une bonne formation en algorithmique et structures de donnÃ©es. Le/la candidat(e) doit faire preuve de trÃ¨s bonnes qualitÃ©s pÃ©dagogiques et aptitudes Ã la recherche. Le/la candidat(e) doit avoir une trÃ¨s bonne maÃ®trise du franÃ§ais et une bonne connaissance de l'anglais. Contact Envoyer un CV complet et une lettre de motivation Ã VÃ©ronique BruyÃ¨re (veronique.bruyere(a)umons.ac.be) pour le vendredi 26 juin 2015 au plus tard. Des renseignements complÃ©mentaires peuvent Ãªtre obtenus auprÃ¨s de VÃ©ronique BruyÃ¨re. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 03 59 57 78 50 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

May 22, 2015

Pillar 0.56 : New features, new syntax

by Cyril Ferlicot

Hello, today I created the version 0.56 of Pillar and with this version we'll need to do some changes, sorry. The first change is the numerator. The old numerator was too limited, so i changed it. Now if you put different files into the pillar.conf the numerator will not be reset at each files. The parameters 'startNumberingAtHeaderLevel:' and 'stopNumberingAtHeaderLevel:' are replace by 'level1:', 'level2:', 'level3:', 'level4:', 'level5:'. For now they can take 3 sub-parameters: 'numbering', 'size' and 'renderAs'. numbering: a boolean that say if this header level need to be take in account by the numerator. size: the number of level we want to render. You can put numbering at true and size at 0 if you want your numerator to be reset at a level without rendering the number of this level. renderAs: can be number, roman, letter or upperLetter. Example: pillar.conf: { 'level1': { 'numbering': true, 'size': 1, 'renderAs': 'roman' }, 'level2': { 'numbering': true, 'size': 2, 'renderAs': 'number' }, 'level3': { 'numbering': true, 'size': 1, 'renderAs': 'upperLetter' }, 'level4': { 'numbering': true, 'size': 2, 'renderAs': letter }, 'level5': { 'numbering': false }, } document.pillar: ! Example !! Introduction !!! Beginning !!! Example - Intro !!!! Example 1 !!!! Example 2 !!!!! With X !!!!! With Y !! Explanation Result: I. Example I.1. Introduction A. Beginning B. Example - Intro B.a. Example 1 B.b. Example 2 With X With Y I.2. Explanation In the future we could also add feature like 'delimiter'. The second main change is the Internal Links. Now when you want to reefer to an anchor, a figure or a script you'll need to use *@anchor* instead of *anchor*. I'm sorry for that but that's the easiest way to implement the inter-files links. And so the last main change is the Inter-files links ! Imagine you're writing a book. You have a directory 'Chapter1' which contains the file 'chapter1.pillar' and a directory 'Chapter2' with a file 'chapter2.pillar'. If you want to make a reference to the chapter 1 in the chapter 2 you can create an interfile link you can now use the syntax: *../Chapter1/chapter1.pillar* But be careful ! Remember that pillar can export in different format. And you can export a group of file as separate output files or as one file. So if you don't use an Alias your link will not be render if you export as one output file in LaTeX. And if you export in LaTeX or HTML or Markdown as one output file and you don't have an anchor on your link, the link will be vanish. So I recommend to use inter file links like this: *Chapter 1>../Chapter1/chapter1.pillar@cha:chapter1* when cha:chapter1 is an anchor you need to create at the beginning of the chapter 1. I already changed the links on Enterprise Pharo (you can find a table with the list of the inter-files links on the README.md) On last thing for the people who write book for SquareBracketAssociates: It would be good to have some conventions, so if you create anchors use this form : @sec:nameOfSection for a section @cha:nameOfTheChapter for a title of chapter @fig:nameOfFigure for a figure @spt:nameOfTheScript for a script -- Cheers Cyril Ferlicot

May 22, 2015

Re: [Pharo-users] Generate latex from Pharo

by stepharo

> stream := PROutputStream on: String new writeStream. > configuration := PRCocoonConfiguration new. > stream configuration: configuration. > canvas := PRLaTeXCanvas on: stream. > > canvas raw: '$'. > canvas command name: 'frac'; parameter: 'numerator'; parameter: 'denominator'. > canvas raw: '$'. > canvas flush > Why not? stream := PROutputStream on: String new writeStream. canvas := PRLaTeXCanvas on: stream.

May 22, 2015

Re: [Pharo-users] Any way to create multiple accessors in one time?

by stepharo

Yes I was annoyed too by the fact that it is inconsistent in nautilus sometimes you get a tick list sometimes you have to do it one by one. We tried during a sprint with franck to fix this problem and we ended up seeing that there is a kind of bug in the way the rb metamodel is filled up. We entered a bug entry and published some code but it is not ready. Le 17/5/15 18:42, Julien Delplanque a Ã©crit : > Hi everyone, > > The subject is explicit enough... > > I find it annoying when I have to do lots of click to create each > accessors using the gui... :) > > I suppose it's possible to modify the browser to do that but I wonder > if anyone already did it? > > Regards, > > Julien > >

May 22, 2015