- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Using Gutenberg

by StÃ©phane Ducasse

>>>> >>> >>> I have nothing against pier syntax. But imagine person coming from outside, who used markdown to ask questions on stack overflow and write readmes on github, and here he has to use a different syntax for the same purpose. Just a thought about bringing new people into a community :) >> >> with the same attitute, why do you do smalltalk when there is JS? > > I donât see what is new in Pier. I do not get what something would have to be new in pier. It just WORKS for what it was built and before markdown came alone. OK the world is going to use makrdown until a guy in power will be feed up and add an extension to github and the world will be happy and cry of joy. We are not such people but we have a working solution so that we can write versioned, syntax neutral books and documentation. And we will do it. > Now I know a plan about big extension. Can you understand that pier is working for us? And that we spent time making sure that we can have an infrastructure to really produce documents with it. So why suddenly we should abandon it. Can you think two minutes in our place? Stef here is the pier syntax do you tell me that this is difficult to learn? ! header !! !!! list - # ref * * [[[ code ]]] ==code== So

Oct. 31, 2013

Re: [Pharo-dev] Using Gutenberg

by StÃ©phane Ducasse

On Oct 30, 2013, at 10:36 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > On 30 Oct 2013, at 21:48, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >>>> >>>> >>>> markdown misses a lot of features we need to write a book as you >>>> highlight in your next point. So I don't understand your question :-) >>> >>> If you want to write a comment and display it in Amber I donât see why people have to learn a new markup language when there is markdown. >> >> Because you learn markdown first but pier syntax predates it. and because like that we have one syntax for everything. >> Did you notice that the seaside book was fully written with this syntax and it WORKS!!! > > For me itâs like stating that weâll make one car that will be able to win both Formula 1 and Dakar Rally. sorry but you are wrong. But this is your right not to see what we are doing. >>>>> > > Just talking about newcomers. Ok so they can learn Smalltalk but they cannot learn two changes from markdown. So yes let us focus on them they will write books and documentation for sure. Stef

Oct. 31, 2013

Re: [Pharo-dev] Using Gutenberg

by StÃ©phane Ducasse

Yury could you listen and read what we write? We want one common format so that we can output all the others and like that we do not have "this is in pdf but not in HTML so google cannot find the information" kind of complaint. And we have that! Gutenberg is generating HTML + PDF + whatever we want. So I do not get where is the problem. ANd the solution worked because we wrote with lukas the seaside book in pier format on the web and the book that people buy is based on the web so I do not get you. Stef

Oct. 31, 2013

Fwd: [ci-announces] Imminent maintenance

by Camillo Bruni

We're good again :) Begin forwarded message: > From: Emmanuel Jeanvoine <emmanuel.jeanvoine(a)inria.fr> > Hello, > > After a difficult investigation, the IT team has fixed the problem. > All the slaves have also been restarted and the CI service is now fully > working. If the Jenkins instance of the projects fail to see the > slaves, you can restart them using the web portal > (http://ci.inria.fr) In case of problem, do not hesitate to contact > the support team (ci-support(a)inria.fr) > > Sorry again for the downtime, > Emmanuel.

Oct. 31, 2013

Re: [Pharo-dev] inria ci problem - content encoding error when clicking 'new job' in JobTemplate page

by Camillo Bruni

probably :), I put you on admin, could you try again? On 2013-10-29, at 15:29, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Is this error happening because my user is neither an Admin nor a Slave Admin > and therefore I cannot create jobs? > > > Thanks > > Paul > > > Paul DeBruicker wrote >> Hi - >> >> >> After logging in, when I visit this page: >> >> https://ci.inria.fr/pharo-contribution/view/all/newJob >> >> I get a 'content encoding error' and nothing is displayed in the browser. >> >> >> Is there another way to create a job? >> >> >> Thanks >> >> Paul > > > > > > -- > View this message in context: http://forum.world.st/inria-ci-problem-content-encoding-error-when-clicking… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 31, 2013

Re: [Pharo-dev] My talk today at Smalltalks 2013

by Esteban Lorenzano

ouch! On Oct 31, 2013, at 8:03 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Cool. Just a notice, Spec is mentioned two times on slide 4. > > -- Pavel > > 2013/10/30 Esteban Lorenzano <estebanlm(a)gmail.com>: >> Here are the slides: >> >> http://www.slideshare.net/pharoproject/smalltalks13-pharo-techoverview >> >> I think it didn't went so bad... :) >> >> Esteban >> >

Oct. 31, 2013

Re: [Pharo-dev] Losing instance variable addition

by Esteban Lorenzano

I'm with Doru here, we already have the capability of extend completely the system (not just to extend methods). Even if can be dangerous, that's a choice of the user. Our tools should empower the features of the language, not restrict them. On Oct 31, 2013, at 7:49 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-10-31, at 09:55, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > >> Basically here we discuss how to introduce in Pharo stateful class extension and stateful traits. I like these features a lot because it means I would be able to reuse the same class differently depending on the context and the surrounding classes. But if we overuse that we will definitely go into chaos. Martin tried in Mist and he concluded that he should have class composition instead of stateful traits / class extension. > > right, using stateful traits a quite a bit different than directly adding inst vars ;). > This way you can easily ensure that the added variable is only visible to the new code and hence you do not run into the override limbo. Now that we have first-class slots, doing these things gets much easier (note that stateful traits was an example implementation in the slot paper). > > I think the resulting "mess", which we already have with normal traits, is the lack of tools. For instances, pharo didn't properly respect traits in the IDE for years with the result that most of the trait methods slowly vanished.

Oct. 31, 2013

Changes in change browser or lists, a bug?

by Gisela Decuzzi

I wanted to navigate between changes in change browser and it seems that is only possible using the checkbox, here is the case: https://pharo.fogbugz.com/f/cases/12046/Select-change-in-changeBrowser-clic… But not sure if this is a bug

Oct. 31, 2013

Re: [Pharo-dev] My talk today at Smalltalks 2013

by Pavel Krivanek

Cool. Just a notice, Spec is mentioned two times on slide 4. -- Pavel 2013/10/30 Esteban Lorenzano <estebanlm(a)gmail.com>: > Here are the slides: > > http://www.slideshare.net/pharoproject/smalltalks13-pharo-techoverview > > I think it didn't went so bad... :) > > Esteban >

Oct. 31, 2013

Jenkins Down

by Camillo Bruni

With a one day grace period [1] all our Jenkins instances are now down, the only slaves that remains is our mac slave. [1] https://wiki.inria.fr/ciportal/Event_20131030_cs best regards, camillo

Oct. 31, 2013