- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] First commit

by Stephane Ducasse

Tx evan! We will have a look and this is great to have a new contributor!!! Stef On Tue, May 2, 2017 at 3:23 AM, Evan Donahue <emdonahu(a)gmail.com> wrote: > Thanks. I have resubmitted and it seems to have worked. If anyone wants to > let me know if it looks like I did everything right, I can hopefully move > on > to tackling other things. > > Thanks, > Evan > > > > -- > View this message in context: http://forum.world.st/First- > commit-tp4944984p4945091.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

May 7, 2017

Re: [Pharo-dev] ./pharo --help returns exit code 1 on ubuntu

by Ben Coman

[CC vm-dev] On Sat, May 6, 2017 at 7:04 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > On Friday 05 May 2017 02:11 PM, Andrei Chis wrote: > >> ... >> ./pharo -help >> unknown option: -help >> Common <option>s: >> --help print this help message, then exit >> >> Then `./pharo -help` returns an exit code of 1 on mac/linux while >> `./pharo --help` returns a exit code of 0 on mac and 1 on linux. >> > > It is --help on Pharo and -help on other compiles (see below). Can anyone > shed light on the legacy compatibility comment in : > > ---- platforms/unix/vm/sqUnixMain.c ---- > 1421 /* legacy compatibility */ /*** XXX to be removed at > some time ***/ > 1422 > Looking just at just the file, it appears this is comment is strongly associated with the code below, but git blame [1] indicates the comment is 7 years old, while the code below is 7 months old. ??? [1] https://github.com/OpenSmalltalk/opensmalltalk-vm/blame/995e7aedc3b5aeb7690… cheers -ben > > 1423 #ifdef PharoVM > 1424 # define VMOPTION(arg) "--"arg > 1425 #else > 1426 # define VMOPTION(arg) "-"arg > 1427 #endif > > It's still not clear why running the vm to print the help of the version >> should exit with an error code. >> > > Agreed. I think --help and --version should return 0. I think the 1 was to > catch incorrect/unknown arguments. > > If I learn the rationale behind the change, I can propose a patch to fix > this. > > Regards .. Subbu > > >

May 7, 2017

Re: [Pharo-dev] Respect Pharo and respect us

by Tudor Girba

+1 Doru > On May 6, 2017, at 12:28 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi guys > > Could we have discussion about ***PHARO*** in the Pharo-dev mailing-list? > Can we get a bit of respect? > Should we create a private dev mailing-list so that we can get our focus? > I start to get bored to have to mute threads. I let you imagine the threads I'm muting. > > In addition, I would really like that you ask yourself when is the last time that you > did something for Pharo if ever. You see doing something for Pharo is as easy as > - removing typo from a book > - adding a comment in a method > - helping a newbie > but often you prefer to talk I know why because this is easy. > > So you do not need to have the perfect X&*^*&^ system to take 10 min of your > great life to HELP (see above) > > Our goal is to build Pharo and we would love other people to help > or at least do not use our bandwidth about other goals. > > So respect Pharo and us. > > Stef > -- www.tudorgirba.com www.feenk.com "We are all great at making mistakes."

May 6, 2017

Iceberg

by Aliaksei Syrel

Hi, It is amazing to see how fast Pharo progresses and moves closer to release. Therefore it may happen that after a week of absence there is so much new stuff that I just loose track of changes and sometimes old behaviour does not correspond new reality and "nothing works" :) Probably it is my case now. I would like to work on a project hosted on github. I tried iceberg:dev-0.4, iceberg:dev-0.5, iceberg-master but didn't succeed.. Here is what I get when try to clone repository both from Playground or by using "+" clone button in Iceberg both dev-04 and dev-05 [image: Inline images 1] If I try to load Iceberg master in the Image I get this: [image: Inline images 2] I am sure I do something wrong, so I recorded three videos - one for every Iceberg version. â Iceberg-0.4.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTLTZvejdYTkNfaWM/view?usp=drive…> ââ Iceberg-0.5.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTbDJNZnJMeUJEYk0/view?usp=drive…> ââ Iceberg-master.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTVzhGQmJOVzN3akU/view?usp=drive…> â VM: pharo-mac-i386-201705051953-b8db6de Image: 60482 OS: macOS Sierra 10.12.4 P.S. Still getting black screen when open an Image until I click... Cheers, Alex

May 6, 2017

Re: [Pharo-dev] [Zinc] How do I set the entry limit for ZnMultiValueDictionary?

by Max Leske

> > On 5 May 2017, at 17:11, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Max, > >> On 5 May 2017, at 16:59, Max Leske <maxleske(a)gmail.com> wrote: >> >> Hi, >> >> I'm performing a legal request that has more than 4000 parameters. This causes the Zinc server to return 400: Bad Request because ZnMultiValueDictionary is limited to 256 entries by default. >> >> The dictionary has the option to remove the limit or to adjust it with a dynamic variable. Unfortunately, I don't see any way to properly configure this without monkey patching Zinc. Ideally, I'd like to remove the limit (which can't be done through the dynamic variable by the way because when the dynamic variable answers nil, the default will be set to 256). >> >> The first thing that comes to mind is to move this setting to ZnConstants, but then I don't see any way to configure ZnConstants either (ZnConstants is referenced directly by its users). Maybe ZnConstants could be changed to hold a concrete constants class (itself by default). >> >> In any case, I think this setting should be configurable and the configuration should be possible through one single entry point, together with options like #codec. >> >> Thoughts? >> >> Cheers, >> Max > > You are the first one to complain about this limit. > > This one and other resource limits exist to protect the client/server against abuse and attacks. I'm aware of that but have not other way to do this right now. We have mod_security with a higher value configured for that. > > I think what is needed is something like ZnServer>>#withMaximumEntitySizeDo: which uses the server option #maximumEntitySize. Would that work for you, you think ? Yes, it would. I've implemented the change, closely following the semantics of #withMaximumEntitySizeDo:. While I was working on that I discovered another problem I had which I also fixed by dispatching to ZnConstants. The problem being, that I set the codec on the server to GRNullCodec, but ZnPercentEncoder would still always use a ZnUTF8Encoder to decode requests. The result was an error when the server tried to write wide strings onto the stream (usually ZnUTF8Encoder: UTF-8 -> WideString, GRPharoUtf8Codec: WideString -> UTF-8). I've attached the patches. A couple of notes: - #defaultMaximumNumberOfDictionaryEntries and #maximumDictionaryEntries: have the same implementation, which is unnecessary in my opinion but I've copied the code from #maximumEntitySize:. - I'm not sure whether storing the option a second time on ZnServer makes sense, but, again, I stuck to the existing implementation - #withMaximumNumberOfDictionaryEntriesDo: also checks the dynamic variable, which is overkill I think, as ZnConstants does the same thing. Again, I stuck to the existing implementation (which means that ZnConstants is actually thread agnostic and references to dynamic variables should probably all be on ZnConstants) Cheers, Max > > Sven > > >

May 6, 2017

Re: [Pharo-dev] Anyone meeting up night before Pharo Days (17th?)

by Yuriy Tymchuk

Hey Tim, Iâm going to arrive in Lille on May 17 and I was just about to ask if someone wants to have a beer/dinner that day in the evening :). Cheers. Uko > On 6 May 2017, at 13:21, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Tim thursday evening we go to a nice restaurant downtown. > In any case this is better to have a n hotel downtown ;) > > On Sat, May 6, 2017 at 12:58 PM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: > Hi guys - I managed to get a âweeknight passâ so that I can come to Pharo days and try and catch up with all the progress you have made. > > Iâm taking a Eurostar on Wed night (17th) and wondering if anyone is meeting up the night before on the 17th? I donât arrive until 8:30 - but maybe some of you are having some post supper drinks somewhere? > > I have booked a hotel near the venue, but Iâm thinking that I may change it, to somewhere in town as I think it might make more sense as Iâm sure folks may end up eating in town anyway. > > > Tim >

May 6, 2017

Re: [Pharo-dev] Anyone meeting up night before Pharo Days (17th?)

by Stephane Ducasse

Tim thursday evening we go to a nice restaurant downtown. In any case this is better to have a n hotel downtown ;) On Sat, May 6, 2017 at 12:58 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Hi guys - I managed to get a âweeknight passâ so that I can come to Pharo > days and try and catch up with all the progress you have made. > > Iâm taking a Eurostar on Wed night (17th) and wondering if anyone is > meeting up the night before on the 17th? I donât arrive until 8:30 - but > maybe some of you are having some post supper drinks somewhere? > > I have booked a hotel near the venue, but Iâm thinking that I may change > it, to somewhere in town as I think it might make more sense as Iâm sure > folks may end up eating in town anyway. > > > Tim >

May 6, 2017

Re: [Pharo-dev] ./pharo --help returns exit code 1 on ubuntu

by K K Subbu

On Friday 05 May 2017 02:11 PM, Andrei Chis wrote: > ... > ./pharo -help > unknown option: -help > Common <option>s: > --help print this help message, then exit > > Then `./pharo -help` returns an exit code of 1 on mac/linux while > `./pharo --help` returns a exit code of 0 on mac and 1 on linux. It is --help on Pharo and -help on other compiles (see below). Can anyone shed light on the legacy compatibility comment in : ---- platforms/unix/vm/sqUnixMain.c ---- 1421 /* legacy compatibility */ /*** XXX to be removed at some time ***/ 1422 1423 #ifdef PharoVM 1424 # define VMOPTION(arg) "--"arg 1425 #else 1426 # define VMOPTION(arg) "-"arg 1427 #endif > It's still not clear why running the vm to print the help of the version > should exit with an error code. Agreed. I think --help and --version should return 0. I think the 1 was to catch incorrect/unknown arguments. If I learn the rationale behind the change, I can propose a patch to fix this. Regards .. Subbu

May 6, 2017

Anyone meeting up night before Pharo Days (17th?)

by Tim Mackinnon

Hi guys - I managed to get a âweeknight passâ so that I can come to Pharo days and try and catch up with all the progress you have made. Iâm taking a Eurostar on Wed night (17th) and wondering if anyone is meeting up the night before on the 17th? I donât arrive until 8:30 - but maybe some of you are having some post supper drinks somewhere? I have booked a hotel near the venue, but Iâm thinking that I may change it, to somewhere in town as I think it might make more sense as Iâm sure folks may end up eating in town anyway. Tim

May 6, 2017

Re: [Pharo-dev] Pharo booklet collection

by Stephane Ducasse

Hi phil yes I loved this idea. We got burned by that too. About pillar. The departure of Damien was not expected and it slows us quite a bit. We (mainly me helped with maxime) are working on - making the pillar core nicer - less dependencies - and with a small in image renderer :) We had fun with guille - In the pharo 60 version I started to clean the command-line. - merged many unmerged changes. But even with all the tests it is not easy.... I'm testing in addition with reall - book production - slides - html But it takes time and energy. I'm trying to remove the dependencies to magritte for example. Stef [image: Inline image 1] On Sat, May 6, 2017 at 9:30 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > For books, there is the docker-texlive thing from Damien that we > looked into yesterday because TexLive was giving some headaches. > > https://github.com/philippeback/docker-texlive > > has my current thing for one to build a container with all > prerequisites for TexLive and Pharo installed. > > Idea is to clone the book repo on the host and get into an container > to build the book. > > There is a /work volume that can be mapped onto the host with the > docker run's -v command. > > Then just use ./download.sh in there to install Pharo and pillar in > the container. Do not do that in the host or you'll end up with wrong > versions (like my host is CentOS and the container is Ubuntu, even > worse with host is macOS or Windows). > > Then "make book" should give a book in build/ > There is a "make wipeout" command that obliterates the build folder > for good so you can start clean. No harm done on your files. > > Will document more of this but woul dbe nice if someone could check > this out too. > > There is a script in base/ to build the docker image. > > Phil > > On Sat, May 6, 2017 at 9:20 AM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: > > I fixed it. > > The code for the web site in on github. > > > > Stef > > > > On Tue, May 2, 2017 at 10:32 PM, Esteban A. Maringolo < > emaringolo(a)gmail.com> > > wrote: > >> > >> Correct link seems to be > >> > >> > >> http://files.pharo.org/books-pdfs/booklet-Glorp/2017-05-02- > Glorp.spiral.pdf > >> Esteban A. Maringolo > >> > >> > >> 2017-05-02 17:28 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> > link for glorp gives smacc book error > >> > > >> > On Tue, May 2, 2017 at 10:25 PM, Stephane Ducasse > >> > <stepharo.self(a)gmail.com> > >> > wrote: > >> >> > >> >> Hi Pharoers > >> >> > >> >> You are lucky. The "Pharo booklet collection" edited by S. Ducasse is > >> >> arriving... > >> >> > >> >> Are you ready to read nice and focused booklets? > >> >> > >> >> You can find at http://files.pharo.org/books/ in beta version: > >> >> > >> >> Smacc: the Smalltalk Compiler Compiler by J. Brant, T. Goubier, J. > >> >> Lecerf > >> >> and S. Ducasse. > >> >> Glorp: the Object Relational Mapper framework by E. Maringolo, N. > Pratt > >> >> and R. Withney > >> >> > >> >> All the book material is hosted on > >> >> https://github.com/SquareBracketAssociates so you can contribute! > Fix > >> >> typos > >> >> and propose new material. > >> >> > >> >> We are planning a booklet on Magritte, Reddit in 10 cool classes, > >> >> Voyage, > >> >> and Mocking with BabyMock and Mocketry, XML (but we need a writer) > and > >> >> potentially PetitParser. > >> >> > >> >> If you have material for a tutorial and you would like to be part of > >> >> the > >> >> Pharo Booklet Collection contact S. Ducasse. > >> >> > >> >> S. Ducasse > >> > > >> > > >> > > > >

May 6, 2017