November 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Fuel: fix for Squeak trunk

by Nicolas Cellier

I've opened https://code.google.com/p/fuel/issues/detail?id=204 with an attachment Also note https://pharo.fogbugz.com/f/cases/12052/Fuel-could-store-LargeNegativeInteg… 2013/11/2 Max Leske <maxleske(a)gmail.com> > So far we donât have a public inbox and Iâm not too familiar with STHub > and read/write permissions. Concerning your suggestion from the other > thread a public inbox would certainly make sense though. > Iâll let you know what we can come up with (STHub seems to be down right > now so I canât even give you access right now. But you can send me your fix > through mail). > > Max > > On 02.11.2013, at 09:46, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > Thanks, and is there a public .mcz inbox, or does it require special > rights? > > > 2013/11/2 Max Leske <maxleske(a)gmail.com> > >> The Fuel bug tracker is hosted by Google: https://code.google.com/p/fuel/ >> >> On 01.11.2013, at 22:42, Nicolas Cellier < >> nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> > I have an easy fix for Fuel on Squeak trunk. >> > It concerns the FuelCompatibility layer, so I hesitate to publish on >> Pharo fogbugz... >> > Is there a dedicated bug tracker? >> > What is the preferred procedure? >> > >> > Nicolas >> >> >> > >

Nov. 2, 2013

[pharo-project/pharo-core]

by GitHub

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

Nov. 2, 2013

[pharo-project/pharo-core] 621d1a: 30535

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 621d1a92551b11f3dcefe280c25a5cbeb4b03e5e https://github.com/pharo-project/pharo-core/commit/621d1a92551b11f3dcefe280… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-02 (Sat, 02 Nov 2013) Changed paths: A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script190.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30535.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/README.md A Text-Scanning.package/LegacyCharacterBlockScanner.class/definition.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/private/characterPointSetX_.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/private/lastCharacterExtentSetX_.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/private/lastSpaceOrTabExtentSetX_.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/scanning/characterBlockAtPoint_index_in_.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/scanning/indentationLevel_.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/scanning/placeEmbeddedObject_.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/stop conditions/cr.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/stop conditions/crossedX.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/stop conditions/endOfRun.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/stop conditions/paddedSpace.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/stop conditions/setFont.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/stop conditions/setStopConditions.st A Text-Scanning.package/LegacyCharacterBlockScanner.class/instance/stop conditions/tab.st A Text-Scanning.package/LegacyCharacterScanner.class/README.md A Text-Scanning.package/LegacyCharacterScanner.class/class/class initialization/initialize.st A Text-Scanning.package/LegacyCharacterScanner.class/definition.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/initialization/initialize.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/initialize/initializeStringMeasurer.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/initialize/wantsColumnBreaks_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/private/addEmphasis_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/private/addKern_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/private/setActualFont_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/private/setAlignment_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/private/setConditionArray_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/private/setFont_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/private/textColor_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/private/text_textStyle_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanner methods/columnBreak.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanner methods/isBreakableAtIndex_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanner methods/scanJapaneseCharactersFrom_to_in_rightX_stopConditions_kern_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanner methods/scanMultiCharactersFrom_to_in_rightX_stopConditions_kern_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanner methods/setFont.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanning/basicScanCharactersFrom_to_in_rightX_stopConditions_kern_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanning/embeddedObject.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanning/handleIndentation.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanning/indentationLevel.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanning/indentationLevel_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanning/leadingTab.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanning/measureString_inFont_from_to_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanning/placeEmbeddedObject_.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanning/plainTab.st A Text-Scanning.package/LegacyCharacterScanner.class/instance/scanning/scanCharactersFrom_to_in_rightX_stopConditions_kern_.st A Text-Scanning.package/LegacyCompositionScanner.class/README.md A Text-Scanning.package/LegacyCompositionScanner.class/definition.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/accessing/rightX.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/scanning/composeFrom_inRectangle_firstLine_leftSide_rightSide_.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/scanning/setActualFont_.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/stop conditions/columnBreak.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/stop conditions/cr.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/stop conditions/crossedX.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/stop conditions/endOfRun.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/stop conditions/placeEmbeddedObject_.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/stop conditions/setFont.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/stop conditions/setStopConditions.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/stop conditions/space.st A Text-Scanning.package/LegacyCompositionScanner.class/instance/stop conditions/tab.st R Text-Scanning.package/MultiCharacterScanner.class/instance/multilingual scanning/addCharToPresentation_.st R Text-Scanning.package/MultiCharacterScanner.class/instance/multilingual scanning/removeLastCharFromPresentation.st R Text-Scanning.package/MultiCompositionScanner.class/instance/accessing/presentation.st R Text-Scanning.package/MultiCompositionScanner.class/instance/accessing/presentationLine.st R Text-Scanning.package/MultiCompositionScanner.class/instance/multilingual scanning/addCharToPresentation_.st R Text-Scanning.package/MultiCompositionScanner.class/instance/multilingual scanning/getPresentation.st R Text-Scanning.package/MultiCompositionScanner.class/instance/multilingual scanning/getPresentationLine.st R Text-Scanning.package/MultiCompositionScanner.class/instance/multilingual scanning/removeLastCharFromPresentation.st R Text-Scanning.package/MultiDisplayScanner.class/instance/private/presentationText_.st Log Message: ----------- 30535 12030 Incorporate Squeak CharacterScanner clean-up https://pharo.fogbugz.com/f/cases/12030 (Step 1/1) http://files.pharo.org/image/30/30535.zip

Nov. 2, 2013

Re: [Pharo-dev] smalltalkhub is down

by Tudor Girba

Hi, Thanks for the suggestion. I am happy you are excited about the promise of GitHub. The only thing left to do is to make it happen, and I kindly invite you to join the others interested in precisely making it happen. Just send a message around showing your availability to code in this direction, and I am sure that people will point you to what is left to do. Doru On Sat, Nov 2, 2013 at 2:21 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > and its alive again ! > > If anyone cares about my personal opinion, and I hope not many people do , > I think it would be better for Pharoers to embrace Github. Not because > smalltalkhub is more prone to crashes , not because it has much less > features, but because of the amount of exposer it can give to our > community. > > I think that if more and more Github users, and there are tons of them out > there, starting seeing Pharo project popping around like mushrooms , they > may ask the question "What the hell is Pharo" and maybe just maybe this > bring more people to our side that may try Pharo , love it and want to help > us make it more awesome. > > So if we could make committing to Gihub as convenient as committing to > Smalltalkhub then its a matter of porting projects to it. Imagine what > would happen if one of those great smalltalkhub projects became the project > of the month for Github. > > > On Sat, Nov 2, 2013 at 1:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > >> >> On 02 Nov 2013, at 12:23, Johan Brichau <johan(a)inceptive.be> wrote: >> >> > >> >> On 02 Nov 2013, at 05:51, Marcus Denker <marcus.denker(a)inria.fr> >> wrote: >> >> >> >> Something is fundamentally wrong here. >> > >> > Yes. And it is hurting the trust people have in smalltalkhub. This is >> not the way to promote the community either. >> > >> > I hope there are at least monitoring and auto-restart services running! >> > >> > Johan >> >> I suspect that the problem is that a database (Mongo DB) is involved so >> that before each (potentially automatic) restart a human has to make sure >> that the database is not corrupt. If the application/webapp and the DB are >> really very well separated then that should be less of a problem. >> >> That being said, the situation should definitively be improved ;-) >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 2, 2013

Re: [Pharo-dev] smalltalkhub is down

by kilon alios

and its alive again ! If anyone cares about my personal opinion, and I hope not many people do , I think it would be better for Pharoers to embrace Github. Not because smalltalkhub is more prone to crashes , not because it has much less features, but because of the amount of exposer it can give to our community. I think that if more and more Github users, and there are tons of them out there, starting seeing Pharo project popping around like mushrooms , they may ask the question "What the hell is Pharo" and maybe just maybe this bring more people to our side that may try Pharo , love it and want to help us make it more awesome. So if we could make committing to Gihub as convenient as committing to Smalltalkhub then its a matter of porting projects to it. Imagine what would happen if one of those great smalltalkhub projects became the project of the month for Github. On Sat, Nov 2, 2013 at 1:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 02 Nov 2013, at 12:23, Johan Brichau <johan(a)inceptive.be> wrote: > > > > >> On 02 Nov 2013, at 05:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> > >> Something is fundamentally wrong here. > > > > Yes. And it is hurting the trust people have in smalltalkhub. This is > not the way to promote the community either. > > > > I hope there are at least monitoring and auto-restart services running! > > > > Johan > > I suspect that the problem is that a database (Mongo DB) is involved so > that before each (potentially automatic) restart a human has to make sure > that the database is not corrupt. If the application/webapp and the DB are > really very well separated then that should be less of a problem. > > That being said, the situation should definitively be improved ;-) > > >

Nov. 2, 2013

Re: [Pharo-dev] smalltalkhub is down

by Sven Van Caekenberghe

On 02 Nov 2013, at 12:23, Johan Brichau <johan(a)inceptive.be> wrote: > >> On 02 Nov 2013, at 05:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Something is fundamentally wrong here. > > Yes. And it is hurting the trust people have in smalltalkhub. This is not the way to promote the community either. > > I hope there are at least monitoring and auto-restart services running! > > Johan I suspect that the problem is that a database (Mongo DB) is involved so that before each (potentially automatic) restart a human has to make sure that the database is not corrupt. If the application/webapp and the DB are really very well separated then that should be less of a problem. That being said, the situation should definitively be improved ;-)

Nov. 2, 2013

Re: [Pharo-dev] smalltalkhub is down

by Johan Brichau

> On 02 Nov 2013, at 05:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Something is fundamentally wrong here. Yes. And it is hurting the trust people have in smalltalkhub. This is not the way to promote the community either. I hope there are at least monitoring and auto-restart services running! Johan

Nov. 2, 2013

Re: [Pharo-dev] flatCollect:

by Tudor Girba

Indeed, it would be more elegant, but streamContents: is only defined in SequeanceableCollection, so it is not generic enough. Doru On Sat, Nov 2, 2013 at 11:21 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > BTW, it seems #flatten in 2.0 has become #flattened in 3.0 and that too > might needs the #species > > Would it also not be better and more elegant to say > > self species streamContents: [ :stream | > â¦ ] > > ? > > On 02 Nov 2013, at 09:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > On 01 Nov 2013, at 23:55, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > >> Hi, > >> > >> I see that Pharo 3.0 has a Collection>>flatCollect:. This is great as > the method proved to be very valuable in the context of Moose. > >> > >> However, the current Pharo implementation is less ideal: > >> > >> Collection>>flatCollect: aBlock > >> ^ Array streamContents: > >> [:stream | > >> self do: [:ea | stream nextPutAll: (aBlock value: ea)]] > >> > >> The Moose one is: > >> Collection>>flatCollect: aBlock > >> "Evaluate aBlock for each of the receiver's elements and answer the > >> list of all resulting values flatten one level. Assumes that > aBlock returns some kind > >> of collection for each element. Equivalent to the lisp's mapcan" > >> "original written by a. Kuhn and released under MIT" > >> > >> | stream | > >> self isEmpty ifTrue: [ ^ self copy ]. > >> stream := (self species new: 0) writeStream. > >> self do: [ :each | stream nextPutAll: (aBlock value: each) ]. > >> ^ stream contents > >> > >> The difference is in the type returned. The Pharo one always returns > Array, while the Moose one returns a collection of the same species as the > receiver. > > > > Sounds right, returning #species. > > > >> Does anyone have anything against the Moose implementation? > >> > >> Doru > >> > >> -- > >> www.tudorgirba.com > >> > >> "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 2, 2013

Re: [Pharo-dev] smalltalkhub is down

by kilon alios

Find whoever is responsible for this and make him listen to Justin Bieber for 6 hours straight, problem solved. I know its cruel , but its the only way to ensure this wont happen again. Does that mean that smalltalkhub has become increasingly popular or its unrelated to traffic load ? On Sat, Nov 2, 2013 at 11:51 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > Yes, and exactly as last week I can not do *anything*. And everyone who > could do something is in Argentina, I guess sleeping right now. > > We really need to change this. And best before we have exactly the same > next saturday, again. > (Sadly, as said, I can do *absolutely* nothing, I can not even do anything > to change that I can do nothing.) > > Something is fundamentally wrong here. > > Marcus > > > On Sat, Nov 2, 2013 at 8:47 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> smalltalkhub is down: >> http://www.downforeveryoneorjustme.com/smalltalkhub.com >> >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > > > -- > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de >

Nov. 2, 2013

Re: [Pharo-dev] flatCollect:

by Sven Van Caekenberghe

BTW, it seems #flatten in 2.0 has become #flattened in 3.0 and that too might needs the #species Would it also not be better and more elegant to say self species streamContents: [ :stream | â¦ ] ? On 02 Nov 2013, at 09:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 01 Nov 2013, at 23:55, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> I see that Pharo 3.0 has a Collection>>flatCollect:. This is great as the method proved to be very valuable in the context of Moose. >> >> However, the current Pharo implementation is less ideal: >> >> Collection>>flatCollect: aBlock >> ^ Array streamContents: >> [:stream | >> self do: [:ea | stream nextPutAll: (aBlock value: ea)]] >> >> The Moose one is: >> Collection>>flatCollect: aBlock >> "Evaluate aBlock for each of the receiver's elements and answer the >> list of all resulting values flatten one level. Assumes that aBlock returns some kind >> of collection for each element. Equivalent to the lisp's mapcan" >> "original written by a. Kuhn and released under MIT" >> >> | stream | >> self isEmpty ifTrue: [ ^ self copy ]. >> stream := (self species new: 0) writeStream. >> self do: [ :each | stream nextPutAll: (aBlock value: each) ]. >> ^ stream contents >> >> The difference is in the type returned. The Pharo one always returns Array, while the Moose one returns a collection of the same species as the receiver. > > Sounds right, returning #species. > >> Does anyone have anything against the Moose implementation? >> >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow"

Nov. 2, 2013