September 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

by stephan

On 14-09-17 19:10, Stephane Ducasse wrote: > I added a pillar file into PharoInProgress > > https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Bint… > > Feel free to edit it and improve it. > I will make sure that it compiles after lunch. Super! Stephan

Sept. 14, 2017

Re: [Pharo-dev] Author name in version Iceberg?

by Stephane Ducasse

Hi guys We worked during years without blame. If you tell me I have a long list of more important items for esteban: - Freetype plugin killing - retina support - Idle Vm - signed mac VM - cleaning host logic in C VM logic - using SDL2 In fact our list is huge and I do not see blame. On Thu, Sep 14, 2017 at 10:57 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 14 Sep 2017, at 10:53, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > AFAIK Esteban is planning to support blame in future at least for Tonel (the > FileTree replacement), however we are not yet there. > > > this ^ > > (but we will support it for both: filetree AND tonel, if possible/easy/not > hard to maintain) > > cheers, > Esteban > > > -- Pavel > > 2017-09-14 10:50 GMT+02:00 stephan <stephan(a)stack.nl>: >> >> On 14-09-17 10:06, Pavel Krivanek wrote: >>> >>> Iceberg currently uses metadata-less format that does not store method >>> timestamp because of the merging conflicts. You cannot do anything now, >>> sorry. >> >> >> No support for blame? >> >> Stephan >> >> > >

Sept. 14, 2017

Re: [Pharo-dev] [Calypso] Toolbar and Statusbar Look - voting time

by Stephane Ducasse

Thanks Denis for your positive mindset and constant willingness to improve. On Thu, Sep 14, 2017 at 3:05 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On 14 September 2017 at 09:24, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> Thank's guys for comments. And thank's Torsten for this initiative. I will >> merge your changes soon. > > RIGHT. > > A bit late to the party, but I agree that the right version is much > easier to read. > > Thanks, > Alistair > > >> 2017-09-14 7:09 GMT+02:00 Max Leske <maxleske(a)gmail.com>: >>> >>> Right >>> >>> >>> On 13 September 2017 at 18:08:26, Torsten Bergmann (astares(a)gmx.de) wrote: >>> >>> Hi all, >>> >>> as you know Denis Kudriashov does a fantastic job in implementing the new >>> Calypso system browser. >>> The plan is that at some point in time will be a replacement for Nautilus >>> in the standard image. >>> Even if not yet integrated one can already use it (either by loading from >>> catalog or github [1]) >>> >>> For me the more I use it (and get used to it) the more I like Calypso and >>> I guess others enjoy it too already. >>> >>> But unfortunately there is a single but very prominently visible UI thing >>> that I dislike on the current look: >>> >>> For the "Pharo3Theme" (light theme) the current implementation of Calypso >>> has a white toolbar in the >>> middle and a white status bar at the bottom. Technically Dennis sets the >>> colors of these morphs to >>> transparent to have this effect (see LEFT example of the attached >>> screenshot) >>> >>> >>> To me this lookes strange and unusual because >>> - usually (on Windows, GTK, Java Swing, Linux window managers) such areas >>> like a status bar follow the window color >>> and are displayed in gray when that is the default window theme color (see >>> [2], [3], [4]) >>> - these white bars would better fit for the "Glamorous Whitespace" theme >>> (as this theme is already more white areas) >>> >>> Also the current white bars do not make a pleasant contrast to the other >>> panes of Calypso: >>> - there is not really a visual distinction to the >>> package/class/protocol-tag/method panes and filters for the middle part >>> (toolbar) >>> - there is not really a visual distinction from the code pane for the >>> bottom part (statusbar) >>> - the divider line in the code pane just stops in a white area without >>> borders >>> >>> To me this looks rather ugly and I would like Pharo to look more >>> professional and clean ;) >>> >>> So I proposed a simple PR [5] today to change this and technically using >>> the window color of the theme - the result can be >>> seen on the right side of the attached screenshot and discussed with Denis >>> on Discord. >>> >>> Denis on the other hand still likes the white approach on the left more >>> while I prefer the right one. >>> >>> He wrote that he wants other people comment on this issue first to which I >>> agree and therefore I write this mail >>> to discuss it here on the dev-list and find out about what the majority in >>> the community prefers. >>> >>> So it would be good if others could >>> - comment about their personal preference >>> - or just vote with "LEFT" (white/transparent) or "RIGHT" (window color) >>> in reply to this mail >>> - or make another proposal (which is only accepted with screenshot and PR >>> ;) >>> >>> Also please do not mix other UI discussions into this thread. Thanks in >>> advance! >>> >>> Bye >>> T. >>> >>> [1] https://github.com/dionisiydk/Calypso >>> [2] >>> http://cdn.osxdaily.com/wp-content/uploads/2011/08/show-status-bar-and-disk… >>> [3] http://i.stack.imgur.com/pgt5n.png >>> [4] http://python.zirael.org/gtk-statusbar1-1.png >>> [5] https://github.com/dionisiydk/Calypso/pull/91 >> >> >

Sept. 14, 2017

Re: [Pharo-dev] Sources location and name, PharoLauncher

by Stephane Ducasse

Kill some images :). We did that for good reasons I do not remember why but this is due to the bootstrap. Stefan we will never be perfect day one. This is not possible for us. Stef On Thu, Sep 14, 2017 at 3:10 PM, stephan <stephan(a)stack.nl> wrote: > On 14-09-17 14:52, Peter UhnÃ¡k wrote: >> >> That's not related to Pharo Launcher. Pharo 7 sources (for alpha images) >> are now shipped with the image, not the VM. > > > That's an issue. I have hundreds of images, and definitely don't need so > many different sources. > > Stephan > >

Sept. 14, 2017

Re: [Pharo-dev] Pharo 6.1 32bit/64bit on CentOS 7 with Iceberg

by phil＠highoctane.be

I used it but not enough to help you with this issue. Phil On Thu, Sep 14, 2017 at 12:22 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Hi, > > Does anybody use Pharo 6.1 (32 or 64 bit) on CentOS 7? > I am getting randomly the following crash when trying to clone a > repository from github. While this might suggest some kind of of out memory > error there should be enough memory. > > PrimitiveFailed: primitive #allocateExecutablePage in FFICallbackThunk > class failed > FFICallbackThunk class(Object)>>primitiveFailed: > FFICallbackThunk class(Object)>>primitiveFailed > FFICallbackThunk class>>allocateExecutablePage > [ ExecutablePages add: self allocateExecutablePage ] in FFICallbackThunk > class>>unusedBlockInExecutablePage in Block: [ ExecutablePages add: self > allocateExecutablePage...etc... > [ caught := true. > self wait. > blockValue := mutuallyExcludedBlock value ] in Semaphore>>critical: in > Block: [ caught := true.... > BlockClosure>>ensure: > Semaphore>>critical: > FFICallbackThunk class>>unusedBlockInExecutablePage > FFICallbackThunk class>>privateFinalizingNew > FFICallbackThunk class>>newCCall > CallbackForIA32(Callback)>>callbackEvaluator: > Callback class>>forCallbackEvaluator: > LGitTransportCertificateCheckCallback(FFICallback)>>signature:block: > LGitTransportCertificateCheckCallback class(FFICallback > class)>>signature:block: > LGitTransportCertificateCheckCallback class(LGitCallback class)>>on: > LGitRemoteCallbacks class>>newCertificateCheckCallback > LGitRemoteCallbacks class>>defaults > LGitRemoteCallbacks class>>withProvider: > LGitCloneOptions class>>withCredentialsProvider: > [ | repo cloneOptions | > repo := LGitRepository on: self location. > cloneOptions := LGitCloneOptions > withCredentialsProvider: IceCredentialsProvider default. > repo clone: url options: cloneOptions. > aBranchName ifNotNil: [ repo checkout: aBranchName ]. > (LGitRemote of: repo named: 'origin') > lookup; > setUrl: url ] in IceLibgitLocalRepository>>cloneRepositoryFrom:branch: > in Block: [ | repo cloneOptions |... > [ self checkInitialized. > aBlock value ] in LGitGlobal class>>runSequence: in Block: [ self > checkInitialized.... > [ activeProcess psValueAt: index put: anObject. > aBlock value ] in LGitActionSequence(DynamicVariable)>>value:during: in > Block: [ activeProcess psValueAt: index put: anObject.... > BlockClosure>>ensure: > LGitActionSequence(DynamicVariable)>>value:during: > LGitActionSequence class(DynamicVariable class)>>value:during: > LGitGlobal class>>runSequence: > IceLibgitLocalRepository>>cloneRepositoryFrom:branch: > IceRepositoryCreator>>createRepository > [ (IceRepositoryCreator new > url: remoteUrl; > subdirectory: repoPath; > branchName: self projectVersion; > createRepository) register ] in MCGitHubRepository>>getOrCreateIcebergRepository > in Block: [ (IceRepositoryCreator new... > OrderedCollection(Collection)>>detect:ifFound:ifNone: > > Cheers, > Andrei >

Sept. 14, 2017

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

by Stephane Ducasse

I added a pillar file into PharoInProgress https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Bint… Feel free to edit it and improve it. I will make sure that it compiles after lunch. Stef On Thu, Sep 14, 2017 at 6:49 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > !! How to render automatically your pillar file as pdf > > We will use bintray to store the latest pdf and we will use github the > released pdf. > > !!! Create an account in bintray > Create an account on bintray at https://bintray.com/ > You may link it or not to your github account > > !!! Obtain an encoded API key for BinTray > > In your bintray profile get your API key (copy it to your copy paste buffer) > > In your machine in the github folder > >> travis login --auto >> travis encrypt Your API Key from bintray > > You use the resulting key in your .travis.yml configuration file. > > !!! Add and edit the .travis.yml file > > Here is the .travis.yml of the Learning programming project > Not that the configuration also > > sudo: required > services: > - docker > > before_install: > - docker pull dpollet/texlive:pillar > > script: > - docker run --tty --rm --volume $PWD:/work dpollet/texlive:pillar > make spiralbook > > deploy: > - provider: bintray > file: .bintray.json > on: > repo: SquareBracketAssociates/LearningOOPWithPharo > skip_cleanup: true > user: ducasse > key: > secure: DLT5e+3+U3jaooTLVN6JPcavMS+5XzFwNIfsK7QLYefzOZfBR8lt2vHtX2OxcdyKNfuzh0EaIDUR9a6+/Eg/wAcxjFDEO94ftb7rD7YHJ1Tc7r4AaeKwrdwyL6VgbN0ZNZqtXsTWGg+4XgHvSq0KVAR9K1IKSwJYPWwjJwDexakY2/ZpRg6R0OgaZwhtTEbbUn/pnoVQl3VfNlCjiI+ZLDqPKf/UfovVv7tzqdHeLK73MJN36Ri8IGTP5QaSYHBBko8mTv4EoVH7HuuSLAa60NBOScksYY5LjsS7OdzIwipmk4xwxcp2QXtVjf2uNKCKIISVRMzesdmUnsuL/qReJh7pfn21a38ZEEjJPPWSnwA8iI+GHUiCcLuHdw1+ilmIqxF3w8gSunM3aUv4a/qQm641DpGPawnYBbnFGPyEkxpCB1HXIsRRJeBs2UEkFmhOHyGWGl0+jx3iihwe72HMKRYeXcDHKOn1gU+pJQ50PBXFsTotOr7wkZ6OGsKO0XecNsZGodsQ4lPVxfJolnKhkxIouzCagd3wO0iseG1vOyi5JrRT+NPsZp7TKBrHIDAUb0LG+F8qC/IXHhTYo7ZywF5ZjIV9UZo/kZP0EQ8pstUlD4V4DWRYV1KQSpORM01wpdcZFDb5ExLvEck6Sv1cuW9QYBst+lDVpoSpbXSnSDc= > > > !! Add and Edit the .bintray.json file > > Here is the one of the > https://github.com/SquareBracketAssociates/LearningOOPWithPharo > > more .bintray.json > > [[[ > > { > "package": { > "name": "Loop", > "repo": "wip", > "subject": "squarebracketassociates", > "desc": "Learning OOP with Pharo", > "licenses": ["MIT"], > "website_url": > "https://github.com/SquareBracketAssociates/LearningOOPWithPharo", > "issue_tracker_url": > "https://github.com/SquareBracketAssociates/LearningOOPWithPharo/issues", > "vcs_url": > "https://github.com/SquareBracketAssociates/LearningOOPWithPharo.git", > "labels": ["work-in-progress"] > }, > > "version": { > "name": "latest", > "desc": "Latest successful build" > }, > > "files": [ > { > "includePattern": "build/(learningoop).pdf", > "uploadPattern": "$1-wip.pdf", > "matrixParams": { "override": 1 } > } > ], > "publish": true > } > > ]]] > > > !! for Github integration > > For a given checkout you should generate the associated token. > > [[[ > travis setup releases > ]]] > > Here is the full .travis.yml with the github integration > > [[[ > > sudo: required > services: > - docker > > before_install: > - docker pull dpollet/texlive:pillar > > script: > - docker run --tty --rm --volume $PWD:/work dpollet/texlive:pillar > make spiralbook > > deploy: > - provider: bintray > file: .bintray.json > on: > repo: SquareBracketAssociates/LearningOOPWithPharo > skip_cleanup: true > user: ducasse > key: > secure: ThnjhD8OMRlL5NmsK8dGQR4mpzXG2Kj2NeWHA5oHCO4YTaK0fKLPHF8YcjlyQorESX6+Z/Q0ihtTq1/3GguH8rzjAS8DrgArB3Stcg6npfyB3svyeVWXTKP8EPLHtenBnLANWTj/tYfHd6egDltJlxGMrEd5tHzl8CNlD+mmfQA1VhXUEmh8pw8P6VfFDWiL+bHG/Am1DI8SspcuQbYcKzh6ZdadvXwpEfQr07VTc0w4zygRk6h8z+76wX8N7xebr66aLe9FipZ0d3dYYfhZl3mtsOoUJmvGpnsSYt3h3I9TnOTeZjGAUEfzxdoZ6CRMIExUhNU7VEBMN4FKP8Oic8Eu1i/Ay7cM74mwGgJCX8DE0M/y0DJqJoKEk+NojoZfSgSzwslE1hXSZSaAJoTr9EDkZwEpVDCep42TVZyOYa+GICZCWpO999KYZlm8ItD4EJsqu8s2pipEMmcLGbGDBejuQ/30NRvelNG6xcT0wTg4595zNuP4k9cOYG9RddlqDzy8E333oz+cJ2R9zolsQpNHZtsQvKvbamRt0fsKjOgGv/a4Wslp1ZczWezRbBCxWC8wvtYSn1MWraQUGh6E3OrljoplbgUmOY/XLsAJeeFxIAmOwUzo2PK5S43nEhKQQNr/CmP4TAL9P3wbsBhQ/WXa4f8lUSeexDzrK7qY8J0= > - provider: releases > file: build/learningoop.pdf > on: > tags: true > skip_cleanup: true > api_key: > secure: pRfu3fr35BzqQDi1ul0SubPSwO8zcyIidqLRZPz3XIrH4qoy1Zgnq785dmB7ziNQqH+VJyh7askSFY3JLxL0d4P0eUgj2ZDIOhJsUQQ/ihevOBWbxlMOoEPjQfzA11l8WrNCQ566KrcYiISRi7bCg698kPTWSRwOmmvqXOJe5zGkuUbVmMNUV2oxaNV4JC8kVyVWHYy0nNMLEX/hzRZRh1+8K34/ds+fZ7irLrbDWMbKGHCyuLCSqv+zJJdu99nWLTclrCxFzK4DEHaMlFiO7wkUpyQLwZ38EDnb3E7iv045jSqCx3XB+DMRG1Da2/9BIXl0mho5ELdEvfGVAbjI2no5FWd0H1cs4/banAePCFnM7ZscJBaPWgVajB7EzrcADJUoxpmU6+6n1aIC3CnjscfAHqSAKGv8CO/Jh+Uirc8ATRpSqa73f2Nnj9tRCqwCOnFOCEzu0w5l3Ppz2Qpif04P+QbebZehSVaBJ4W01R2i8Rac3IuZDhZVaek1X24HFxUOd/rvHpbhz8eeANdnsWCTkAm+0sD+iKsWKICRMxFZfCK/SPldAcjXZsOsEMTqfx7ZWyCc7GeesQWcmW+z3shziyQd9tdeArJWLwacly3hH3WeyuUD5JyPF9klvDBtHgTVajdU4yp+3oXsrtTmetnBz+RESxQGdLgZRlQBQog= > > ]]] > > > !! How to add a new released file in your git hub account > > To release a pdf that will be stored on github in the booklet repo we > should create a annotated tag. > > [[[ > git tag -a v1.0-Pharo50 > git push --tags > ]]] > > > > > > > > > > > > > > > > > > > > > > travis encrypt 7dec59756c31e5e75e33fcfe0d0d435a0e04a02d > > On Thu, Sep 14, 2017 at 11:15 AM, stephan <stephan(a)stack.nl> wrote: >> On 25-08-17 16:42, Stephane Ducasse wrote: >>> >>> I'm writing a doc of the process so that other people can do it for >>> their private projects. >> >> >> I know how to copy and rename an existing project, and put that on github. >> What else do I need to do? Register with bintray, register with travis, >> generate keys in some way? >> >> Stephan >> >> >>

Sept. 14, 2017

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

by Stephane Ducasse

!! How to render automatically your pillar file as pdf We will use bintray to store the latest pdf and we will use github the released pdf. !!! Create an account in bintray Create an account on bintray at https://bintray.com/ You may link it or not to your github account !!! Obtain an encoded API key for BinTray In your bintray profile get your API key (copy it to your copy paste buffer) In your machine in the github folder > travis login --auto > travis encrypt Your API Key from bintray You use the resulting key in your .travis.yml configuration file. !!! Add and edit the .travis.yml file Here is the .travis.yml of the Learning programming project Not that the configuration also sudo: required services: - docker before_install: - docker pull dpollet/texlive:pillar script: - docker run --tty --rm --volume $PWD:/work dpollet/texlive:pillar make spiralbook deploy: - provider: bintray file: .bintray.json on: repo: SquareBracketAssociates/LearningOOPWithPharo skip_cleanup: true user: ducasse key: secure: DLT5e+3+U3jaooTLVN6JPcavMS+5XzFwNIfsK7QLYefzOZfBR8lt2vHtX2OxcdyKNfuzh0EaIDUR9a6+/Eg/wAcxjFDEO94ftb7rD7YHJ1Tc7r4AaeKwrdwyL6VgbN0ZNZqtXsTWGg+4XgHvSq0KVAR9K1IKSwJYPWwjJwDexakY2/ZpRg6R0OgaZwhtTEbbUn/pnoVQl3VfNlCjiI+ZLDqPKf/UfovVv7tzqdHeLK73MJN36Ri8IGTP5QaSYHBBko8mTv4EoVH7HuuSLAa60NBOScksYY5LjsS7OdzIwipmk4xwxcp2QXtVjf2uNKCKIISVRMzesdmUnsuL/qReJh7pfn21a38ZEEjJPPWSnwA8iI+GHUiCcLuHdw1+ilmIqxF3w8gSunM3aUv4a/qQm641DpGPawnYBbnFGPyEkxpCB1HXIsRRJeBs2UEkFmhOHyGWGl0+jx3iihwe72HMKRYeXcDHKOn1gU+pJQ50PBXFsTotOr7wkZ6OGsKO0XecNsZGodsQ4lPVxfJolnKhkxIouzCagd3wO0iseG1vOyi5JrRT+NPsZp7TKBrHIDAUb0LG+F8qC/IXHhTYo7ZywF5ZjIV9UZo/kZP0EQ8pstUlD4V4DWRYV1KQSpORM01wpdcZFDb5ExLvEck6Sv1cuW9QYBst+lDVpoSpbXSnSDc= !! Add and Edit the .bintray.json file Here is the one of the https://github.com/SquareBracketAssociates/LearningOOPWithPharo more .bintray.json [[[ { "package": { "name": "Loop", "repo": "wip", "subject": "squarebracketassociates", "desc": "Learning OOP with Pharo", "licenses": ["MIT"], "website_url": "https://github.com/SquareBracketAssociates/LearningOOPWithPharo", "issue_tracker_url": "https://github.com/SquareBracketAssociates/LearningOOPWithPharo/issues", "vcs_url": "https://github.com/SquareBracketAssociates/LearningOOPWithPharo.git", "labels": ["work-in-progress"] }, "version": { "name": "latest", "desc": "Latest successful build" }, "files": [ { "includePattern": "build/(learningoop).pdf", "uploadPattern": "$1-wip.pdf", "matrixParams": { "override": 1 } } ], "publish": true } ]]] !! for Github integration For a given checkout you should generate the associated token. [[[ travis setup releases ]]] Here is the full .travis.yml with the github integration [[[ sudo: required services: - docker before_install: - docker pull dpollet/texlive:pillar script: - docker run --tty --rm --volume $PWD:/work dpollet/texlive:pillar make spiralbook deploy: - provider: bintray file: .bintray.json on: repo: SquareBracketAssociates/LearningOOPWithPharo skip_cleanup: true user: ducasse key: secure: ThnjhD8OMRlL5NmsK8dGQR4mpzXG2Kj2NeWHA5oHCO4YTaK0fKLPHF8YcjlyQorESX6+Z/Q0ihtTq1/3GguH8rzjAS8DrgArB3Stcg6npfyB3svyeVWXTKP8EPLHtenBnLANWTj/tYfHd6egDltJlxGMrEd5tHzl8CNlD+mmfQA1VhXUEmh8pw8P6VfFDWiL+bHG/Am1DI8SspcuQbYcKzh6ZdadvXwpEfQr07VTc0w4zygRk6h8z+76wX8N7xebr66aLe9FipZ0d3dYYfhZl3mtsOoUJmvGpnsSYt3h3I9TnOTeZjGAUEfzxdoZ6CRMIExUhNU7VEBMN4FKP8Oic8Eu1i/Ay7cM74mwGgJCX8DE0M/y0DJqJoKEk+NojoZfSgSzwslE1hXSZSaAJoTr9EDkZwEpVDCep42TVZyOYa+GICZCWpO999KYZlm8ItD4EJsqu8s2pipEMmcLGbGDBejuQ/30NRvelNG6xcT0wTg4595zNuP4k9cOYG9RddlqDzy8E333oz+cJ2R9zolsQpNHZtsQvKvbamRt0fsKjOgGv/a4Wslp1ZczWezRbBCxWC8wvtYSn1MWraQUGh6E3OrljoplbgUmOY/XLsAJeeFxIAmOwUzo2PK5S43nEhKQQNr/CmP4TAL9P3wbsBhQ/WXa4f8lUSeexDzrK7qY8J0= - provider: releases file: build/learningoop.pdf on: tags: true skip_cleanup: true api_key: secure: pRfu3fr35BzqQDi1ul0SubPSwO8zcyIidqLRZPz3XIrH4qoy1Zgnq785dmB7ziNQqH+VJyh7askSFY3JLxL0d4P0eUgj2ZDIOhJsUQQ/ihevOBWbxlMOoEPjQfzA11l8WrNCQ566KrcYiISRi7bCg698kPTWSRwOmmvqXOJe5zGkuUbVmMNUV2oxaNV4JC8kVyVWHYy0nNMLEX/hzRZRh1+8K34/ds+fZ7irLrbDWMbKGHCyuLCSqv+zJJdu99nWLTclrCxFzK4DEHaMlFiO7wkUpyQLwZ38EDnb3E7iv045jSqCx3XB+DMRG1Da2/9BIXl0mho5ELdEvfGVAbjI2no5FWd0H1cs4/banAePCFnM7ZscJBaPWgVajB7EzrcADJUoxpmU6+6n1aIC3CnjscfAHqSAKGv8CO/Jh+Uirc8ATRpSqa73f2Nnj9tRCqwCOnFOCEzu0w5l3Ppz2Qpif04P+QbebZehSVaBJ4W01R2i8Rac3IuZDhZVaek1X24HFxUOd/rvHpbhz8eeANdnsWCTkAm+0sD+iKsWKICRMxFZfCK/SPldAcjXZsOsEMTqfx7ZWyCc7GeesQWcmW+z3shziyQd9tdeArJWLwacly3hH3WeyuUD5JyPF9klvDBtHgTVajdU4yp+3oXsrtTmetnBz+RESxQGdLgZRlQBQog= ]]] !! How to add a new released file in your git hub account To release a pdf that will be stored on github in the booklet repo we should create a annotated tag. [[[ git tag -a v1.0-Pharo50 git push --tags ]]] travis encrypt 7dec59756c31e5e75e33fcfe0d0d435a0e04a02d On Thu, Sep 14, 2017 at 11:15 AM, stephan <stephan(a)stack.nl> wrote: > On 25-08-17 16:42, Stephane Ducasse wrote: >> >> I'm writing a doc of the process so that other people can do it for >> their private projects. > > > I know how to copy and rename an existing project, and put that on github. > What else do I need to do? Register with bintray, register with travis, > generate keys in some way? > > Stephan > > >

Sept. 14, 2017

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

by Eliot Miranda

> On Sep 14, 2017, at 7:07 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 14.09.2017 um 10:17 schrieb Denis Kudriashov <dionisiydk(a)gmail.com>: >> >> Hello. >> >> I guess we are agree to rename. I will prepare pull request for Pharo. And Squeak is up to you. >> >> Here is the new messages: >> - pinInMemory >> - unpinInMemory >> - isPinnedInMemory >> - setPinnedInMemory: >> >> What was decision about #pinInMemoryDuring: ? Do we need it? >> > I understand Eliot in a way that there is no real point in unpinning objects. Hence pinDuring: is basically never useful and therefor adding a selectir has rather a negative impact +1 > > Norbert >> 2017-09-14 9:28 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: >>> +1 for pinInMemory >>> >>> It explains what it does. >>> >>> On 9/14/17, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>> > Hi Norbert, >>> > >>> >> On Sep 13, 2017, at 3:18 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >> >>> >> >>> >>> Am 14.09.2017 um 00:09 schrieb Eliot Miranda <eliot.miranda(a)gmail.com>: >>> >>> >>> >>> Hi Denis, >>> >>> >>> >>> On Tue, Sep 12, 2017 at 9:29 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> >>> wrote: >>> >>>> Hi Eliot. >>> >>>> >>> >>>> I know and I only talk about new messages. I am not trying to rethink >>> >>>> full meta model of Smalltalk. >>> >>>> By the way #class is very common message and it is handy to use short >>> >>>> name. But pinning messages will be used rarely in very specific >>> >>>> applications. So no much sense to preserve them in short version. >>> >>> >>> >>> Agreed. So we have to decide whether to go with pinInMemory or >>> >>> pinObject, pinObject being suggested by Norbert because it matched >>> >>> isReadOnlyObject. Personally I like pinInMemory. Norbert, do you feel >>> >>> strongly about pinObject et al? >>> >>> >>> >> No I don't. It feels only good to me if there is a requirement not to >>> >> implement selectors that are likely to be used in user code. I'm ok with >>> >> pinInMemory although I asked myself where can it be pinned elsewhere if >>> >> not in memory. So the suffix in memory doesn't add anything but also moves >>> >> the selector out of user space. >>> > >>> > Well I think Denis' point is that pinInMemory removes ambiguity with pin for >>> > other uses and I agree. So I for one am happy to change it to pinInMemory >>> > et al. >>> > >>> >> >>> >> Norbert >>> >> >>> >>>> >>> >>>> 2017-09-12 18:05 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >>> >>>>> Hi Denis, >>> >>>>> >>> >>>>> >>> >>>>>> On Sep 12, 2017, at 2:39 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> >>>>>> wrote: >>> >>>>>> >>> >>>>>> I am really wonder guys. I thought you are not big funs of Object >>> >>>>>> protocol. >>> >>>>>> Current pinning messages are a new set of very generic messages in the >>> >>>>>> Object. >>> >>>>> >>> >>>>> Yes, and that's because this is a fundamental property of all >>> >>>>> non-immediate objects. Do you object to the #class message? Should it >>> >>>>> be #classObject because it might conflict with #class used in an >>> >>>>> educational or socioeconomic model? All objects other than immediates >>> >>>>> can move. Pinning stops that movement. It applies generally. So the >>> >>>>> protocol belongs in Object. >>> >>>>> >>> >>>>> >>> >>>>>> >>> >>>>>> About Norbert idea. >>> >>>>>> - bePinnedObject is not bad convention. But I would prefer the memory >>> >>>>>> suffix because it reflects the low level behaviour. >>> >>>>>> >>> >>>>>> 2017-09-11 14:16 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>>>>> yes, me :) >>> >>>>>>> >>> >>>>>>> I do not see a reason to change them, tbh. >>> >>>>>>> for me they are comprensible as they are now and it does not adds >>> >>>>>>> more information pinInMemory or pinMemory. >>> >>>>>>> >>> >>>>>>> Esteban >>> >>>>>>> >>> >>>>>>> >>> >>>>>>>> On 11 Sep 2017, at 11:56, Denis Kudriashov <dionisiydk(a)gmail.com> >>> >>>>>>>> wrote: >>> >>>>>>>> >>> >>>>>>>> Anybody else? >>> >>>>>>>> >>> >>>>>>>> 2017-08-31 10:29 GMT+02:00 Pavel Krivanek >>> >>>>>>>> <pavel.krivanek(a)gmail.com>: >>> >>>>>>>>> >>> >>>>>>>>> >>> >>>>>>>>> 2017-08-31 10:24 GMT+02:00 Denis Kudriashov >>> >>>>>>>>> <dionisiydk(a)gmail.com>: >>> >>>>>>>>>> Hi. >>> >>>>>>>>>> >>> >>>>>>>>>> We now have very generic message names: >>> >>>>>>>>>> - pin >>> >>>>>>>>>> - unpin >>> >>>>>>>>>> - setPinned: >>> >>>>>>>>>> - isPinned >>> >>>>>>>>>> >>> >>>>>>>>>> Problem that they collide with possible domain related names. >>> >>>>>>>>>> For example I implemented pinning of tabs in Calypso and I found >>> >>>>>>>>>> that I overrides #pin and #isPinned messages. Then I fix it with >>> >>>>>>>>>> different names. >>> >>>>>>>>>> Probably menus also uses pin word but without overrides >>> >>>>>>>>>> >>> >>>>>>>>>> What you think about renaming pinning messages? Something like: >>> >>>>>>>>>> - pinMemory >>> >>>>>>>>> >>> >>>>>>>>> I would use pinInMemory >>> >>>>>>>>> >>> >>>>>>>>> -- Pavel >>> >>>>>>>>> >>> >>>>>>>>>> - unpinMemory >>> >>>>>>>>>> - isMemoryPinned >>> >>>>>>>>>> - setPinnedMemory: >>> >>>>>>>>>> - pinMemoryDuring: (if we will introduce it) >>> >>>>>>>>>> >>> >>>>>>>>>> I think it is easy to do now because not much code uses pinning >>> >>>>>>>>> >>> >>>>>>>> >>> >>>>>>> >>> >>>>>> >>> >>>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> _,,,^..^,,,_ >>> >>> best, Eliot >>> >> >>> > >>> >>

Sept. 14, 2017

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

by Norbert Hartl

> Am 14.09.2017 um 10:17 schrieb Denis Kudriashov <dionisiydk(a)gmail.com>: > > Hello. > > I guess we are agree to rename. I will prepare pull request for Pharo. And Squeak is up to you. > > Here is the new messages: > - pinInMemory > - unpinInMemory > - isPinnedInMemory > - setPinnedInMemory: > > What was decision about #pinInMemoryDuring: ? Do we need it? > I understand Eliot in a way that there is no real point in unpinning objects. Hence pinDuring: is basically never useful and therefor adding a selectir has rather a negative impact Norbert > 2017-09-14 9:28 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: >> +1 for pinInMemory >> >> It explains what it does. >> >> On 9/14/17, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> > Hi Norbert, >> > >> >> On Sep 13, 2017, at 3:18 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> >> >> >>> Am 14.09.2017 um 00:09 schrieb Eliot Miranda <eliot.miranda(a)gmail.com>: >> >>> >> >>> Hi Denis, >> >>> >> >>> On Tue, Sep 12, 2017 at 9:29 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >> >>> wrote: >> >>>> Hi Eliot. >> >>>> >> >>>> I know and I only talk about new messages. I am not trying to rethink >> >>>> full meta model of Smalltalk. >> >>>> By the way #class is very common message and it is handy to use short >> >>>> name. But pinning messages will be used rarely in very specific >> >>>> applications. So no much sense to preserve them in short version. >> >>> >> >>> Agreed. So we have to decide whether to go with pinInMemory or >> >>> pinObject, pinObject being suggested by Norbert because it matched >> >>> isReadOnlyObject. Personally I like pinInMemory. Norbert, do you feel >> >>> strongly about pinObject et al? >> >>> >> >> No I don't. It feels only good to me if there is a requirement not to >> >> implement selectors that are likely to be used in user code. I'm ok with >> >> pinInMemory although I asked myself where can it be pinned elsewhere if >> >> not in memory. So the suffix in memory doesn't add anything but also moves >> >> the selector out of user space. >> > >> > Well I think Denis' point is that pinInMemory removes ambiguity with pin for >> > other uses and I agree. So I for one am happy to change it to pinInMemory >> > et al. >> > >> >> >> >> Norbert >> >> >> >>>> >> >>>> 2017-09-12 18:05 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> >>>>> Hi Denis, >> >>>>> >> >>>>> >> >>>>>> On Sep 12, 2017, at 2:39 AM, Denis Kudriashov <dionisiydk(a)gmail.com> >> >>>>>> wrote: >> >>>>>> >> >>>>>> I am really wonder guys. I thought you are not big funs of Object >> >>>>>> protocol. >> >>>>>> Current pinning messages are a new set of very generic messages in the >> >>>>>> Object. >> >>>>> >> >>>>> Yes, and that's because this is a fundamental property of all >> >>>>> non-immediate objects. Do you object to the #class message? Should it >> >>>>> be #classObject because it might conflict with #class used in an >> >>>>> educational or socioeconomic model? All objects other than immediates >> >>>>> can move. Pinning stops that movement. It applies generally. So the >> >>>>> protocol belongs in Object. >> >>>>> >> >>>>> >> >>>>>> >> >>>>>> About Norbert idea. >> >>>>>> - bePinnedObject is not bad convention. But I would prefer the memory >> >>>>>> suffix because it reflects the low level behaviour. >> >>>>>> >> >>>>>> 2017-09-11 14:16 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>>>>>> yes, me :) >> >>>>>>> >> >>>>>>> I do not see a reason to change them, tbh. >> >>>>>>> for me they are comprensible as they are now and it does not adds >> >>>>>>> more information pinInMemory or pinMemory. >> >>>>>>> >> >>>>>>> Esteban >> >>>>>>> >> >>>>>>> >> >>>>>>>> On 11 Sep 2017, at 11:56, Denis Kudriashov <dionisiydk(a)gmail.com> >> >>>>>>>> wrote: >> >>>>>>>> >> >>>>>>>> Anybody else? >> >>>>>>>> >> >>>>>>>> 2017-08-31 10:29 GMT+02:00 Pavel Krivanek >> >>>>>>>> <pavel.krivanek(a)gmail.com>: >> >>>>>>>>> >> >>>>>>>>> >> >>>>>>>>> 2017-08-31 10:24 GMT+02:00 Denis Kudriashov >> >>>>>>>>> <dionisiydk(a)gmail.com>: >> >>>>>>>>>> Hi. >> >>>>>>>>>> >> >>>>>>>>>> We now have very generic message names: >> >>>>>>>>>> - pin >> >>>>>>>>>> - unpin >> >>>>>>>>>> - setPinned: >> >>>>>>>>>> - isPinned >> >>>>>>>>>> >> >>>>>>>>>> Problem that they collide with possible domain related names. >> >>>>>>>>>> For example I implemented pinning of tabs in Calypso and I found >> >>>>>>>>>> that I overrides #pin and #isPinned messages. Then I fix it with >> >>>>>>>>>> different names. >> >>>>>>>>>> Probably menus also uses pin word but without overrides >> >>>>>>>>>> >> >>>>>>>>>> What you think about renaming pinning messages? Something like: >> >>>>>>>>>> - pinMemory >> >>>>>>>>> >> >>>>>>>>> I would use pinInMemory >> >>>>>>>>> >> >>>>>>>>> -- Pavel >> >>>>>>>>> >> >>>>>>>>>> - unpinMemory >> >>>>>>>>>> - isMemoryPinned >> >>>>>>>>>> - setPinnedMemory: >> >>>>>>>>>> - pinMemoryDuring: (if we will introduce it) >> >>>>>>>>>> >> >>>>>>>>>> I think it is easy to do now because not much code uses pinning >> >>>>>>>>> >> >>>>>>>> >> >>>>>>> >> >>>>>> >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> _,,,^..^,,,_ >> >>> best, Eliot >> >> >> > >> >

Sept. 14, 2017

Re: [Pharo-dev] Sources location and name, PharoLauncher

by stephan

On 14-09-17 14:52, Peter UhnÃ¡k wrote: > That's not related to Pharo Launcher. Pharo 7 sources (for alpha images) > are now shipped with the image, not the VM. That's an issue. I have hundreds of images, and definitely don't need so many different sources. Stephan

Sept. 14, 2017