Re: [Pharo-dev] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: [squeak-dev] Unicode Support))

> On 07 Dec 2015, at 23:58, Ben Coman wrote: > > On Tue, Dec 8, 2015 at 3:54 AM, H. Hirzel wrote: >> Hello >> >> According to http://www.unicode.org/cldr/charts/27/collation/de.html the >> German >> phonebook sort order is >> >> a A ä Ä ą̈ Ą̈ ǟ

Re: [Pharo-dev] License agreement - are you kidding me?

On 12/07, webwarrior wrote: > 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

[Pharo-dev] [Pharo5] integration of FastTable needed

Hi, FastTable recently has seen some important fixes. We are seeing people reporting the issues that are fixed again as they are only fixed in the repository, but these changes are not yet in Pharo5. Can the maintainer do a sync? In general, these “externally” managed project should sync

Re: [Pharo-dev] displayingProgress on demand

Hi To let you know finally I used the RewriteRuleBuilder http://myfuncoding.blogspot.cz/2015/02/video-presentation-of-rewrite-tool.html which generated the rule and installed the code (the only minor detail is that class methods are not browsed by the rule browser): [ : job | | index | index

Re: [Pharo-dev] Quick debugging failed #assert:equals tests (Differ in comment)

+1 On Mon, Dec 7, 2015 at 8:50 AM, Torsten Bergmann wrote: > Hi > > the #assert:equals method is often used in Test cases: we have 2491 > senders in > recent Pharo5.0 Latest update: #50487. > > Anytime I have to debug a failing test using it I find it hard to compare > the >

Re: [Pharo-dev] Quick debugging failed #assert:equals tests (Differ in comment)

Nice to get it in Pharo. Many years ago I saw it in Dolphin 2015-12-07 12:50 GMT+01:00 Torsten Bergmann : > Hi > > the #assert:equals method is often used in Test cases: we have 2491 > senders in > recent Pharo5.0 Latest update: #50487. > > Anytime I have to debug a failing test

[Pharo-dev] [pharo-project/pharo-core]

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

[Pharo-dev] [pharo-project/pharo-core] 320769: 50488

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 320769988140aadea83fe1a598e23830ab075c1d https://github.com/pharo-project/pharo-core/commit/320769988140aadea83fe1a598e23830ab075c1d Author: Jenkins Build Server Date:

[Pharo-dev] DNU when accepting an empty string

Hi if I select a method, and remove eveyrthing and press accept I get a DNU. I would like to fix that for newbies. https://pharo.fogbugz.com/f/cases/17205/DNU-when-accepting-an-empty-string I proposed one fix but I would love to have someone to have a look at it (I'm preparing the lectures for

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

OK Max. In the last version you can find the "likely" final version. It's extremely simple, easy to use, and very very little code. Only one override. All WADynamicVariables subclasses handled automatically. All you need to do is to register the handler: app filter configuration at:

Re: [Pharo-dev] displayingProgress on demand

Hi Sven 2015-12-06 17:34 GMT-03:00 Sven Van Caekenberghe : > There is still #do:displayingProgress: > > There is Job. > > In general, the collection API should not be concerned with GUI matters, > does it ? > > Believe me when you're executing a large workflow processing 50Gb files

Re: [Pharo-dev] displayingProgress on demand

Hi Hernán, Le 07/12/2015 18:16, Hernán Morales Durand a écrit : Hi Sven 2015-12-06 17:34 GMT-03:00 Sven Van Caekenberghe >: There is still #do:displayingProgress: There is Job. In general, the collection API should not be concerned with GUI

Re: [Pharo-dev] [squeak-dev] Unicode Support

> On 06 Dec 2015, at 22:07, Sven Van Caekenberghe wrote: > > Ah yes, Go is a good example, thanks Mark. > > After reading these two blog articles: > > http://blog.golang.org/strings > http://blog.golang.org/normalization > > And especially after looking through their

Re: [Pharo-dev] Unicode Support

I am sorry but one of your basic assumptions is completely wrong: 'Les élèves Français' encodeWith: #iso99591. => #[76 101 115 32 233 108 232 118 101 115 32 70 114 97 110 231 97 105 115] 'Les élèves Français' utf8Encoded. => #[76 101 115 32 195 169 108 195 168 118 101 115 32 70 114 97 110

Re: [Pharo-dev] Unicode Support

> On 07 Dec 2015, at 11:51 , EuanM wrote: > > And indeed, in principle. > > On 7 December 2015 at 10:51, EuanM wrote: >> Verifying assumptions is the key reason why you should documents like >> this out for review. >> >> Sven - >> >> I'm confident I

Re: [Pharo-dev] Unicode Support

And indeed, in principle. On 7 December 2015 at 10:51, EuanM wrote: > Verifying assumptions is the key reason why you should documents like > this out for review. > > Sven - > > Cuis is encoded with ISO 8859-15 (aka ISO Latin 9) > > Sven, this is *NOT* as you state, ISO

[Pharo-dev] [pharo-project/pharo-core]

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

[Pharo-dev] [pharo-project/pharo-core] 606269: 40626

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 60626987f9c7151f82a7ad72ab5022fd2f588899 https://github.com/pharo-project/pharo-core/commit/60626987f9c7151f82a7ad72ab5022fd2f588899 Author: Jenkins Build Server Date:

Re: [Pharo-dev] displayingProgress on demand

> On 06 Dec 2015, at 21:34, Sven Van Caekenberghe wrote: > > There is still #do:displayingProgress: > > There is Job. > > In general, the collection API should not be concerned with GUI matters, does > it ? this. also including notifications “just in case someone needs it”

Re: [Pharo-dev] Help needed: old issues issue tracker entries

> On 05 Dec 2015, at 19:31, Marcus Denker wrote: > > >> On 30 Nov 2015, at 13:21, marcus.den...@inria.fr wrote: >> >> Hi, >> >> The issue tracker has 658 open issues. This number is more or less constant. >> > > down to 642! Down to 638. Can *YOU* help to get it to

Re: [Pharo-dev] Help needed: old issues issue tracker entries

Thanks a lot, Marcus for this encouragements! Doru > On Dec 7, 2015, at 6:15 AM, Marcus Denker wrote: > > >> On 05 Dec 2015, at 19:31, Marcus Denker wrote: >> >> >>> On 30 Nov 2015, at 13:21, marcus.den...@inria.fr wrote: >>> >>> Hi, >>>

[Pharo-dev] Quick debugging failed #assert:equals tests (Differ in comment)

Hi the #assert:equals method is often used in Test cases: we have 2491 senders in recent Pharo5.0 Latest update: #50487. Anytime I have to debug a failing test using it I find it hard to compare the expected and actual value when it is a string in the debugger panes. Pharo tools come to the

Re: [Pharo-dev] [Pharo-users] Help needed: old issues issue tracker entries

The over 600 number looks scary sometimes.. but just by doing one after the other, we it is actually doable. The proof is that we closed 1587 already for Pharo5… and for Pharo all versions we are at 14295 issues “done”. 638 looks small compared to that. Marcus > On 07 Dec 2015, at 12:30,

Re: [Pharo-dev] Help needed: old issues issue tracker entries

> Can *YOU* help to get it to 637? Without activity/reply for some time and no clear action --- maybe close as stale?: * https://pharo.fogbugz.com/f/cases/10047/Regex-not-independant-of-platform * https://pharo.fogbugz.com/f/cases/13479/ValueHolder-and-NewValueHolder-do-not-have-the-same-api *

Re: [Pharo-dev] Help needed: old issues issue tracker entries

> On 07 Dec 2015, at 13:42, Peter Uhnak wrote: > >> Can *YOU* help to get it to 637? > > Without activity/reply for some time and no clear action --- maybe close > as stale?: > > * https://pharo.fogbugz.com/f/cases/10047/Regex-not-independant-of-platform > * >

Re: [Pharo-dev] Unicode Support

> On 07 Dec 2015, at 1:05 , EuanM wrote: > > Hi Henry, > > To be honest, at some point I'm going to long for the for the much > more succinct semantics of healthcare systems and sports scoring and > administration systems again. :-) > > codepoints are any of *either* > -

Re: [Pharo-dev] License agreement - are you kidding me?

Hi webwarrior (or whatever your name now is ;) There is always room for improvements - even for better guidance on how to become a contributor. There are good reasons to do things the way they are done now - and yes some of them are not optimal because of history or because of sparse time.

Re: [Pharo-dev] License agreement - are you kidding me?

Hi Stef, I think of it as a Pharo Driver's License: you can't drive without a license! I would think you would need to verify identity, so I am surprised a notarized image of a form of ID is not required: drivers license or passport. You would need this for any hotel or car rental. It's a

Re: [Pharo-dev] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: [squeak-dev] Unicode Support))

On Tue, Dec 8, 2015 at 3:54 AM, H. Hirzel wrote: > Hello > > According to http://www.unicode.org/cldr/charts/27/collation/de.html the > German > phonebook sort order is > > a A ä Ä ą̈ Ą̈ ǟ Ǟ ạ̈ Ạ̈ ḁ̈ Ḁ̈ b B c C d D e E f F g G h H i I j J k K > l L m M n N o O ö Ö ǫ̈ Ǫ̈

Re: [Pharo-dev] displayingProgress on demand

Hi Thierry 2015-12-07 14:43 GMT-03:00 Thierry Goubier : > Hi Hernán, > > Le 07/12/2015 18:16, Hernán Morales Durand a écrit : > >> Hi Sven >> >> 2015-12-06 17:34 GMT-03:00 Sven Van Caekenberghe > >: >> >> There is still

Re: [Pharo-dev] License agreement - are you kidding me?

Hi, To be more specific: - Copyright is granted by law at creation time in most countries. - MIT is a license that works inside the copyright concept. - The copyright is preserved but the only thing the MIT imposes is the condition that authorship is retained whenever someone uses the code. This

[Pharo-dev] CollectionValueHolder additions

Hi, when (any) ValueHolder changes, a ValueChanged announcement is fired. My question: Would it be a good idea to add ValueAdded and ValueRemoved for CollectionValueHolder? Otherwise there's no way to meaningfully observe changes. -- Peter

[Pharo-dev] License agreement - are you kidding me?

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

Re: [Pharo-dev] displayingProgress on demand

Here is my take on it. http://smalltalkhub.com/#!/~Latsabben/GafletFremgangFremviser Best regards, Henrik From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Hernán Morales Durand Sent: Tuesday, December 8, 2015 12:28 AM To: Pharo Development List

Re: [Pharo-dev] License agreement - are you kidding me?

Considering that there are a couple of responses and the fact that you guys are so easily offended, I will not answer everyone but just state couple of theses. 0. I will not reveal my real name, because I value privacy. Nickname is sufficient for identification purposes. Any other information

Re: [Pharo-dev] License agreement - are you kidding me?

Hello webwarrior It would be logical to make contribution to an open source project easy, right? Yes but not at the price of legal mess. Well, in bigger projects some burocracy is inevitable, but usually has some valid reasons behind it. We have strong reasons and they are quite baked by

Re: [Pharo-dev] License agreement - are you kidding me?

This ensures the legal thing is no bull and that the rights are indeed MIT. There has been cases of problems and this ensured that lawyers could quickly sort things out. Phil On Dec 7, 2015 7:31 PM, "webwarrior" wrote: > It would be logical to make contribution to an open

Re: [Pharo-dev] License agreement - are you kidding me?

Hello webwarrior, Most of your claims are correct, and you could be the best coder but there *is* a trust factor. And part of such trust is built by making life easier to the core team. Maybe the pharo team could implement "closed verification" for cases like yours? Now how do we trust you do

Re: [Pharo-dev] displayingProgress on demand

Hi Henrik I checked, thank you for sharing an elegant approach (although my issue with automatic code transformation remains). May you comment why you implemented another progress bar? Does support stacked progress bars? Do you plan to add labels? Hernán 2015-12-07 21:04 GMT-03:00 Henrik