- Pharo-users - lists.pharo.org

Re: [Pharo-users] about a pillar based output format for Epicea

by Stephane Ducasse

I'm because Pillar is central to all my writings around Pharo (books, slides,...). We also want to use it for a lecture on open-source development. Pillar got too complex and we should simplify its architecture. I'm working on a new version of Cocoon but this tedious and I got stuck in managing initialisation of fields (from text to objects). now I will continue to work but task switching is killing me. Guillermo is helping me from time to time and damien helps me with the makefile/latex. I will first finish all the slides for my lectures at Prague first. Now we made - sure that we can run archetype without being forced to passed by the command-line. - and many changes and cleanup. Now we should work on - Make sure that we identify for real bugs showing up in the three different archetypes (slides, books...). - Avoid to convert to JSON files to apply mustache. - Rethink the architecture. - Like removing the dependency on magritte from the core. - Avoid a lot of strange behavior related to metadata handling. Stef On Wed, Aug 2, 2017 at 6:15 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Pillar is becoming central in the way I produce documents. > Is there anyone working on improving Pillar? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Aug 2, 2017, at 11:55 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi martin >> >> I would like to wlak over epicea objects and save the changed methods >> to be able to write booklets faster. >> What advices can you give me? >> Create a special visitor? >> >> Stef >> > >

Aug. 2, 2017

Re: [Pharo-users] Spotter question. "Spotter" search keyword need font setting from Pharo Setting Value.

by Ben Coman

Thanks for taking the time to let us know of your problem. By "report", I think Alex meant create on Issue on our tracker. Take a look at the top part of http://pharo.org/contribute-propose-fix and the video. cheers -ben On Wed, Aug 2, 2017 at 3:11 PM, peter yoo <onionmixer(a)gmail.com> wrote: > of course. i can report. look attached image please. i try this process. > > 1. open spotter(shift + enter) > 2. press "shift + ctrl + mouse click" to spotter keyword area > 3. explore object. > > can look this...... it's bad try? >

Aug. 2, 2017

Re: [Pharo-users] Settings - Server Mode - should I use it?

by Ben Coman

hi Tim, This is Pharo! You can dig in to understand it yourself. ;) 1. On the setting, right-click and "Browse". 2. Scroll down to... label: 'Server mode' then on #serverMode, right-click > Code Search > Implementors of it 3. Looking at WorldState>>serverMode, click "Senders" and you'll come to WorldState>>interCyclePause: Look for senders of this and inspect MinCycleLapse. Basically that setting makes the UI loop delay for a longer time ==> less CPU but I don't know whether that loop still runs in headless mode. I guess if you are bootstrapping your Lambda image, you can choose. But since your Lambda is meant to finish quite quickly, alternatively maybe during image shutdown you could set a flag such that next startup #interCyclePause: blocks for 500ms and if the image exits cleanly and quickly, #doOneCycleNowFor: is never executed at all. cheers -ben On Wed, Aug 2, 2017 at 10:39 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Hi - I hadnât looked in the settings browser much before, but I was > looking at what settings there were and noticed âserver modeâ. > > Should I be enabling this when building a headless server image to run on > Lambda? I saw a 2016 post by John Brant that indicated it made a difference > when doing some benchmarking in the image (presumably headful) - but Iâm > wondering if when running headless on a server whether it really makes a > difference. > > Has anyone played with this much before? > > Tim >

Aug. 2, 2017

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

by Mariano Martinez Peck

On Wed, Aug 2, 2017 at 12:04 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Iâd be curious about your script if it is easily handy > As said, nothing fancy at all [1]. And it keeps evolving all the time as Pharo evolves too. > (I did notice a blog article you wrote on StartupLoader a while back). > > Yeah, but that post is not a bit outdated as StartupLoader changed quite a bit since I wrote the article. But the idea is still the same. > By the way - I really appreciated your article "Moving contexts > and debuggers between images with Fuelâ - > Thanks. Yes, that fact made us won the first price [2]. I still remember I was sit on my living room, preparing the demo for ESUG I was thinking how could I show Fuel in a cool manner. I knew at that point we were able to serialize closures, methods, classes, etc... but I just thought "what If I serialize the debugger?". I took me 5 minutes to try it out and realized it worked from the first run hahaa. That was one of my top 5 best programming days of my life hahaha. This feature was then used for the "Fuel out stack" and to revive CI failure tests locally. > it inspired me to figure it out for debugging on AWS lambda (which is very > cool BTW - and Iâll write it up soon when I have it bedded in) > > Cool. I have been following your emails about having a small image and a small vm and I am very interesting on that. Well, I should be considering which was my PhD [3] hahaha [1] http://ws.stfx.eu/OCV4GOA5D6DR [2] http://www.esug.org/wiki/pier/Conferences/2011/InnovationTechnologyAwards [3] https://marianopeck.wordpress.com/2012/11/07/dr-mariano-martinez-peck/ Cheers, > Tim > > On 2 Aug 2017, at 15:10, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > On Wed, Aug 2, 2017 at 10:50 AM, Tim Mackinnon <tim(a)testit.works> wrote: > >> Mariano - out of curiosity, how do you build your image - do you use zero >> conf and then apply a known .st script? (I used to use pharo launcher back >> in the day - but now I find that zeroconf is actually handier anyway). >> >> > My work flow explained below is only for when I am using stable Pharo for > a paid client. In this case, I am not grabbing Pharo latest code all the > time. Only every in a while. So, my workflow is as follow: > > 1) with zero conf I simply grab image and vm (I try to keep my app working > with latest stable) > > 2) Apply a known load script that we keep maintained (this is somehwere in > a wiki). This script contains: > 2.1) settings of Author, Monticello username and pass etc. > 2.2) Several custom settings/preferences that I like to change to > the default image (this could be replaced by startup preferences thingy). > 2.3) Workaround for bugs I hit and that are not backported to > stable version. > 2.4) Install 3er party libs I want for my development image > (Calypso browser, code critics (now integrated), etc etc). > 2.5) Finally, I load my app code. > > > 3) Once I am done loading all of it, I save that image as > "PharoMyAppTemplate.image". And I never do real work with that image. > > 4) Each time I need a new image (to make a new feature, a bug fix, > whatever) I take "PharoMyAppTemplate.image" and I do a "save as" with > either number like "PharoMyApp1.image" or "PharoMyAppBug3232.image" or > ""PharoMyAppNewFeature.image" etc. I create these images many times and I > don't have a strong policy on when to create new ones. Whenever I create > one of these images, I upload my app code to latest code. > > 5) Every in a while, I update my template image. Mostly when I change my > dependencies. > > I can share the script if you want. > > Cheers, > > > > >> Tim >> >> On 2 Aug 2017, at 13:24, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> >> >> >> On Wed, Aug 2, 2017 at 9:16 AM, Tim Mackinnon <tim(a)testit.works> wrote: >> >>> Hi - Iâve noticed that when I download a new image+vm with zeroconf (in >>> a fresh directory) - that when I launch it, the setting Tools | Software >>> Config Mgnmnt | Monticello | Local Cache Directory has a value that points >>> to a directory from one of my earlier images. >>> >>> Is this normal (does it store this information somewhere on my computer >>> so that different setups can access it)? >>> >>> At first I thought this was annoying - but Iâm now wondering if this is >>> useful as Iâm guessing that there isnât any reason to have separate caches >>> for version controlled libraries and so maybe I should actually set it to >>> some common directory? >>> >>> What is the recommended strategy? >>> >>> >> My strategy is to use a shared repository for all my images. As part of >> my build image scripts I do something like this: >> >> >> " =============== Personal Settings ================ " >> MCCacheRepository cacheDirectory: '/Users/mariano/Pharo/localRepo/' asFileReference.MCGitHubRepository cacheDirectory: '/Users/mariano/Pharo/localRepo/' asFileReference.GTPlayBook cacheDirectory: '/Users/mariano/Pharo/play-cache/' asFileReference. >> >> GTPlayBook stashDirectory: '/Users/mariano/Pharo/play-stash/' >> asFileReference. >> >> >> I guess you save stuff: >> >> find /Users/mariano/Pharo/localRepo/ -type f | wc -l >> >> *32301* >> >> du -sh /Users/mariano/Pharo/localRepo >> *6.1G* /Users/mariano/Pharo/localRepo >> >> >> Not only you save disk space, but also: >> 1) Each image build is likely to take less time as many files will be >> already in the cache (no need to redownload it). >> 2) it works as a yet another backup of your code and other packages. >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Mariano http://marianopeck.wordpress.com

Aug. 2, 2017

Re: [Pharo-users] about a pillar based output format for Epicea

by Alexandre Bergel

Pillar is becoming central in the way I produce documents. Is there anyone working on improving Pillar? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Aug 2, 2017, at 11:55 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi martin > > I would like to wlak over epicea objects and save the changed methods > to be able to write booklets faster. > What advices can you give me? > Create a special visitor? > > Stef >

Aug. 2, 2017

Re: [Pharo-users] Spotter question. "Spotter" search keyword need font setting from Pharo Setting Value.

by Alexandre Bergel

Add your screenshot to the fogbuz entry. Do you have the url of the entry? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Aug 2, 2017, at 3:11 AM, peter yoo <onionmixer(a)gmail.com> wrote: > > of course. i can report. look attached image please. i try this process. > > 1. open spotter(shift + enter) > 2. press "shift + ctrl + mouse click" to spotter keyword area > 3. explore object. > > can look this...... it's bad try? > <ì¤í¬ë¦°ì·, 2017-08-02 16-07-34.png>

Aug. 2, 2017

about a pillar based output format for Epicea

by Stephane Ducasse

Hi martin I would like to wlak over epicea objects and save the changed methods to be able to write booklets faster. What advices can you give me? Create a special visitor? Stef

Aug. 2, 2017

GT Playground, pages dropdown menu - how does it work?

by Tim Mackinnon

Hi - overtime I think I understand how the pages dropdown for the playground works, it then doesnât do what I expect? I have learned that double clicking a page tab will put the page into the stash directory with a name (which is cool), but then it doesnât always seem to appear in the dropdown list - however I have learned that Spotter will find these pages if I use #playgâ¦ So if spotter can find them, why does the playground dropdown seem to temperamental, or am I missing some obvious trick for clearing a cache or something like that? Or maybe its a bug? It would be nice if it would work, as its very handy as quick way to swap to a script. Tim

Aug. 2, 2017

Re: [Pharo-users] What sets the Monticello Local Cache Directory default in a new image?

by Tim Mackinnon

Iâd be curious about your script if it is easily handy (I did notice a blog article you wrote on StartupLoader a while back). By the way - I really appreciated your article "Moving contexts and debuggers between images with Fuelâ - it inspired me to figure it out for debugging on AWS lambda (which is very cool BTW - and Iâll write it up soon when I have it bedded in) Tim > On 2 Aug 2017, at 15:10, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: > > > > On Wed, Aug 2, 2017 at 10:50 AM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: > Mariano - out of curiosity, how do you build your image - do you use zero conf and then apply a known .st script? (I used to use pharo launcher back in the day - but now I find that zeroconf is actually handier anyway). > > > My work flow explained below is only for when I am using stable Pharo for a paid client. In this case, I am not grabbing Pharo latest code all the time. Only every in a while. So, my workflow is as follow: > > 1) with zero conf I simply grab image and vm (I try to keep my app working with latest stable) > > 2) Apply a known load script that we keep maintained (this is somehwere in a wiki). This script contains: > 2.1) settings of Author, Monticello username and pass etc. > 2.2) Several custom settings/preferences that I like to change to the default image (this could be replaced by startup preferences thingy). > 2.3) Workaround for bugs I hit and that are not backported to stable version. > 2.4) Install 3er party libs I want for my development image (Calypso browser, code critics (now integrated), etc etc). > 2.5) Finally, I load my app code. > > > 3) Once I am done loading all of it, I save that image as "PharoMyAppTemplate.image". And I never do real work with that image. > > 4) Each time I need a new image (to make a new feature, a bug fix, whatever) I take "PharoMyAppTemplate.image" and I do a "save as" with either number like "PharoMyApp1.image" or "PharoMyAppBug3232.image" or ""PharoMyAppNewFeature.image" etc. I create these images many times and I don't have a strong policy on when to create new ones. Whenever I create one of these images, I upload my app code to latest code. > > 5) Every in a while, I update my template image. Mostly when I change my dependencies. > > I can share the script if you want. > > Cheers, > > > > Tim > >> On 2 Aug 2017, at 13:24, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: >> >> >> >> On Wed, Aug 2, 2017 at 9:16 AM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> Hi - Iâve noticed that when I download a new image+vm with zeroconf (in a fresh directory) - that when I launch it, the setting Tools | Software Config Mgnmnt | Monticello | Local Cache Directory has a value that points to a directory from one of my earlier images. >> >> Is this normal (does it store this information somewhere on my computer so that different setups can access it)? >> >> At first I thought this was annoying - but Iâm now wondering if this is useful as Iâm guessing that there isnât any reason to have separate caches for version controlled libraries and so maybe I should actually set it to some common directory? >> >> What is the recommended strategy? >> >> >> My strategy is to use a shared repository for all my images. As part of my build image scripts I do something like this: >> >> >> " =============== Personal Settings ================ " >> >> MCCacheRepository cacheDirectory: '/Users/mariano/Pharo/localRepo/' asFileReference. >> MCGitHubRepository cacheDirectory: '/Users/mariano/Pharo/localRepo/' asFileReference. >> GTPlayBook cacheDirectory: '/Users/mariano/Pharo/play-cache/' asFileReference. >> GTPlayBook stashDirectory: '/Users/mariano/Pharo/play-stash/' asFileReference. >> >> >> I guess you save stuff: >> >> find /Users/mariano/Pharo/localRepo/ -type f | wc -l >> 32301 >> >> du -sh /Users/mariano/Pharo/localRepo >> 6.1G /Users/mariano/Pharo/localRepo >> >> >> Not only you save disk space, but also: >> 1) Each image build is likely to take less time as many files will be already in the cache (no need to redownload it). >> 2) it works as a yet another backup of your code and other packages. >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/> > > > > > -- > Mariano > http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>

Aug. 2, 2017

Settings - Server Mode - should I use it?

by Tim Mackinnon

Hi - I hadnât looked in the settings browser much before, but I was looking at what settings there were and noticed âserver modeâ. Should I be enabling this when building a headless server image to run on Lambda? I saw a 2016 post by John Brant that indicated it made a difference when doing some benchmarking in the image (presumably headful) - but Iâm wondering if when running headless on a server whether it really makes a difference. Has anyone played with this much before? Tim

Aug. 2, 2017