- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #1025: CompletionFallBack

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1025 was: SUCCESS. The Pull Request #5258 was integrated: "CompletionFallBack" Pull request url: https://github.com/pharo-project/pharo/pull/5258 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionFallBack Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 28, 2019

Re: [Pharo-dev] BlueInk removal

by Esteban Maringolo

On Thu, Nov 28, 2019 at 6:14 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > This is all true, BUT ... > > Very few people attempt to do fundamental changes/cleanups/subsystem-replacements in the core image. This all true, BUT ... :-) > This takes a lot of work, is never easy and almost always has issues. This is exactly why you "roll out" features. > Resources are limited as well, in theory things can be done better, in practice in the real world, not so much. Resources are limited to everyone, commercial vendors, sponsored ones like Pharo and, last but not least, "users" [1]. [1] That, like me, read these discussions and only participate in the list because sometimes they seem biased because of a lack of consideration/feedback. I won't argue against the enormous progress and things being done by the whole Pharo team, but IMO minimizing the use of resources (time/effort) as a whole is more an objective than a resources thing. > The alternative is to never touch anything and stay stagnant. This is a false dichotomy. But can't deny its punch. :-) Regards, Esteban A. Maringolo

Nov. 28, 2019

[Pharo 8.0] Build #1024: CompletionFallBack

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1024 was: FAILURE. The Pull Request #5258 was integrated: "CompletionFallBack" Pull request url: https://github.com/pharo-project/pharo/pull/5258 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionFallBack Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 28, 2019

Re: [Pharo-dev] [Mm10s] 2019-11-25

by Steven Costiou

Le 2019-11-28 14:15, ducasse a Ã©crit : > Thanks steven > If you need beta tester please let me know. Yes please, the halt/bp window in the debugger needs feedback. Start a P8 image, then reload spec https://github.com/pharo-spec/Spec then load NewTools https://github.com/pharo-spec/NewTools It should be active by default. Steven. > S. > >> On 28 Nov 2019, at 11:29, Steven Costiou <steven.costiou(a)kloum.io> wrote: >> >> ### Last week: >> >> - halt/breakpoint manager in the spec debugger: see all halt/breakpoints and (de)activate them in one click. When deactivated, a halt/breakpoint just prints a log message in the Transcript. >> >> - Pharo IOT book writing >> >> ### This week (starting 2019-11-25): >> >> - Pharo IOT book writing >> >> - add a "watch variable" window in the debugger to track variables during debugging >> >> ### Pipeline >> >> - Pharo IOT book >> >> - Enhancing the spec debugger: better breakpoint support, adding missing features (menus, options), fixing bugs >> >> - Integrating object-centric debugging in the spec2 tools >> >> - Writing a chapter/documentation about the Pharo debugger

Nov. 28, 2019

[Pharo 8.0] Build #1023: 5102-FastTable-Horizontal-Scrolling-not-implemented

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1023 was: SUCCESS. The Pull Request #5107 was integrated: "5102-FastTable-Horizontal-Scrolling-not-implemented" Pull request url: https://github.com/pharo-project/pharo/pull/5107 Issue Url: https://github.com/pharo-project/pharo/issues/5102 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 28, 2019

[ANN] freezing Pharo 8.0 development

by Esteban Lorenzano

Hi, After talk about current situation of P8 development, we decided we have already a version that is very stable (with some remaining problems, we know) and we think this is something we can release before start the new batch of breaking changes (move to headless vm by default, new object centric debugger, etc, etc, etc.) So, I am declaring the development status on âcode freezeâ and we will start working on stabilisation hoping to have a releasable version by end December, beginning of January (yes, this will be a short cycle, but that will allow us to make some iterations needed without the pressure of releasing on April). Enjoy, Esteban

Nov. 28, 2019

Re: [Pharo-dev] [Mm10s] 2019-11-25

by ducasse

Thanks steven If you need beta tester please let me know. S. > On 28 Nov 2019, at 11:29, Steven Costiou <steven.costiou(a)kloum.io> wrote: > > ### Last week: > > - halt/breakpoint manager in the spec debugger: see all halt/breakpoints and (de)activate them in one click. When deactivated, a halt/breakpoint just prints a log message in the Transcript. > > - Pharo IOT book writing > > > > ### This week (starting 2019-11-25): > > - Pharo IOT book writing > > - add a "watch variable" window in the debugger to track variables during debugging > > > ### Pipeline > > - Pharo IOT book > > - Enhancing the spec debugger: better breakpoint support, adding missing features (menus, options), fixing bugs > > - Integrating object-centric debugging in the spec2 tools > > - Writing a chapter/documentation about the Pharo debugger >

Nov. 28, 2019

Re: [Pharo-dev] MDLApplication

by Cyril Ferlicot

On Thu, Nov 28, 2019 at 11:26 AM Julien Delplanque <julien.delplanque(a)inria.fr> wrote: > > Hello Sven, > > Did you try https://github.com/jecisc/MDBaseGenerator ? > To help with discoverability, I migrated the project from my repository to DuneSt. The previous link should still work with Github redirections. > It generates a nice template for starting a new MDL webapp. > > I do not know about MDLApplication. > > Cheers, > > Julien > > -- Cyril Ferlicot https://ferlicot.fr

Nov. 28, 2019

Re: [Pharo-dev] MDLApplication

by Sven Van Caekenberghe

> On 28 Nov 2019, at 11:55, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On Thu, Nov 28, 2019 at 11:17 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi, >> >> I am trying to use MaterialDesignLite (master branch in Pharo 7). The demo works perfectly. >> >> Now, I thought I would start writing a small web app by subclassing MDLApplication, since that seems to set up things properly. >> >> Is that class finished ? How am I supposed to use it ? There are screens, but how are these rendered ? Do I have to do this myself ? Must there not be an idea of a current screen ? >> >> MDLScreen is in fact an empty class. >> >> Although there are units tests for MDLApplication, there is no subclass, so no actual user. It feels a bit as if the demo should/could use it. >> > > Hi, > > This class was introduced at the beginning of MDL and was used by its creator. > > This person does not contribute anymore and I never really used it so > I do not know how useful it is. I will add an issue to take a look and > either improve it or deprecate it to not make people lose time. Thanks Cyril, I suspect it was not finished and it was a bit confusing. > https://github.com/DuneSt/MaterialDesignLite/issues/292 > > As Julien told you, I usually start a standard MDL application with > the generator I wrote to get the basic infrastructure. > > I hope it helps you getting started smoothly. > >> Sven > > -- > Cyril Ferlicot > https://ferlicot.fr

Nov. 28, 2019

Re: [Pharo-dev] MDLApplication

by Cyril Ferlicot

On Thu, Nov 28, 2019 at 11:17 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > I am trying to use MaterialDesignLite (master branch in Pharo 7). The demo works perfectly. > > Now, I thought I would start writing a small web app by subclassing MDLApplication, since that seems to set up things properly. > > Is that class finished ? How am I supposed to use it ? There are screens, but how are these rendered ? Do I have to do this myself ? Must there not be an idea of a current screen ? > > MDLScreen is in fact an empty class. > > Although there are units tests for MDLApplication, there is no subclass, so no actual user. It feels a bit as if the demo should/could use it. > Hi, This class was introduced at the beginning of MDL and was used by its creator. This person does not contribute anymore and I never really used it so I do not know how useful it is. I will add an issue to take a look and either improve it or deprecate it to not make people lose time. https://github.com/DuneSt/MaterialDesignLite/issues/292 As Julien told you, I usually start a standard MDL application with the generator I wrote to get the basic infrastructure. I hope it helps you getting started smoothly. > Sven -- Cyril Ferlicot https://ferlicot.fr

Nov. 28, 2019