Re: [Pharo-dev] About a better filedialog

What is cool is that you can add bookmarks :) I did it to list the place where I store all my iceberg repo :) > On 18 Mar 2019, at 20:31, ducasse wrote: > > Hi guys > > I did a pass (ported to P7, tonel, some little fixes) on the file-dialog > developed by Peter Uhnak and I think that it

[Pharo-dev] About a better filedialog

Hi guys I did a pass (ported to P7, tonel, some little fixes) on the file-dialog developed by Peter Uhnak and I think that it would be good to propose it by default in the image. what do you think? https://github.com/Ducasse/file-dialog I would also like that the filedialog

Re: [Pharo-dev] About Iceberg

 On Tue, 19 Feb 2019 at 10:06, Hilaire wrote: > I join your thank you note, although I only use one half, the tonel > part, it is pleasant to be able to commit to file base repository and > use related tools. > > Le 19/02/2019 à 09:50, Sven Van Caekenberghe a écrit : > > This is a thank you

Re: [Pharo-dev] About Iceberg

I join your thank you note, although I only use one half, the tonel part, it is pleasant to be able to commit to file base repository and use related tools. Le 19/02/2019 à 09:50, Sven Van Caekenberghe a écrit : > This is a thank you note about Iceberg. -- Dr. Geo http://drgeo.eu

[Pharo-dev] About Iceberg

Hi, This is a thank you note about Iceberg. I have been moving all my external and internal Pharo code to git/tonel/7 and on multiple occasions I have been pleasantly surprised about the functionality and performance of Iceberg. Basically, it just works. Finally, Pharo code lives in standard

[Pharo-dev] About resurrecting the RE package and plugin

--- Begin Message --- Hi I would really like to resurrect the REPlugin and its image side abstraction because I think that this is important to support Perl level regex since it will help people to reuse their knowledge. If you are interested in helping let us know. Stef <> --- End Message 

Re: [Pharo-dev] About contribution process, people participation and communication (WAS: Re: [ANN] Pharo 8.0 development started)

On Sun, 30 Dec 2018 at 23:28, Esteban Lorenzano via Pharo-dev < pharo-dev@lists.pharo.org> wrote: > > Now, while the general direction was explained, I think I failed to > communicate several things. > For what I can think at this moment (for sure there are a lot more): > > - I failed to

[Pharo-dev] About contribution process, people participation and communication (WAS: Re: [ANN] Pharo 8.0 development started)

--- Begin Message --- Hi Torsten (again), What I see in your mails, and what I think is most important to discuss, is a subjacent critique about the way we communicate our changes. And maybe more than that: a disagreement about the general direction of changes in process. While I recognise we

Re: [Pharo-dev] About #zipped / #unzipped

https://github.com/pharo-project/pharo/pull/1947 > On 26 Oct 2018, at 22:28, Stephane Ducasse wrote: > > +1 > > On Tue, Oct 23, 2018 at 10:50 AM Marcus Denker wrote: >> >> >> >>> On 18 Oct 2018, at 20:59, Sven Van Caekenberghe wrote: >>> >>> Hi, >>> >>> Given >>>

Re: [Pharo-dev] About #zipped / #unzipped

+1 On Tue, Oct 23, 2018 at 10:50 AM Marcus Denker wrote: > > > > > On 18 Oct 2018, at 20:59, Sven Van Caekenberghe wrote: > > > > Hi, > > > > Given > > https://pharo.fogbugz.com/f/cases/21858/Cleanup-remaining-DeprecatedFileSystem-users > > [where we need more help !!] I found String>>#zipped

Re: [Pharo-dev] About #zipped / #unzipped

> On 18 Oct 2018, at 20:59, Sven Van Caekenberghe wrote: > > Hi, > > Given > https://pharo.fogbugz.com/f/cases/21858/Cleanup-remaining-DeprecatedFileSystem-users > [where we need more help !!] I found String>>#zipped to be one of the users > of the deprecated RWBinaryOrTextStream.

[Pharo-dev] About #zipped / #unzipped

Hi, Given https://pharo.fogbugz.com/f/cases/21858/Cleanup-remaining-DeprecatedFileSystem-users [where we need more help !!] I found String>>#zipped to be one of the users of the deprecated RWBinaryOrTextStream. Although this usage is easy enough to fix, I think the current #zipped / #unzipped

Re: [Pharo-dev] About the infinite debugger

Yes, we have to check all the scenarios. The problems with the UI process is not resolved at all. On Tue, Aug 7, 2018 at 11:11 PM Denis Kudriashov wrote: > I have more special cases where debugger hangs: > 19662 >

Re: [Pharo-dev] About the infinite debugger

I have more special cases where debugger hangs: 19662 , 19928 , 20274

Re: [Pharo-dev] About the infinite debugger

Hi. Good job guys. I just checked my case 19848 . And it is now fixed. Thanks 2018-06-29 15:48 GMT+01:00 Guillermo Polito : > Hi all, > > during today's sprint we

Re: [Pharo-dev] About the infinite debugger

Hi Steven, The thing about your fix was mainly that it only worked for the case of running tests. We could however reproduce this bug from a playground too. At first, replacing #pass to #debug looked like a hack to me :) Just looking at the code of runCaseForDebug:, I felt the correct thing to

Re: [Pharo-dev] About the infinite debugger

El dom., 5 de ago. de 2018 17:28, Tim Mackinnon escribió: > Guys - this really needs attention - I’ve spend hours now trying to debug > some code and most of it is in closing infinite debuggers. It makes a > mockery of our tagline - “awesome debugging”. We can change the tagline to "limitless

Re: [Pharo-dev] About the infinite debugger

Hi, i had no answer to my comments on fogbuz (one of the first) so i assumed it was not a good idea. In the usecases i used to reproduce the bug, replacing "ex pass" by "ex debug" in runCaseForDebug:solved the problem. See the analysis on fogbuz. Did not have any side effect, but i do not

Re: [Pharo-dev] About the infinite debugger

Guys - this really needs attention - I’ve spend hours now trying to debug some code and most of it is in closing infinite debuggers. It makes a mockery of our tagline - “awesome debugging”. And the extra irony is that I’m debugging some file path stuff for exercism, to make it easier for

Re: [Pharo-dev] About the infinite debugger

bump > Am 04.07.2018 um 02:28 schrieb Martin McClure : > >> On 07/03/2018 05:02 PM, Martin McClure wrote: >>> On 06/29/2018 07:48 AM, Guillermo Polito wrote: >>> I know that the exception handling/debugging has been modified several >>> times in the latest years (some refactorings, hiding

Re: [Pharo-dev] About the infinite debugger

On 07/03/2018 05:02 PM, Martin McClure wrote: > On 06/29/2018 07:48 AM, Guillermo Polito wrote: >> I know that the exception handling/debugging has been modified several >> times in the latest years (some refactorings, hiding contexts...), we >> unfortunately don't have tests for it, so I'd like

Re: [Pharo-dev] About the infinite debugger

On 06/29/2018 07:48 AM, Guillermo Polito wrote: > Hi all, > > during today's sprint we have been working with lots of people on the > infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/). > We have checked the emails sent in the latest month. Then, together > with Quentin, Pablo,

Re: [Pharo-dev] About the infinite debugger

> On 30 Jun 2018, at 02:56, Eliot Miranda wrote: > > Hi Guille, > > On Jun 29, 2018, at 7:48 AM, Guillermo Polito > wrote: > >> Hi all, >> >> during today's sprint we have been working with lots of people on the >> infinite debugger problem

Re: [Pharo-dev] About the infinite debugger

Hi Guille, > On Jun 29, 2018, at 7:48 AM, Guillermo Polito > wrote: > > Hi all, > > during today's sprint we have been working with lots of people on the > infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/). We have > checked the emails sent in the latest month. Then,

Re: [Pharo-dev] About the infinite debugger

Great news! I hope this fixes it once and for all. For some reason this bug bit me several times in several Pharo releases. Thank you all for your dedication. On 29/06/2018 11:48, Guillermo Polito wrote: > Hi all, > > during today's sprint we have been working with lots of people on the >

Re: [Pharo-dev] About the infinite debugger

On Fri, Jun 29, 2018 at 5:58 PM Ben Coman wrote: > > > On 29 June 2018 at 22:48, Guillermo Polito > wrote: > >> Hi all, >> >> during today's sprint we have been working with lots of people on the >> infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/). We >> have checked the

Re: [Pharo-dev] About the infinite debugger

On 29 June 2018 at 22:48, Guillermo Polito wrote: > Hi all, > > during today's sprint we have been working with lots of people on the > infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/). We > have checked the emails sent in the latest month. Then, together with > Quentin,

[Pharo-dev] About the infinite debugger

Hi all, during today's sprint we have been working with lots of people on the infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/). We have checked the emails sent in the latest month. Then, together with Quentin, Pablo, Pavel, Yoan we have been discussing and testing hypothesis

Re: [Pharo-dev] About infinite debuggers in tests (https://pharo.fogbugz.com/f/cases/22085/Infinite-debugger)

Hi Steven, I'll take a look at this later this week, no time now, but: did you check that the debugger makes a copy of the UI process when there is an exception in the UI process? Because that is also part of the problem I believe. On Mon, Jun 11, 2018 at 2:18 PM, Steven Costiou wrote: > Hi, >

[Pharo-dev] About infinite debuggers in tests (https://pharo.fogbugz.com/f/cases/22085/Infinite-debugger)

Hi, Is that normal that in the following method we do "EX PASS" (at the end)? runCaseForDebug: aTestCase [ aTestCase announce: TestCaseStarted withResult: self. aTestCase runCaseManaged. aTestCase announce: TestCaseEnded withResult: self. "To not affect performance of big test

Re: [Pharo-dev] About UFFI documentation deprecation.

Take all the questions/answers you will get most frequent question and this is cheap to do. There is FAQ session at the end of the booklet. The more stupid people like me will be able to use UFFI the better Pharo will be. We should help C-agnostic people to use and master UFFI. Stef On Sat,

Re: [Pharo-dev] About UFFI documentation deprecation.

> On 17 Feb 2018, at 14:56, Esteban Lorenzano wrote: > > mmm… message received :) It was not directed especially to you, but you get the idea: it does not matter how cool the software is, it needs proper documentation for others to derive value from it. > But! I have

Re: [Pharo-dev] About UFFI documentation deprecation.

mmm… message received :) But! I have to declare: uFFI booklet is not bad. Is just incomplete… (there are three small sections missing). We will never cover all possible usages and for that my idea was always to add “annexes” with all problems emerging and answered on the list… so to answer

Re: [Pharo-dev] About UFFI documentation deprecation.

Fair enough. "If it is not documented, it does not exist" > On 17 Feb 2018, at 08:37, Stephane Ducasse wrote: > > About https://github.com/SquareBracketAssociates/Booklet-uFFI > > > Dear (poor) reader, since years I tried to convince people > understanding FFI to

[Pharo-dev] About UFFI documentation deprecation.

About https://github.com/SquareBracketAssociates/Booklet-uFFI Dear (poor) reader, since years I tried to convince people understanding FFI to finish this documentation. But I failed. Apparently documenting FFI is not important enough. So I stopped to try and in the future I will remove simply

Re: [Pharo-dev] About method comments

Hi, Stef I have an idea for this problem, 1. method should have it's comment like class comment 2. method comment has two versions, one for developer another for reader 3. developder's comment will be saved in source or changes file 4. reader's comment will be saved in its own file 5. system

Re: [Pharo-dev] About method comments

A method comment should tell - what it is doing, what are the preconditions - then some concerns about the implementation You can give a try to document methods of fileSystem or SUnit as Katas. Stef On Sat, Feb 10, 2018 at 5:54 AM, Sean P. DeNigris wrote: > Esteban A.

Re: [Pharo-dev] About method comments

Esteban A. Maringolo wrote > Commenting an accesor is redundant, IMO. Typically, yes, and there are other examples. Esteban A. Maringolo wrote > I think that having a public guideline on how to comment > methods would be positive for the community Interesting idea. Any suggestions? -

Re: [Pharo-dev] About method comments

You see I take some core classes and I read the code and I comment when I understand what a method does. And I do that 15 min from time to time. And just doing this will improve Pharo. When I learn something I take 2 min to add a comment. Stef On Fri, Feb 9, 2018 at 9:13 PM, Jan Vrany

Re: [Pharo-dev] About method comments

Hi Esteban, On Fri, 2018-02-09 at 15:17 -0300, Esteban A. Maringolo wrote: > > And rename refactorings usually don't rename the comments > (hopefully). > Why hopefully? Java IDEs rename references to the method also in comments, I found it very nice. Why it should not? I'm just curious. Best,

Re: [Pharo-dev] About method comments

2018-02-09 8:10 GMT-03:00 Sven Van Caekenberghe : > name > "Returns the receiver's name" > ^ name > > Would also pass a simple test, while it is quite useless. > > I would say that any public, non-trivial methods need a comment. Commenting an accesor is redundant, IMO. And

Re: [Pharo-dev] About method comments

One more reason to do reviews. Now that it is super easy with iceberg there is less reason to do so. Norbert > Am 09.02.2018 um 12:10 schrieb Sven Van Caekenberghe : > > > >> On 9 Feb 2018, at 12:04, Stephane Ducasse wrote: >> >> Hi guys >> >> From

Re: [Pharo-dev] About method comments

> On 9 Feb 2018, at 12:04, Stephane Ducasse wrote: > > Hi guys > > From now on I will VETO the introduction of code where methods are not > commented. > I'm FEDUP FEDUP FEDUP to spend my time commenting methods that I do > not know and understand, juts because the

[Pharo-dev] About method comments

Hi guys >From now on I will VETO the introduction of code where methods are not commented. I'm FEDUP FEDUP FEDUP to spend my time commenting methods that I do not know and understand, juts because the original author thought that this is obvious. NOTHING IS OBVIOUS So I will check if we can

Re: [Pharo-dev] about diff paths

'/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/Chapters/Scheme.pillar' asFileReference path relativeToPath: '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/Chapters/' asFileReference path In fact /

[Pharo-dev] about diff paths

Hi I want to know the path from a given point in a path for example '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/Chapters/Scheme.pillar' asFileReference path relativeToPath: (Path /

Re: [Pharo-dev] About values....

Well. Give me 1 Billion euros and let us bet. :) On Wed, Jan 10, 2018 at 5:19 PM, Dimitris Chloupis wrote: > On Mon, Jan 8, 2018 at 11:28 PM Stephane Ducasse > wrote: >> >> https://youtu.be/keCwRdbwNQY >> >> I would love to have $ to market

Re: [Pharo-dev] About values....

On Mon, Jan 8, 2018 at 11:28 PM Stephane Ducasse wrote: > https://youtu.be/keCwRdbwNQY > > I would love to have $ to market Pharo but I like this talk > > Stef > > Let's be sincere here, there would have been no Apple without Steve. Ironically even Steve was not aware

Re: [Pharo-dev] About values....

Thanks for your cool signature :) On Tue, Jan 9, 2018 at 9:20 PM, Stephane Ducasse wrote: > Yes of course :) > I like the think differently :) > > > On Tue, Jan 9, 2018 at 10:37 AM, Sven Van Caekenberghe > wrote: > >> >> >> On 8 Jan 2018, at 22:28,

Re: [Pharo-dev] About values....

Yes of course :) I like the think differently :) On Tue, Jan 9, 2018 at 10:37 AM, Sven Van Caekenberghe wrote: > > > On 8 Jan 2018, at 22:28, Stephane Ducasse wrote: > > https://youtu.be/keCwRdbwNQY > > I would love to have $ to market Pharo but I like

Re: [Pharo-dev] About values....

> On 8 Jan 2018, at 22:28, Stephane Ducasse wrote: > > https://youtu.be/keCwRdbwNQY > > I would love to have $ to market Pharo but I like this talk > > Stef Bah, we have this: World Menu > Help > Pharo Zen ProfStef pharoZenValuesContents. Sven -- Sven Van

[Pharo-dev] About values....

https://youtu.be/keCwRdbwNQY I would love to have $ to market Pharo but I like this talk Stef

[Pharo-dev] about copyAllTo:

Hi I have the gut feeling that copyAllTo: is not really nice because unclear. The comments are unclear on the "flattening" It is unclear that it flattens the leaves or not. I mean A B x C D y z A copyAllTo: K do we get K B x C D

Re: [Pharo-dev] About a shared trello board

;) Yes So Esteban proposed to use the github project and we started a set of focus projects On Wed, Dec 13, 2017 at 12:45 PM, Norbert Hartl wrote: > > >> Am 13.12.2017 um 10:58 schrieb Stephane Ducasse : >> >> Hi >> >> I'm thinking that we are not

Re: [Pharo-dev] About a shared trello board

> Am 13.12.2017 um 10:58 schrieb Stephane Ducasse : > > Hi > > I'm thinking that we are not good at communicating and coordinating effort > I would like start a (read only) and welcome contributions on demand > trello board > so that we know each others on what parts

[Pharo-dev] About a shared trello board

Hi I'm thinking that we are not good at communicating and coordinating effort I would like start a (read only) and welcome contributions on demand trello board so that we know each others on what parts of pharo we are currently working and what are the next steps. Does it make sense for you

[Pharo-dev] About margin and rectangle

Hi While harvesting the old change of Henrik on margins and the idea that Rectangle should not be used to express margins. I looked at expandBy: comment In fact I would like to make sure that that no rectangle is passed as argument and that we can deprecate asMargin from the Rectangle class (we

[Pharo-dev] About margin and 16969

Hi henrik I started to rescue your fix on wrong use of rectangle. Then I noticed that you change the height of a margin. We defined it as height ^ self bottom + self top Since we were considering that the height of a margin is the total amount of space around. and you as height ^ self

Re: [Pharo-dev] about SortFunctions

Not really, but I'd be interested in understanding why it's overengineering for Ordering but not for Boolean… On 9 November 2017 at 14:16, Denis Kudriashov wrote: > Hi Damien. > > 2017-11-09 14:00 GMT+01:00 Damien Pollet : > >> >> >> On 7 November

Re: [Pharo-dev] about SortFunctions

Hi Damien. 2017-11-09 14:00 GMT+01:00 Damien Pollet : > > > On 7 November 2017 at 14:48, Denis Kudriashov > wrote: >> >> And we already have VM based String compare: with strange logic returning >>> 1, 2, 3. So we already can optimize current

Re: [Pharo-dev] about SortFunctions

On 9 November 2017 at 14:00, Damien Pollet wrote: > Order by: aMappingBlock > people sorted: (Order by: #name) , (Order by: #age) > > Lesser >> #, innerOrder > ^ self > > Equal >> #, innerOrder > ^ innerOrder > oh well, I got the Order composition and the Ordering

Re: [Pharo-dev] about SortFunctions

On 7 November 2017 at 14:48, Denis Kudriashov wrote: > > And we already have VM based String compare: with strange logic returning >> 1, 2, 3. So we already can optimize current String>>threeWayCompareTo:. >> > > Maybe good idea to open ticket and modify image level methods

Re: [Pharo-dev] about SortFunctions

Which is weird because I think the magic is its decentralized nature. > On Nov 6, 2017, at 1:52 PM, Ben Coman wrote: > > Some would say it was github that "made" git (popular).

Re: [Pharo-dev] about SortFunctions

2017-11-07 14:45 GMT+01:00 Denis Kudriashov : > 2017-11-07 14:40 GMT+01:00 Nicolas Cellier gmail.com>: > >> >> >> 2017-11-07 14:20 GMT+01:00 Denis Kudriashov : >> >>> I have new question. Why we really need

Re: [Pharo-dev] about SortFunctions

2017-11-07 14:40 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2017-11-07 14:20 GMT+01:00 Denis Kudriashov : > >> I have new question. Why we really need threeWayCompareTo:? >> DefaultSortFunction can implement it using standard comparison methods.

Re: [Pharo-dev] about SortFunctions

2017-11-07 14:20 GMT+01:00 Denis Kudriashov : > I have new question. Why we really need threeWayCompareTo:? > DefaultSortFunction can implement it using standard comparison methods. > > But what would the DefaultSortFunction use? 2 among the 3 selectors < = > ? It's just

Re: [Pharo-dev] about SortFunctions

2017-11-07 13:59 GMT+01:00 Denis Kudriashov : > 2017-11-07 13:50 GMT+01:00 Thierry Goubier : > >> >> 10 years ago now, we designed a DSL above our parallel language, with the same kind of tradeoffs you described there. We ended up discarding

Re: [Pharo-dev] about SortFunctions

I have new question. Why we really need threeWayCompareTo:? DefaultSortFunction can implement it using standard comparison methods. 2017-11-05 0:37 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > Hi all, > I started a discussion with Denis in a pull request >

Re: [Pharo-dev] about SortFunctions

2017-11-07 13:50 GMT+01:00 Thierry Goubier : > > 10 years ago now, we designed a DSL above our parallel language, with the >>> same kind of tradeoffs you described there. We ended up discarding it, >>> because we had to maintain the full procedural code for the cases we

Re: [Pharo-dev] about SortFunctions

2017-11-07 13:47 GMT+01:00 Denis Kudriashov : > 2017-11-07 13:11 GMT+01:00 Thierry Goubier : > >> >> Now, if you explained me something like that: >> >> people nilFirst ascending >> >> Then I'd be more convinced. Or even >> >> people sorted

Re: [Pharo-dev] about SortFunctions

2017-11-07 13:37 GMT+01:00 Denis Kudriashov : > > 2017-11-07 13:11 GMT+01:00 Thierry Goubier : > >> 2017-11-07 12:09 GMT+01:00 Nicolas Cellier > l.com>: >> >>> Concerning syntactic sugar (even if it's pure Smalltalk)

Re: [Pharo-dev] about SortFunctions

2017-11-07 13:11 GMT+01:00 Thierry Goubier : > > Now, if you explained me something like that: > > people nilFirst ascending > > Then I'd be more convinced. Or even > > people sorted nilFirst ascending (if one would prefer restricting the > implementations of

Re: [Pharo-dev] about SortFunctions

2017-11-07 13:11 GMT+01:00 Thierry Goubier : > 2017-11-07 12:09 GMT+01:00 Nicolas Cellier gmail.com>: > >> Concerning syntactic sugar (even if it's pure Smalltalk) I have same >> cicrconspection >> > In the case of #name >> #size it's like

Re: [Pharo-dev] about SortFunctions

2017-11-07 12:09 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2017-11-07 11:36 GMT+01:00 Thierry Goubier : > >> >> >> 2017-11-07 11:24 GMT+01:00 Denis Kudriashov : >> >>> >>> 2017-11-07 9:23 GMT+01:00 Nicolas Cellier

Re: [Pharo-dev] about SortFunctions

2017-11-07 11:55 GMT+01:00 Denis Kudriashov : > > > 2017-11-07 11:36 GMT+01:00 Thierry Goubier : > >> >> >> 2017-11-07 11:24 GMT+01:00 Denis Kudriashov : >> >>> >>> 2017-11-07 9:23 GMT+01:00 Nicolas Cellier

Re: [Pharo-dev] about SortFunctions

2017-11-07 11:36 GMT+01:00 Thierry Goubier : > > > 2017-11-07 11:24 GMT+01:00 Denis Kudriashov : > >> >> 2017-11-07 9:23 GMT+01:00 Nicolas Cellier > l.com>: >> >>> I have other ideas yet. >>> >>> The selector

Re: [Pharo-dev] about SortFunctions

2017-11-07 9:23 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > I have other ideas yet. > > The selector undefinedFirst is good, but the implementation not so. > I don't like the UndefinedSortFunction: too specific, compose oddly... > > If we defined <=> in Boolean

Re: [Pharo-dev] about SortFunctions

2017-11-07 11:36 GMT+01:00 Thierry Goubier : > > > 2017-11-07 11:24 GMT+01:00 Denis Kudriashov : > >> >> 2017-11-07 9:23 GMT+01:00 Nicolas Cellier > l.com>: >> >>> I have other ideas yet. >>> >>> The selector

Re: [Pharo-dev] about SortFunctions

2017-11-07 11:37 GMT+01:00 Norbert Hartl : > > Am 07.11.2017 um 11:24 schrieb Denis Kudriashov : > > > 2017-11-07 9:23 GMT+01:00 Nicolas Cellier l.com>: > >> I have other ideas yet. >> >> The selector undefinedFirst is

Re: [Pharo-dev] about SortFunctions

> Am 07.11.2017 um 11:24 schrieb Denis Kudriashov : > > > 2017-11-07 9:23 GMT+01:00 Nicolas Cellier >: > I have other ideas yet. > > The selector undefinedFirst is good, but the

Re: [Pharo-dev] about SortFunctions

2017-11-07 11:24 GMT+01:00 Denis Kudriashov : > > 2017-11-07 9:23 GMT+01:00 Nicolas Cellier l.com>: > >> I have other ideas yet. >> >> The selector undefinedFirst is good, but the implementation not so. >> I don't like the

Re: [Pharo-dev] about SortFunctions

2017-11-07 9:23 GMT+01:00 Nicolas Cellier : > I have other ideas yet. > > The selector undefinedFirst is good, but the implementation not so. > I don't like the UndefinedSortFunction: too specific, compose oddly... > > In the PR, collatedBy: is the way to tell

Re: [Pharo-dev] about SortFunctions

2017-11-07 10:30 GMT+01:00 Denis Kudriashov : > On Mon, Nov 6, 2017 at 9:52 PM, Nicolas Cellier >> wrote: >> > Travis has just seeded the very simple and light library with chaining: >> > >> > points sorted: #x ascending , #y

Re: [Pharo-dev] about SortFunctions

> > On Mon, Nov 6, 2017 at 9:52 PM, Nicolas Cellier > wrote: > > Travis has just seeded the very simple and light library with chaining: > > > > points sorted: #x ascending , #y descending. > > > > Denis then added possibility to sort properties even if

Re: [Pharo-dev] about SortFunctions

> On 7 Nov 2017, at 01:21, Nicolas Cellier > wrote: > > Back to the thread: https://github.com/pharo-project/pharo/pull/440 Thx! > 2017-11-06 22:52 GMT+01:00 Ben Coman : > > > On Tue, Nov 7, 2017 at 4:52 AM, Nicolas Cellier >

Re: [Pharo-dev] about SortFunctions

I have other ideas yet. The selector undefinedFirst is good, but the implementation not so. I don't like the UndefinedSortFunction: too specific, compose oddly... In the PR, collatedBy: is the way to tell how we sort properties (if you have a better name, go, it's bikesheding day) "sort by

Re: [Pharo-dev] about SortFunctions

Back to the thread: https://github.com/pharo-project/pharo/pull/440 2017-11-06 22:52 GMT+01:00 Ben Coman : > > > On Tue, Nov 7, 2017 at 4:52 AM, Nicolas Cellier gmail.com> wrote: > >> >>> MC is not so bad. OK branches are not named (or neeed not

Re: [Pharo-dev] about SortFunctions

On Tue, Nov 7, 2017 at 4:52 AM, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > >> MC is not so bad. OK branches are not named (or neeed not be), GUID are > inferior to SHA, etc... > The biggest difference comes from github, that is the social environment, > not necessarily git. >

Re: [Pharo-dev] about SortFunctions

On Mon, Nov 6, 2017 at 9:52 PM, Nicolas Cellier wrote: > > > 2017-11-06 21:04 GMT+01:00 Stephane Ducasse : >> >> Hi nicolas >> >> While I know the ascending and other protocol, it is still unclear to >> me the composition aspect. Did

Re: [Pharo-dev] about SortFunctions

2017-11-06 21:04 GMT+01:00 Stephane Ducasse : > Hi nicolas > > While I know the ascending and other protocol, it is still unclear to > me the composition aspect. Did Travis write a tutorial > can we can use as documentation/comment? > > BTW > "Example: #('abc' 'de'

Re: [Pharo-dev] about SortFunctions

Hi nicolas While I know the ascending and other protocol, it is still unclear to me the composition aspect. Did Travis write a tutorial can we can use as documentation/comment? BTW "Example: #('abc' 'de' 'fghi') sorted: #size asscending" => "Example: (#('abc' 'de' 'fghi') sorted: #size)

Re: [Pharo-dev] about SortFunctions

On Mon, Nov 6, 2017 at 10:20 AM, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > > > 2017-11-06 10:51 GMT+01:00 Sven Van Caekenberghe : > >> >> >> > On 6 Nov 2017, at 10:37, Nicolas Cellier > l.com> wrote: >> > >> > Because it's a cross

Re: [Pharo-dev] about SortFunctions

2017-11-06 10:51 GMT+01:00 Sven Van Caekenberghe : > > > > On 6 Nov 2017, at 10:37, Nicolas Cellier gmail.com> wrote: > > > > Because it's a cross dialect library and because contributing in Squeak > is so much easier for me. > > > > I like the social

Re: [Pharo-dev] about SortFunctions

> On 6 Nov 2017, at 10:37, Nicolas Cellier > wrote: > > Because it's a cross dialect library and because contributing in Squeak is so > much easier for me. > > I like the social power provided by github and i know how to use git, at > least as an expert

Re: [Pharo-dev] about SortFunctions

Oh, I hope we will be able improve this process. But personally when I set up it first time everything start to be smooth. And when I repeat it from scratch it takes just couple of minutes. 2017-11-06 10:37 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > Because it's a cross

Re: [Pharo-dev] about SortFunctions

Because it's a cross dialect library and because contributing in Squeak is so much easier for me. I like the social power provided by github and i know how to use git, at least as an expert beginner. But it took me two hours to pick a pharo image, fork and clone the pharo repository, pick a pharo

Re: [Pharo-dev] about SortFunctions

It is difficult to compare to current Pharo version. Why you not produce Pharo pull request? 2017-11-06 0:06 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > I've put some of the proposed composition features into > > http://source.squeak.org/inbox/Collections-nice.766.mcz >

Re: [Pharo-dev] About Collator

2017-11-05 20:11 GMT+01:00 Denis Kudriashov : > > 2017-11-05 18:41 GMT+01:00 Nicolas Cellier gmail.com>: > >> As for -1 , 0 , 1, we must encode 3 possible results: >> >> value1 is before value2 (<) >> value1 is same rank as value2 (=) >> value1

Re: [Pharo-dev] about SortFunctions

I've put some of the proposed composition features into http://source.squeak.org/inbox/Collections-nice.766.mcz http://source.squeak.org/inbox/CollectionsTests-nice.283.mcz http://source.squeak.org/inbox/Collections-nice.766.diff http://source.squeak.org/inbox/CollectionsTests-nice.283.diff

Re: [Pharo-dev] About Collator

2017-11-05 18:41 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > As for -1 , 0 , 1, we must encode 3 possible results: > > value1 is before value2 (<) > value1 is same rank as value2 (=) > value1 is after value2 (>) > While it is well known comparison logic I would like to

<    1   2   3   4   5   6   7   8   9   10   >