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

Re: [Pharo-users] Yet another Pharo in docker

by Sean P. DeNigris

Marcus Denker-4 wrote > I would like to coordinate to have something official in April. As you investigate this, check out the barebones Docker support in the `docker` branch of my smalltalkCI fork [1]. It is a proof-of-concept wrapper of the Docker infrastructure, so that (kind of like Slang), you can stay in Pharo instead of learning and writing Dockerfiles by hand. Commits trigger container(s) to be built automatically on DockerHub [2] which are in daily use in my CI builds. Here is an example: | toolDependencies commands | toolDependencies := #('ca-certificates' curl unzip wget git). commands := OrderedCollection new add: (SCIDockerComment contents: 'Pharo (32-bit)'); add: (SCIDockerFROM new baseImage: 'ubuntu:16.04'); addAll: (aPlatform sciDockerDependencyCommandsGivenTools: toolDependencies); yourself. ^ self new instructions: commands; yourself. Which gets turned into something like this [3]: I wrote it to use it in my CI builds, so at the time smalltalkCI seemed like the most appropriate host, but it could live anywhere and could easily be extracted. IIRC it has no dependencies ATM. # Pharo (32-bit) FROM ubuntu:16.04 RUN dpkg --add-architecture i386 RUN apt-get -qq update && apt-get -qq install \ ca-certificates \ curl \ git \ libcurl3:i386 \ libfontconfig1:i386 \ libfreetype6:i386 \ libgl1-mesa-glx:i386 \ libsqlite3-0:i386 \ libssl1.0.0:i386 \ libx11-6:i386 \ unzip \ wget \ && rm -rf /var/lib/apt/lists/* RUN echo "Pharo 32-bit prerequisities installed." 1. https://github.com/seandenigris/smalltalkCI/tree/docker/repository/Smalltal… 2. https://hub.docker.com/r/seandenigris/pharo/ 3. https://github.com/seandenigris/smalltalkCI/blob/docker/docker/Dockerfile ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 22, 2018

Re: [Pharo-users] ZnClient - receiving/parsing malformed cookie 'expires' value

by Sven Van Caekenberghe

Hi Paul, > On 20 Mar 2018, at 01:45, PAUL DEBRUICKER <pdebruic(a)gmail.com> wrote: > > Hi - This is more of an FYI than anything > > > I'm interacting with an API that is sending "expires=0" value as part of the only cookie of their response. > > > Changing #expiresTimeStamp to > > > (self expires isNil or:[self expires size<28] ) ifTrue:[ ^ DateAndTime now + 1 day ]. > ^ ZnUtils parseHttpDate: self expires > > > fixes my issue but maybe there's a better way to handle cookie parsing errors > > > Paul HTTP Cookies are pretty tricky, and ZnCookie seems like a crude implementation, but I don't want to fix that right now, as it works. So I tried to fix your issue a bit like you suggested: === Name: Zinc-HTTP-SvenVanCaekenberghe.474 Author: SvenVanCaekenberghe Time: 22 March 2018, 5:05:39.517798 pm UUID: 55204037-6424-0d00-9e5a-3eaa0cba9811 Ancestors: Zinc-HTTP-SvenVanCaekenberghe.473 fix ZnCookie>>#isExpired with expires=0 attribute, so that (ZnCookie name: 'foo' value: '123') expires: '0'; isExpired. returns false. Cookies with missing or bogus expire attribute never expire. Thx Paul De Bruicker === I hope this works for you. Thx, Sven

March 22, 2018

Re: [Pharo-users] Yet another Pharo in docker

by Sean P. DeNigris

Herby VojÄÃk wrote > if you still find this docker useful, should > I add you as contributor in dockerhub and write access in git so you > could make builds for 70 Sure, can't hurt. Thanks. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 22, 2018

Re: [Pharo-users] Problem setting up Tide demo - pls. Instructions for manual labor, identify culprit?

by Herbert VojÄÃk

Well, this probably needs talking. Best approach to running with current Amber is indeed "use new project. move old source by hand". In fact, it is not that bad as it looks, as many things work as they should. But if anything does not, it would need an exchange of errors from console, current state of files etc. to pinpoint it. Why didn't you join the amber chat, that would be ideal platform to clear things up one issue at a time? Re: I would like to start from tide ... if it contains old code, it would probably be better to replace its seed with new working one. IMNSHO. Actually. Amber is just a library accompanied with tools to ease its integration (`amber init`, `grunt devel`, etc.) but in pronciple, it is just an AMD library, so if you are familiar with JS ecosystem, you could just look into index.html, Gruntfile.js and a few other places maybe to get how it is stitched together (and understand what the tide configuration wanted to achieve). I actually don't know what was tide's approach, but I hope it did not try to deviate very much from the "canonical" way project was structured by `amber init` at the time - the "problem" is, this configuration/setup thing has changed since. If it actually generates "pre-setup" project of its own (tailored to how things were back then), it would be best as I already told to make it produce modern version of the same. But I don't know if that is the case.`fg Nevertheless, this is probably better solved in chat by exchanging error outputs etc. and finding what's wrong. But, I would repeat, I'd go for "start from new project, move tide into it". From what you posted so far, it seems the only files that are owned by project are a few tide packages in "tide" namespace; otherwise everything else is a dependency. So move .st files into new project, update Gruntfile.js to properly list them in all needed places, run `grunt` to compile, and index.html should be loadable including everything. If something's wrong, either `grunt` spews some error, or the browser console has them when loading fails. Herby in_pharo_users(a)nym.hush.com wrote: > Hi Esteban, hi Herbert, > > On 22.3.2018 at 12:07 AM, herby(a)mailbox.sk wrote: >> [...] >> So if tide indeed fills fs with all the needed pieces so it then only > needs a few 'load deps' steps, then >> make it work by hand, then > ^^^^^^^^^^^^^^^^^^^^^^^^^^ >> simply remove all transient pieces (node_modules/, bower_components/, > config.js, src/*.js) and you have nice new state >> in which it should all start. > > I would really like to. But how can I even identify what is needed or > missing? > > I do know little bout the inner workings of Amber. > > I can only see that I cannot find some Amber side components used by > Tide's demo page. > > I do not even know if these still exist in the newest Amber tags, or > need to be replaced or reconstructed... > > ************ > --> Can you give me a direction of how to make it work by hand? > ************ > > > The only way I could emagine from my state of knowledge would be to > integrate the existing Amber > side Tide components into a new Amber instance, modifying them along the > way according to possible > changes in Amber. Quite a tedious approach, especially as nothing > Tide-ish is supposed to be working at start. > > >> You should then update the old tide seed file tree with the new > updated one. > > I would really prefer to use the original working configuration as a > base line > initially and then go for subsequent Amber and Pharo updates. > > When I follow the Tide installation instructions, the result should be a > working base line but it does not work. > > Who is the culprit? > > Is there an error in Tide, esp. the demo page, > is the Tide seed file tree etc. kaputt, or > does bower deliver a wrong configuration (possibly result of the move > from git to LOL) or > something else? > > ************ > Is there a way to restore the configuration that Tide requests? > Or is Tide in an inconsitent state? > Why does it not work? > ************ > > > > > > > > On 22.3.2018 at 12:07 AM, herby(a)mailbox.sk wrote: > > On March 21, 2018 11:18:42 PM GMT+01:00, in_pharo_users(a)nym.hush.com > wrote: > >Hi Esteban, hi Herbert, > > > >so, formally, it is a Tide integration issue now, IMHO. > > > >As I understand it now: > > > >Tide's setup procedure generates a file system out of a Monticello > >archive > >and puts Tide related extensions for Amber in it. Then the user is > >directed to that fs's root > >to install Amber. (That seems a little odd, as these extensions are to > >be integrated > >in the Amber image and seem to have a stonger adhesion there.) > > > >The part of the procedure to install Tide is now invalid relating to > >Amber. > > > >Should I try the following: > > > >*** > > > >I have a brand new allmost perfectly working Amber installation. > > > >I scavenge the elements mentioned by Herbert below and move them to > >the Tide stub, > >instead of using the Tide/Monticello generated 'bower install' script. > > No, if Tide's approach is to generate a skeleton which only needs to > get dependencies, then it is very reasonable approach indeed. > > The 'amber init' command actually does the same: fills fs from > template then runs 'npm install' to get tooling, 'bower install' to > get project dependencies, including amber itself, 'grunt' to compile > .st files into .js files and 'grunt devel' to set up environment to > development mode loader. > > 'That seems a little odd, as these extensions are to be integrated > in the Amber image' not odd at all as there is no true image - that > whole filetree is 'the source for the image build' and actual > 'image' only exists at runtime by loading all components into > memory. Amber is just another library to load. > > So if tide indeed fills fs with all the needed pieces so it then > only needs a few 'load deps' steps, then make it work by hand, then > simply remove all transient pieces (node_modules/, > bower_components/, config.js, src/*.js) and you have nice new state > in which it should all start. > > You should then update the old tide seed file tree with the new > updated one. > > >Then run 'grunt devel'. > >Is this all I need? > > > >Is there a way to explicitly describe the objects I need? > >Or is there a way to check what exactly is missing? > > > >*** > > > >But would it not be a better approach to update the Tide setup > >procedure? > >How would that work? > >Kind regards, > > > >basket > >On 21.3.2018 at 9:54 PM, "Herbert VojÄÃk" wrote:In newer version of > >Amber the loading code changed significantly, as > >promises are used (best way to migrate old code is to actually created > > > >new project using `amber init` and only move the needed pieces > >(src/*.st > >files, .amd.json files, lists of packages in deploy.js / testing.js / > >devel.js / Gruntfile.js) to the new structure). > > > >Also "searched in bower path" is wrong, paths are mapped differently, > >using .amd.json files (which I think are set correctly), but of > >course, > >`grunt devel` must be run at least once for mapping to happen (it is > >run > >as part of `amber init`, so new project is set up fine; but in case > >.amd.json files are changed, it should be rerun). > > > >Herby > > > >in_pharo_users(a)nym.hush.com wrote: > > > Hi Esteban, > > > > > > after I got Amber running separately, I set up Tide according to > > > > > > https://github.com/tide-framework/tide > > > ; readme.md > > > > > > Everything went fine so far, but after the page loaded, Helios did > >not > > > pop. Blank page. > > > > > > So I looked into the page source and, suspiciously, at line 18 I > >found > > > > > > **** > > > > > > require( > > > [ > > > "amber/devel", > > > "amber/helpers", > > > "tide/Tide-Amber-Core", > > > "tide/Tide-Amber-Exceptions", > > > "tide/Tide-Amber-Examples", > > > "tide/Tide-Amber-Tests" > > > ], > > > function (smalltalk) { > > > smalltalk.initialize({defaultAmdNamespace: 'tide'}); > > > smalltalk.popupHelios(); > > > } > > > **** > > > > > > I searched for all required paths in the bower path, but could not > >find only the first two. > > > > > > Can you kindly give me a hint how to proceed to get it running? > > > > > > Kind regards, > > > > > > basket > > > >

March 22, 2018

Re: [Pharo-users] RTDoubleScrollBar is not rendered properly in html

by Alexandre Bergel

Hi! Scroll bar are not exportable to HTML, as benefits in doing so are not really apparent. What would be the ideal behavior? Will removing scrollbars when exporting to HTML sufficient for your need? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 22, 2018, at 11:20 AM, Andrei Stebakov <lispercat(a)gmail.com> wrote: > > When I do > v @ RTDoubleScrollBar. > and then export to HTML > the bars are rendered in the middle of HTML page and they don't actually scroll. > I checked in in Chrome and IE on windows. Could you guys take a look?

March 22, 2018

Re: [Pharo-users] Issues with recent Pharos reading files

by Stephane Ducasse

Hi andrew do you have a reproducible case? or a stackk trace? Stef On Wed, Mar 21, 2018 at 10:50 PM, Andrew P. Black <apblack(a)pdx.edu> wrote: > >> On 20 Mar 2018, at 23:01 , Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> @Andrew, about the directories issue, can you provide me a full stack trace and even better a way to reproduce it? > > I sent a lengthy message in this thread explaining the circumstances. Is that enough? If not I can try opening a file many times and see if I can reproduce the breaking of the primitive. Iâm pretty sure thatâs what was happening (many hours of debugging on an aeroplane), but did not try to recreate the problem â I was just glad to be able to fix it and move on with my work. > > And my battery was dead. 9 hours on a B 737-200 with no power :-(. Pharo eats batteries for breakfast, lunch and dinner! > > Andrew > >

March 22, 2018

Re: [Pharo-users] Problem setting up Tide demo - pls. Instructions for manual labor, identify culprit?

by in_pharo_users＠nym.hush.com

Hi Esteban, hi Herbert, On 22.3.2018 at 12:07 AM, herby(a)mailbox.sk wrote: > [...] > So if tide indeed fills fs with all the needed pieces so it then only needs a few 'load deps' steps, then > make it work by hand, then ^^^^^^^^^^^^^^^^^^^^^^^^^^ > simply remove all transient pieces (node_modules/, bower_components/, config.js, src/*.js) and you have nice new state > in which it should all start. I would really like to. But how can I even identify what is needed or missing? I do know little bout the inner workings of Amber. I can only see that I cannot find some Amber side components used by Tide's demo page. I do not even know if these still exist in the newest Amber tags, or need to be replaced or reconstructed... ************ --> Can you give me a direction of how to make it work by hand? ************ The only way I could emagine from my state of knowledge would be to integrate the existing Amber side Tide components into a new Amber instance, modifying them along the way according to possible changes in Amber. Quite a tedious approach, especially as nothing Tide-ish is supposed to be working at start. > You should then update the old tide seed file tree with the new updated one. I would really prefer to use the original working configuration as a base line initially and then go for subsequent Amber and Pharo updates. When I follow the Tide installation instructions, the result should be a working base line but it does not work. Who is the culprit? Is there an error in Tide, esp. the demo page, is the Tide seed file tree etc. kaputt, or does bower deliver a wrong configuration (possibly result of the move from git to LOL) or something else? ************ Is there a way to restore the configuration that Tide requests? Or is Tide in an inconsitent state? Why does it not work? ************ On 22.3.2018 at 12:07 AM, herby(a)mailbox.sk wrote:On March 21, 2018 11:18:42 PM GMT+01:00, in_pharo_users(a)nym.hush.com wrote: >Hi Esteban, hi Herbert, > >so, formally, it is a Tide integration issue now, IMHO. > >As I understand it now: > >Tide's setup procedure generates a file system out of a Monticello >archive >and puts Tide related extensions for Amber in it. Then the user is >directed to that fs's root >to install Amber. (That seems a little odd, as these extensions are to >be integrated >in the Amber image and seem to have a stonger adhesion there.) > >The part of the procedure to install Tide is now invalid relating to >Amber. > >Should I try the following: > >*** > >I have a brand new allmost perfectly working Amber installation. > >I scavenge the elements mentioned by Herbert below and move them to >the Tide stub, >instead of using the Tide/Monticello generated 'bower install' script. No, if Tide's approach is to generate a skeleton which only needs to get dependencies, then it is very reasonable approach indeed. The 'amber init' command actually does the same: fills fs from template then runs 'npm install' to get tooling, 'bower install' to get project dependencies, including amber itself, 'grunt' to compile .st files into .js files and 'grunt devel' to set up environment to development mode loader. 'That seems a little odd, as these extensions are to be integrated in the Amber image' not odd at all as there is no true image - that whole filetree is 'the source for the image build' and actual 'image' only exists at runtime by loading all components into memory. Amber is just another library to load. So if tide indeed fills fs with all the needed pieces so it then only needs a few 'load deps' steps, then make it work by hand, then simply remove all transient pieces (node_modules/, bower_components/, config.js, src/*.js) and you have nice new state in which it should all start. You should then update the old tide seed file tree with the new updated one. >Then run 'grunt devel'. >Is this all I need? > >Is there a way to explicitly describe the objects I need? >Or is there a way to check what exactly is missing? > >*** > >But would it not be a better approach to update the Tide setup >procedure? >How would that work? >Kind regards, > >basket >On 21.3.2018 at 9:54 PM, "Herbert VojÄÃk" wrote:In newer version of >Amber the loading code changed significantly, as >promises are used (best way to migrate old code is to actually created > >new project using `amber init` and only move the needed pieces >(src/*.st >files, .amd.json files, lists of packages in deploy.js / testing.js / >devel.js / Gruntfile.js) to the new structure). > >Also "searched in bower path" is wrong, paths are mapped differently, >using .amd.json files (which I think are set correctly), but of >course, >`grunt devel` must be run at least once for mapping to happen (it is >run >as part of `amber init`, so new project is set up fine; but in case >.amd.json files are changed, it should be rerun). > >Herby > >in_pharo_users(a)nym.hush.com wrote: >> Hi Esteban, >> >> after I got Amber running separately, I set up Tide according to >> >> https://github.com/tide-framework/tide >> ; readme.md >> >> Everything went fine so far, but after the page loaded, Helios did >not >> pop. Blank page. >> >> So I looked into the page source and, suspiciously, at line 18 I >found >> >> **** >> >> require( >> [ >> "amber/devel", >> "amber/helpers", >> "tide/Tide-Amber-Core", >> "tide/Tide-Amber-Exceptions", >> "tide/Tide-Amber-Examples", >> "tide/Tide-Amber-Tests" >> ], >> function (smalltalk) { >> smalltalk.initialize({defaultAmdNamespace: 'tide'}); >> smalltalk.popupHelios(); >> } >> **** >> >> I searched for all required paths in the bower path, but could not >find only the first two. >> >> Can you kindly give me a hint how to proceed to get it running? >> >> Kind regards, >> >> basket >>

March 22, 2018

Re: [Pharo-users] Commits Using Iceberg

by Asbath

Okay, I am on 64 bits. On 22/03/2018 10:00, Guillermo Polito wrote: > Hi Asbath, are you in 32 or 64 bits? > > We've seen problems in Pharo 6.1 64bits using iceberg while calling > external libraries. > > On Thu, Mar 22, 2018 at 9:15 AM, Asbath via Pharo-users > <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote: > > > > ---------- Forwarded message ---------- > From:Â Asbath <asamabiyalou(a)yahoo.com <mailto:asamabiyalou@yahoo.com>> > To: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> > Cc: > Bcc: > Date:Â Thu, 22 Mar 2018 09:15:14 +0100 > Subject:Â Commits Using Iceberg > Hi everybody, > > I am using Iceberg on Pharo 6. My OS is Ubuntu 16.04. > > When I try to commit my local changes on the remote branch, the > Pharo Image is closed, when I click on Commit and Push (after > providing the comment). Those commits are registered, but not > published. > > I don't know what is the matter !? > > > Thanks, have a nice day > > > Asbath > > > > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - _http://www.cnrs.fr_ > > > *Web:* _http://guillep.github.io_ > > *Phone: *+33 06 52 70 66 13 >

March 22, 2018

RTDoubleScrollBar is not rendered properly in html

by Andrei Stebakov

When I do v @ RTDoubleScrollBar. and then export to HTML the bars are rendered in the middle of HTML page and they don't actually scroll. I checked in in Chrome and IE on windows. Could you guys take a look?

March 22, 2018

Re: [Pharo-users] Yet another Pharo in docker

by Norbert Hartl

Me, too. Sadly I donât find time to prepare that properly. Thinks to consider are as always desktop and server environments. As I can see and Herby is tweaking DISPLAY variables, his approach is used to start a pharo inside a docker container but have the display opened on the host computer. What I use is a docker container that has a vm installed, you give it an image and the container is usable in a standalone fashion everywhere. Both are useful and should be considered when choosing names for the docker images. We should create an organization at hub.docker.com <http://hub.docker.com/> for pharo. It would be best to have an offical organisation here but the effort is a little bigger to achieve this. I wanted to do it but time is really sparse right now. Additionally we need to come to a conclusion what vm to use. We put quite some effort to get a process of producing real linux packages for distribution. Sadly the vm building process is not ready for making it part of this process so this lacks behing which means the vms of the opensuse build service are not up-to-date. If the process of the vm is fixed this can be an automatic process to release linux packages automatically if there is no vm version. So at first we could use a zeroconf downloaded vm inside a pharo image and hopefully later this can be exchanged by the linux ones. The github repo for the docker files already exists in https://github.com/pharo-project/pharo-docker <https://github.com/pharo-project/pharo-docker> If there is a coordination initiative for docker please include me! Norbert > Am 22.03.2018 um 09:48 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > > Hi, > > I would like to coordinate to have something official in April. > > Marcus > >> On 21 Mar 2018, at 18:32, Herbert VojÄÃk <herby(a)mailbox.sk> wrote: >> >> BTW, Sean (or anyone else), if you still find this docker useful, should I add you as contributor in dockerhub and write access in git so you could make builds for 70 (I do not use 70, so not knowing when is it the good point to make new build). Or is there some ETA to official one built from Pharo jenkins itself? >> >> Herby >> >> Herbert VojÄÃk wrote: >>> >>> >>> Herbert VojÄÃk wrote: >>>> >>>> >>>> Sean P. DeNigris wrote: >>>>> Sean P. DeNigris wrote >>>>>>> https://hub.docker.com/r/herbysk/pharo/ >>>>>> How are the images built from https://lolg.it/herby/pharo-docker? >>>>> >>>>> Researching a bit it seems that Docker Hub only supports GitHub and >>>>> BitBucket, and IIUC you can't change the image name if you use >>>>> automated >>>>> building. Therefore, I assume you're going something custom. Is it >>>>> manual? >>>> >>>> Manual. I actually replied to original question, but mail got stuck in >>>> moderation b/c it has empty subject or something. >>>> >>>> Whenever I see there is significant change / the project needs to have >>>> the new changes in, I rebuild and reupload manually. >>> >>> Also, I pointed out in that lost mail, I only created this docker out of >>> necessity since there isn't pharo official one. Having official one >>> generated from Jenkins would be nice. >>> >>>> >>>> Herby >>>> >>>>> Or is there a way to set up triggers for a custom solution? Thanks. >>>>> >>>>> >>>>> >>>>> ----- >>>>> Cheers, >>>>> Sean >>>>> -- >>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>>> >>>> >>> >> > >

March 22, 2018