November 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

by despotadesdibujau

Sven Van Caekenberghe-2 wrote > Great work, Gabriel, thanks for sharing. I have yet to look at what you > did in detail, but what is your pending issue exactly, because I don't > understand "the staless image". Could you elaborate ? > > Sven Thanks!!! Ja!, I wanted to say "stateless":eliminate the possibility of modify the state of the image once it is in production. That I did was downloaded the minimal image of Pharo, I faced with some issues to load my application using filetree or github. I found the solution just loading through Monticello the missing dependecies that Metacello needed to use filetree and github repositories. I delivered an application to a final user just using the minimal image and it is working. My idea is to prepare a minimal image with every tool for load code:Monticello,Metacello suporting all types of repositories (filetree,github,gitbucket, gitlab,...etc),...etc. Then, when my application is loaded, unload those tools and disable the command line handlers (if is posible), and eliminate all unnecessary files like changes and sources ( thank you <http://forum.world.st/How-to-deploy-headless-app-without-changes-and-source…> ). Gabriel -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Nov. 19, 2017

Re: [Pharo-dev] Bloc Naming Suggestion

by Tudor Girba

I think itâs not a bad idea. Doru > On Nov 19, 2017, at 4:31 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > What do you think about removing the #Attribute suffix from all the > BrTextAttribute subclasses? The names seem pretty long (e.g. > BrFontGenericFamilyAttribute, the longest) and IMHO `BrTextAttribute > subclass: #BrFontWeight` is adequately intention revealing. Thoughts? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Nov. 19, 2017

Bloc Naming Suggestion

by Sean P. DeNigris

What do you think about removing the #Attribute suffix from all the BrTextAttribute subclasses? The names seem pretty long (e.g. BrFontGenericFamilyAttribute, the longest) and IMHO `BrTextAttribute subclass: #BrFontWeight` is adequately intention revealing. Thoughts? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Nov. 19, 2017

Re: [Pharo-dev] [ANN] Willow 4.0.0 released!

by Stephan Eggermont

Op 16-11-2017 om 15:44 schreef Gabriel Cotelli: > Hi, > > We're happy to announce the general availability of Willow and it's > related projects in the Web Stack ecosystem hosted at > https://github.com/ba-st/. > > Willow is a Web Interaction Library that eases the burden of creating > AJAX-based web applications. The project goals are: Interesting approach. Might be useful to use as a target for (QC)Magritte. So much things to try out, and not enough time! Stephan

Nov. 19, 2017

Re: [Pharo-dev] Stuck trying to contribute

by Stephan Eggermont

Is all this summarized on Guille's (and Thorstens) pages? Stephan

Nov. 19, 2017

Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

by Sven Van Caekenberghe

> On 19 Nov 2017, at 01:33, gabriel sor <despotadesdibujau(a)gmail.com> wrote: > > Hi, > In in the past days, in the context of the Smalltalks 2017 conference, I talked about my attempt to deploy on production using the minimal image of Pharo . > My goal was prepare an inmutable or staless minimal image for deploy, without sources nor changes files. > The results are exposed in this tutorial. > The size of the image is 16 MB and it has loaded Seaside. > Just I have a pendeing issue: the staless image but everything else is done and working. Great work, Gabriel, thanks for sharing. I have yet to look at what you did in detail, but what is your pending issue exactly, because I don't understand "the staless image". Could you elaborate ? Sven

Nov. 19, 2017

Deploying using the latest minimal image of Pharo (6.1)

by gabriel sor

Hi, In in the past days, in the context of the Smalltalks 2017 conference, I talked about my attempt <https://docs.google.com/presentation/d/1CEyubkv1DT7kQi3oDpHoYWnbeR5YZKhX-mV…> to deploy on production using the minimal image of Pharo . My goal was prepare an inmutable or staless minimal image for deploy, without sources nor changes files. The results are exposed in this tutorial <https://github.com/despotadesdibujau/southsmalltalks/blob/master/docs/how-t…> . The size of the image is 16 MB and it has loaded Seaside. Just I have a pendeing issue: the staless image but everything else is done and working.

Nov. 19, 2017

Re: [Pharo-dev] nil suspend

by Nicolas Cellier

It sounds like a left over... no time stamp in Squeak, so it must be old. Display reverse; reverse means we wanted to catch when such oddity was necessary. (I would do it differently with an Exception and a MessageTally like I already exhibited several times) The fact that reverse; reverse was commented is more difficult to interpret... Is it really necessary? I removed the method in a Squeak image, and so fare nothing wrong happened, but it does not prove anything. The best is to ask in Squeak lists, maybe someone can remember... Or carefully analyze all senders of suspend... 2017-11-18 22:36 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > Hi, > > I was looking at nil (already funny) and found a very interesting method: > > suspend > "Kills off processes that didn't terminate properly" > "Display reverse; reverse." "<-- So we can catch the suspend bug" > Processor terminateActive > > It means that the following code is probably the shortest way to kill your > image (save first!) > > nil suspend > > It terminates a UI process if evaluated from anywhere using CMD+d :D > > Cheers, > Alex >

Nov. 18, 2017

nil suspend

by Aliaksei Syrel

Hi, I was looking at nil (already funny) and found a very interesting method: suspend "Kills off processes that didn't terminate properly" "Display reverse; reverse." "<-- So we can catch the suspend bug" Processor terminateActive It means that the following code is probably the shortest way to kill your image (save first!) nil suspend It terminates a UI process if evaluated from anywhere using CMD+d :D Cheers, Alex

Nov. 18, 2017

Re: [Pharo-dev] nil inspect

by Nicolas Cellier

Ah OK, it's expected then? I find that surprising, because I could maybe want to look at meta side like I can for other elementary objects: [image: Images intÃ©grÃ©es 1] 2017-11-18 22:03 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: > Yes > > [image: Inline images 1] > > Cheers, > Alex > > On 18 November 2017 at 21:56, Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com> wrote: > >> Anyone tried 'nil inspect' recently? >> > >

Nov. 18, 2017