- Pharo-users - lists.pharo.org

Re: [Pharo-users] can I somehow test the contents of a package

by phil＠highoctane.be

I have made some edits. Please check. https://drive.google.com/uc?id=1yjAdoDnfoMvxGf9KG2RGedjXvNQdwOee&export=dow… Archive password: 7777

Feb. 14, 2020

[ANN] Teachable on GitHub

by Torsten Bergmann

I moved Teachable project now to GitHub: https://github.com/astares/Pharo-Teachable The Project shows the power of Smalltalk meachanisms within Pharo and can be useful for dynamic mock object building in unit tests. Docu and load instructions are included in the project site. Side note: ========== You can also easily load it via catalog within Pharo 8/9: - take a fresh clean Pharo image using PharoLauncher - click on "regular network connection" in the Quick setup sectiono of Pharo welcome window (this allows spotter to show catalog projects) - open Spotter (SHIFT+ENTER) and key in "Teachable", hit ENTER to load via catalog Another possibility is to search for "Teachable" in Catalog utility directly (Tools -> Catalog Browser). Have fun T.

Feb. 14, 2020

[ANN] Pharo-YUML

by Torsten Bergmann

Hi, I published some very simple utility code on https://github.com/astares/Pharo-YUML to easily generate links for YUML. Use the load expression given on the project site or load "YUML" from catalog. Allows you to get a class hierarchy image of an existing Pharo class. It could help to include simple class hierarchy pictures into your (markdown or other) documentation. Example: YUMLGenerator open: String opens a browser to let YUML generate the class hierarchy of String. The clip the URL to your docu as image, for instance in markdown write: ![Hierarchy of String](https://yuml.me/diagram/class/class/[String],[String]%5E-[ByteString],[String]%5E-[Symbol],[Symbol]%5E-[ByteSymbol],[Symbol]%5E-[WideSymbol],[String]%5E-[WideString]) If you need the URL directly then use YUMLGenerator new generateHierarchyFor: String Docu is in https://github.com/astares/Pharo-YUML/blob/master/README.md including an example picture. Maybe it is useful for others too. Thx T.

Feb. 14, 2020

enhance object presentation in the inspector for documentation

by Renaud de Villemeur

Hi all. I really like the ability we have in the browser to set and signal method with sample code so we can run them easily by a simple click. The pragma <example> or <script: > are really helpful to document entry point or keep example as small script directly with the code. To have a better grasp of certain object I create, I look at the possibility in the inspector to provide custom object representation. It look like if I add the pragma <gtInspectorPresentationOrder: XX> to some method, it will be added in the inspector as an extra tab with custom representation. Morphic widget are a good example of this. With a quick investigation, I can see that the presentation in those tabs are done by instances of GLMCompositePresentation Given all the discussion I can see on Glamour and GToolkit (for example https://discordapp.com/channels/223421264751099906/445970167495786497/64814…) <https://discordapp.com/channels/223421264751099906/445970167495786497/64814…>, I was wondering if it's was worth the time to understand how to create custom object representation with Glamour or if it will be deprecated in Pharo 9, and what could be the alternatives. Any advise/comment would be welcome. Renaud

Feb. 13, 2020

Re: [Pharo-users] Setting a model for a Spec UI in Pharo 8

by Renaud de Villemeur

Hi Bren. Are you doing it with Spec2 ? >From my understanding, Spec2 is an MVP framework (Model-View-Presenter) - The model represent the domain logic of the application - The presenter let the developer do the UI programmaticaly and connect it to the Model. - The UI drawing is then managed by Pharo through the Spec2 interperter. First, I subclass Model for my domain model class. For the UI, I subclass SpPresenterWithModel. In the UI >> initialize method, I set the model with something like: 'self model: MyModel new' In the UI >> connectPresenters, when one of my value changed, I called 'self announcingObject valueChanged' I also overwrite UI >> modelChanged with 'self fillFormWithWorkingModel', where fillFormWithWorkingModel link the UI to the model to reflect change. If you want to look at a fully working example, you can take a look at my sourdough calculator: Metacello new baseline: 'Sourdough'; repository: 'github://rvillemeur/Sourdough/src'; load It's a small project for calculating sourdough proportion when doing bread. The model is doing basic proportion calculation (the project includes tests). The UI is using Spec2, and is connected with the model. Hope this helps. Renaud Feb. 12, 2020, 17:26 by asparagi(a)hhhh.org: > Hi fellow Pharo folks, > > TL;DR: The only apparent way to open a standalone presenter on a user-specified model, SpPresenter>>on:, has a comment suggesting it will be deprecated. > > As a follow-up to my previous question in case someone DuckDuckGoes it in the future, it seems that adding self modelChanged to SpPresenterWithModel>>setAnnouncingObject: breaks the Spec2 demos. So, I backed my fix out of my image. This has several implications: > > - To actually change an SpPresenterWithModel's model, one must send model: and then modelChanged. This seems to break encapsulation. > - The Spec2 demos seem to rely on modelChanged not arriving before the UI opens. This seems fragile, and reduces the utility of using the demos as examples for writing non-demo code. > - Since I can't send modelChanged from model:, I must apparently use SpPresenter>>on: to open a standalone instance of my subclass of SpPresenterWithModel on a model I supply (e.g. (BLFunctionPresenter on: aModel) openWithSpec). I was avoiding this because unfortunately, the comment foreshadows deprecation but does not explain what to use instead. I do not understand how a subclass of SpPresenterWithModel can be composable after this deprecation. > > So, I have a solution for now, but I am still looking for the supported way to open a standalone presenter on a user-specified model. > > Bren > >> On Feb 8, 2020, at 3:22 PM, Bren <asparagi(a)hhhh.org> wrote: >> >> ï»¿Hi Pharo friends, >> >> TL;DR: How should one open a presenter on a user-specified model? Is SpPresenterWithModel>>setAnnouncingObject: missing a call to modelChanged? >> >> The long version: >> I am trying to write a UI for my threat modeling tool using Spec in Pharo 8. I had trouble getting my first presenter to show me my model. My current VERY WIP tiny code is available from git@github.com:octotrike/groundhog.git, on branch pharo-sp-presenter-question. >> >> I wanted to do something like this (paraphrased from the class comment for my BLFunctionPresenter class): >> >> BLFunctionPresenter new >> model: aModel; >> openWithSpec >> >> Unfortunately, the UI continued to show the default announcingObject (nil), even though announcingObject had changed as expected. >> >> The examples I found showed either >> - a containing presenter getting an event, changing instance variables on a presenter it contains, and sending modelChanged, or >> - a presenter hard coded to show a model that is globally accessible. >> >> In the end, I added self modelChanged to the end of SpPresenterWithModel>>setAnnouncingObject:. It seemed like this method changed announcingObject and registered this presenter to receive modelChanged every time changes to the announcingObject occurred. However, in cases like the one I am describing, the change is replacement of the entire announcingObject, so no announcingObject sends modelChanged. >> >> Was/is this a bug in Spec? Or is there something else I should be doing to open a Spec UI on a model that is neither global nor specified by a parent presenter? >> >> Bren >>

Feb. 13, 2020

Re: [Pharo-users] Setting a model for a Spec UI in Pharo 8

by Bren

ï»¿Hi fellow Pharo folks, TL;DR: The only apparent way to open a standalone presenter on a user-specified model, SpPresenter>>on:, has a comment suggesting it will be deprecated. As a follow-up to my previous question in case someone DuckDuckGoes it in the future, it seems that adding self modelChanged to SpPresenterWithModel>>setAnnouncingObject: breaks the Spec2 demos. So, I backed my fix out of my image. This has several implications: - To actually change an SpPresenterWithModel's model, one must send model: and then modelChanged. This seems to break encapsulation. - The Spec2 demos seem to rely on modelChanged not arriving before the UI opens. This seems fragile, and reduces the utility of using the demos as examples for writing non-demo code. - Since I can't send modelChanged from model:, I must apparently use SpPresenter>>on: to open a standalone instance of my subclass of SpPresenterWithModel on a model I supply (e.g. (BLFunctionPresenter on: aModel) openWithSpec). I was avoiding this because unfortunately, the comment foreshadows deprecation but does not explain what to use instead. I do not understand how a subclass of SpPresenterWithModel can be composable after this deprecation. So, I have a solution for now, but I am still looking for the supported way to open a standalone presenter on a user-specified model. Bren > On Feb 8, 2020, at 3:22 PM, Bren <asparagi(a)hhhh.org> wrote: > > ï»¿Hi Pharo friends, > > TL;DR: How should one open a presenter on a user-specified model? Is SpPresenterWithModel>>setAnnouncingObject: missing a call to modelChanged? > > The long version: > I am trying to write a UI for my threat modeling tool using Spec in Pharo 8. I had trouble getting my first presenter to show me my model. My current VERY WIP tiny code is available from git@github.com:octotrike/groundhog.git, on branch pharo-sp-presenter-question. > > I wanted to do something like this (paraphrased from the class comment for my BLFunctionPresenter class): > > BLFunctionPresenter new > model: aModel; > openWithSpec > > Unfortunately, the UI continued to show the default announcingObject (nil), even though announcingObject had changed as expected. > > The examples I found showed either > - a containing presenter getting an event, changing instance variables on a presenter it contains, and sending modelChanged, or > - a presenter hard coded to show a model that is globally accessible. > > In the end, I added self modelChanged to the end of SpPresenterWithModel>>setAnnouncingObject:. It seemed like this method changed announcingObject and registered this presenter to receive modelChanged every time changes to the announcingObject occurred. However, in cases like the one I am describing, the change is replacement of the entire announcingObject, so no announcingObject sends modelChanged. > > Was/is this a bug in Spec? Or is there something else I should be doing to open a Spec UI on a model that is neither global nor specified by a parent presenter? > > Bren

Feb. 12, 2020

Re: [Pharo-users] [Pharo-dev] [ANN] uFFI Booklet v1.0

by ducasse

there was a draft of a chapter and we remove it. So probably for a following version :) S. > On 12 Feb 2020, at 20:34, phil(a)highoctane.be wrote: > > Nice. > > Are callbacks going to be detailed in a future version? > > They are pretty powerful as one can write a pharo callback to a c method and for debugging, it is golden. > > Phil > á§ > > On Wed, Feb 12, 2020 at 6:02 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > Iâm preparing the website :) > >> On 12 Feb 2020, at 10:30, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: >> >> Hi all, >> >> We have been working a lot in the last months in the documentation of uFFI, and we are happy to announce a first stable version of it that youâll find in a link below :) >> The booklet talks about uFFI, how to use it, how marshalling works, how to use structures, unions, etc. >> And it is aimed for the version present on Pharo8.0. >> >> https://github.com/SquareBracketAssociates/Booklet-uFFI/releases/tag/v1.0.1 <https://github.com/SquareBracketAssociates/Booklet-uFFI/releases/tag/v1.0.1> >> >> Of course, a v1 does not mean itâs perfect. Future versions will include new chapters/features that are on the pipeline such as callbacks and how to specify string encodings in your bindings. >> Also, so if you find something to fix, to add, to remove, or something hard to follow, let us know >> - by email or >> - by issue (will be easier to track actually than an email) or >> - by PR (and we will have a boost of happiness in addition) >> >> Cheers, >> Guille in behalf of everybody that helped and contributed to this > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

Feb. 12, 2020

Re: [Pharo-users] [Pharo-dev] [ANN] uFFI Booklet v1.0

by phil＠highoctane.be

Nice. Are callbacks going to be detailed in a future version? They are pretty powerful as one can write a pharo callback to a c method and for debugging, it is golden. Phil á§ On Wed, Feb 12, 2020 at 6:02 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Iâm preparing the website :) > > On 12 Feb 2020, at 10:30, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Hi all, > > We have been working a lot in the last months in the documentation of > uFFI, and we are happy to announce a first stable version of it that youâll > find in a link below :) > The booklet talks about uFFI, how to use it, how marshalling works, how to > use structures, unions, etc. > And it is aimed for the version present on Pharo8.0. > > https://github.com/SquareBracketAssociates/Booklet-uFFI/releases/tag/v1.0.1 > > Of course, a v1 does not mean itâs perfect. Future versions will include > new chapters/features that are on the pipeline such as callbacks and how to > specify string encodings in your bindings. > Also, so if you find something to fix, to add, to remove, or something > hard to follow, let us know > - by email or > - by issue (will be easier to track actually than an email) or > - by PR (and we will have a boost of happiness in addition) > > Cheers, > Guille in behalf of everybody that helped and contributed to this > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >

Feb. 12, 2020

Re: [Pharo-users] [ANN] uFFI Booklet v1.0

by Steffen MÃ¤rcker

Great! Thanks for the effort of putting this example-driven booklet together! Steffen Guillermo Polito schrieb am Wed Feb 12 2020 10:30:31 GMT+0100 (MitteleuropÃ¤ische Normalzeit): Hi all, We have been working a lot in the last months in the documentation of uFFI, and we are happy to announce a first stable version of it that youâll find in a link below :) The booklet talks about uFFI, how to use it, how marshalling works, how to use structures, unions, etc. And it is aimed for the version present on Pharo8.0. https://github.com/SquareBracketAssociates/Booklet-uFFI/releases/tag/v1.0.1 Of course, a v1 does not mean itâs perfect. Future versions will include new chapters/features that are on the pipeline such as callbacks and how to specify string encodings in your bindings. Also, so if you find something to fix, to add, to remove, or something hard to follow, let us know - by email or - by issue (will be easier to track actually than an email) or - by PR (and we will have a boost of happiness in addition) Cheers, Guille in behalf of everybody that helped and contributed to this

Feb. 12, 2020

Re: [Pharo-users] About DuneSt / ChartJs

by Sven Van Caekenberghe

Hi Pierce, I did actually use the following expression: Metacello new githubUser: 'DuneSt' project: 'ChartJs' commitish: 'master' path: 'src'; baseline: 'ChartJs'; onUpgrade: [ :e | e useIncoming ]; onConflictUseLoaded; onWarningLog; load. Thinking about it, maybe the #onUpgrade: and #onConflictUseLoaded can't used together, I don't know. I normally load Seaside3 as a dependency to Bootstrap: spec baseline: 'Bootstrap' with: [ spec repository: 'github://astares/Seaside-Bootstrap:master/src' ]. which loads Seaside as: seaside3: spec spec baseline: 'Seaside3' with: [ spec loads: #('default' 'REST'); repository: 'github://SeasideSt/Seaside:master/repository' ] while ChartJS uses: seaside3: spec spec baseline: 'Seaside3' with: [ spec repository: 'github://SeasideSt/Seaside:v3.4.x/repository' ] Maybe the differences in URL (the version tag) and maybe also the groups make them incompatible/different ? Sven > On 12 Feb 2020, at 01:10, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > On Tue, Feb 11, 2020 at 05:06:44PM +0100, Sven Van Caekenberghe wrote: >> NeoJSON and Seaside are already in my project's dependencies, but >> Seaside3 seems to never resolve to the same thing, so I would like to >> skip that. Is that possible ? I have this issue often with Seaside. I >> could fork and edit the baseline, but I'd rather not. > > I do the following near the top of my load script: > > Metacello new > baseline: 'Seaside3'; > repository: '...'; > load; > lock. > > And when loading other packages that may want to load another version of > Seaside: > > Metacello new > baseline: 'whatever'; > repository: '...'; > onConflictUseLoaded; > load. > > I tried doing ifTrue:ifFalse: conditional loading in my baseline to test > for Seaside, but it didn't work. > > Pierce > >

Feb. 12, 2020