August 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

by H. Hirzel

Thank you, Evan, for an alternative load script. Unfortunately it gives the same error message. I use a recent, pristine Pharo 6.1 installation on a 64bit Ubuntu based Linux. On 8/4/18, Evan Donahue <emdonahu(a)gmail.com> wrote: > Try: > > Metacello new > githubUser: 'jmari' project: 'JupyterTalk' commitish: 'master' > path: > 'repository'; > baseline: 'JupyterTalk'; > load > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Aug. 7, 2018

Cargo & Future Proofing Releases

by Evan Donahue

Hi, I will have a few general interest packages to release in the near future, for performance testing, contracts, and the like, and I'm wondering what the current story is for package release. I've heard some things about an upcoming "Cargo" package manager, so I'm wondering what the timeline on that is and whether I should be doing anything in anticipation of that, whether I should be putting things on the old Catalog, and just generally what the standard story is right now for releasing packages. Thanks, Evan

Aug. 7, 2018

Re: [Pharo-users] Pharo Launcher & Stored Settings

by Evan Donahue

Hmm, the only things I'm trying to accomplish are 1) use Pharo Launcher and 2) have each new image keep its repositories separate, as advised by others on the list, so that different images can check out different branches. Does that set up require custom scripting to adjust the repo path? The cache path does seem to do the required adjusting on its own, but the 'metacello default directory' path defaults to that crazy thing that's not a path on my computer: /builds/workspace/Pharo-6.0-Update-Step-1-Tracker PS, Is the 'store settings' button in the settings menu the standard way to configure cross-image preferences, because that seems to also save things like these paths that should be generated anew with each new image. Maybe I should stick with one single place for repos and just configure these paths to be global? Thanks -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 7, 2018

Re: [Pharo-users] transactions on pharo objects

by Carlo

Hi This research from VPRI may be useful: Worlds: Controlling the Scope of Side Effects <http://www.vpri.org/pdf/tr2011001_final_worlds.pdf> and Experiments with Worlds <http://www.vpri.org/pdf/m2013002_experiments.pdf> (Alessandro Warth, Yoshiki Ohshima, Ted Kaehler, and Alan Kay) They had a JS and Squeak version running which can be found at http://www.tinlizzie.org/~awarth/worlds/ <http://www.tinlizzie.org/~awarth/worlds/> Regards Carlo On 30 Jul 2018, at 15:16, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: Hi, is there some library or approach how to do transactions in pharo? And I don't mean database transactions, but directly in memory on Pharo objects... e.g. p := Person new. transaction do: [ p name: 'Nobody'. p age: 70. ] on: Error do: [ transaction rollback. ]. self assert: p name equals: 'Nobody'. self assert: p age equals: 70. transaction do: [ p name: 'Somebody'. p age: 1 / 0. ] on: Error do: [ transaction rollback. ]. self assert: p name equals: 'Nobody'. self assert: p age equals: 70. Any pointers appreciated. Thanks, Peter

Aug. 6, 2018

Re: [Pharo-users] BS Web and Pharo

by Esteban A. Maringolo

Ditto here, and I'm already subscribed to the newsletter! So it's not only nagging, but also superfluous. On 03/08/2018 21:42, Tim Mackinnon wrote: > Yeah - that babyâ¦ I hate seeing it over and overâ¦ presumably its some js > that a third part coughed up (badly). > > Tim > >> On 4 Aug 2018, at 00:05, CÃ©drick BÃ©ler <cdrick65(a)gmail.com >> <mailto:cdrick65@gmail.com>> wrote: >> >> I guess that one ... >> As the general warning in cookies (grrr), or the gpdr or .... >> <image1.png> >> >> EnvoyÃ© de mon iPhone >> >> Le 3 aoÃ»t 2018 Ã 22:17, Damien Pollet <damien.pollet+pharo(a)gmail.com >> <mailto:damien.pollet+pharo@gmail.com>> a Ã©critÂ : >> >>> On Thu, 2 Aug 2018 at 18:15, Tim Mackinnon <tim(a)testit.works >>> <mailto:tim@testit.works>> wrote: >>> >>> Â the constant pestering to sign up for the Pharo newsletter. >>> >>> >>> which pestering, where ? :confused:Â > -- Esteban A. Maringolo

Aug. 6, 2018

Re: [Pharo-users] Pillar Book Tester

by Siemen Baader

Very cool, this should be very useful to keep documentation up-to-date. Good job! cheers Siemen On Tue, Jul 31, 2018 at 11:25 AM Quentin DUCASSE (CI_2020) < quentin.ducasse(a)ensta-bretagne.org> wrote: > Hello everyone! > > I am currently in an internship within the RMoD team and would like to > present my work. My internship subject was the following: âHow to test > documents (books, slides) written in Pillar?â. Let me first introduce > Pillar then what I managed to implement and what is left to do. > > > > -*What is Pillar?* > > > > Pillar is a markup syntax and associated tools to write and generate > documentation, books, slide-based presentations or websites. Pillar syntax > is similar to Markdownâs one but its emphasis is stressed on publishing to > different formats/languages (Markdown, html, LateX, pdf). > > > > -*What does it mean to âtest a bookâ?* > > > -- *Display code within the book* > > Pillar syntax allows you to write codeblocks, showing a part of code. The > inside of a codeblock allows one to display any part of code you might > want to. For example: > > [[[ > > YourClass >> yourMethod > > ^ âblaâ > > ]]] > > This codeblock presents a method definition, the other two possible > codeblocks are the following: > > > Class definition > > [[[ > > Object subclass: #YourClass > > instanceVariableNames: '' > > classVariableNames: '' > > package: YourPackage' > > ]]] > > > Example > > [[[ > > 1+1 > > >>> 2 > > ]]] > > > > -- *How to test it?* > > The use of â>>>â and parameters in the codeblock will help us to test the > code within it. The BookTester will turn examples into tests. > > > > Testing examples: > > [[[testcase=true > > 3+4 becomes self assert: (3+4) equals: 7 > > >>>7 > > ]]] > > > Testing methodDefinitions and classDefinitions: > > > > Testing method or class definitions resumes is the same as testing if the > compilation of the method does not raise any error. It can help make sure > your book is up to date with the latest Pharo version. Those tests are done > the same way as testing an example: stating methodDefinition=true or > classDefinition=true as code block parameters will make them elible for > tests. Now, we are adding more features to code block or Pillar to help > book writers. > > > > -*Additional Features* > > In Pillar, several annotations can be used for different purposes like > including columns/tables/citations/figures/linksâ¦ > > > > -- * Loading code:* loader > > ${loader:account=QDucasse|project=TestBook|tag=Chapter1}$ > > allows you to load the github project as it was in the commit tagged > Chapter1. This will help you test every chapter of your code with its > current progression and also allow you to test the objects you are defining > in your book. > > > - *Executing Tests:* run > > ${run:testClass=YourClassTest}$ runs the test defined in the class > testClass. And of course this testClass can be > > > Other annotations have been added to help you write your book: > > > - * Display a class definition:* showClass: > > ${showClass:className=YourClass}$ displays a codeblock with the class > definition within it > > This helps you quickly include a class definition you want to display in > your book. Combined with the loader it means that the code can be the > source of your book. > > > > - * Display a method definition:* showMethod: > > ${showMethod:className=YourClass|methodName=yourMethod}$ will display a > codeblock with the method definition within it > > This helps you quickly include a method definition you want to display in > your book. > > > > - * Screenshot:* > > > ${showMethod:packageName=yourPackage|className=YourClass|methodName=yourMethod|caption|width|label}$ > > saves a screenshot of a Calypso browser open at the selected package, > class and method and includes it in both your book (using the designated > Pillar figure reference) and the figures subfolder in the pillar book > folder (saved as PNG). > > > -*Future objectives* > > > > One of the future improvements would be to make everyone able to write > examples and test them in the comments of method definitions. It is already > partially possible â3+4 >>> 7â will be highlighted differently and if > printed will display â7->7â. However, an automation or UI improvement would > be nice. > > > > I hope this gave you the will to write something you had in mind. Are > there any books you want to try the tools on? Feel free to ask ! > > > > Quentin Ducasse > >

Aug. 5, 2018

Volunteer for proof reading English text

by Hilaire

Hi, Since a few weeks I am writing English texts about the Dynabook. The idea is to share opinion on the topic, and see if there are interests, opinions, comments., etc. As for now I am looking at how it relates with pedagogy. Later I hope to think more on its technical dimension. However I am looking for a supplementary native English speaking native to help proof reading it. Each text is not very long, so it is not a lot of work. If you are willing to help, please email me at hilaire [at] drgeo.eu (I can't read email address from the list message as I am reading it through the gmane newsgroup and email address are encoded). Thanks Hilaire -- Dr. Geo http://drgeo.eu

Aug. 5, 2018

Re: [Pharo-users] Pharo Launcher & Stored Settings

by Sean P. DeNigris

Evan Donahue wrote > Is there a way to handle settings that should be different for every > imageâ¦ Startup script? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 5, 2018

Pharo Launcher & Stored Settings

by Evan Donahue

Is there a way to handle settings that should be different for every image when using Pharo Launcher? In particular, Settings > Software Configuraiton > Monticello > Default Local Repository & Local Cache Directory should be specific to the new image, but if I ever store settings for any reason, they get saved and incorrectly propagate to fresh images. Also, they are initialized wrong in the first place. How can I avoid this issue without manually adjusting these paths every time I make a new image? Thanks, Evan

Aug. 4, 2018

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

by Evan Donahue

Try: Metacello new githubUser: 'jmari' project: 'JupyterTalk' commitish: 'master' path: 'repository'; baseline: 'JupyterTalk'; load -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 4, 2018