July 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo 64bit planned?

by Eliot Miranda

Hi David, On Fri, Jul 17, 2015 at 3:22 PM, David <stormbyte(a)gmail.com> wrote: > I did not see any progress over the time in making a (stable) release > of pharo in 64 bit flavor. > > For servers, it is a common practice (and also a good one if no 32bit > executables are planned) to completelly disable 32bit support (by not > compiling any library in 32bit, disabling emulation of 32bit in > kernel), and also performance, as under 64bit, 32bit code runs slightly > slower. > > The above make enough reasons to make it interesting to have a 64bit > version of pharo, but... Is it intended/in progress? Or nothing really > at the moment? > 64-bit development of Spur is in progress. There is a somewhat functional 64-bit Squeak Spur image and a functional Linux 64-bit Stack interpreter. Coincidentally I'm currently working on an input event processing bug which only occurs in the real VM. You may know that the next release of Pharo (Pharo 6?) is intended to be a Spur release. Esteban Lorenzano is working on the Pharo Spur bootstrap. I am working in Squeak and my priorities are first, to get the Spur Squeak 64-bit image working fully on the Stack Interpreter and then to work on an x64 JIT VM. I expect that by the time Pharo 6 is ready to release, the 64-bit version will also be ready. Hope this helps. -- _,,,^..^,,,_ best, Eliot

July 17, 2015

Pharo 64bit planned?

by David

I did not see any progress over the time in making a (stable) release of pharo in 64 bit flavor. For servers, it is a common practice (and also a good one if no 32bit executables are planned) to completelly disable 32bit support (by not compiling any library in 32bit, disabling emulation of 32bit in kernel), and also performance, as under 64bit, 32bit code runs slightly slower. The above make enough reasons to make it interesting to have a 64bit version of pharo, but... Is it intended/in progress? Or nothing really at the moment?

July 17, 2015

Re: [Pharo-dev] Tiling Window Manager: Enable on load

by phil＠highoctane.be

I use both. Le 17 juil. 2015 21:55, "Sean P. DeNigris" <sean(a)clipperadams.com> a Ã©crit : > laurent laffont wrote > > And hide the taskbar too ? > > I guess that makes sense since there is a window list in the TWM bar. Your > call... > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Tiling-Window-Manager-Enable-on-load-tp4837513p483800… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

July 17, 2015

Re: [Pharo-dev] [Pharo-users] Searching for similiar projects

by Sean P. DeNigris

Jigyasa Grover wrote > Yes, I tried removing '?' from the file name but the signal is still red. Same color, different reason :) Check the error logs and you will see that the git repo gets cloned but there is a different error afterward https://ci.inria.fr/pharo-contribution/job/sQuick/11/PHARO=40,VERSION=stabl… ----- Cheers, Sean -- View this message in context: http://forum.world.st/Searching-for-similiar-projects-tp4837427p4838004.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2015

What happend to my smalltalkhub project?

by Nicolai Hess

I had at least one project at smalltalk hub NicolaiHess/AthensSketch But now, I don't see any project, no watchlist and the list of activities only lists the last three weeks. ? nicolai

July 17, 2015

Re: [Pharo-dev] Tiling Window Manager: Enable on load

by Sean P. DeNigris

laurent laffont wrote > And hide the taskbar too ? I guess that makes sense since there is a window list in the TWM bar. Your call... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Tiling-Window-Manager-Enable-on-load-tp4837513p483800… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2015

Re: [Pharo-dev] Bloc borders

by Aliaksei Syrel

Sorry, I meant BlRoundedRectangleView has solid by default - because of corner radius. It's kind of specific case. I use mainly rounded rectangle view. Cheers, Alex On Fri, Jul 17, 2015 at 9:46 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi Stephan, > > Could be. Rectangle view has solid border as border style by default. > There are two ways: make sure that all views has null border by default or > make sure all borders are invisible (width=0, color=transparent) by > default. The only issue is that the solid border is the most used border > type, so there is no actual need to force users each time set it manually. > So, would you prefear to have first or second option? > > Cheers, > Alex > On Jul 17, 2015 8:17 PM, "Stephan Eggermont" <stephan(a)stack.nl> wrote: > >> Hi Alex, Alain >> >> >Name: Bloc-Core-AliakseiSyrel.608 >> >Author: AliakseiSyrel >> >Time: 17 July 2015, 6:07:03.160521 pm >> >UUID: ab99af8c-7bce-4c4d-bd92-319fe33c0f51 >> >Ancestors: Bloc-Core-AlainPlantec.607 >> > >> >set default color of solid border to transparent, otherwise all >widgets >> have visible border by default >> >> Uhm, isn't that exactly what is supposed to happen? >> A solid border is supposed to be visible by default. >> If you don't want a border, don't add one? >> The default border style is BlNullRectanglerBorder >> >> Stephan >> >> >> >> >>

July 17, 2015

Re: [Pharo-dev] Bloc borders

by Aliaksei Syrel

Hi Stephan, Could be. Rectangle view has solid border as border style by default. There are two ways: make sure that all views has null border by default or make sure all borders are invisible (width=0, color=transparent) by default. The only issue is that the solid border is the most used border type, so there is no actual need to force users each time set it manually. So, would you prefear to have first or second option? Cheers, Alex On Jul 17, 2015 8:17 PM, "Stephan Eggermont" <stephan(a)stack.nl> wrote: > Hi Alex, Alain > > >Name: Bloc-Core-AliakseiSyrel.608 > >Author: AliakseiSyrel > >Time: 17 July 2015, 6:07:03.160521 pm > >UUID: ab99af8c-7bce-4c4d-bd92-319fe33c0f51 > >Ancestors: Bloc-Core-AlainPlantec.607 > > > >set default color of solid border to transparent, otherwise all >widgets > have visible border by default > > Uhm, isn't that exactly what is supposed to happen? > A solid border is supposed to be visible by default. > If you don't want a border, don't add one? > The default border style is BlNullRectanglerBorder > > Stephan > > > > >

July 17, 2015

Bloc borders

by Stephan Eggermont

Hi Alex, Alain >Name: Bloc-Core-AliakseiSyrel.608 >Author: AliakseiSyrel >Time: 17 July 2015, 6:07:03.160521 pm >UUID: ab99af8c-7bce-4c4d-bd92-319fe33c0f51 >Ancestors: Bloc-Core-AlainPlantec.607 > >set default color of solid border to transparent, otherwise all >widgets have visible border by default Uhm, isn't that exactly what is supposed to happen? A solid border is supposed to be visible by default. If you don't want a border, don't add one? The default border style is BlNullRectanglerBorder Stephan

July 17, 2015

Re: [Pharo-dev] Comments in STON

by Sven Van Caekenberghe

> On 16 Jul 2015, at 21:28, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Guille, > > I understand the problem. > > The reason is that STONCStyleCommentsSkipStream was/is a quick hack and does not know/understand anything about strings. > > It seems that the C preprocessor ignores comments in C strings, so we could consider adding that. > > Basically STONCStyleCommentsSkipStream>>#nextNonCommentChar should know when it is inside a string and then ignore comments. But that means, in the case of STON/JSON, handling both ' (single) and " (double) quoted strings as well as interpret \' and \". All this should be doable, but it is not that easy to do elegantly. I'll see what I can do. === Name: STON-Core-SvenVanCaekenberghe.62 Author: SvenVanCaekenberghe Time: 17 July 2015, 7:50:06.278051 pm UUID: 949e54c8-9da8-4e91-ab44-55105bff349c Ancestors: STON-Core-SvenVanCaekenberghe.61 Added new STONCStyleCommentsSkipStream feature: Comments inside single and double quote delimited strings are ignored. Backslash escapes for single and double quotes inside strings are honored. === Name: STON-Tests-SvenVanCaekenberghe.57 Author: SvenVanCaekenberghe Time: 17 July 2015, 7:50:38.683873 pm UUID: ad125293-a41b-45a6-a0fe-016dd5e02f7b Ancestors: STON-Tests-SvenVanCaekenberghe.56 Added new STONCStyleCommentsSkipStream feature: Comments inside single and double quote delimited strings are ignored. Backslash escapes for single and double quotes inside strings are honored. === Now you can do: testCommentInString self assert: (STONCStyleCommentsSkipStream on: '''/*comment*/''' readStream) upToEnd equals: '''/*comment*/'''. self assert: (STONCStyleCommentsSkipStream on: '{''foo'':''/*comment*/bar''}' readStream) upToEnd equals: '{''foo'':''/*comment*/bar''}'. self assert: (STONCStyleCommentsSkipStream on: '{''foo'':''//comment\''bar''}' readStream) upToEnd equals: '{''foo'':''//comment\''bar''}'. self assert: (STONCStyleCommentsSkipStream on: '{"foo":"/*comment*/bar"}' readStream) upToEnd equals: '{"foo":"/*comment*/bar"}'. self assert: (STONCStyleCommentsSkipStream on: '{"foo":"//comment\"bar"}' readStream) upToEnd equals: '{"foo":"//comment\"bar"}' > Sven > >> On 16 Jul 2015, at 17:35, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> Hi Sven! >> >> I'm finally using the new STON with comments and I found one little problem: my ston file has urls :/ >> >> { >> // comment ok, skipped >> /* comment ok, skipped */ >> "aURL": "http://ouch.it.will.be.skipped/and/break?my=ston" >> } >> >> That is, doing: >> >> STON fromStreamWithComments: '{ >> // comment ok, skipped >> /* comment ok, skipped */ >> "aURL": "http://ouch.it.will.be.skipped/and/break?my=ston" >> }' readStream >> >> Will fail with an invalid input error because after skipping comments my STON stream remains like >> >> STON fromStreamWithComments: '{ >> "aURL": "http: >> } >> >> Any thoughts? >> Guille >> >> El dom., 14 de jun. de 2015 a la(s) 3:06 a. m., stepharo <stepharo(a)free.fr> escribiÃ³: >> >> >> Le 10/6/15 20:39, Sven Van Caekenberghe a Ã©crit : >>>> On 10 Jun 2015, at 15:13, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> This is in the entreprise book. I added a subsection on comments. >>>> May be I committed but forgot to push. >>>> Now I did it. >>> And now I see it. >>> I made a small change. >> super! >> >>> >>>> Stef >>>> >>>> >>>> Le 9/6/15 21:50, Sven Van Caekenberghe a Ã©crit : >>>>> Where exactly can I find what you changed ? >>>>> I don't see any commit of you on github ... >>>>> >>>>>> On 09 Jun 2015, at 20:10, stepharo <stepharo(a)free.fr> wrote: >>>>>> >>>>>> >>>>>> >>>>>> Le 9/6/15 20:06, stepharo a Ã©crit : >>>>>>> I will update the STON chapter :) >>>>>> Done :) >>>>>> >>>>>>> Le 8/6/15 23:39, Sven Van Caekenberghe a Ã©crit : >>>>>>>> I would do it like this: use a wrapping stream to skip comments. >>>>>>>> >>>>>>>> === >>>>>>>> Name: STON-Core-SvenVanCaekenberghe.59 >>>>>>>> Author: SvenVanCaekenberghe >>>>>>>> Time: 8 June 2015, 11:34:32.886167 pm >>>>>>>> UUID: 7ab942b5-9d1a-44c3-9d58-da29feb72380 >>>>>>>> Ancestors: STON-Core-SvenVanCaekenberghe.58 >>>>>>>> >>>>>>>> Add experimental STONCStyleCommentsSkipStream and tests >>>>>>>> === >>>>>>>> Name: STON-Tests-SvenVanCaekenberghe.54 >>>>>>>> Author: SvenVanCaekenberghe >>>>>>>> Time: 8 June 2015, 11:34:52.918771 pm >>>>>>>> UUID: 3dcb2c9c-6efe-4d62-bf36-3bbe91f09d08 >>>>>>>> Ancestors: STON-Tests-SvenVanCaekenberghe.53 >>>>>>>> >>>>>>>> Add experimental STONCStyleCommentsSkipStream and tests >>>>>>>> === >>>>>>>> >>>>>>>> Then you can do as follows: >>>>>>>> >>>>>>>> STON fromStream: (STONCStyleCommentsSkipStream on: 'Point[/* this is X*/ 1, /* this is Y*/ 2] // Nice huh ?' readStream). >>>>>>>> >>>>>>>> => 1@2 >>>>>>>> >>>>>>>> STON fromStream: (STONCStyleCommentsSkipStream on: '// Here is how you create a point: >>>>>>>> Point[ >>>>>>>> // this is X >>>>>>>> 1, >>>>>>>> // this is Y >>>>>>>> 2 ] >>>>>>>> // Nice huh ?' readStream). >>>>>>>> >>>>>>>> => 1@2 >>>>>>>> >>>>>>>> This helper class would be useable in other contexts too (like NeoJSON). >>>>>>>> >>>>>>>> The advantage is that it does not change the STON (or JSON) syntax itself, it just add some functionality for those who want it. >>>>>>>> >>>>>>>> What do you think ? >>>>>>>> >>>>>>>> Sven >>>>>>>> >>>>>>>> PS: this probably needs some more testing >>>>>>>> >>>>>>>>> On 08 Jun 2015, at 17:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>>>>>> >>>>>>>>>> On 08 Jun 2015, at 17:03, Damien Cassou <damien.cassou(a)inria.fr> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Sven Van Caekenberghe <sven(a)stfx.eu> writes: >>>>>>>>>> >>>>>>>>>>> I am not so sure we should add that. >>>>>>>>>>> >>>>>>>>>>> The JSON spec explicitly does not allow comments because of fear of abuse (that the comments would be used to add semantic meaning outside the spec). >>>>>>>>>> really? That's surprising. Comments in configuration files are very >>>>>>>>>> important. Even more when the configuration files are templates for new >>>>>>>>>> users. >>>>>>>>> I know some people are using STON in ways that I did not originally anticipate, that is of course cool, but writing configuration files was not the original goal. STON is a version of JSON that is closer to our object model. >>>>>>>>> >>>>>>>>> Like I said, I will think about it. >>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Damien Cassou >>>>>>>>>> http://damiencassou.seasidehosting.st >>>>>>>>>> >>>>>>>>>> "Success is the ability to go from one failure to another without >>>>>>>>>> losing enthusiasm." --Winston Churchill >>>>>>> >>>>> >>>> >>> >>> >> >> >

July 17, 2015