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

Re: [Pharo-dev] Pharo on bitnami

by stepharo

Le 8/6/15 11:37, mikefilonov a Ã©crit : > I think it is a good idea to get Pharo at Bitnami as it will increase the > visibility of the project to the world and put us to the rightful place > alongside with other platforms like Python, Ruby and other :) Moreover it > opens new clouds like Azure, Google Cloud (and whatever Bitnami is partnered > with in the future) for Pharo users. It is quite curious what they mean by > partnership and what they expect from it. > > Back to Pharocloud: yes, we already have this kind of appliances and we can > create any appliances needed â you name it, we publish it â no need to even > have a poll or a contest. We are currently working on several great new > mashup appliances like Pharo+Mongo. I hope those new appliances will bring > new power to Pharo web development. We are starting a tutorial for showing pharo dev and we would love to have Pharo + seaside + magritte + voyage + mongoDB and we should probably talk to you when the tutorial will be in a better shape to see how we can get a price for the book reader. > > Also there is a project on integration of Pharocloud with Digital Ocean and > Amazon EC2 clouds, I hope to release it soon. > > So having this, Pharcloud self hosting, Pharocloud Managed Servers, > on-permise installations (Pharocloud downloadable ISO [1]) and the support > of the community I am totally sure that we can have the best in-house > Pharo-centric cloud. ;) > > > > -- > View this message in context: http://forum.world.st/Pharo-on-bitnami-tp4830833p4830905.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

June 14, 2015

Re: [Pharo-dev] Comments in STON

by stepharo

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 >>>>> >>> >> > >

June 14, 2015

Inexact draiwing in roassal?

by Javier PimÃ¡s

Hi guys, I'm drawing a chart with roassal2 and just discovered that lines are not being drawn exactly as expected. Maybe this is a known problem? I'm running on a few months old pharo4beta image, in linux. Here I attach a screenshot corresponding to the code below. There are more evident examples but this one is easier to debug as it is a straight line made of many segments (zooming a bit you'll see the thin reference line and notice the blue line "bends"). Thanks for reading! Cheers, Javier test | b ds events | events := { 10.0 @ 1.0. 9.0 @ 2.0. 8.0 @ 3.0. 7.0 @ 4.0. 6.0 @ 5.0. 5.0 @ 6.0. 4.0 @ 7.0. 3.0 @ 8.0. 2.0 @ 9.0. 1.0 @ 10.0. 0.0 @ 11.0}. b := RTGrapherBuilder new. b extent: 400 @ 200. ds := RTDataSet new. ds dotShape circle color: Color red. ds interaction fixedPopupText: [ :e | e printString ]. ds points: events. ds connectColor: Color blue. ds x: [ :e | e y ]. ds y: [ :e | e x ]. b add: ds. b axisXWithNumberOfTicks: events size. ^b build [image: Inline image 1] -- Javier PimÃ¡s Ciudad de Buenos Aires

June 13, 2015

Re: [Pharo-dev] Magritte3 in Pharo 5.0

by Stephan Eggermont

On 13/06/15 20:38, Stephan Eggermont wrote: > On 13/06/15 02:23, Sean P. DeNigris wrote: >> Loading via catalog browser gives: "'This package depends on the >> following >> classes: GRDelegatingStream You must resolve these dependencies >> before..." >> >> Any idea what we should do? >> > > Stable loads an old version of Grease Do we need Pharo5.x platform everywhere now? Stephan

June 13, 2015

Re: [Pharo-dev] Magritte3 in Pharo 5.0

by Stephan Eggermont

On 13/06/15 02:23, Sean P. DeNigris wrote: > Loading via catalog browser gives: "'This package depends on the following > classes: GRDelegatingStream You must resolve these dependencies before..." > > Any idea what we should do? > Stable loads an old version of Grease Stephan

June 13, 2015

Re: [Pharo-dev] what is the simple way to get an input?

by Matthieu Lacaton

Isn't it* userInput := UIManager default request: 'Enter whatever you want'* ? 2015-06-13 19:00 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi > > I was reading a book that teaches programming in python and they have > input(x) that > requests inputs and stores it? > > What is our equivalent? > > Stef > >

June 13, 2015

Re: [Pharo-dev] EnableHaltOnce shortcut

by stepharo

Le 13/6/15 10:41, Franck Warlouzet a Ã©crit : > Ok thanks, I already checked the shortcuts with cmd + e and they are > related to add methods or classes in Group in Nautilus. I was thinking > that devs used more often haltOnce than Groups. which is totally true. So I would sawp and add haltOnce. People do not use it because they are not hacking in UI enough, Stef > > I will do your tip and duplicate the item now, thank you Ben. > > Cheers, > Franck > > > From: btc(a)openinworld.com > > Date: Sat, 13 Jun 2015 09:20:58 +0800 > > To: pharo-dev(a)lists.pharo.org > > Subject: Re: [Pharo-dev] EnableHaltOnce shortcut > > > > On Fri, Jun 12, 2015 at 9:40 PM, Franck Warlouzet > > <franck.warlouzet(a)hotmail.fr> wrote: > > > Hello, > > > > > > I really would like to have a shortcut to "Halt enableHaltOnce". > What could > > > be a good combinaison ? I thought about cmd e, h (for Enable Halt) > but I do > > > not know if it is already taken. > > > > > > What do you think about it ? > > > > You can check with "World > System > Keymap Browser" and type "+ e". > > What I often do is use the halos on the "World > System > Enable > > halt/inspect once" menu item to duplicate it onto the background, > > which acts like a button. > > cheers -ben > >

June 13, 2015

what is the simple way to get an input?

by stepharo

Hi I was reading a book that teaches programming in python and they have input(x) that requests inputs and stores it? What is our equivalent? Stef

June 13, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 7b783b: 50112

by stepharo

Le 12/6/15 22:22, Torsten Bergmann a Ã©crit : >> 12986 Increase speed of accessing sourceCode >> https://pharo.fogbugz.com/f/cases/12986 > Wow! Searching through sources using Finder in latest Pharo 5 is now > super fast ... a good candidate for a backport to Pharo 4 (if possible). > > Thanks Camillo! Martin :) > > Bye > T. > >

June 13, 2015

Dead data in smalltalkhub, who has access to the mongodb?

by Stephan Eggermont

https://pharo.fogbugz.com/default.asp?14968 Dead data in Smalltalkhub: VOMongoError: Lazy reference not found ShTeam: OID(3583374428) Someone with mongo access might want to check all references Stephan

June 13, 2015