Re: [Pharo-users] [Pharo-dev] Pillar 0.56 : New features, new syntax
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 I. Chapter 1 On 23 May 2015 at 08:44, Norbert Hartl wrote: > Cyril, > > Am 22.05.2015 um 23:12 schrieb Cyril Ferlicot : > > 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
Re: [Pharo-users] [Pharo-dev] Pillar 0.56 : New features, new syntax
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 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 > I. Chapter 1 > > On 23 May 2015 at 08:44, Norbert Hartl wrote: > > Cyril, > > > > Am 22.05.2015 um 23:12 schrieb Cyril Ferlicot >: > > > > 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 > >
Re: [Pharo-users] [OT] Pharo pi machine
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!
[Pharo-users] Lectures in africa :)
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
