- Pharo-dev - lists.pharo.org

Re: AST Transformation Techniques

by Sean P. DeNigris

hogoww wrote > I'm aware of Julien Delplanque which has done something a bit like this, > or my own project. Thanks! Both interesting and good to know about. Your project took me a while to understand by reading and rereading the examples in the readme, but I really like the block idea. I think Julien's could work for my use case because there is a feature to generate his AST model from an existing method. One day, I'd love to sit down and properly compare all three approaches. I'll add it to the never-ending TODOs! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Nov. 17, 2020

Re: AST Transformation Techniques

by hogoww

Hi Sean, I'm aware of Julien Delplanque which has done something a bit like this, or my own project. Julien's has a good documentation. Repo: https://github.com/juliendelplanque/PharoCodeGenerator You also have my own project, which takes a different approach that might be more what you want. (I didn't document it as well though...): https://github.com/hogoww/PlainPharoCode Quickly, my way of doing things is to use blocks instead of strings. This ensures that the generated code is at least well formed. This also enables code highlighting [...]. It then replaces variables using the lexical scope (except for block args if i recall correctly, since shadowing is not a feature of pharo) ```smalltalk generateValidatorVisitOf: aClass Â Â Â "add an empty behavior visit method" Â Â Â | method body anInstance visitClass errors | "IV of the visitor" Â Â anInstance := aClass name asAnInstance. Â visitClass :=Â aClass name asVisitClassSelector. Â Â Â body := [:aClass | Â Â Â Â Â Â [ super visitClass: {aClass} ] Â Â Â Â Â Â on: AssertionFailure Â Â Â Â Â Â do: [errors := errors + 1 ] ]. method := visitClass asMethodWithBody: body Â Â Â Â Â Â withArguments: {(#aClass -> anInstance )} asDictionary. Â Â Â structureValidatorVisitorClass compile: method asString classified: 'visiting' ``` This is a temp variable, used as a selector, which will be replace when evaluating the #asMethodWithBody:withArguments: message send. The temp var visitClass is a string that will describe the name of the method when sending the #asMethodWithBody:withArguments: message. This is the block that we want to generate. The temp var errors has no value, which means it already has the right name. this will not be replaced. The message send asMethodWithBody will do the required replacements. As said earlier , block arguments cannot be replaced using the same method, as Pharo disabled shadowing. We currently have to compile the string version of the method. Although slow, this has not yet been an issue (I hope that color way of describing a method is readable :D) This will for example give the folowing output: ```smalltalk visitExpression: anExpression Â Â Â [ super visitExpression: anExpression ] Â Â Â Â Â Â on: AssertionFailure Â Â Â Â Â Â do: [ errors := errors + 1 ] ``` I took a simple ish example, but we can do more advanced stuff, like concatenating blocks. You can find more example in the following project in which I use PlainPharoCode exclusively to generate my code: https://github.com/hogoww/C-AST. (In the ASTCGenerator class) (You will need a moose image). I hope you find this interesting ! Have a nice day ! Pierre. On 16/11/2020 23:55, sean(a)clipperadams.com wrote: > > To generate code, I used to use templates like the following > (contrived example): > > ```smalltalk > > |template := 'method1| > > |^ {returnValue}'.| > > |template format: { #returnValue -> 2 } asDictionary| > > ``` > > This is *okay* for simple cases, but can get unwieldy, and doesn't > benefit from e.g. (early) compiler warnings. It is also lacking when > one wants to offer the behavior as a method and also as a script with > no dependencies (maybe for CI). > > To overcome some of these limitations, I started saving the code > template as an actual method and transforming the AST, e.g.: > > ```smalltalk > > |"Convert baseline##: method"| > > |methodTree := (self methodNamed: selector) parseTree.| > > |methodTree selector: #baseline:.| > > |methodTree pragmas at: 1 put: (RBPragmaNode selector: #baseline > arguments: #()).| > > |commonBlockBody := methodTree statements first arguments last body.| > > |commonBlockBody statements| > > |detect: [ :e | e selector = #repository: ]| > > |ifFound: [ :repoSetter | commonBlockBody removeNode: repoSetter ].| > > || > > |"Compile baseline method"| > > |baseline compile: methodTree newSource classified: 'baseline'| > > ``` > > When I started doing this, I noticed two things: > > 1. There were idioms that were repeated over and over. > > 2. It still isn't super easy to turn a method into a script with no > dependencies (e.g. self sends) > > So, I did a spike to wrap a few common idioms for this use case. It > works like this. Say you have a method like this: > > ``` > > |SmallRemoteGitRepository>>#addRemote: urlString as: nameString| > > |"Assumes repo is loaded"| > > || > > || repo remote || > > |repo := IceRepository registry detect: [ :e | e name = self > projectName ].| > > |remote := IceGitRemote name: nameString url: urlString.| > > |repo addRemote: remote.| > > |remote fetch| > > ``` > > And you want to also provide it as source code for a script with no > dependencies. You can do: > > ``` > > |SmallRemoteGitRepository >>#scriptToAddRemote: urlString as: nameString| > > || method transformer || > > |method := SmallRemoteGitRepository methodNamed: #addRemote:as:.| > > |transformer := method peAST_Transformer| > > |beScript;| > > |addStatementFirst: #projectName , ' := ' , self projectName printString;| > > |addStatementFirst: #nameString , ' := ' , nameString printString;| > > |addStatementFirst: #urlString , ' := ' , urlString printString;| > > |replaceNodeDetect: [ :e | e isMessage and: [ e selector = > #projectName ] ]| > > |withNode: (RBVariableNode named: #projectName).| > > |^ transformer newSource| > > ``` > > which would generate (for example, for a particular instance): > > ``` > > || repo remote projectName || > > |urlString := 'git@github.com:magritte-metamodel/magritte.git'.| > > |nameString := 'upstream'.| > > |projectName := 'Magritte'.| > > |repo := IceRepository registry detect: [ :e | e name = projectName ].| > > |remote := IceGitRemote name: nameString url: urlString.| > > |repo addRemote: remote.| > > |remote fetch| > > ``` > > So my questions are: > > - Does something like this already exist? > > - Are there better ways to solve this problem? > > - Does this solution look promising/generally-helpful? >

Nov. 17, 2020

AST Transformation Techniques

by sean＠clipperadams.com

To generate code, I used to use templates like the following (contrived example): \`\`\`smalltalk `template := 'method1` ` ^ {returnValue}'.` `template format: { #returnValue -> 2 } asDictionary` \`\`\` This is \*okay\* for simple cases, but can get unwieldy, and doesn't benefit from e.g. (early) compiler warnings. It is also lacking when one wants to offer the behavior as a method and also as a script with no dependencies (maybe for CI). To overcome some of these limitations, I started saving the code template as an actual method and transforming the AST, e.g.: \`\`\`smalltalk `"Convert baseline##: method"` ` methodTree := (self methodNamed: selector) parseTree.` ` methodTree selector: #baseline:.` ` methodTree pragmas at: 1 put: (RBPragmaNode selector: #baseline arguments: #()).` ` commonBlockBody := methodTree statements first arguments last body.` ` commonBlockBody statements` ` detect: [ :e | e selector = #repository: ]` ` ifFound: [ :repoSetter | commonBlockBody removeNode: repoSetter ].` ` ` ` "Compile baseline method"` ` baseline compile: methodTree newSource classified: 'baseline'` \`\`\` When I started doing this, I noticed two things: 1\. There were idioms that were repeated over and over. 2\. It still isn't super easy to turn a method into a script with no dependencies (e.g. self sends) So, I did a spike to wrap a few common idioms for this use case. It works like this. Say you have a method like this: \`\`\` `SmallRemoteGitRepository>>#addRemote: urlString as: nameString` ` "Assumes repo is loaded"` ` ` ` | repo remote |` ` repo := IceRepository registry detect: [ :e | e name = self projectName ].` ` remote := IceGitRemote name: nameString url: urlString.` ` repo addRemote: remote.` ` remote fetch` \`\`\` And you want to also provide it as source code for a script with no dependencies. You can do: \`\`\` `SmallRemoteGitRepository >>#scriptToAddRemote: urlString as: nameString` ` | method transformer |` ` method := SmallRemoteGitRepository methodNamed: #addRemote:as:.` ` transformer := method peAST_Transformer` ` beScript;` ` addStatementFirst: #projectName , ' := ' , self projectName printString;` ` addStatementFirst: #nameString , ' := ' , nameString printString;` ` addStatementFirst: #urlString , ' := ' , urlString printString;` ` replaceNodeDetect: [ :e | e isMessage and: [ e selector = #projectName ] ]` ` withNode: (RBVariableNode named: #projectName).` ` ^ transformer newSource` \`\`\` which would generate (for example, for a particular instance): \`\`\` `| repo remote projectName |` `urlString := 'git@github.com:magritte-metamodel/magritte.git'.` `nameString := 'upstream'.` `projectName := 'Magritte'.` `repo := IceRepository registry detect: [ :e | e name = projectName ].` `remote := IceGitRemote name: nameString url: urlString.` `repo addRemote: remote.` `remote fetch` \`\`\` So my questions are: \- Does something like this already exist? \- Are there better ways to solve this problem? \- Does this solution look promising/generally-helpful?

Nov. 16, 2020

This week (46/2020) on the Issue Tracker

by Marcus Denker

We merged 20 pull requests and closed 17 issue tracker entries this week. For someone interested in following this more closely: Github has a feature to get an email for all the changes that happen in both the issues and the pull requests. To get emails for those, on the github page you can (after logging in), "watch" the repository. https://github.com/pharo-project/pharo/ There are more PRs done but not merged, they often just need a final review! You can find them here: https://github.com/pharo-project/pharo/pulls Merge spec 0.7.6 #7713 ====================== Spec is an example of a project that is developed in itâs own repository and then merged only when a release is done. We merged 0.7.6 this week, it consists itself of many commits, of course. Here is the ChangeLog: - several enhancements and bugfixes to SpPopoverPresenter. - in SpStyle, introduced the concept of environment variables. Now we can define EnvirontmentFont and EnvironmentColor to reference environment defined variables. - fixed usage of minWidth/minHeight in styles. - fix pharo-spec/Spec#960 - fixed in how SpBoxLayout calculates widths and heights, allowing the toolbar to take its real place. - fixed alignments in SpBoxLayout (hAlign* and vAlign* options now work properly). - added SpToolbarPopoverButtonPresenter. - SpMillerColumnPresenter now understands removeAllFrom: - in tables, fixed the usage of showColumnHeaders (now it show headers even if headers are nil). - in tables, fixed image columns with fixed widths (now calculate correctly the width). - SpCodePresenter commands use new selector extractor. First Class Variables ===================== - Simplify-MetaLinkInstaller #7669 This PR simplifies MetaLinkInstaller by taking advantage of the new unified Variable hierarchy. (first step, more can be done) https://github.com/pharo-project/pharo/pull/7669 - Unify-OCInstanceScope-Behavior #7704 Simplify Name Analysis even more. self/super and friends are now looked up in the global scope. https://github.com/pharo-project/pharo/pull/7704 Debugger Improvements ===================== - Added <debuggerCompleteToSender> pragma to user-level object error-handling protocol methods #7714 (this fixes TDD style development for these cases) https://github.com/pharo-project/pharo/pull/7714 - Return the package column to the debugger #7700 https://github.com/pharo-project/pharo/pull/7700 Fluid Class Definition ======================= Work is progressing... - 7706-New-class-definition-does-not-like-superclass-change #7717 https://github.com/pharo-project/pharo/pull/7717 - 7687-Cannot-remove-a-Trait-written-with-the-fluid-syntax #7689 https://github.com/pharo-project/pharo/pull/7689 - 7522--Fluid--Adding-Setting-for-fluid-Syntax #7686 https://github.com/pharo-project/pharo/pull/7686 - 7690-fluid-printer-has-some-duplicated-logic- #7691 https://github.com/pharo-project/pharo/pull/7691 - 7684-New-trait-UI-wizard-cannot-display-the-package-name-in-apostrophe #7697 https://github.com/pharo-project/pharo/pull/7697 Fixes ===== Fix issue 7703: Build 817 has broken parser #7703 #7708 https://github.com/pharo-project/pharo/pull/7708 Returning default error value only on Error #7705 https://github.com/pharo-project/pharo/pull/7705 fix-fasttable-minHeight #7685 https://github.com/pharo-project/pharo/pull/7685 Cleanups ======== EmbeddedFreeTypeFontFontDescription should be EmbeddedFreeTypeFontDescription https://github.com/pharo-project/pharo/pull/7709 Typo in ClyClassWithUndeclares class comment #7707 https://github.com/pharo-project/pharo/pull/7707 7682-ClassHierarchyPrinter-on-steroid-should-be-back- #7683 https://github.com/pharo-project/pharo/pull/7683 Cleanup Files-Tests package #7712 https://github.com/pharo-project/pharo/pull/7712 CleanBlockChecker-Cleanup #7666 https://github.com/pharo-project/pharo/pull/7666

Nov. 12, 2020

Re: [Pharo-users] [Ann] Pharo new version available & mooc needs subtitle translaters

by StÃ©phane Ducasse

Thanks!!! > On 9 Nov 2020, at 18:02, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > > > El miÃ©., 4 nov. 2020 a las 5:30, StÃ©phane Ducasse (<stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>>) escribiÃ³: > Hello > > We are about to launch the new version of the Pharo mooc. Spread the word around you. It will open the 9th of november > https://www.fun-mooc.fr/courses/course-v1:inria+41024+session01/about <https://www.fun-mooc.fr/courses/course-v1:inria+41024+session01/about> > > > This new version contains > 70 new videos about the Pharo ide (in french and english voice) + subtitles > better english dubs > > Now we are looking for help for the subtitles > All the subtitles of the previous mooc and the new ones are at > https://github.com/pharo-mooc/PharoMooc/tree/master/2020-All-Subtitles-Reor… <https://github.com/pharo-mooc/PharoMooc/tree/master/2020-All-Subtitles-Reor…> > The new ones in folders named C048SD or 2018-Prese* > The old ones in folders named C019SD. > > > I will help to translate the new ones to Spanish. > > Cheers, > > HernÃ¡n -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle 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

Nov. 11, 2020

Re: [Pharo-users] [Ann] Pharo new version available & mooc needs subtitle translaters

by StÃ©phane Ducasse

thanks! > On 10 Nov 2020, at 10:17, Tomohiro Oda <tomohiro.tomo.oda(a)gmail.com> wrote: > > I'll work on new Japanese subtitles. > --- > tomo > > 2020å¹´11æ4æ¥(æ°´) 17:30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> Hello >> >> We are about to launch the new version of the Pharo mooc. Spread the word around you. It will open the 9th of november >> https://www.fun-mooc.fr/courses/course-v1:inria+41024+session01/about >> >> >> This new version contains >> 70 new videos about the Pharo ide (in french and english voice) + subtitles >> better english dubs >> >> Now we are looking for help for the subtitles >> All the subtitles of the previous mooc and the new ones are at >> https://github.com/pharo-mooc/PharoMooc/tree/master/2020-All-Subtitles-Reor… >> The new ones in folders named C048SD or 2018-Prese* >> The old ones in folders named C019SD. >> >> For example in https://github.com/pharo-mooc/PharoMooc/tree/master/2020-All-Subtitles-Reor… >> you see the files for the old videos that we will reuse for this new mooc >> as well as the subtitles in french and english for the new videos. >> >> We are looking for subtitles in Spanish, Japanese for the new files: >> in C048 and 2018-PresequelOOP-ENG folder, files named W*-Live* or W*-Redo* >> >> Of course we would love to have the subtitles in portugese and german too, and any other language :). >> >> Thanks in advance for your time. But this mooc is really important for our community. >> >> S. >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Aurore Dalle >> 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 >> -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle 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

Nov. 11, 2020

Re: [Pharo-users] [Ann] Pharo new version available & mooc needs subtitle translaters

by Tomohiro Oda

I'll work on new Japanese subtitles. --- tomo 2020å¹´11æ4æ¥(æ°´) 17:30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > Hello > > We are about to launch the new version of the Pharo mooc. Spread the word around you. It will open the 9th of november > https://www.fun-mooc.fr/courses/course-v1:inria+41024+session01/about > > > This new version contains > 70 new videos about the Pharo ide (in french and english voice) + subtitles > better english dubs > > Now we are looking for help for the subtitles > All the subtitles of the previous mooc and the new ones are at > https://github.com/pharo-mooc/PharoMooc/tree/master/2020-All-Subtitles-Reor… > The new ones in folders named C048SD or 2018-Prese* > The old ones in folders named C019SD. > > For example in https://github.com/pharo-mooc/PharoMooc/tree/master/2020-All-Subtitles-Reor… > you see the files for the old videos that we will reuse for this new mooc > as well as the subtitles in french and english for the new videos. > > We are looking for subtitles in Spanish, Japanese for the new files: > in C048 and 2018-PresequelOOP-ENG folder, files named W*-Live* or W*-Redo* > > Of course we would love to have the subtitles in portugese and german too, and any other language :). > > Thanks in advance for your time. But this mooc is really important for our community. > > S. > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Aurore Dalle > 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 >

Nov. 10, 2020

Re: [Ann] Pharo new version available & mooc needs subtitle translaters

by HernÃ¡n Morales Durand

El miÃ©., 4 nov. 2020 a las 5:30, StÃ©phane Ducasse (< stephane.ducasse(a)inria.fr>) escribiÃ³: > Hello > > We are about to launch the new version of the Pharo mooc. Spread the word > around you. It will open the 9th of november > https://www.fun-mooc.fr/courses/course-v1:inria+41024+session01/about > > > This new version contains > 70 new videos about the Pharo ide (in french and english voice) + subtitles > better english dubs > > Now we are looking for help for the subtitles > All the subtitles of the previous mooc and the new ones are at > > https://github.com/pharo-mooc/PharoMooc/tree/master/2020-All-Subtitles-Reor… > The new ones in folders named C048SD or 2018-Prese* > The old ones in folders named C019SD. > I will help to translate the new ones to Spanish. Cheers, HernÃ¡n

Nov. 9, 2020

This week (45/2020) on the Issue Tracker

by Marcus Denker

Last week we merged 29 Pull Requests and closed 27 Issue tracker entries. Here are the merged pull requests: Breakpoints =========== More fixes related to Breakpoints. This now makes UI update work correctly for VariableBreapoints. In addition we speed up link setting again for MetaLinks by not announcing them by default and let Breakpoints handle the UI updating. - VariableBreakpoint-fix-BrowserUpdate #7672 https://github.com/pharo-project/pharo/pull/7672 - MetaLink-DoNotAnnounceByDefault #7676 https://github.com/pharo-project/pharo/pull/7676 - 6731 use announcements instead of ad hoc observer in breakpoints #7641 https://github.com/pharo-project/pharo/pull/7641 - MetaLinkInstaller-do-not-rely-on-MetaLinkChanged #7636 https://github.com/pharo-project/pharo/pull/7636 - enable-testInsteadVariableReadTemp #7671 https://github.com/pharo-project/pharo/pull/7671 - Tests of VariableBreakpointTests now check that the Break exception has been raised, instead of checking the Halt exception #7626 https://github.com/pharo-project/pharo/pull/7626 New Features ============= - ReClassVariableNeitherReadNorWrittenRule #7667 https://github.com/pharo-project/pharo/pull/7667 - left-option-key-in-mac-should-allow-to-enter-special-characters #7673 https://github.com/pharo-project/pharo/pull/7673 - Fixed #7487. Added protocol column to ClyQueryBrowser #7629 https://github.com/pharo-project/pharo/pull/7629 - [DrTests] Other test hierarchies than TestAssertable are not handled by DrTest #7483 https://github.com/pharo-project/pharo/pull/7483 Fluid Class Definitions ======================= - 7536--Fluid--Propose-a-small-class-template-and-a-full #7646 https://github.com/pharo-project/pharo/pull/7646 - 7648-Fluid-rescue-test-for-compactClassDefinition-and-compactTraitDefinition #7649 https://github.com/pharo-project/pharo/pull/7649 - 7584-Fluid-Complex-slot-should-force-display-of-fluid-class-definition #7657 https://github.com/pharo-project/pharo/pull/7657 - 7536--Fluid--Propose-a-small-class-template-and-a-full #7646 https://github.com/pharo-project/pharo/pull/7646 Fixes and Small improvements ======================== - Updating Image to support correctly TFFI #7663 https://github.com/pharo-project/pharo/pull/7663 - Enhancements to Selector Extractor #7660 https://github.com/pharo-project/pharo/pull/7660 - add deprecated #isSpecial #7664 https://github.com/pharo-project/pharo/pull/7664 - 7653-Removal-of-SystemReporter-breaks-smalltalkCI #7656 https://github.com/pharo-project/pharo/pull/7656 - 7585-Fix-dependency-to-get-a-green-bar-again #7633 https://github.com/pharo-project/pharo/pull/7633 - 7613-Settings-not-storing-correct-values #7623 https://github.com/pharo-project/pharo/pull/7623 - Fixed #7627. Changing canonicalClassName of True and False to Boolean #7635 https://github.com/pharo-project/pharo/pull/7635 - [improvement] change name of 'paste...' command to be clearer #7619 https://github.com/pharo-project/pharo/pull/7619 Cleanups ======== - identityIncludesFontProvider: should be test extension #7670 https://github.com/pharo-project/pharo/pull/7670 - Cleanups in Fonts-Infrastructure and Fonts-Infrastructure-Tests-Logical #7618 https://github.com/pharo-project/pharo/pull/7618 - Rename #simulated into #isSimulatedStyle #7644 https://github.com/pharo-project/pharo/pull/7644 - 7652-What-is-the-purpose-of-testObjectFormatInstSize #7654 https://github.com/pharo-project/pharo/pull/7654 - Fixed #7187. Removed SystemReporter and SizeReporter. They were replaced with Spec-based StSystemReporter and StSizeReporter #7637 https://github.com/pharo-project/pharo/pull/7637 - 7366-Small-Cleanup-SystemOrganizer #7630 https://github.com/pharo-project/pharo/pull/7630 - Deprecated withSqueakLineEndings. Fixed #7446 #7621 https://github.com/pharo-project/pharo/pull/7621 - ClyQuery-supportsWriteBarrier-cleanup #7632 https://github.com/pharo-project/pharo/pull/7632

Nov. 6, 2020

[Ann] Pharo new version available & mooc needs subtitle translaters

by StÃ©phane Ducasse

Hello We are about to launch the new version of the Pharo mooc. Spread the word around you. It will open the 9th of november https://www.fun-mooc.fr/courses/course-v1:inria+41024+session01/about This new version contains 70 new videos about the Pharo ide (in french and english voice) + subtitles better english dubs Now we are looking for help for the subtitles All the subtitles of the previous mooc and the new ones are at https://github.com/pharo-mooc/PharoMooc/tree/master/2020-All-Subtitles-Reor… The new ones in folders named C048SD or 2018-Prese* The old ones in folders named C019SD. For example in https://github.com/pharo-mooc/PharoMooc/tree/master/2020-All-Subtitles-Reor… you see the files for the old videos that we will reuse for this new mooc as well as the subtitles in french and english for the new videos. We are looking for subtitles in Spanish, Japanese for the new files: in C048 and 2018-PresequelOOP-ENG folder, files named W*-Live* or W*-Redo* Of course we would love to have the subtitles in portugese and german too, and any other language :). Thanks in advance for your time. But this mooc is really important for our community. S. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle 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

Nov. 4, 2020