- Pharo-users - lists.pharo.org

Re: [Pharo-users] Image growing size

by Ben Coman

On Wed, Feb 4, 2015 at 12:49 AM, Laura Risani <laura.risani(a)gmail.com> wrote: > Hi all, > > The official image i've downloaded weighted about 40 MB. Now its size is > about 200 MB. What is the explanation? Is this normal or have i done > something wrong? > > I haven't been using globals, just downloaded and defined some packages. > The only over persistent thing i've done is to keep > > an instance variable in some classes > Do you mean class-instance-variable? http://pharo.gforge.inria.fr/PBE1/PBE1ch6.html > i wanted to have a unique instance. > > > Best, > Laura >

Feb. 4, 2015

Fwd: [Pharo-dev] why smalltalk is the best system to support object-oriented thinking :)

by stepharo

Better on this list. -------- Message transfÃ©rÃ© -------- Sujet : [Pharo-dev] why smalltalk is the best system to support object-oriented thinking :) Date : Tue, 03 Feb 2015 21:15:39 +0100 De : stepharo <stepharo(a)free.fr> RÃ©pondre Ã : Pharo Development List <pharo-dev(a)lists.pharo.org> Pour : pharo-dev >> Pharo Development List <pharo-dev(a)lists.pharo.org> Here is the presentation I did at Brescia http://www.slideshare.net/pharoproject/the-best-system-for-objectoriented-t…

Feb. 4, 2015

Re: [Pharo-users] [Pharo-dev] spotter preview

by Norbert Hartl

> Am 03.02.2015 um 13:25 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > > >> On 02 Feb 2015, at 22:02, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> Hi, >> >> The Glamorous Team is happy to present a new feature in Spotter: preview (you toggle it with Cmd+p). We think this boosts the usefulness of the Spotter interface significantly. >> >> <spotter-method-preview.png> Really cool. I updated my pharo4 to 474 and can see the preview. But once switched on it seems to stay that way. Cmd+P does not remove the preview. Closing and opening the spotter again shows the preview opened. Norbert >> >> For more details, please take a look at: >> http://www.humane-assessment.com/blog/boosting-gtspotter-with-preview <http://www.humane-assessment.com/blog/boosting-gtspotter-with-preview> >> >> This is available in the Moose image, and it will soon be integrated in the Pharo one. >> > > This is now in Pharo4 update 473 (the latest one from today). > > Marcus >

Feb. 4, 2015

Re: [Pharo-users] Pharo on Raspberry Pi 2

by Annick Fron

There is a Jenkins build for Pharo done by Jean-Baptiste Arnaud. The usability is mainly hindered by the windowing system, which is VERY slow. On the raspberry, there is the possibility to replace X11 by wayland, and I read wrappers should exist to move from one to the other. Wayland can use the Raspberry GPU, which is VERY fast. Besides, JBâs version relies on pharoS and not pharo, so remains behind the main pharo development. But nobody has done that yet. Annick Le 2 fÃ©vr. 2015 Ã 16:11, Thierry Goubier <thierry.goubier(a)gmail.com> a Ã©crit : > > > 2015-02-02 16:01 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > Which platform ?... > http://dev.windows.com/en-us/featured/raspberrypi2support > > Oh, Linux for me will be perfect, thanks :) > > > On Mon, Feb 2, 2015 at 9:21 PM, Ignacio Sniechowski <0800nacho(a)gmail.com> wrote: > Thierry, > Pharo runs in the previous RPI, the problem actually is not more horsepower but a JIT VM. > I think Tim was working in that, but the VM is not quiet there yet. > From my experience, Pharo at this stage is only barely usable. But if the VM was similar in specification to that of the x86 architecture I can bet that Pharo will run perfectly well doing some tricks. > > I guessed as well. I was just considering how much more powerfull (and closer to standard ARM platforms?) the version 2 of the Pi seems to be. > > Thierry

Feb. 4, 2015

Re: [Pharo-users] Monticello review web application

by Sven Van Caekenberghe

> On 04 Feb 2015, at 09:46, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 04 Feb 2015, at 09:33, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi Mike, >> >> I just tried your application and it works well. Simple but effective. >> > > One question: Could we benefit from that for daily review of Pharo fixes? I don't know if it can compare slices (MCZ's with dependent/required packages). >> It is of course sometimes a bit hard to get to an actual URL ;-) >> >> Good work. >> >> Sven >> >>> On 04 Feb 2015, at 02:33, mikefilonov <mikefilonov(a)gmail.com> wrote: >>> >>>> Where you tool takes its input? >>> >>> The tool requires a full URL to mcz package file for both base and target >>> versions. This allows to compare versions on different locations. I attached >>> the screenshot of the form : >>> >>> <http://forum.world.st/file/n4803522/Monticello_Seaside_Review.png> >>> >>> You may easily log in http://review.pharocloud.com/ as there is no >>> registration and stuff (I used Mozilla Persona) so you see the form like in >>> three clicks. >>> >>>> Ok I split this method into one in the superclass and one in the >>>> superclass. >>> >>> This is one of the reasons why my tool requires full URL for both base and >>> target - so it is not restricted only to ancestor comparing. With Monticello >>> Seaside Review you can compare v43 with v46, which could be the final >>> version of you change. >>> >>>> What I would love is to bind it with epicea. The users can comment the >>> >>> Sorry, but I did not quite get the idea. Could you please describe a use >>> case how Epicea is used in a development process? >>> >>> Thank you, >>> Mike >>> >>> >>> >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/Monticello-review-web-application-tp4803443p4803522.h… >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >> >> > >

Feb. 4, 2015

Re: [Pharo-users] Monticello review web application

by mikefilonov

If the app is useful I will go on with the development. I have following roadmap in my mind: * REST API so review can be created automatically * Mail notifications * List of reviewers * Review state like "approved, denied", minimum number of approves need to for review to "pass" * Comment linked to a line -- View this message in context: http://forum.world.st/Monticello-review-web-application-tp4803443p4803559.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 4, 2015

Re: [Pharo-users] Monticello review web application

by Marcus Denker

> On 04 Feb 2015, at 09:33, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Mike, > > I just tried your application and it works well. Simple but effective. > One question: Could we benefit from that for daily review of Pharo fixes? > It is of course sometimes a bit hard to get to an actual URL ;-) > > Good work. > > Sven > >> On 04 Feb 2015, at 02:33, mikefilonov <mikefilonov(a)gmail.com> wrote: >> >>> Where you tool takes its input? >> >> The tool requires a full URL to mcz package file for both base and target >> versions. This allows to compare versions on different locations. I attached >> the screenshot of the form : >> >> <http://forum.world.st/file/n4803522/Monticello_Seaside_Review.png> >> >> You may easily log in http://review.pharocloud.com/ as there is no >> registration and stuff (I used Mozilla Persona) so you see the form like in >> three clicks. >> >>> Ok I split this method into one in the superclass and one in the >>> superclass. >> >> This is one of the reasons why my tool requires full URL for both base and >> target - so it is not restricted only to ancestor comparing. With Monticello >> Seaside Review you can compare v43 with v46, which could be the final >> version of you change. >> >>> What I would love is to bind it with epicea. The users can comment the >> >> Sorry, but I did not quite get the idea. Could you please describe a use >> case how Epicea is used in a development process? >> >> Thank you, >> Mike >> >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/Monticello-review-web-application-tp4803443p4803522.h… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> > >

Feb. 4, 2015

Re: [Pharo-users] Monticello review web application

by Sven Van Caekenberghe

Hi Mike, I just tried your application and it works well. Simple but effective. It is of course sometimes a bit hard to get to an actual URL ;-) Good work. Sven > On 04 Feb 2015, at 02:33, mikefilonov <mikefilonov(a)gmail.com> wrote: > >> Where you tool takes its input? > > The tool requires a full URL to mcz package file for both base and target > versions. This allows to compare versions on different locations. I attached > the screenshot of the form : > > <http://forum.world.st/file/n4803522/Monticello_Seaside_Review.png> > > You may easily log in http://review.pharocloud.com/ as there is no > registration and stuff (I used Mozilla Persona) so you see the form like in > three clicks. > >> Ok I split this method into one in the superclass and one in the >> superclass. > > This is one of the reasons why my tool requires full URL for both base and > target - so it is not restricted only to ancestor comparing. With Monticello > Seaside Review you can compare v43 with v46, which could be the final > version of you change. > >> What I would love is to bind it with epicea. The users can comment the > > Sorry, but I did not quite get the idea. Could you please describe a use > case how Epicea is used in a development process? > > Thank you, > Mike > > > > > > > -- > View this message in context: http://forum.world.st/Monticello-review-web-application-tp4803443p4803522.h… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Feb. 4, 2015

Re: [Pharo-users] Image growing size

by ClÃ©ment Bera

Hello, There could be many reasons why you would have such a big image. The most common reason is the monticello metadata, as Phil said. Another reason could be because some caches and objects that are flushed on snapshot, so if you looked at the image size at runtime and not the file size (for example, the Display object, which is huge, is not in the snapshot, same thing for the AST cache) it is bigger. Another reason is that you may have kept persistent some data that refers to a huge graph of objects / a lot of objects. In the past, it happened to me that I kept errors in a collection to be able to debug them after the program execution (debugging directly the error would crash the image because it was errors in critical processes), but those errors were referencing a huge graph of nodes and after several thousands errors the image was overflowing its 1Gb limit. So what do you keep persistent in your application ? Does it refer to a lot of objects without you knowing it ? 2015-02-03 18:31 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Try to open monticello and select any repo, right click and clear the > package cache. > > If you are using monticello that is. > > Also close all windows, open a workspace and do the > > 10 timesRepeat: [ Smalltalk garbageCollect]. > > HTH > Phil > Le 3 fÃ©vr. 2015 17:49, "Laura Risani" <laura.risani(a)gmail.com> a Ã©crit : > > Hi all, >> >> The official image i've downloaded weighted about 40 MB. Now its size is >> about 200 MB. What is the explanation? Is this normal or have i done >> something wrong? >> >> I haven't been using globals, just downloaded and defined some packages. >> The only over persistent thing i've done is to keep an instance variable in >> some classes i wanted to have a unique instance. >> >> >> Best, >> Laura >> >

Feb. 4, 2015

Re: [Pharo-users] REST approach?

by olivier auverlot

Zinc + Seaside REST is a very good solution that I use every days ;-) Olivier 2015-02-04 7:13 GMT+01:00 S Krish <krishnamachari.sudhakar(a)gmail.com>: > > Seaside REST / Teapot aka Sinatra from Ruby .... hope to push this > framework further > > On Wed, Feb 4, 2015 at 9:35 AM, Cameron Sanders via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > >> >> >> ---------- Forwarded message ---------- >> From: Cameron Sanders <camsanders(a)aol.com> >> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> Cc: >> Date: Tue, 3 Feb 2015 23:05:21 -0500 >> Subject: REST approach? >> >> Our app runs on Pharo and Gemstone and must continue to do so. We use >> Zinc and Seaside. We require credentialing. >> >> What tools do people recommend using for setting up a REST server? >> Straight Zinc? Any tips? >> >> Thanks in advance! >> Cam >> >> >

Feb. 4, 2015