- Pharo-dev - lists.pharo.org

Losing instance variable addition

by StÃ©phane Ducasse

Hi guys we are losing instance variables addition when loading a package. Here is the example: Gofer new url: 'http://smalltalkhub.com/mc/gisela/Flamel/main'; version: 'Flamel-GiselaDecuzzi.94'; load Normally RBProgramNode should have three new instance variables and not this is not the case. Is it a known bug? Stef

Oct. 30, 2013

Re: [Pharo-dev] Pharo presentation at Smalltalk 2013

by dimitris chloupis

a minor correction , its not "get an impact" its "have an impact". Great slides , I would love to see the video accompanying the slides . Its really surprising how many new projects Pharo has brought forward. And so many things to look forward to. Keep up the great work and keep motivating us :)Â On Wednesday, 30 October 2013, 19:17, Igor Stasenko <siguctua(a)gmail.com> wrote: i got the message :) On 30 October 2013 16:22, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >http://www.slideshare.net/pharoproject/2013smalltalksconference-pharo-is-yo… > >Stef > -- Best regards, Igor Stasenko.

Oct. 30, 2013

Re: [Pharo-dev] Using Gutenberg

by Damien Cassou

On Wed, Oct 30, 2013 at 5:53 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > 1) If we want something like markdown, why not to use Markdown? 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 :-) > 2) When I think about the book I think about something nice. I donât think that markdown is good for books. Thatâs exactly what I encountered. I wanted to start with this updated version of RBE and wanted to use Gutenberg so it will be possible to put the book on iBook store and Amazon and read it on iDevices and Kindles. But When I started to rewrite latex source in Gutenberg Iâve found that a lot of details are going to be missing, because the is no support in Gutenberg for them. because the code is simple, well tested and written in Smalltalk, we can add the features we need. > Thatâs my main question: why wonât we write books in ePub (because it the #1 eBooks format) and confer it to .mobi (for kindles) as the formats can be converted without a problem. Iâd also enjoy to write books in iBooks Author, but it will be hard to cooperate as not everybody is using Mac. I don't know ePub but from what I can't see, it is not simpler than LaTeX. We want people to write books easily. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 30, 2013

Re: [Pharo-dev] Pharo presentation at Smalltalk 2013

by Igor Stasenko

i got the message :) On 30 October 2013 16:22, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > > > http://www.slideshare.net/pharoproject/2013smalltalksconference-pharo-is-yo… > > Stef > -- Best regards, Igor Stasenko.

Oct. 30, 2013

Re: [Pharo-dev] Using Gutenberg

by Camillo Bruni

On 2013-10-30, at 17:53, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > This makes sense. But I have 2 opinions: > > 1) If we want something like markdown, why not to use Markdown? I burnt my fingers already on markdown :), so the major problem is that we do not have a complete parser yet. The current version is something like 90% ready, but lacks for instance proper support for lists. Feel free to contribute ;): http://smalltalkhub.com/#!/~dh83/petitmarkdown

Oct. 30, 2013

Re: [Pharo-dev] Using Gutenberg

by Yuriy Tymchuk

This makes sense. But I have 2 opinions: 1) If we want something like markdown, why not to use Markdown? 2) When I think about the book I think about something nice. I donât think that markdown is good for books. Thatâs exactly what I encountered. I wanted to start with this updated version of RBE and wanted to use Gutenberg so it will be possible to put the book on iBook store and Amazon and read it on iDevices and Kindles. But When I started to rewrite latex source in Gutenberg Iâve found that a lot of details are going to be missing, because the is no support in Gutenberg for them. Thatâs my main question: why wonât we write books in ePub (because it the #1 eBooks format) and confer it to .mobi (for kindles) as the formats can be converted without a problem. Iâd also enjoy to write books in iBooks Author, but it will be hard to cooperate as not everybody is using Mac. Cheers. Uko On 30 Oct 2013, at 17:36, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Wed, Oct 30, 2013 at 4:09 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> Why do we need Pier-Gutenberg? Why canât we gust use ePub for example? > > We need a simple text based syntax (like for wiki) to write > documentation fast (e.g., books, class comments, method comments). I > don't know ePub, but it looks a lot like HTML, which is way too > verbose for our needs. Gutemberg looks more like Mardown and Org-mode. > The difference with these 2 is that everything is written in Smalltalk > so it is easy to customize to our needs and embed in Pharo (e.g., to > show beautiful class comments in Nautilus, just like in Amber: > http://forum.world.st/attachment/4684866/0/Screen%20Shot%202013-05-02%20at%…) > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Oct. 30, 2013

Re: [Pharo-dev] Using Gutenberg

by Damien Cassou

On Wed, Oct 30, 2013 at 4:09 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Why do we need Pier-Gutenberg? Why canât we gust use ePub for example? We need a simple text based syntax (like for wiki) to write documentation fast (e.g., books, class comments, method comments). I don't know ePub, but it looks a lot like HTML, which is way too verbose for our needs. Gutemberg looks more like Mardown and Org-mode. The difference with these 2 is that everything is written in Smalltalk so it is easy to customize to our needs and embed in Pharo (e.g., to show beautiful class comments in Nautilus, just like in Amber: http://forum.world.st/attachment/4684866/0/Screen%20Shot%202013-05-02%20at%…) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 30, 2013

Re: [Pharo-dev] Using Gutenberg

by Damien Cassou

On Wed, Oct 30, 2013 at 3:36 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Gutemberg is an addon for Pier CMS to write a book in Pier syntax. > It can convert into PDF. Details here: soon Gutemberg will be indepent of Pier and only dependent on Pier syntax and parser (code name 'Pillar') : http://www.smalltalkhub.com/#!/~Pier/Pillar -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 30, 2013

Re: [Pharo-dev] Changing non-copying selectors to #...InPlace

by Sven Van Caekenberghe

On 30 Oct 2013, at 14:06, Max Leske <maxleske(a)gmail.com> wrote: > To continue the discussion on this topic (stemming from issue 11635) Iâm starting a new thread. Please share your thoughts. > > Form the other thread: > >> Personally I'm for more intention revealing selectors; I quite like #shuffled and #shuffleInPlace. If we can agree on a different naming scheme we should then apply it to other methods aswell of course (e.g. #sorted, #sortInPlace). > > My proposition is to keep the selectors named #â¦d (#shuffled, #sorted, etc.), which operate on a copy, and rename the others (#shuffle, #sort, etcâ¦) to #â¦InPlace (#shuffleInPlace, #sortInPlace, etc.). The rational behind this is that (to my mind) the current scheme is not intention revealing (e.g. #shuffle vs. #shuffled). Which is especially problematic for newcomers. > > Max Hmm, I am not sure. If you follow this to its logical conclusion than a huge amount of methods would need an #InPlace suffix. I understand that you are trying so fix a possible confusion, but in the case of sorting the confusion is inherent: if you are lazy, a beginner, or just donât care about performance because the collections are small, getting a sorted copy back is the best solution; but if you care about performance and the collections a large, destructive sorting is a necessary option. Good comments in #sort and #sorted with cross references should help, that is why there are comments.

Oct. 30, 2013

Pharo presentation at Smalltalk 2013

by StÃ©phane Ducasse

http://www.slideshare.net/pharoproject/2013smalltalksconference-pharo-is-yo… Stef

Oct. 30, 2013