[Pharo-dev] curious

I wasn't what to title this post. Please just take a moment to inspect... Object subclasses collect: [:class| class -> class methods size] thenSelect: [:map| (map value between: 1 and: 5) and: (map key printString first = $P) ]. Then choose (a random example)... "PackageChecker->1" item

Re: [Pharo-dev] , for vector creation

On Thu, Oct 26, 2017 at 11:45 PM, Tudor Girba wrote: > Thanks everyone for the nice discussion. > > So, after all arguments, we will remove Number>>, from Bloc. > > I think using Number>>, for vector creation makes quite some sense. > However, we have already seen that we

Re: [Pharo-dev] Github API on github

On Thu, Oct 26, 2017 at 9:51 PM, Norbert Hartl wrote: > Now the interesting question > > *drumroll* > > Will iceberg use this library??? > > Norbert > What risk would this have to Iceberg losing is generality to other git/non-git repos? cheers -ben > > > Am

Re: [Pharo-dev] feenk log

On Thu, Oct 26, 2017 at 4:00 AM, Tudor Girba wrote: > Hi, > > > On Oct 25, 2017, at 8:11 PM, Sean P. DeNigris > wrote: > > > > Denis Kudriashov wrote > >> Good initiative. > > > > +1 :) > > > > > > Denis Kudriashov wrote > >> Here is my twitter

Re: [Pharo-dev] feenk log

On Thu, Oct 26, 2017 at 2:15 PM, Clément Bera wrote: > Hi, > > Good work, > > In PolyMaths/SciSmalltalk vectors and matrix are already implemented > efficiently. I would recommend to share the same implementation. > By this, you mean move the "base" vector/matrix objects

Re: [Pharo-dev] Why 2017 sizeInMemory = 0?

Hi Marcus, On Thu, Oct 26, 2017 at 1:09 AM, Marcus Denker wrote: > > > On 26 Oct 2017, at 10:05, Denis Kudriashov wrote: > > Hi. > > Question from discord, why: > > 2017 sizeInMemory = 0 > > ? > > Looks like a bug, but maybe there is some reason

[Pharo-dev] [Pharo 7.0-dev] Build #230: SUCCESS

There is a new Pharo build available! The status of the build #230 was: SUCCESS. Could not extract further issue information from commit message: https://api.github.com/repos/pharo-project/pharo/pulls/386

[Pharo-dev] [Pharo 7.0-dev] Build #229: SUCCESS

There is a new Pharo build available! The status of the build #229 was: SUCCESS. Could not extract further issue information from commit message: Import so that we can do pull request review with latest version. Build Url:

Re: [Pharo-dev] , for vector creation

I do not turn on autoformatting and use the format menu entry on an as needed basis. Autoformatting on Seaside renderOn: methods is a royal PITA. Phil On Thu, Oct 26, 2017 at 8:44 PM, Peter Uhnák wrote: > > Autoformatting messing with my parentheses is just a mistake. > > I

Re: [Pharo-dev] , for vector creation

+1 BTW we should start looking for an location for PharoDays 2018 :) On Thu, Oct 26, 2017 at 5:53 PM, Tim Mackinnon wrote: > This turned into a much more interesting thread than I expected (gosh you > learn lots of stuff by reading comments). > > But I am impressed that

Re: [Pharo-dev] , for vector creation

Doru I was thinking that you would also have BlMargin because Margin is a nice concept. When I introduced it with Igor it simplified a lot of code in expand, shrink and other operations. Stef On Thu, Oct 26, 2017 at 11:39 AM, Tudor Girba wrote: > Hi, > > To make the

Re: [Pharo-dev] New Version of Zinc is using a deprecated method and breaking all the users

ah ok now I understand why we could not review pull requests. Thanks for taking care of that pablo. Stef On Thu, Oct 26, 2017 at 6:19 PM, teso...@gmail.com wrote: > Hello, >Zinc-Http is using a method that has been deprecated long time ago > and is affecting all the

Re: [Pharo-dev] , for vector creation

> Autoformatting messing with my parentheses is just a mistake. > I put them in, leave them where they are, 'kay? I do not need an editor that rewrites what I tell it. AST power or not. By the same argument you can tear apart any property of autoformatting. "Why is it messing with my indentation

Re: [Pharo-dev] , for vector creation

you could do 1 x + 2 y + 5 z and that expression will give you a 3d vector. but it creates a lot of intermediate objects On Thu, Oct 26, 2017 at 2:04 PM, Chris Cunningham wrote: > > > On Thu, Oct 26, 2017 at 7:09 AM, Sean P. DeNigris > wrote:

Re: [Pharo-dev] , for vector creation

Excellent decision Doru! Thanks Alexandre > On Oct 26, 2017, at 8:45 AM, Tudor Girba wrote: > > Thanks everyone for the nice discussion. > > So, after all arguments, we will remove Number>>, from Bloc. > > I think using Number>>, for vector creation makes quite some

[Pharo-dev] Zinc and Zodiac - Synching/Contributing

Hi Sven, for Zinc there is a new issue: 1. Zinc is using #asBytesDescription. It should not be used as it is deprecated https://github.com/pharo-project/pharo/pull/401 there is also 2. https://pharo.fogbugz.com/f/cases/20557 which is not yet integrated. I also proposed some

Re: [Pharo-dev] , for vector creation

On Thu, Oct 26, 2017 at 7:09 AM, Sean P. DeNigris wrote: > Maybe we can follow the FS/PP pattern > and scope the message to only-vector-like-things via an initial message, so > just like `$f asParser, …`, have `1 {vector-appropriate-message}, …`? > > So, something like 1

[Pharo-dev] New Version of Zinc is using a deprecated method and breaking all the users

Hello, Zinc-Http is using a method that has been deprecated long time ago and is affecting all the users of Zinc. I have created the issue ( https://pharo.fogbugz.com/f/cases/20596/Zinc-should-not-use-asBytesDescription-as-it-is-deprecated) and a PR to fix it in Pharo

Re: [Pharo-dev] , for vector creation

This turned into a much more interesting thread than I expected (gosh you learn lots of stuff by reading comments). But I am impressed that Feenk listened to what people were saying, distilled it down and didn’t take their ball home - thanks guys. Sometimes in all of these slightly robust

Re: [Pharo-dev] , for vector creation

Thanks everyone for the nice discussion. So, after all arguments, we will remove Number>>, from Bloc. I think using Number>>, for vector creation makes quite some sense. However, we have already seen that we have a few places where we have vectors: Bloc, PolyMath and Moose-Algos. The Bloc

Re: [Pharo-dev] , for vector creation

Tudor Girba-2 wrote > You mean like sending @ to a number, right? :) Ha ha, you got me ;) - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] , for vector creation

A clear separation between Point and Vector makes perfectly sense. Ideally, Point should be deprecated then. Otherwise it is a complexity growth. Hilaire Le 26/10/2017 à 11:39, Tudor Girba a écrit : To make the conversation more interesting, in Bloc we also have BlPoint with subclasses for

Re: [Pharo-dev] , for vector creation

Hi, > On Oct 26, 2017, at 4:09 PM, Sean P. DeNigris wrote: > > Peter Uhnák wrote >> But in both cases #, is sent to FileReference/Petit parser instance, so it >> is contained. >> You would use it on a (generic) Number and tie it to specific Bloc >> meaning. > > Yes, this

Re: [Pharo-dev] , for vector creation

Peter Uhnák wrote > But in both cases #, is sent to FileReference/Petit parser instance, so it > is contained. > You would use it on a (generic) Number and tie it to specific Bloc > meaning. Yes, this is exactly the problem. It is a reintroduction of a message like #name, which plagued us for so

Re: [Pharo-dev] Github API on github

> On 26 Oct 2017, at 15:51, Norbert Hartl wrote: > > Now the interesting question > > *drumroll* > > Will iceberg use this library??? what Guille did is an extract of Iceberg github api which at the time was a reinterpretation of Torsten’s api. I guess is possible,

Re: [Pharo-dev] Github API on github

Now the interesting question *drumroll* Will iceberg use this library??? Norbert > Am 26.10.2017 um 15:06 schrieb Tudor Girba : > > Even more awesomeness :). Thanks for doing this! > > Doru > > >> On Oct 26, 2017, at 2:02 PM, Torsten Bergmann

Re: [Pharo-dev] Github API on github

Even more awesomeness :). Thanks for doing this! Doru > On Oct 26, 2017, at 2:02 PM, Torsten Bergmann wrote: > > I already contacted Guille in a private message on this one. > > Because now we have three (sorted in order of appearance): > > 1.

Re: [Pharo-dev] Github API on github

I already contacted Guille in a private message on this one. Because now we have three (sorted in order of appearance): 1. https://balletie.github.io/GitHub/ (from Balletie, very complete) 2. https://github.com/astares/GitHub-API (a wrapper I wrote to play with the API) 3.

Re: [Pharo-dev] OSWindow in Pharo 6.1 stable

Thanks Ronie. Please keep us posted with the progress. Cheers, Doru > On Oct 19, 2017, at 7:48 PM, Ronie Salgado wrote: > > Hi Clément, > > Last night I was checking again the VM. If I remove the hack in the > ioProcessEvents, I can receive the events with SDL2, but as

Re: [Pharo-dev] Github API on github

Awesome. Doru > On Oct 20, 2017, at 10:07 AM, Guillermo Polito > wrote: > > Hi guys, > > I extracted and extended some of the github API from iceberg, so it can be > used as a standalone project. Maybe this is useful for somebody. > >

Re: [Pharo-dev] feenk log

Hi Doru, you say BLVector is implemented as having instance vars x,y instead of using an Array (like polymath), i guess perhaps because of speed considerations? but i wonder why you then dont use FloatArrays for vectors, their precision, although generally bad, is sufficient for graphics and they

Re: [Pharo-dev] , for vector creation

Hi, To make the conversation more interesting, in Bloc we also have BlPoint with subclasses for 2D, 3D and 4D. The reason for this is that we model explicitly the intention of usage even if they share the instance variable names. We did not use Point because we needed 3D and 4D as well and

[Pharo-dev] [Pharo 7.0-dev] Build #228: 20026-Diff-has-incorrect-positions-red-and-green-colors-of-changed-text

There is a new Pharo build available! The status of the build #228 was: SUCCESS. The Pull Request #396 was integrated: "20026-Diff-has-incorrect-positions-red-and-green-colors-of-changed-text" Pull request url: https://github.com/pharo-project/pharo/pull/396 Issue Url:

Re: [Pharo-dev] , for vector creation

Hi, > On Oct 26, 2017, at 10:36 AM, Denis Kudriashov wrote: > > 2017-10-26 10:20 GMT+02:00 Tudor Girba : > Hi, > > On Oct 26, 2017, at 10:10 AM, Denis Kudriashov wrote: > > > > Another question. > > > > Will not these vectors

Re: [Pharo-dev] UnifiedFFI Docs

> On 25 Oct 2017, at 21:39, Todd Blanchard wrote: > > OK, new question. > > How do I file this in? I was able to load tonel from iceberg. I added the > repo and it gave me a choice of packages to load and I loaded them using the > iceberg browser. > > I added this to

Re: [Pharo-dev] UnifiedFFI Docs

> On 25 Oct 2017, at 19:58, Todd Blanchard wrote: > > I did not - had no idea it existed. > > Is if fair to say that the 32 bit warning in the readme does not apply to > Pharo 64 bit? is not. I never tested it on 64bit :) in theory, it should work out of the box, but

Re: [Pharo-dev] , for vector creation

2017-10-26 10:20 GMT+02:00 Tudor Girba : > Hi, > > On Oct 26, 2017, at 10:10 AM, Denis Kudriashov > wrote: > > > > Another question. > > > > Will not these vectors deprecate Point in future ? Imaging that we will > completely move to Bloc. > > No.

Re: [Pharo-dev] feenk log

Hi Clément, I did not know that you had an interest in optimizing vector and matrix operations. Awesome! We definitely want to take a look at synergies. These low level things are needed for Bloc, but they definitely do not have to be in Bloc. Doru > On Oct 26, 2017, at 8:15 AM, Clément

Re: [Pharo-dev] , for vector creation

Hi, > On Oct 26, 2017, at 7:00 AM, Nicolai Hess wrote: > > > > Am 25.10.2017 10:50 PM schrieb "Torsten Bergmann" : > Hi, > > there might be reasons for an own 2D vector class (instead of using Point). > But still I dislike the reimplementation of ","

Re: [Pharo-dev] , for vector creation

> On Oct 26, 2017, at 8:52 AM, Peter Uhnák wrote: > > Automatic formatting will turn it into > > vector := 1,3,4,5,7,-2. > > Which is not as nice. While this can be an issue, I see it as secondary, because formatting should help recognize intention, not force us to comply

Re: [Pharo-dev] , for vector creation

Hi, > On Oct 26, 2017, at 10:10 AM, Denis Kudriashov wrote: > > Another question. > > Will not these vectors deprecate Point in future ? Imaging that we will > completely move to Bloc. No. Point is a perfectly reasonable data structure to describe a position. A Vector

Re: [Pharo-dev] , for vector creation

Hi, > On Oct 25, 2017, at 10:53 PM, Stephane Ducasse > wrote: > > In Polymath I guess that the vectors are longer. Vectors can be longer. We just use 2D and 3D in Bloc. > But if I'm correct it > is #( 12 23) asVector. I like this one. We’ll definitely take a look.

Re: [Pharo-dev] Why 2017 sizeInMemory = 0?

Because it is an immediate value. On 26 Oct 2017 10:06, "Denis Kudriashov" wrote: Hi. Question from discord, why: 2017 sizeInMemory = 0 ? Looks like a bug, but maybe there is some reason for this.

Re: [Pharo-dev] Why 2017 sizeInMemory = 0?

> On 26 Oct 2017, at 10:05, Denis Kudriashov wrote: > > Hi. > > Question from discord, why: > > 2017 sizeInMemory = 0 > > ? > > Looks like a bug, but maybe there is some reason for this. #sizeInMemory only takes into account object header size and the size of the

Re: [Pharo-dev] , for vector creation

Another question. Will not these vectors deprecate Point in future ? Imaging that we will completely move to Bloc. And what about Rectangle? (Bloc implements own BlRectangle). 2017-10-26 9:26 GMT+02:00 p...@highoctane.be : > #(1 3 4 5 7 -2) asVector > > Meh. > Ugly. > > {

[Pharo-dev] Why 2017 sizeInMemory = 0?

Hi. Question from discord, why: 2017 sizeInMemory = 0 ? Looks like a bug, but maybe there is some reason for this.

Re: [Pharo-dev] , for vector creation

#(1 3 4 5 7 -2) asVector Meh. Ugly. { 1. 3. 4. a. b } asVector is the natural consequence. v := (1,3,4,5,7,-2) asVector keeps the parens. But why do I need to do that? Autoformatting messing with my parentheses is just a mistake. I put them in, leave them where they are, 'kay? I do not need

Re: [Pharo-dev] , for vector creation

Automatic formatting will turn it into vector := 1,3,4,5,7,-2. Which is not as nice. And even though it looks ok for literal numbers (#(1 3 4 5 7 -2) asVector would work too), this starts to look quite generic: vector := width, height, depth. Question: why not extend @ notation? x @ y @ z?

[Pharo-dev] [ANN] Pharo Consortium New Platinum Member: JPMorgan Chase

The Pharo Consortium is very happy to announce that JPMorgan Chase has joined the Consortium as a Platinum Member. About - JPMorgan Chase: https://www.jpmorganchase.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to

Re: [Pharo-dev] , for vector creation

I also like the , message for those vectors and the concatenation of dimensions makes sense. vector := (1,3,4,5,7,-2). looks how it should be. Readable, easy to translate vector stuff from reference text. Phil On Thu, Oct 26, 2017 at 7:00 AM, Nicolai Hess wrote: > >

Re: [Pharo-dev] feenk log

Hi, Good work, In PolyMaths/SciSmalltalk vectors and matrix are already implemented efficiently. I would recommend to share the same implementation. In the next few years, I think we will improve the performance of those vectors/matrix library using the processor vector instructions, and it