Re: [Pharo-dev] , for vector creation

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 "," because for me so far it has the meaning of "concatenating things". Like concatenating

Re: [Pharo-dev] , for vector creation

I would note that 1 ! 2 creates/extends an ETuple in eLinda. - HH On Wed, Oct 25, 2017 at 16:53, Stephane Ducasse wrote: > In Polymath I guess that the vectors are longer. But if I'm correct it is #( > 12 23) asVector. Doru did you look at Jun because Jun introduced

Re: [Pharo-dev] feenk log

Tudor Girba-2 wrote > We now have BlScalableElement which handles the zooming Gotcha. So an entire "World" (I'm assuming that's a Bloc Space?) can be zoomed in and out? - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] , for vector creation

2017-10-25 22:53 GMT+02:00 Stephane Ducasse : > In Polymath I guess that the vectors are longer. But if I'm correct it > is #( 12 23) asVector. > And I am wondering, Polymath already implements linear algebra. Right? Can we just use it in Bloc? > > Doru did you look at

Re: [Pharo-dev] feenk log

On Wed, Oct 25, 2017 at 7:04 PM, Aliaksei Syrel wrote: > Hi Stef, > > In this email I will enumerate what features are missing that we are aware > of. The problem is that we discover what we need spontaneously during > experiments and not beforehand :) Yes for the extras

Re: [Pharo-dev] feenk log

Ok :) Stef On Wed, Oct 25, 2017 at 7:58 PM, Tudor Girba wrote: > Hi Stef, > > The log is not a replacement of the roadmap. It is only to help people see > what we do live. > > The roadmap and documentation are coming as well, but these are separate. > > Cheers, > Doru > >

Re: [Pharo-dev] , for vector creation

In Polymath I guess that the vectors are longer. But if I'm correct it is #( 12 23) asVector. Doru did you look at Jun because Jun introduced 3DPoint and I wonder if they did not introduce Vector? What would be the alternatives for vector? Any idea how this is done in other languages 1~>2 1!2

[Pharo-dev] , for vector creation

Hi, there might be reasons for an own 2D vector class (instead of using Point). But still I dislike the reimplementation of "," because for me so far it has the meaning of "concatenating things". Here you redefine it to create vector instances and it works only up to three so far. Right? I

Re: [Pharo-dev] feenk log

2017-10-25 22:00 GMT+02:00 Tudor Girba : > 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 questions:… > > >

Re: [Pharo-dev] feenk log

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 questions:… > > Mine are: > 1. Is it possible/easy/smooth to zoom in/out? We now have

Re: [Pharo-dev] UnifiedFFI Docs

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 the iceberg browser and there are no packages listed and I have absolutely no clue how to

Re: [Pharo-dev] , for vector creation

Hi, Vector is not Bloc-sepcific. We just need it in Bloc and because there wasn’t any, we now have one in Bloc. But, it can be pulled out without any issues. Cheers, Doru > On Oct 25, 2017, at 8:21 PM, Peter Uhnák wrote: > > For example, in FileReference is adds a file

Re: [Pharo-dev] , for vector creation

> > For example, in FileReference is adds a file extension. PetitParser uses > it as a sequence operator. > 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. Maybe have a polymorphic

Re: [Pharo-dev] feenk log

Denis Kudriashov wrote > Good initiative. +1 :) Denis Kudriashov wrote > Here is my twitter questions:… Mine are: 1. Is it possible/easy/smooth to zoom in/out? 2. Is there an equivalent to Morphic-stepping? - Cheers, Sean -- Sent from:

[Pharo-dev] , for vector creation

Hi, As mentioned in the separate thread, we played with introducing the extension: , aNumber ^ BlVector2D x: self y: aNumber This means that (10,20) will return a 2D vector. We also have (10,20,30) which returns a 3D vector. , is used for different meanings already in the image beside

Re: [Pharo-dev] feenk log

Hi, That is the point of making fine grained things explicit: to have the chance to disagree and discuss :). I will spawn a separate thread. Doru > On Oct 25, 2017, at 7:42 PM, Alexandre Bergel wrote: > >> Personally (10, 20) for a vector is not really nice and I

Re: [Pharo-dev] feenk log

Hi Stef, The log is not a replacement of the roadmap. It is only to help people see what we do live. The roadmap and documentation are coming as well, but these are separate. Cheers, Doru > On Oct 25, 2017, at 6:45 PM, Stephane Ducasse wrote: > > Doru having a few

Re: [Pharo-dev] UnifiedFFI Docs

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? > On Oct 25, 2017, at 7:35 AM, Esteban Lorenzano wrote: > > :) > > Did you look at this project: >

Re: [Pharo-dev] feenk log

> Personally (10, 20) for a vector is not really nice and I would really > like to have a discussion before. +1 The Pharo syntax should remain an asset, not become a trap. Alexandre > > > On Wed, Oct 25, 2017 at 6:45 PM, Stephane Ducasse > wrote: >> Doru having

Re: [Pharo-dev] feenk log

Hi Stef, In this email I will enumerate what features are missing that we are aware of. The problem is that we discover what we need spontaneously during experiments and not beforehand :) Missing / broken - error handling library. If there is an exception during event handling or rendering,

Re: [Pharo-dev] Pharo Process question

Well I would dream to give my superpower to attract bugs to anybody else. Because sometimes this is tiring. Yesterday a class comment changes of mine broke our jenkins process. Do not ask me why and how it is possible. But it did. Stef On Wed, Oct 25, 2017 at 12:40 PM, Norbert Hartl

Re: [Pharo-dev] feenk log

Hi Denis, The reason for BlVector2D is that we also have BlVector*3*D. In case of translation a Point (x@y) should be converted to (x,y,0). For scale it is converted as (x,y,1). You see, the same Point object has different meanings when it comes to different transformations. Additionally, Point

Re: [Pharo-dev] feenk log

Personally (10, 20) for a vector is not really nice and I would really like to have a discussion before. On Wed, Oct 25, 2017 at 6:45 PM, Stephane Ducasse wrote: > Doru having a few tweets is nice but I do not think that you > communicate well around bloc. > > What I

Re: [Pharo-dev] feenk log

Doru having a few tweets is nice but I do not think that you communicate well around bloc. What I would like to get is a roadmap for Bloc V1.0. - Here are the missing features (documentation), - Here are where we are. Because else it feels like Bloc will never ends. You will argue and tell me

Re: [Pharo-dev] feenk log

Doru using comma for creating vectors is not really because it will just make the life of type inferencers more difficult. On Wed, Oct 25, 2017 at 5:53 PM, Tudor Girba wrote: > Hi, > > Our team is working on a couple of projects that are relevant for the core of > Pharo,

Re: [Pharo-dev] feenk log

Hi. Good initiative. Here is my twitter questions: - What the reason to introduce BlVector2D instead of using existing Point? - How often this vector will be constructed by hands in user code? It is related to my question about comma message: is it really needed? Now you can evaluate (10*,* 20)

Re: [Pharo-dev] [Pharo 7.0-dev] Build #227: 20589-update-iceberg-to-062

copy of the changelog: v0.6.2 This is a bugfix release. Issues: #486 Failing cloning behind a proxy bug #490 trying to browse an iceberg package in monticello raises error bug #457 Iceberg fails to parse valid URLs bug #489 timeout when trying to clone a private gitlab repo bug #488 remoteurl

[Pharo-dev] [Pharo 7.0-dev] Build #227: 20589-update-iceberg-to-062

There is a new Pharo build available! The status of the build #227 was: SUCCESS. The Pull Request #397 was integrated: "20589-update-iceberg-to-062" Pull request url: https://github.com/pharo-project/pharo/pull/397 Issue Url: https://pharo.fogbugz.com/f/cases/20589 Build Url:

[Pharo-dev] feenk log

Hi, Our team is working on a couple of projects that are relevant for the core of Pharo, namely GT and Bloc/Brick. At ESUG we were asked by several people, and Stef in particular, to make the progress on these projects more transparent. To this end, we will start two streams of signals: - fine

Re: [Pharo-dev] Bloc Feedback

Hi Sean, > On Oct 25, 2017, at 2:14 PM, Sean P. DeNigris wrote: > > Aliaksei Syrel wrote >> I don't understand how you guys find these kind of bugs :D > > We have a talent for destruction ;) > > > Aliaksei Syrel wrote >> Aha, I forgot about it, thanks! At this point

Re: [Pharo-dev] UnifiedFFI Docs

:) Did you look at this project: https://github.com/estebanlm/libclang-pharo-bindings/ ? it was using parseTranslationUnit (no 2)… there you can find how is being used (I just converted it to tonel format, but older versions are in

Re: [Pharo-dev] Bloc Feedback

Aliaksei Syrel wrote > I don't understand how you guys find these kind of bugs :D We have a talent for destruction ;) Aliaksei Syrel wrote > Aha, I forgot about it, thanks! At this point BlTextEditElement is only > used internally by Moldable Editor so I will probably move it away from > Bloc.

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

> On 25 Oct 2017, at 14:02, Sean P. DeNigris wrote: > > Sven Van Caekenberghe-2 wrote >> And here is how to do it in Pharo… > > It would be great to add something like this to Launcher Yeah, but file readStreamDo: [ :in | sha256 := SHA256 hashStream: in ]. is very

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

Sven Van Caekenberghe-2 wrote > And here is how to do it in Pharo… It would be great to add something like this to Launcher - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] Bloc status

That’s great it works for you. Be careful that using Metacello baseline script does not update the local GIT repositories to the latest versions. Check my recent post in Moose: http://forum.world.st/RTExampleFactory-is-missing-sourceClass-tp4990173p4991063.html

Re: [Pharo-dev] Pharo Process question

But don't complain for the coming weeks about things not working ;) Norbert > Am 25.10.2017 um 12:16 schrieb Stephane Ducasse : > > Thanks guys. > Let us move to tonel :) > So I have to watch out then before pushing the button ;) > Stef > > > On Wed, Oct 25, 2017 at

Re: [Pharo-dev] Pharo Process question

Thanks guys. Let us move to tonel :) So I have to watch out then before pushing the button ;) Stef On Wed, Oct 25, 2017 at 10:10 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > > > On Tue, Oct 24, 2017 at 9:49 PM, Esteban Lorenzano > wrote: > >> >> >> > On 24

[Pharo-dev] [ANN] LAM Research upgraded to Platinum Membership

The Pharo Consortium is very happy to announce that LAM Research has upgraded to Platinum Member status. About - LAM Research: http://www.lamresearch.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

>> >>> Would it not be cleaner if the signature was next to the resource ? Like >>> >>> http://files.pharo.org/platform/Pharo6.1-mac.zip.sha256.txt >>> >>> Or is that the next step ? >>> >> >> Already there. But a signature like that is not a guarantee if it is >> downloaded from the same

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

> On 25 Oct 2017, at 10:33, Marcus Denker wrote: > > > >> On 25 Oct 2017, at 10:23, Sven Van Caekenberghe wrote: >> >> Great! >> >> And here is how to do it in Pharo: >> >> signature := >>

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

> On 25 Oct 2017, at 10:33, Marcus Denker wrote: > > > >> On 25 Oct 2017, at 10:23, Sven Van Caekenberghe wrote: >> >> Great! >> >> And here is how to do it in Pharo: >> >> signature := >>

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

> On 25 Oct 2017, at 10:23, Sven Van Caekenberghe wrote: > > Great! > > And here is how to do it in Pharo: > > signature := > 'https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-5-Publish/lastSuccessfulBuild/artifact/Pharo6.1-mac.zip.sha256.txt' > asUrl retrieveContents

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

Great! And here is how to do it in Pharo: signature := 'https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-5-Publish/lastSuccessfulBuild/artifact/Pharo6.1-mac.zip.sha256.txt' asUrl retrieveContents findTokens: Character separators. hash := signature first. signedFile := signature second. url

Re: [Pharo-dev] Pharo Process question

On Tue, Oct 24, 2017 at 9:49 PM, Esteban Lorenzano wrote: > > > > On 24 Oct 2017, at 21:47, Stephane Ducasse > wrote: > > > > Hi > > > > are the pending PR reevaluated when one PR is integrated? > Unfortunately not on every integration... We should

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

How to validate a Pharo6 download with the example of the mac download: 1) get the checksum file (note: uses SSL): https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-5-Publish/lastSuccessfulBuild/artifact/Pharo6.1-mac.zip.sha256.txt 2) download Pharo:

Re: [Pharo-dev] Bloc status

Hi, > On Oct 25, 2017, at 12:02 AM, Sean P. DeNigris wrote: > > Juraj Kubelka wrote >> Or you may share repositories among images… kIceRepository >> sharedRepositoriesLocationString > > That was it! It was >

[Pharo-dev] [Pharo 7.0-dev] Build #226: 20569-Update-Layout-class-comment

There is a new Pharo build available! The status of the build #226 was: SUCCESS. The Pull Request #385 was integrated: "20569-Update-Layout-class-comment" Pull request url: https://github.com/pharo-project/pharo/pull/385 Issue Url: https://pharo.fogbugz.com/f/cases/20569 Build Url: