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

Re: [Pharo-dev] latex exporter in Pillar

by kilon alios

last time I asked footnotes were not supported by Pillar. However you can use Latex syntax to add a footnote. see section 3.9 here about using Latex syntax ---> https://www.gitbook.io/book/damiencassou/pillar and here is how to add footnotes in Latex ---> http://en.wikibooks.org/wiki/LaTeX/Footnotes_and_Margin_Notes On Wed, Sep 10, 2014 at 2:27 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > How can I have a footnote? > > Alexandre > > > On Sep 7, 2014, at 5:10 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > Hi, > > > > I just tried to do the following: > > > > 1. I took the book skeleton > > https://github.com/pillar-markup/book-skeleton > > > > 2. I executed download.sh > > > > 3. I executed compile.sh > > > > This works out of the box. > > > > Could you point us more exactly to where the problem appears? > > > > Cheers, > > Doru > > > > > > On Fri, Sep 5, 2014 at 9:53 PM, Alexandre Bergel < > alexandre.bergel(a)me.com> wrote: > > I have discovered another problem. > > > > In my latex template I have: > > > > \chapter{{{{title}}}} > > > > In the produced .tex file, this lines becomes > > > > \chapter} > > > > This is a rather serious issue that prevents me from using Pillar :-( > > Is there a chance to see this fixed? > > > > Instead of {{{ â¦ }}} which heavily conflicts with Latex, can it be {-{ â¦ > }-} instead ? > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > On Sep 4, 2014, at 3:03 AM, Damien Cassou <damien.cassou(a)gmail.com> > wrote: > > > >> On Wed, Sep 3, 2014 at 9:24 PM, Alexandre Bergel > >> <alexandre.bergel(a)me.com> wrote: > >>> -=-=-=-= > >>> \newcommand{\ct}[1]} > >>> -=-=-=-= > >> > >> > >> I know the problem. I think this is a bad interaction between the > >> mustache template and LaTeX use of '}}'. > >> > >> The workaround for you would be to specify your own LaTeX template > >> where all macros are in a dedicated external file (copy/paste what we > >> do for the book from > >> > https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english/tr… > ). > >> > >> -- > >> Damien Cassou > >> http://damiencassou.seasidehosting.st > >> > >> "Success is the ability to go from one failure to another without > >> losing enthusiasm." > >> Winston Churchill > >> > > > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Sept. 10, 2014

from time to time I get a crash when increasing the main window size

by stepharo

basicNew value: new: replaceFrom:to:with:startingAt: new: basicNew new: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: value: primShowRectLeft:right:top:bottom: value: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: I will try to reproduce it.

Sept. 10, 2014

Re: [Pharo-dev] OrderedCollection protocols are broken: a potential fix

by Sven Van Caekenberghe

I added a slice for https://pharo.fogbugz.com/f/cases/13985/OrderedCollection-do-and-reverseDo-… On 09 Sep 2014, at 12:53, Nicolai Hess <nicolaihess(a)web.de> wrote: > fogbugz entry for fixing the menu builder > 13979 > PragmaMenuBuilder relies on modifying a collection while iterating over it. > > > > > 2014-09-03 22:59 GMT+02:00 stepharo <stepharo(a)free.fr>: > Clement we should fix the code of the menu :) > > Stef > > > On 3/9/14 15:25, ClÃ©ment Bera wrote: >> Hello, >> >> Sven you are right, the old compiler was consistent in the sense that it always iterated over all the elements, including the ones added with #add: and #addLast: while iterating over the collection. >> On the other hand, VW is consistent with the Opal implementation for #to:do: in the sense that they iterate only on the elements of the collection excluding the ones added while iterating. >> >> #add:after: and co do not work well if you edit the collection while iterating over it for sure :). >> >> It's too late for "don't modify a collection while iterating it" because the system does it, for example, to build the world menu. So I think the solution is in two steps: >> - removing code which edit the collection while iterating over it. As most frameworks work both on Pharo and VW and that the behavior is different I think there shouldn't be that much, so fixing the Pharo image may be enough. >> - be consistent in our collection protocol, basically by rewriting do: and reverseDo: like that: >> >> FROM: >> do: aBlock >> "Override the superclass for performance reasons." >> | index | >> index := firstIndex. >> [index <= lastIndex] >> whileTrue: >> [aBlock value: (array at: index). >> index := index + 1] >> TO: >> do: aBlock >> "Override the superclass for performance reasons." >> firstIndex to: lastIndex do: [ :index | >> aBlock value: (array at: index) ] >> >> >> >> >> >> 2014-09-03 14:05 GMT+02:00 Camille Teruel <camille.teruel(a)gmail.com>: >> >> On 3 sept. 2014, at 11:42, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> >> > Hello guys, >> > >> > I was looking into the OrderedCollection protocols recently to see how well the sista optimizer perform with it methods, and I realized that this is completely broken. >> > >> > For example: >> > >> > col := #(1 2 3 4 5) asOrderedCollection. >> > col do: [ :elem | elem trace . >> > elem < 4 ifTrue: [ col add: col size + 1 ]]. >> > >> > => '12345678' >> > >> > However: >> > >> > col := #(1 2 3 4 5) asOrderedCollection. >> > col collect: [ :elem | elem trace . >> > elem < 4 ifTrue: [ col add: col size + 1 ]]. >> > >> > => '12345' >> > >> > This means that #do: and #reverseDo: iterate over all the elements of the collection,*including* the ones that you are adding while iterating over the collection, whereas all the other OrderedCollection protocols, such as #collect:, #select:, iterates over all the elements of the collection, *excluding* the ones you are adding while iterating over the collection. >> > >> > Marcus argued that one should not edit a collection while iterating over it, however this point is not valid as the World menu relies on this feature, using #do: to iterate over the elements of the OrderedCollection including the one it is adding while iterating over the collection. Changing the implementation makes the world menu display half of its items. >> > >> > I don't like this difference because it is inconsistent. For example, refactoring a #do: into a #collect: can simply not work because they do not iterate over the same elements if you are editing the collection while iterating over it. >> > >> > In VW, the protocols are consistent and iterating over a collection never iterates over the elements one is adding while iterating over it. Therefore, I believe most frameworks should expect this behavior (at least the ones cross smalltalk) which sounds the most correct. >> > >> > I think we should fix the world menu implementation and make the protocols consistent. Alternatively, we can let VW be a much more consistent Smalltalk environment than Pharo. What do you think ? >> >> >> The thing is to find alternative implementations that are efficient enough (no copy). Maybe we can get some inspirations from VW for that (how do they do BTW?). >> You should also check with other kinds of collection because they may act differently than OrderedCollection. >> So in the end it depends on the amount of effort needed to make all collections consistent with this new requirement and on the resulting overhead. >> If it's too much, I think that following the old advice "don't modify a collection while iterating it" is enough. If one really needs to do such kind of things he should consider an alternative design like using a zipper for example. >> >> Camille >> >> > >> > Clement >> > >> >> >> > >

Sept. 10, 2014

Re: [Pharo-dev] Pharo Success Stories on homepage

by Craig Latta

> ...we should always deal with decision makers who are concerned with > business benefits and not technological conformity with the herd. I quite agree, and I'm most interested in success stories which highlight such people. I want to show those stories to those who hesitate because they think they'll have a hard time expanding a team. -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Sept. 10, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40216 Home: https://github.com/pharo-project/pharo-core

Sept. 10, 2014

[pharo-project/pharo-core] da7050: 40216

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: da70500fab822af929ba9ae3f26d4f2ddd015918 https://github.com/pharo-project/pharo-core/commit/da70500fab822af929ba9ae3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-10 (Wed, 10 Sep 2014) Changed paths: M Collections-Sequenceable.package/LinkedList.class/instance/adding/add_after_.st M Collections-Sequenceable.package/LinkedList.class/instance/adding/add_before_.st M Collections-Strings.package/ByteString.class/class/initialization/initialize.st M MenuRegistration.package/PragmaMenuAndShortcutRegistration.class/instance/menu protocol/with_.st M MenuRegistration.package/PragmaMenuBuilder.class/instance/private/interpretRegistration_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script216.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40216.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40216 13979 PragmaMenuBuilder relies on modifying a collection while iterating over it. https://pharo.fogbugz.com/f/cases/13979 13983 Temporary variables not read AND written in LinkedList https://pharo.fogbugz.com/f/cases/13983 13984 Temporary variables not read and written in ByteString class>>#initialize https://pharo.fogbugz.com/f/cases/13984 http://files.pharo.org/image/40/40216.zip

Sept. 10, 2014

Re: [Pharo-dev] latex exporter in Pillar

by Alexandre Bergel

How can I have a footnote? Alexandre On Sep 7, 2014, at 5:10 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I just tried to do the following: > > 1. I took the book skeleton > https://github.com/pillar-markup/book-skeleton > > 2. I executed download.sh > > 3. I executed compile.sh > > This works out of the box. > > Could you point us more exactly to where the problem appears? > > Cheers, > Doru > > > On Fri, Sep 5, 2014 at 9:53 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > I have discovered another problem. > > In my latex template I have: > > \chapter{{{{title}}}} > > In the produced .tex file, this lines becomes > > \chapter} > > This is a rather serious issue that prevents me from using Pillar :-( > Is there a chance to see this fixed? > > Instead of {{{ â¦ }}} which heavily conflicts with Latex, can it be {-{ â¦ }-} instead ? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Sep 4, 2014, at 3:03 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > >> On Wed, Sep 3, 2014 at 9:24 PM, Alexandre Bergel >> <alexandre.bergel(a)me.com> wrote: >>> -=-=-=-= >>> \newcommand{\ct}[1]} >>> -=-=-=-= >> >> >> I know the problem. I think this is a bad interaction between the >> mustache template and LaTeX use of '}}'. >> >> The workaround for you would be to specify your own LaTeX template >> where all macros are in a dedicated external file (copy/paste what we >> do for the book from >> https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english/tr…) >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 9, 2014

Re: [Pharo-dev] Pharo Success Stories on homepage

by phil＠highoctane.be

I know the feeling :-) That's why we should always deal with decision makers who are concerned with business benefits and not technological conformity with the herd. Phil On Tue, Sep 9, 2014 at 5:36 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Yes please. The co-owner of my company asked me, worried, if we were > the only ones using "this technology". > > :) > > Esteban A. Maringolo > > > 2014-09-09 12:33 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > yes, we are slowly uploading themâ¦ maybe we should speed up the process > :) > > > > Esteban > > > > On 09 Sep 2014, at 17:28, Torsten Bergmann <astares(a)gmx.de> wrote: > > > >> The new homepage shows only 2 (!) success story. But we have so many > >> as one can see here: > >> > >> http://rmod.lille.inria.fr/archives/events/2012PharoConf/SuccessStories > >> http://files.pharo.org/successStories > >> > >> This gives a false impression on the homepage to newcomers. If it is a > >> time issue then at least the links should be added. > >> > >> > >> > >> > > > > > >

Sept. 9, 2014

Re: [Pharo-dev] latex exporter in Pillar

by Alexandre Bergel

Yes, it works. I will use that template instead... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Sep 7, 2014, at 5:10 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I just tried to do the following: > > 1. I took the book skeleton > https://github.com/pillar-markup/book-skeleton > > 2. I executed download.sh > > 3. I executed compile.sh > > This works out of the box. > > Could you point us more exactly to where the problem appears? > > Cheers, > Doru > > > On Fri, Sep 5, 2014 at 9:53 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > I have discovered another problem. > > In my latex template I have: > > \chapter{{{{title}}}} > > In the produced .tex file, this lines becomes > > \chapter} > > This is a rather serious issue that prevents me from using Pillar :-( > Is there a chance to see this fixed? > > Instead of {{{ â¦ }}} which heavily conflicts with Latex, can it be {-{ â¦ }-} instead ? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Sep 4, 2014, at 3:03 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > >> On Wed, Sep 3, 2014 at 9:24 PM, Alexandre Bergel >> <alexandre.bergel(a)me.com> wrote: >>> -=-=-=-= >>> \newcommand{\ct}[1]} >>> -=-=-=-= >> >> >> I know the problem. I think this is a bad interaction between the >> mustache template and LaTeX use of '}}'. >> >> The workaround for you would be to specify your own LaTeX template >> where all macros are in a dedicated external file (copy/paste what we >> do for the book from >> https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english/tr…) >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Sept. 9, 2014

Re: [Pharo-dev] New Cog VMs available

by Eliot Miranda

ugh, I am not a good script kiddie. Various bugs in my upload scripts plus a slip in the manifests means I've freshened the files in http://www.mirandabanda.org/files/Cog/VM/VM.r3072. Hopefully these are complete and correct now. On Mon, Sep 8, 2014 at 7:58 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > ...at http://www.mirandabanda.org/files/Cog/VM/VM.r3072. > > CogVM binaries as per VMMaker.oscog-eem.876/r3072 > > Fix bad regression in FilePlugin>>primitiveFileSetPosition introduces > around > r2797 that breaks > 1Gb file access. > > Change manifest files on Windows to make app HIGHDPIAWARE. Create a > manifest for the consolevm and include it in the archive. > > Fix bug with become where duplicate entries in the input > array would crash the system (thanks Igor). > > Make nameOfClass: more robust, in both the real and simulated VMs. > > Regenerate sources after refactoring Slang code to ask classes what methods > they want to include based on their initializationOptions inst var instead > of the centralized VMMaker. > > Generate Spur Newspeak VMs with the new CompiledMethod header format. > This will > break the Newspeak Spur bootstrap until NOF generation and/or loading is > fixed. > > > -- > best, > Eliot > -- best, Eliot

Sept. 9, 2014