Re: [Pharo-dev] [TechTalk] April 12: GIT with Iceberg

This is today 5:00 PM - 7:00 PM (UTC+02:00) There is a calendar entry to download at: https://association.pharo.org/event-2797068 > On 10 Apr 2018, at 16:34, Marcus Denker wrote: > > Hi, > > There next TechTalk will be April 12: GIT with Iceberg > > https://

[Pharo-dev] [Newsletter] Content Needed

Hi, The Pharo Monthly Newsletter is working quite well. https://newsletter.pharo.org We now reached a level where it is not just 3 things, but much much more.. of course this comes with a downside: - Sometimes topics that would be worth a small article a

Re: [Pharo-dev] request Calypso added as a "project" in Fogbugz

> On 13 Apr 2018, at 11:28, Ben Coman wrote: > > Can Calypso be added as a "project" in Fogbugz? > I went to create an issue but could not find an appropriate place to file it > under. > I added it. > As a backup I add an issue to the github tracker... > https://github.com/dionisiydk/Calyps

[Pharo-dev] [ANN] Pharo Sprint Apr 20

Pharo Sprint Apr 20 https://association.pharo.org/event-2789579 We will organize a Pharo sprint / Moose dojo Apr 20 , starting at 10:00am. (Local Time Paris). Goals of this sprint: • Pharo 7 issues Remote Sprint Remotely, you can join us on Discord. During the s

Re: [Pharo-dev] [Pharo-users] [TechTalk] April 12: GIT with Iceberg

do next week: -> an update to the description on the website how to commit to PR -> Do a short video of how to do contribute to Paro7 (as a replacement of the video tutorial I did). Marcus > > On Thu, Apr 12, 2018, 03:10 Marcus Denker <mailto:marcus.den...@

Re: [Pharo-dev] [Pharo 7.0-dev] Build #775: Revert "21429-Watchpoints-should-be-cleaned-when-system-changed"

It is nice how easy a faulty merge can be reverted now… > On 17 Apr 2018, at 13:33, ci-pharo-ci-jenki...@inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #775 was: SUCCESS. > > The Pull Request #1209 was integrated: "Revert > "21429-Watchpoints-shoul

Re: [Pharo-dev] Fun with AST evaluation

> On 18 Apr 2018, at 07:41, Stephane Ducasse wrote: > > So this means that we could also have a simple hover showing the variable > values when debugging. > It could be used for that, but then we did have already lookupSymbol: on context (we added that so we can easily use any valid variabl

Re: [Pharo-dev] Fun with AST evaluation

> On 18 Apr 2018, at 08:11, Marcus Denker wrote: > > > >> On 18 Apr 2018, at 07:41, Stephane Ducasse wrote: >> >> So this means that we could also have a simple hover showing the variable >> values when debugging. >> > It could be used for th

Re: [Pharo-dev] Fun with AST evaluation

> On 17 Apr 2018, at 17:45, Marcus Denker wrote: > > Hi, > > This is fun experiment: > > Every RBValueNode subclass evaluates to something. So why not implement a > #evaluate method? > I have committed the code (with tests) here: https://github.com/ph

Re: [Pharo-dev] [ANN] Pharo Sprint Apr 20

This is tomorrow. > On 13 Apr 2018, at 14:32, Marcus Denker wrote: > > Pharo Sprint Apr 20 > > https://association.pharo.org/event-2789579 > > We will organize a Pharo sprint / Moose dojo Apr 20 , starting at > 10:00am. (Local Time Paris). &

Re: [Pharo-dev] [Pharo 7.0-dev] Build #796: 21761-change-asDoItIn-to-asDoItForContext

For AST evaluation I continue to improve things step-by-step. e.g. this PR - improves the method that wraps ASTs into doit-methods in the case where we want to execute for a certain context (#asDoItForContext: does all the magic of rewriting temps and adding a return) - OpalCompiler>>#parse w

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

> On 23 Apr 2018, at 11:38, Sven Van Caekenberghe wrote: > > Hi, > > I got the new Iceberg working on the latest Pharo 7 (used it to commit > something to P3) - authentication should be OK then I guess. It feels much > better. > > I would like to try contributing to Pharo again. > > Has ht

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

>> >> we are finishing an iteration that will speed things up. >> IMO it should be a lot simpler, but well. >> Tomorrow I will record a new “how to contribute”. > > OK, I will wait a day or two. > But please (someone) also write a short document. > I will update the description with the conten

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

> On 23 Apr 2018, at 12:47, Torsten Bergmann wrote: > > Hi Sven > > if you like you can also use my > "https://github.com/astares/pharo-contributor"; - at least > on Ubuntu (where I wrote, tested and use it) > Ah, yes, this reminds me to have a look at your contribution tool again, too. (

Re: [Pharo-dev] Fix for 21809

> On 29 Apr 2018, at 16:17, Hilaire wrote: > > Hi, > > More freedom in the text color for tooltips for a better visibility (see > screenshot). > > https://pharo.fogbugz.com/f/cases/21809/Both-tooltips-text-and-background-color-should-be-property-of-a-graphic-Theme > > Change set fix attach

Re: [Pharo-dev] [Pharo 7.0-dev] Build #890: 21896-Cleanup-Shout

Builds are failing du to CI problems…. e.g this one missing workspace /builds/workspace/branch_Pipeline_development-CMOUMEH7DVLJPL2EIJ6VPEHUQRS3W4AK3FD4ESTKJ3YGKZERQFUQ on pharo-ci-jenkins2-bootstrap-unix-2 But the granularity of PRs are very small (and they are tested on the PR level, too), so

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

> > > For ByteArray, I didn't check recently in Pharo, but I know that it's quite a > mess in Squeak because some methods are in Alien, other in FFI, other in base > Squeak... > IMO all methods should be in core Squeak/Pharo because of general usage (like > decoding binary data). > I want to

Re: [Pharo-dev] File/Stream changes: one Integer decoder/encoder to rule them all

> On 14 May 2018, at 15:09, Nicolas Cellier > wrote: > > > > 2018-05-14 14:44 GMT+02:00 Marcus Denker <mailto:marcus.den...@inria.fr>>: > > > > > > For ByteArray, I didn't check recently in Pharo, but I know that it's quite > &

[Pharo-dev] Unstable CI: Issue to collect all the error messages

Hi, The CI is a bit unstable. I added an issue tracker entry so we can record what exactly is going wrong (there seem to be 4-5 undefended issues) https://pharo.fogbugz.com/f/cases/21910/CI-is-unstable

[Pharo-dev] [ANN] Pharo Sprint May 25

Pharo Sprint May 25 https://association.pharo.org/event-2789581 We will organize a Pharo sprint / Moose dojo May 25 , starting at 10:00am. (Local Time Paris). Goals of this sprint: • Pharo 7 issues Remote Sprint Re

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

> On 4 Apr 2018, at 18:02, Marcus Denker wrote: > > Hi, > > Some code is very “active”, executed all the time, e.g. collections, > graphics… or imagine if you work on the compiler or debugger. > > It would really be nice if we could test a change before accepti

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

> On 16 May 2018, at 18:21, Denis Kudriashov wrote: > > Hi Marcus. > I commented on github. > > 2018-05-16 18:34 GMT+03:00 Marcus Denker <mailto:marcus.den...@inria.fr>>: > > > > On 4 Apr 2018, at 18:02, Marcus Denker > <mailto:marcus.den...

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

> On 17 May 2018, at 11:46, Denis Kudriashov wrote: > > > 2018-05-17 10:53 GMT+03:00 Marcus Denker <mailto:marcus.den...@inria.fr>>: > On 16 May 2018, at 18:21, Denis Kudriashov <mailto:dionisi...@gmail.com>> wrote: >> >> Hi Marcus. >> I

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

> > To me the fact that it uses a meta-link is purely an implementation artefact, > other than for breakpoints, watchpoints, where we annotate > the AST with actions… > > I only speak about management implementation. The way how registries of > breakpoints and watchpoints are maintained and use

Re: [Pharo-dev] Idea and proof of concept: Accept for Test

> On 17 May 2018, at 12:59, Denis Kudriashov wrote: > > > 2018-05-17 13:00 GMT+03:00 Marcus Denker <mailto:marcus.den...@inria.fr>>: > >> I really wonder if this is the same as breakpoint. E.g. it only applies to >> the whole method, it is not an “act

[Pharo-dev] [TechTalk] TODAY, 17h: Pillar

Hi, Today, 17h europe time. Pharo TechTalk: Pillar https://association.pharo.org/event-2797069 Sorry for the late announcement (we did not know if we could make it today) Marcus

Re: [Pharo-dev] [TechTalk] TODAY, 17h: Pillar

> On 17 May 2018, at 15:44, Marcus Denker wrote: > > Hi, > > Today, 17h europe time. > > Pharo TechTalk: Pillar > https://association.pharo.org/event-2797069 > > Sorry for the late announcement (we did not know if we could make it today) > https://w

[Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

Hi, the #binding: API until now did not allow to shadow globals. But there is actually no reason to forbid that (and it can actually be interesting, e.g. to compile code where one class ref is switched to another). The Pull Request does: - add comment to OCExtraBindingScope - categorize tests

[Pharo-dev] Deprecating addSelector:withMethod:notifying:

Hi, if you try to follow the code that is executed when adding a method, it gets quite complex. One reason was that there where both #basicAddSelector:withMethod and #addSelectorSilently:withMethod. I have cleaned that up already. The next step is addSelector:withMethod:notifying: We never us

Re: [Pharo-dev] [Pharo 7.0-dev] Build #917: 21922-bindings--allow-shadowing-of-Globals

There is still a problem with assignments, I will fix that in another pass as it was already not correct before.. > On 18 May 2018, at 12:20, ci-pharo-ci-jenki...@inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #917 was: SUCCESS. > > The Pull Request

Re: [Pharo-dev] [TechTalk] TODAY, 17h: Pillar

> On 17 May 2018, at 15:44, Marcus Denker wrote: > > Hi, > > Today, 17h europe time. > > Pharo TechTalk: Pillar > https://association.pharo.org/event-2797069 > > Sorry for the late announcement (we did not know if we could make it today) > The r

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> On 18 May 2018, at 10:39, Marcus Denker wrote: > > Hi, > > the #binding: API until now did not allow to shadow globals. But there is > actually no reason to forbid that > (and it can actually be interesting, e.g. to compile code where one class ref > is switched to

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> > A second iteration now makes it work correctly for assignments: > > https://github.com/pharo-project/pharo/pull/1397 > > Smalltalk compiler >bindings: {(#test -> Point)} asDictionary; >evaluate: 'test := 42’. While #bindings: allows us now to add additional bindings or

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> On 23 May 2018, at 11:49, Thierry Goubier wrote: > > Marcus, > > can you do inheritence / masking of a hierarchy of system dictionaries ? > > Could be used to make "kind of" sandboxes, around, say, user code so > that it does not have the ability to override a certain system core. > Yes,

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> On 23 May 2018, at 13:30, Thierry Goubier wrote: > > 2018-05-23 13:20 GMT+02:00 Sean P. DeNigris : >> Marcus Denker-4 wrote >>> method := Smalltalk compiler >>> environment: environment; >>>

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> On 23 May 2018, at 13:47, Marcus Denker wrote: > > > >> On 23 May 2018, at 13:30, Thierry Goubier wrote: >> >> 2018-05-23 13:20 GMT+02:00 Sean P. DeNigris : >>> Marcus Denker-4 wrote >>>> method := Smalltalk compiler >>>&g

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> On 23 May 2018, at 13:53, Marcus Denker wrote: > > > >> On 23 May 2018, at 13:47, Marcus Denker wrote: >> >> >> >>> On 23 May 2018, at 13:30, Thierry Goubier wrote: >>> >>> 2018-05-23 13:20 GMT+02:00 Sean P. DeNigris : &

Re: [Pharo-dev] files.pharo.org, get.pharo.org problems?

> On 23 May 2018, at 21:20, Martin McClure wrote: > > On 05/23/2018 11:57 AM, Martin McClure wrote: >> I'm getting 503 errors on attempts to contact both sites -- is this a known >> issue? no, this is a commercial Hoster where we do not administer the servers. We did that to have more stable

Re: [Pharo-dev] files.pharo.org, get.pharo.org problems?

> On 24 May 2018, at 14:19, Sean P. DeNigris wrote: > > Marcus Denker-4 wrote >> We need to think about finding another. > > I've had success with https://www.siteground.com/ and > http://www.namecheap.com for personal hosting, but can't say about bulk >

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> On 18 May 2018, at 10:39, Marcus Denker wrote: > > Hi, > > the #binding: API until now did not allow to shadow globals. But there is > actually no reason to forbid that > (and it can actually be interesting, e.g. to compile code where one class ref > is switched to

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> > Shortcomings: > -> extensions are not treated, only the main package > -> Not used much, for sure needs testing to see if this really works. —> there might be other places in addition global #compilerClass: where we need to point to the overlay version For th

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> > So what can we do with this? If you develop a compiler, it is always very > annoying that any change that you do actually breaks the compiler if you do > it wrong. Larger changes over multiple methods get quite hard to do. > > One thing that we will soon have is the “accept for test” featu

Re: [Pharo-dev] [Pharo 7.0-dev] Build #969: 21964-SmalltalkImage-transforming-deprecations-for-old-API

Hello, this puts some transformers on method on “SmalltalkImage” to force people to use “Smalltalk globals” when accessing the global environment. For now these methods are in “Deprecated70”, but we will move them to some compatibility package and not actually remove them for some time. This j

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> On 28 May 2018, at 12:07, Marcus Denker wrote: > >> >> Shortcomings: >> -> extensions are not treated, only the main package >> -> Not used much, for sure needs testing to see if this really works. > > —> there might be other pl

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

> On 29 May 2018, at 11:41, Marcus Denker wrote: > > > >> On 28 May 2018, at 12:07, Marcus Denker > <mailto:marcus.den...@inria.fr>> wrote: >> >>> >>> Shortcomings: >>> -> extensions are not treated, only the main packa

Re: [Pharo-dev] [Pharo 7.0-dev] Build #987: 21928-Remove-PluggableButtonMorph-option-to-use-gradient-since-its-not-used-and-style-it-decided-by-the-theme

/builds/workspace/branch_Pipeline_development-CMOUMEH7DVLJPL2EIJ6VPEHUQRS3W4AK3FD4ESTKJ3YGKZERQFUQ/32/vmtarget/pharo: line 11: 20806 Terminated "$DIR"/"pharo-vm/pharo" --nodisplay "$@" script returned exit code 143 > On 30 May 2018, at 12:06, ci-pharo-ci-jenki...@inria.fr wrote: > > There

Re: [Pharo-dev] server slow

We really need to switch the server again to something better. I will work on that in June. > On 1 Jun 2018, at 03:55, Ben Coman wrote: > > Server access is very slow for me right now. It took 20 seconds to bring up > the directory index for... > https://files.pharo.org/image

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

> On 5 Jun 2018, at 18:55, Martin Dias wrote: > > On Tue, Jun 5, 2018 at 12:35 PM Cyril Ferlicot D. > wrote: >>> >> >> Hello Martin, >> >> Thank you for the clarification. >> >> Can we start to change things in Epicea (like renaming tests packages to >> follow the convention) or do you st

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

> On 5 Jun 2018, at 20:49, Martin Dias wrote: > > On Tue, Jun 5, 2018 at 3:30 PM Hernán Morales Durand > wrote: >> What are Ombu and Hiedra? > > Hello Hernán, this is how I described them: > > Ombu: > "Epicea has a small subproject, named Ombu, which provides simple > persistence. By defaul

[Pharo-dev] #literals and #hasLiteral: not in sync

Hi, As you might now, we abuse the literals of compiled methods to hold on to the class and the literal. (and the place used to store the literal is used for additional properties if there are some). So right now we have the problem that #literals just returns all the literals and clients do “a

[Pharo-dev] [Issue Tracker] Please check issue tracker

Hi, If you -> submitted an issue in the past -> have been involved in some discussion about an issue ===> please check the issue tracker. There are many cases where e.g. - some issue has been fixed but the issue tracker entry is not closed - where a discussion cam

Re: [Pharo-dev] #literals and #hasLiteral: not in sync

literals: syntaxLiterals, semanticLiterals, userLiterals, > sourceCodeLiterals > I am not sure. that looks even more complex to me. > 2018-06-08 11:17 GMT+03:00 Marcus Denker <mailto:marcus.den...@inria.fr>>: > Hi, > > As you might now, we abuse the literals of compiled

Re: [Pharo-dev] Pharo 7 and Traits ?

> On 14 Jun 2018, at 12:56, Sven Van Caekenberghe wrote: > > Bump. > >> On 5 Nov 2017, at 23:19, Sven Van Caekenberghe wrote: >> >> Hi, >> >> So what is the story with Pharo 7 and Traits ? >> >> I may be wrong, but were they not removed but flattened ? >> >> How are external libraries th

Re: [Pharo-dev] Recent Pharo does not work (to me) with "El Capitan"

> On 13 Jun 2018, at 23:41, Esteban Lorenzano wrote: > > > >> On 13 Jun 2018, at 22:57, Jordi Delgado wrote: >> >> Yes, I did. Same result. >> >> All the same happens with the latest version of Squeak. >> >> I tried with High Sierra. In HS Pharo 6.1 starts, the image opens but >> then it

[Pharo-dev] 1500 pull requests closed

Hi, As of today, we closed 1500 pull requests: https://github.com/pharo-project/pharo/pulls These of course range from trivialities to merging sub-systems with hundreds of commits… Marcus

[Pharo-dev] @pharoproject: > 2000 followers

@pharoproject on twitter now has >2000 followers: https://twitter.com/pharoproject

Re: [Pharo-dev] strange debugging

Thanks, I made a note and will look (I hope next week) > On 15 Jun 2018, at 01:07, Ben Coman wrote: > > Not sure if this is intended behaviour... > > in a brand new build 71053, open a browser GTGenericStackDebuggerTest >> > testBasic > > right-click and choose "Debug" > > the debugger opens

[Pharo-dev] Call for TechTalks

Hi, As you might now, we organised “tech talks” in the past: https://pharo.org/TechTalk We would like to continue the next half of 2018 with this series. The form itself is quite open: it can be a lecture, a demo, or just some “guided” discussion on Discord

Re: [Pharo-dev] memory leak

> On 2 Jun 2018, at 17:53, John Brant wrote: > > On 05/26/2018 05:21 AM, Tudor Girba wrote: >> Yes, Glamour is stable since years. Yes, we did have some leak issues that >> appeared along the way. Last year, we discovered that a memory leak came >> from Rubric (specifically there was a globa

Re: [Pharo-dev] Call for TechTalks

That would be great! What date would be good? > On 15 Jun 2018, at 12:44, Serge Stinckwich wrote: > > > > On Fri, Jun 15, 2018 at 11:36 AM Marcus Denker <mailto:marcus.den...@inria.fr>> wrote: > Hi, > > As you might now, we organised “tech talks” in the p

[Pharo-dev] Pharo Sprints second half 2018

Pharo Sprints second half 2018 We organise one Pharo “Sprint” per month were we meet to work on boring issue tracker entries together. Goals of the next sprints: - Fix issues for Pharo7 - Backport important fixes to Pharo6 - Clean issue tracker to prepare for release Pharo7

[Pharo-dev] [ANN] TechTalk Dates second half 2018

Here are the next dates for the Pharo Techtalks. 12 Jul 2018: Pharo TechTalk: Machine Learning with TensorFlow and Pharo https://association.pharo.org/event-2973748 For the others we have no topic yet, but dates are pre-fixed to: 23 Aug 2018: Pharo TechTalk https://association.pharo.o

[Pharo-dev] [ANN] Next Pharo Sprint: Jun 29

We will organize a Pharo sprint / Moose dojo Jun 29, starting at 10:00am. (Local Time Paris). Goals of this sprint: • Pharo 7 issues Remote SprintL Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contri

Re: [Pharo-dev] strange debugging

. (but it is there in case you would run the test again, that is why a once break is nicer). Marcus > On 15 Jun 2018, at 12:18, Marcus Denker wrote: > > Thanks, I made a note and will look (I hope next week) > >> On 15 Jun 2018, at 01:07, Ben Coman wrote: >>

Re: [Pharo-dev] strange debugging

1053, open a browser GTGenericStackDebuggerTest >> > >> testBasic > >> > >> right-click and choose "Debug" > >> > >> the debugger opens about on the third statement. > >> Clicking doesn't improve things, > >> and t

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 (https://pharo.

[Pharo-dev] [ANN] New Academic Partner: ENIT

[ANN] New Academic Partner: ENIT The Pharo Consortium is very happy to announce that ENIT has joined as a Academic Partner. About - ENIT Ecole Nationale d'ingénieurs de Tarbes: http://www.enit.fr - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow compan

[Pharo-dev] [ANN] New Academic Partner: SQLab

The Pharo Consortium is very happy to announce that SQLab has joined as a Academic Partner. About - Software Quality Laboratory, Part of University of Novi Sad: https://sqlab.pmf.uns.ac.rs - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and

[Pharo-dev] [ANN] New Academic Partner: University of Yaoundé 1

The Pharo Consortium is very happy to announce that University of Yaoundé 1 has joined as a Academic Partner. About - University of Yaoundé 1: http://www.uy1.uninet.cm - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to suppo

[Pharo-dev] 12 Jul Pharo TechTalk: Tensorflow

Pharo TechTalk: Tensorflow A regular chat about Pharo. Happens on Discord. The Tech talks are open to both members and non-members! Topic: Machine Learning with TensorFlow and Pharo https://association.pharo.org/event-2973748

Re: [Pharo-dev] A new rule to implement in Pharo ?

> On 13 Aug 2018, at 14:59, Lionel Akue wrote: > > Hello, > > Do you have a rule you would like to get implement in Pharo? > > I am reading about Renraku and I would like to exercise. > > Thanks, > > Lionel Some ideas: - Test Class not in Package with name -Tests - add rule: non-exisitng

Re: [Pharo-dev] [Pharo-users] feenk log

Thanks, recorded for the newsletter: http://newsletter.pharo.org (the one after the next which is going out today, I think). > On 17 Aug 2018, at 06:47, Tudor Girba wrote: > > Hi, > > We again got carried away and forgot to update the world about what is up in > our corner. Here is a

[Pharo-dev] [update 6.1] #60542

60542 - 22305 Backport to Pharo6: "Leave Variable Undeclared" https://pharo.fogbugz.com/f/cases/22305 22298 Backport of the fix of Infinite Debugger https://pharo.fogbugz.com/f/cases/22298

Re: [Pharo-dev] [update 6.1] #60542

> On 17 Aug 2018, at 14:25, Tim Mackinnon wrote: > > Hi Marcus - does this mean that a fresh zero conf of 6.1 will have the > variable undeclared change? If so - then I should remove my port of your fix > into what I load into exercism. Yes! > > This does raise an interesting question - is

[Pharo-dev] [update 6.0] #60543

60543 - 22346 #mustBeBooleanDeOptimizeIn: needs to clean semantic annotation before recompile https://pharo.fogbugz.com/f/cases/22346 22356 CompiledMethod: #methodNode should reuse #parseTree https://pharo.fogbugz.com/f/cases/22356

[Pharo-dev] [ANN] Next Pharo Sprint: Aug 31

We will organize a Pharo sprint / Moose dojo Aug 31, starting at 10:00am. (Local Time Paris). Goals of this sprint: • Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contri

[Pharo-dev] [Pharo7] completion: enabled method preview

Hi, In the last build, we enabled by default the method preview in the code completion dialog. (this is left-arrow). In addition, some cleanups should have made opening the menu the first time faster.

Re: [Pharo-dev] Auto-completion of methods names

> On 4 Sep 2018, at 21:49, Cyril Ferlicot D. wrote: > > Hi, > > Today I tried to launch a Pharo 7 image and I just saw that one of my > setting was failing. > > The setting is from NEC and allow to auto-complete the method name and > could be enable like this: > > NECPreferences overrideMod

[Pharo-dev] Added Pharo8 milestone to issue tracker

Hi, As part of getting ready for the release, we should check all issue tracker entries tagged for pharo7 and decide if they are real show stoppers. I added a Pharo8 Milestone (but when removing the pharo7 milestone, it is in most cases better to just put it on “Later”). Marcus

Re: [Pharo-dev] Pharo Downloads are sluggish

I will have a look how to improve the situation. (I hope to be able to do it by next week). Marcus > On 19 Sep 2018, at 02:10, Esteban Maringolo wrote: > > After sending the previous email I checked the progress and it was aborted > due to a network error. > > > > I retried and app

Re: [Pharo-dev] Mailing list Archive - Bandwidth Limit Exceeded

I will check with support. > On 21 Sep 2018, at 09:49, Torsten Bergmann wrote: > > Hi Marcus, > > I receive a "Bandwidth Limit Exceeded - The server is temporarily unable to > service your request due to the site owner reaching > his/her bandwidth limit. Please try again later." message on >

Re: [Pharo-dev] Mailing list Archive - Bandwidth Limit Exceeded

Fixed. > On 21 Sep 2018, at 09:50, Marcus Denker wrote: > > I will check with support. > >> On 21 Sep 2018, at 09:49, Torsten Bergmann wrote: >> >> Hi Marcus, >> >> I receive a "Bandwidth Limit Exceeded - The server is temporarily unable to

Re: [Pharo-dev] Pharo Downloads are sluggish

without the CDN active, though. Marcus > On 19 Sep 2018, at 15:06, Marcus Denker wrote: > > I will have a look how to improve the situation. > > (I hope to be able to do it by next week). > > Marcus > >> On 19 Sep 2018, at 02:10, Esteban Maringolo

[Pharo-dev] [ANN] Next Pharo Sprint: Sept 28

We will organize a Pharo sprint / Moose dojo Sept 28, starting at 10:00am. (Local Time Paris). Goals of this sprint: • Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contr

[Pharo-dev] [ANN] Pharo Consortium New Bronze Member: Spesenfuchs

The Pharo Consortium is very happy to announce that Spesenfuchs has joined the Consortium as a Bronze Member. About - Spesenfuchs: http://spesenfuchs.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing d

Re: [Pharo-dev] update linux info page again, please [CentOS/RHEL]

Hello, I have added it. https://pharo.org/gnu-linux-installation-64 > On 23 Sep 2018, at 18:32, Petr Fischer via Pharo-dev > wrote: > > > From: Petr Fischer > Subject: update linux info page again, please [CentOS/RHEL] > Date: 23 September 2018 at 18:32:00 CEST > To: pharo-dev@lists

[Pharo-dev] [ANN] Pharo Consortium upgrade to Platinum: ZWEIDENKER

The Pharo Consortium is very happy to announce that ZWEIDENKER has ugraded to be a Platinum member. About - ZWEIDENKER: http://zweidenker.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ong

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary

Hi, It means that the build for this one merge failed… build got much more stable over the last weeks, but we still sometimes have crashes (here it seems to be the text render bug) But this is undefended of the merge: the next build then will take this into account. > On 26 Sep 2018, at 15:24,

Re: [Pharo-dev] [ANN] Success story Mobility Map

The Slides from the ESUG presentation are now inline here: https://www.slideshare.net/zweidenker/docker-and-pharo-zweidenker >>> >>> As presented on ESUG here is the brief description of one of our current >>> projects. >>> >>> Mobility Map >>> —— >>> >>> Mobility Map is a bro

Re: [Pharo-dev] Pharo Downloads are sluggish

Ok, so the upgrade of the server contract did not help. There is a CDN included, I will try to enable that next (but CDNs cache by name, so we need to make sure we invalidate the cache…) I will do a calculation what S3 would cost, too. Marcus > On 3 Oct 2018, at 00:59, Esteban Maringol

Re: [Pharo-dev] Array inspector Items view Selection broken

> On 11 Oct 2018, at 05:44, Tudor Girba wrote: > > Indeed. > > The issue comes from this commit: > https://github.com/pharo-project/pharo/pull/1889 > > I made a revert PR https://github.com/pharo-project/pharo/pull/1902

[Pharo-dev] [ANN] Next Pharo Sprint: Oct 26

We will organize a Pharo sprint / Moose dojo Oct 26, starting at 10:00am. (Local Time Paris). Goals of this sprint: • Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contri

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. Although

Re: [Pharo-dev] Infinite error recursion while saving Pharo70 alpha

> On 7 Nov 2018, at 13:56, Alistair Grant wrote: > > Hi Sven, > > On Wed, 7 Nov 2018 at 10:37, Sven Van Caekenberghe wrote: >> >> >> >>> On 7 Nov 2018, at 10:27, Alistair Grant wrote: >>> >>> Hi Alex, >>> >>> >>> On Wed, 7 Nov 2018 at 10:16, Aliaksei Syrel wrote: Hello, >>

Re: [Pharo-dev] [squeak-dev] Message>>#= & Message>>#hash

> On 20 Nov 2018, at 01:16, Eliot Miranda wrote: > > Hi David, > > On Mon, Nov 19, 2018 at 9:52 AM David T. Lewis > wrote: > On Mon, Nov 19, 2018 at 09:32:17AM -0800, Eliot Miranda wrote: > > Hi All, > > > > In VisualWorks Message implements #= & #hash natural

[Pharo-dev] [ANN] Next Pharo Sprint: Nov 30

We will organize a Pharo sprint / Moose dojo Nov 30, starting at 10:00am. (Local Time Paris). Goals of this sprint: • Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contri

Re: [Pharo-dev] [Ann] Fog 1.0.0-beta

Link to GitHub: https://github.com/sbragagnolo/Fog > On 3 Dec 2018, at 01:20, Santiago Bragagnolo > wrote: > > Hi All! > > I have being working on releasing versions (i should do it more often). > I am happy to announce Fog v1.0.0-beta. I think I found a

Re: [Pharo-dev] periodic auto actions on bug tracker

> On 9 Dec 2018, at 01:50, Ben Coman wrote: > > I support the auto-closing of old tickets to avoid bug bankruptcy. Sometimes > things seem more important at the time and when my own tickets come back > around I get to be more analytical about the effort/reward balance. > > It would be usef

[Pharo-dev] [ANN] Pharo Newsletter December 2018

Hi, Last we the Pharo Newsletter December 2018 was send. You can find the archived version now here: https://mailchi.mp/pharo/pharo-newsletter-december-2018 Marcus

Re: [Pharo-dev] [ANN] Pharo Newsletter December 2018

> On 11 Dec 2018, at 14:08, Marcus Denker wrote: > > Hi, > > Last we the Pharo Newsletter December 2018 was send. > > You can find the archived version now here: > > https://mailchi.mp/pharo/pharo-newsletter-december-2018 > I am looking for content for

  1   2   3   4   5   6   7   8   9   10   >