- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Dec. 9, 2015

Dec. 9, 2015

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

1 0

[pharo-project/pharo-core] 804dcf: 50493
by GitHub Dec. 9, 2015

Dec. 9, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 804dcf1adc2f65b37e1f8b493360d517bda3b3b9 https://github.com/pharo-project/pharo-core/commit/804dcf1adc2f65b37e1f8b49… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-09 (Wed, 09 Dec 2015) Changed paths: A Metacello-MC.package/extension/MCFileTreeRepository/instance/versionInfoFromVersionNamed_.st A Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCanCreateFiletreeRepositoryFromUrlWithRelativePath.st M MonticelloFileTree-Core.package/MCFileTreeRepository.class/class/utility/urlAsFileReference_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50492.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50493.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50492.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50493.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50493 17212 DNU on MCFileRepository class>>#basicFromUrl: https://pharo.fogbugz.com/f/cases/17212 17213 DNU when trying to retrieve version info from filetree repository https://pharo.fogbugz.com/f/cases/17213 http://files.pharo.org/image/50/50493.zip

1 0

[ ANN ] Pharo Days 2016
by Sven Van Caekenberghe Dec. 9, 2015

Dec. 9, 2015

Dear fellow Pharoers, Mark your calendars: on Thursday March 31 & Friday April 1 we are organising the Pharo Days 2016. This year we moved the location to Namur, Belgium, just a bit south of Brussels, at the very beautiful location of the âCercle de Wallonieâ overlooking the river Meuse. Weâll update the following page moving forward. https://medium.com/concerning-pharo/pharo-days-2016-c52fe4d7caf You can ask questions on any of the Pharo mailing lists or you can email the Pharo Board. Let's make this another success, together ! We hope to see as many of you as possible.

1 0

Re: [Pharo-dev] [squeak-dev] Re: [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: Unicode Support))
by H. Hirzel Dec. 9, 2015

Dec. 9, 2015

Hi Stephan What you mention is an edge case. A regular case which is not implemented yet is language insensitive sorting http://www.unicode.org/versions/Unicode8.0.0/UnicodeStandard-8.0.pdf <citation> In some circumstances, an application may need to do language-insensitive sortingâthat is, sorting of textual data without consideration of language-specific cultural expectations about how strings should be ordered. </citation> This is currently not the case as there is no normalization. As the Unicode Character Database [1] is already available in Squeak / Pharo (and could easily be loaded into Cuis) the implementation effort for language-insensitive sorting seems to be in reach without a big effort. [1] http://wiki.squeak.org/squeak/6244 Hannes On 12/9/15, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 08-12-15 22:35, Dale Henrichs wrote: >> What I meant is that you can't _always_ use the code point for >> collation, i.e., sorting based on the value of code points is not always >> correct[1]. > > I have given up on universal sorting when I learned that dutch libraries > sorting of author names depends on the country of origin of the author. > So if Jan van Beek is dutch he will be sorted under B, while if he's > belgian under V. I haven't checked what happens if the author emigrates, > or changes nationality... > > Stephan > > > >

1 0

[pharo-project/pharo-core]
by GitHub Dec. 9, 2015

Dec. 9, 2015

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

1 0

[pharo-project/pharo-core] e3f6b3: 50492
by GitHub Dec. 9, 2015

Dec. 9, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: e3f6b3f61fc8f36d306bbd3d8e0f125a369528ba https://github.com/pharo-project/pharo-core/commit/e3f6b3f61fc8f36d306bbd3d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-09 (Wed, 09 Dec 2015) Changed paths: R Morphic-Core.package/Morph.class/instance/stepping and presenter/startSteppingIn_.st R Morphic-Core.package/PasteUpMorph.class/instance/world state/addMorphs_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50491.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50492.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50491.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50492.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50492 17221 clean dirty packages after metacello update https://pharo.fogbugz.com/f/cases/17221 17219 Class Definitions not in Changes... again again https://pharo.fogbugz.com/f/cases/17219 17217 Remove PasteUpMorph>>#addMorphs: https://pharo.fogbugz.com/f/cases/17217 http://files.pharo.org/image/50/50492.zip

1 0

where is the AST?
by Ben Coman Dec. 9, 2015

Dec. 9, 2015

I am probably misremembering, but I thought I used to be able to do something like... #+ implementors first inspect and spotter would show a CompiledMethod with a tab showing the Bytecode and AST, but I get a RGMethodDefinition that doesn't have those. How do I get those tabs up? This is just for a two minute example for demonstration purposes. cheers -ben

2 1

Help needed: old issues issue tracker entries
by marcus.denker＠inria.fr Dec. 9, 2015

Dec. 9, 2015

Hi, The issue tracker has 658 open issues. This number is more or less constant. We are fixing and integrating *a lot*, alone the last 7 days we managed to close 89 issue tracker entries. But the older entries see not much work. Of course one reason is that everything fixable gets fixed and only hard cases remainâ¦ but cases can be âdifficultâ for many reasons. I would be nice if everyone could help and have a look at older issues: -> Still relevant? -> Maybe already fixed? -> Is the description good? -> What is the next action that needs to be done? And keep in mind that the issue tracker is not a TODO list. If you see something odd and put and issue âoh, this looks oddâ but there is no action for a year, does it really make sense to keep that issue open? Every open issue takes energy away from the others. So please check if issues make sense of this kind: -> âIt would be nice ifâ but not even important enough for the submitter to do -> TODO issues that are huge projects in themselves -> â¦. It would be nice if *you* would check the issue that you have been involved with the last months and see what is needed to solve them. Marcus

9 11

displayingProgress on demand
by HernÃ¡n Morales Durand Dec. 9, 2015

Dec. 9, 2015

Hello everyone, Is there a reason why #collect:displayingProgress: was removed or never included? And as more general question, is there any pointer to automatically add progress bar to iterator messages? For example doing: SmalltalkImage setDisplayProgressTo: MyClass. SmalltalkImage setDisplayProgressTo: MyPackage. and then having all enumeration messages sent in MyClass or MyPackage with a progress bar collect: collect:as: collect:into: collect:thenDo: select: select:as: select:thenDo: select:thenCollect:as: ... HernÃ¡n

9 24

License agreement - are you kidding me?
by webwarrior Dec. 9, 2015

Dec. 9, 2015

It would be logical to make contribution to an open source project easy, right? Well, in bigger projects some burocracy is inevitable, but usually has some valid reasons behind it. When I made some commits to Spec (while it was on github), it was as easy as fork->commit->create pull request. In Pharo, it's already more complicated: you have to register yourself in SmalltalkHub, in fogbugz, in mailing lists. Slices system is also not very intuitive. Then CI system spits out some completely unrelated errors. But OK, I understand that Pharo is unlike, and the team maybe doesn't have time to migrate to some integrated bugtracker/repository/whatever. Then people began asking me of my real name - which is already wierd - why would they need it? And then someone suggested that I must sign license agreement (which is also wierd - MIT license doesn't demand anything like that). I looked at that agreeement. It requires you to provide name, address (???), sgin it and send it via snail mail (WTF???). No, guys, that is beyond good and evil. Either we skip this stupid formality and continue working on the code, or I'm out of this. -- View this message in context: http://forum.world.st/License-agreement-are-you-kidding-me-tp4865853.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

15 19