- Pharo-dev - lists.pharo.org

Re: pharo9 tools moldability

by Danil Osipchuk

Stephane, yes the AbstractFileReference extensions is definitely a very illustrative example. >From a quick glance it all seems to be pretty straightforward. Also I'd like to use this opportunity to congratulate all who worked hard to make the Pharo9 release possible. It is impressive how clean the code and even UI are now, I would say on par with Dolphin which is a high bar. Obviously a lot of care went into this. Also the books and infrastructure around the project - it is amazing. regards, Danil Ð²Ñ, 19 Ð´ÐµÐº. 2021 Ð³. Ð² 00:07, stephane ducasse <stephane.ducasse(a)inria.fr>: > Hi danil > > Have a look at the extension in FileReference for example. > You will see how you can extend the default inspector. > > What you should see is that you can use any Spec20 UI within the panes. > So we get the extensibility without the glamour and we gain the uniformity > of > using Spec20. > > For us the moldability is important. If you have scenario that do not work > we will study because > the current version may need some adjustments. > But what I can garantee is that we want to make sure that we can all build > our own tools. > > Here are the extensions we are using for a new compiler we are building > > > On 18 Dec 2021, at 16:06, Danil Osipchuk <danil.osipchuk(a)gmail.com> wrote: > > Dear all, > > Being a long time smalltalk user (meaning I'm crafting tools for my own > usage for domains I'm working with) I always relied upon the environment > itself to interact with models to spare time creating user interfaces. > Besides plain inspectors I used metafacilities where possible -- seaside, > then omnibrowser and lately glamour toolkit in pharo8. > > Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile > pharo9 looks increasingly neat and I would like to make a transition but > having tools in pharo8 holds me back. > > I would be grateful for any pointers to help me to get started with the > moldable inspectors pharo9 - papers, talks, online discussions, etc. I can > likely figure it out on my own, but having an overall understanding of the > approach concept would save an effort and shorten the trial and error > phase. > (maybe I'm overcomplicating it and just having browsed around inspector > code pragmas is enough to get started) > > > > regards, > Danil > > >

Dec. 19, 2021

Re: pharo9 tools moldability

by Sebastian Jordan Montano

This may interest you: https://modularmoose.org/2021/05/04/how-to-build-a-new-moose-tool.html > De: "Danil Osipchuk" <danil.osipchuk(a)gmail.com> > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > EnvoyÃ©: Samedi 18 DÃ©cembre 2021 15:06:33 > Objet: [Pharo-dev] pharo9 tools moldability > Dear all, > Being a long time smalltalk user (meaning I'm crafting tools for my own usage > for domains I'm working with) I always relied upon the environment itself to > interact with models to spare time creating user interfaces. Besides plain > inspectors I used metafacilities where possible -- seaside, then omnibrowser > and lately glamour toolkit in pharo8. > Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile pharo9 > looks increasingly neat and I would like to make a transition but having tools > in pharo8 holds me back. > I would be grateful for any pointers to help me to get started with the moldable > inspectors pharo9 - papers, talks, online discussions, etc. I can likely figure > it out on my own, but having an overall understanding of the approach concept > would save an effort and shorten the trial and error phase. > (maybe I'm overcomplicating it and just having browsed around inspector code > pragmas is enough to get started) > regards, > Danil

Dec. 19, 2021

Re: pharo9 tools moldability

by stephane ducasse

Hi danil Have a look at the extension in FileReference for example. You will see how you can extend the default inspector. What you should see is that you can use any Spec20 UI within the panes. So we get the extensibility without the glamour and we gain the uniformity of using Spec20. For us the moldability is important. If you have scenario that do not work we will study because the current version may need some adjustments. But what I can garantee is that we want to make sure that we can all build our own tools. Here are the extensions we are using for a new compiler we are building > On 18 Dec 2021, at 16:06, Danil Osipchuk <danil.osipchuk(a)gmail.com> wrote: > > Dear all, > > Being a long time smalltalk user (meaning I'm crafting tools for my own usage for domains I'm working with) I always relied upon the environment itself to interact with models to spare time creating user interfaces. Besides plain inspectors I used metafacilities where possible -- seaside, then omnibrowser and lately glamour toolkit in pharo8. > > Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile pharo9 looks increasingly neat and I would like to make a transition but having tools in pharo8 holds me back. > > I would be grateful for any pointers to help me to get started with the moldable inspectors pharo9 - papers, talks, online discussions, etc. I can likely figure it out on my own, but having an overall understanding of the approach concept would save an effort and shorten the trial and error phase. > (maybe I'm overcomplicating it and just having browsed around inspector code pragmas is enough to get started) > > > > regards, > Danil

Dec. 18, 2021

pharo9 tools moldability

by Danil Osipchuk

Dear all, Being a long time smalltalk user (meaning I'm crafting tools for my own usage for domains I'm working with) I always relied upon the environment itself to interact with models to spare time creating user interfaces. Besides plain inspectors I used metafacilities where possible -- seaside, then omnibrowser and lately glamour toolkit in pharo8. Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile pharo9 looks increasingly neat and I would like to make a transition but having tools in pharo8 holds me back. I would be grateful for any pointers to help me to get started with the moldable inspectors pharo9 - papers, talks, online discussions, etc. I can likely figure it out on my own, but having an overall understanding of the approach concept would save an effort and shorten the trial and error phase. (maybe I'm overcomplicating it and just having browsed around inspector code pragmas is enough to get started) regards, Danil

Dec. 18, 2021

This week (50/2021) on the Pharo Issue Tracker

by Marcus Denker

We merged 15 PRs and closed 9 Issue Tracker entries this week: Modularity ========== - Extract freetype to its own baseline (2nd pass) #10641 https://github.com/pharo-project/pharo/pull/10641 - Register bootstrapped projects #10653 https://github.com/pharo-project/pharo/pull/10653 - Split baseline of threadedffi #10637 https://github.com/pharo-project/pharo/pull/10637 - Make Athens not coupled with FT2 #10646 https://github.com/pharo-project/pharo/pull/10646 Refactoring =========== - Migrating RBAbstractVariables and RBMoveMethod #10626 https://github.com/pharo-project/pharo/pull/10626 Fixes ===== - Fix metacello lock #10633 https://github.com/pharo-project/pharo/pulse - 10294-undefinedIdentifier-is-missing-in-SHRBTextStyler #10648 https://github.com/pharo-project/pharo/pull/10648 - fix a couple of regressions #10662 https://github.com/pharo-project/pharo/pull/10662 - 10651-Resuming-a-exception-that-has-been-signalled-twice-does-not-return-correctly #10652 https://github.com/pharo-project/pharo/pull/10652 Cleanup ======= - Cleanup-DuplcatedMethods-12-13 #10654 https://github.com/pharo-project/pharo/pull/10654 - Cleanup-Spec-Deprecated #10624 https://github.com/pharo-project/pharo/pull/10624 - Unused method in FFI #10660 https://github.com/pharo-project/pharo/pull/10660 - Cleanup: STONWriter categorization #10661 https://github.com/pharo-project/pharo/pull/10661 - Categorize-More-Uncategorized #10649 https://github.com/pharo-project/pharo/pull/10649 - Fixing selector type: RBAddMethodChange>>#class:source:contoller: #10643 https://github.com/pharo-project/pharo/pull/10643

Dec. 17, 2021

Re: one year contract

by Sean Glazier

Hi, I emaile Nicolas a few times but Have not heard back. I would be very interested in working on this project. I have a US corporation setup and we can get to work on it as soons as they want. Kind Regards Sean Glazier On Tue, Jul 27, 2021, 12:08 PM stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > Hello > > this is a one year contract with remote working possibility in Pharo of > course. > We will produce an english version. > > Please contact Nicolas Becu. *Nicolas Becu <nicolas.becu(a)cnrs.fr > <nicolas.becu(a)cnrs.fr>>* > _____________ > Nicolas Becu > Chercheur CNRS > Littoral Environnement et SociÃ©tÃ©s (UMR LIENSs) > TÃ©l : 05 16 49 67 94 > > S > >

Dec. 14, 2021

Re: Zinc redirect?

by Sven Van Caekenberghe

There is now a solution described in the issue: https://github.com/svenvc/zinc/issues/69 > On 10 Dec 2021, at 10:58, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > There is an issue that Ronie created, I am looking into it: > > https://github.com/svenvc/zinc/issues/69 > >> On 10 Dec 2021, at 08:25, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> FYI >> >> >> running catching my train. >> from https://github.com/ronsaldo/form-scene-graph/issues/5#issuecomment-990353154 >> >> >> >> >> >> This seems to be a Zinc error while following a redirect. The following snippet can be used for replicating the issue: >> >> ZnClient new accept: 'application/octet-stream'; "Required by GitHub" url: 'https://api.github.com/repos/ronsaldo/abstract-gpu/releases/assets/49144132'; followRedirects: true; downloadTo: 'agpu.tar.gz' >> >

Dec. 13, 2021

Re: Zinc redirect?

by Sven Van Caekenberghe

There is an issue that Ronie created, I am looking into it: https://github.com/svenvc/zinc/issues/69 > On 10 Dec 2021, at 08:25, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > FYI > > > running catching my train. > from https://github.com/ronsaldo/form-scene-graph/issues/5#issuecomment-990353154 > > > > > > This seems to be a Zinc error while following a redirect. The following snippet can be used for replicating the issue: > > ZnClient new accept: 'application/octet-stream'; "Required by GitHub" url: 'https://api.github.com/repos/ronsaldo/abstract-gpu/releases/assets/49144132'; followRedirects: true; downloadTo: 'agpu.tar.gz' >

Dec. 10, 2021

Zinc redirect?

by stephane ducasse

FYI running catching my train. from https://github.com/ronsaldo/form-scene-graph/issues/5#issuecomment-990353154 This seems to be a Zinc error while following a redirect. The following snippet can be used for replicating the issue: ZnClient new accept: 'application/octet-stream'; "Required by GitHub" url: 'https://api.github.com/repos/ronsaldo/abstract-gpu/releases/assets/49144132'; followRedirects: true; downloadTo: 'agpu.tar.gz <https://api.github.com/repos/ronsaldo/abstract-gpu/releases/assets/49144132';%20followRedirects:%20true;%20downloadTo:%20'agpu.tar.gz>'

Dec. 10, 2021

This week (49/2021) on the Pharo Issue Tracker

by Marcus Denker

We merged 29 PRs and closed 43 issue tracker entries. With Pharo10 in freeze, we focus on fixes and simples cleanups. Fixes ===== - Fixes 10610 - CairoFontExtents is missing a field #10611 https://github.com/pharo-project/pharo/pull/10611 - Fix 10565 - Extract freetype to its own baseline #10566 https://github.com/pharo-project/pharo/pull/10566 - 10536 rubric embedded morphs sometimes misplaced #10558 https://github.com/pharo-project/pharo/pull/10558 - Moving the buggy must be boolean magic support outside of the image #10567 https://github.com/pharo-project/pharo/pull/10567 - Fix for Issue #10269 Replaced RBExtractToTemporaryRefactoring with RBExtractToTemporaryTraâ¦ #10388 https://github.com/pharo-project/pharo/pull/10388 - Fix stability of SUnitTest's related to the process monitoring #10514 https://github.com/pharo-project/pharo/pull/10514 Tests ===== - Made tests for embedded morphs skip as they procuce CI errors. #10628 https://github.com/pharo-project/pharo/pull/10628 Cleanups ======== - 17 PRs "Cleanup newlines and blanks" - Beacon "instance" class variable not capitalized #10614 https://github.com/pharo-project/pharo/pull/10614 - Some cleanups in SUnit-Core #10616 https://github.com/pharo-project/pharo/pull/10616 - Fixing the category of QuotedPrintableMimeConverter>>#newline #10617 https://github.com/pharo-project/pharo/pull/10617

Dec. 10, 2021