- Pharo-users - lists.pharo.org

Help with trying to publish my project in the Pharo Catalog

by Offray Vladimir Luna CÃ¡rdenas

Hi, We will have our first half data week[1] from Thursday 25 Feb to Saturday 27 Feb, and I would like to ease the grafoscopio's installation by making it available via the Pharo catalog. I have followed the video at [1] and published my stable configurationOfGrafoscopio, but I can't see it on http://catalog.pharo.org/ despite of giving it the proper time to the process to run (it runs at 6 pm Colombian time). [1] https://www.youtube.com/watch?v=S5Dbmmln8tA I think that I have followed properly the instructions but I don't know what I'm missing and I'm a little worried about the catalog generation being run 24 four hours, which gives me only two more attempts to know what I'm doing wrong before the event starts. How can I check that the publishing procedure was fine? In a related matter, How can I made the installation procedure to run something at the end of it, like "GrafoscopioBrowser startDockingBar", so the new interface elements inform the user about a proper installation? Of course I could try the previous ways to install and use grafoscopio, but I think that making it smoother on each workshop/hackathon is better (the problem is that most of these ideas come while the event is getting closer). Cheers, Offray

Feb. 23, 2016

Re: [Pharo-users] how to import a grammar file into Pharo

by Stephan Eggermont

On 22/02/16 05:30, Jen D'Souza wrote: > Many thanks! I hope it helps. I tried the Mucca virtualbox image, and it uses a lot of old packages, so I'd expect lots of small issues in migrating Stephan

Feb. 22, 2016

Re: [Pharo-users] [Pharo-dev] Who is using Pharo Launcher and for what

by Tudor Girba

Hi, Sorry, I mixed the threads and I replied by mistake to the wrong one. The reply should have been for the Pillar question :) Cheers, Doru > On Feb 22, 2016, at 2:03 PM, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > Tudor Girba <tudor(a)tudorgirba.com> writes: > >> I use it for writing documentation and blog posts. > > what is the relationship between Pharo Launcher and your documentation > and blog posts? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill -- www.tudorgirba.com www.feenk.com "The coherence of a trip is given by the clearness of the goal."

Feb. 22, 2016

Re: [Pharo-users] [Pharo-dev] Smalltalkhub scheduled maintenance today (February, 22nd)

by Tudor Girba

Thanks indeed, Christophe! Doru > On Feb 22, 2016, at 2:42 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 22-02-16 13:42, Christophe Demarey wrote: >> Smalltalkhub is now back on line! > > Thanks for taking care! > > Stephan > > > -- www.tudorgirba.com www.feenk.com "We cannot reach the flow of things unless we let go."

Feb. 22, 2016

Re: [Pharo-users] #ifCurtailed: multi-thread semantics

by Ben Coman

On Mon, Feb 22, 2016 at 11:08 PM, Ben Coman <btc(a)openinworld.com> wrote: > Just a curiousity. I learnt something new today... > #ifCurtailed blocks are processed in the outer most thread. > > Transcript clear; crShow: Processor activeProcess; show:' - outside'. > p1 := > [ [ Transcript crShow: Processor activeProcess; show: ' - inside'. > 1 second wait. > ] ifCurtailed: [ Transcript crShow: Processor activeProcess; > show: ' - curtailed' . ] > ] newProcess priority: 41. > p1 resume. > p1 terminate. > ==> > a Process(304957184) in nil - outside > a Process(680396800) in nil - inside > a Process(304957184) in nil - curtailed > > This makes some sense since (I guess) the inside thread is terminated > before the curtailed block executes. However another curiousity... > > Transcript clear; crShow: Processor activeProcess; show:' - outside'. > p1 := > [ Transcript crShow: Processor activeProcess; show: ' - middle'. > p2 := > [ [ Transcript crShow: Processor activeProcess; show: ' - inside'. > 1 second wait. > ] ifCurtailed: [ Transcript crShow: Processor > activeProcess; show: ' - curtailed' . > 2 seconds wait ] > ] fork. > 3 second wait. > ] newProcess priority: 41. > p1 resume. > p2 terminate. > ==> > a Process(304957184) in nil - outside > a Process(146580480) in nil - middle > a Process(417340928) in nil - inside > a Process(304957184) in nil - curtailed > > ...why does the curtailed block execute in outside thread rather than > the middle thread which still exists? > > Also interesting is that if the curtailed code contains a wait, it > blocks the whole UI. > > cheers -ben > > btw, I added... > Process>>printOn: aStream > super printOn: aStream. > aStream nextPutAll: '(' , self hash printString , ') in '. > suspendedContext printOn: aStream Further curiosity, the #ensure block is executed by the 'inner' process... Transcript clear; crShow: Processor activeProcess; show:' - outside'. p1 := [ [ Transcript crShow: Processor activeProcess; show: ' - inside'. 1 second wait. ] ensure: [ Transcript crShow: Processor activeProcess; show: ' - curtailed' . ] ] newProcess priority: 41. p1 resume. p1 terminate. ==> a Process(959980800) in nil - outside a Process(636470784) in nil - inside a Process(636470784) in nil - curtailed And wrapping an #ensure: around an #ifCurtailed: makes its block be executed by the 'inner' process... Transcript clear; crShow: Processor activeProcess; show:' - outside'. p1 := [ [ [ Transcript crShow: Processor activeProcess; show: ' - inside'. 1 second wait. ] ifCurtailed: [ Transcript crShow: Processor activeProcess; show: ' - curtailed' ] ] ensure: [ Transcript crShow: Processor activeProcess; show: ' - ensure' . ] ] newProcess priority: 41. p1 resume. p1 terminate. ==> a Process(959980800) in nil - outside a Process(663403776) in nil - inside a Process(663403776) in nil - curtailed a Process(663403776) in nil - ensure BUT!!! Huh!?!? The original example now has the curtailed block executed by the 'inside' process... Transcript clear; crShow: Processor activeProcess; show:' - outside'. p1 := [ [ Transcript crShow: Processor activeProcess; show: ' - inside'. 1 second wait. ] ifCurtailed: [ Transcript crShow: Processor activeProcess; show: ' - curtailed' . ] ] newProcess priority: 41. p1 resume. p1 terminate. ==> a Process(959980800) in nil - outside a Process(329852416) in nil - inside a Process(329852416) in nil - curtailed cheers -ben

Feb. 22, 2016

#ifCurtailed: multi-thread semantics

by Ben Coman

Just a curiousity. I learnt something new today... #ifCurtailed blocks are processed in the outer most thread. Transcript clear; crShow: Processor activeProcess; show:' - outside'. p1 := [ [ Transcript crShow: Processor activeProcess; show: ' - inside'. 1 second wait. ] ifCurtailed: [ Transcript crShow: Processor activeProcess; show: ' - curtailed' . ] ] newProcess priority: 41. p1 resume. p1 terminate. ==> a Process(304957184) in nil - outside a Process(680396800) in nil - inside a Process(304957184) in nil - curtailed This makes some sense since (I guess) the inside thread is terminated before the curtailed block executes. However another curiousity... Transcript clear; crShow: Processor activeProcess; show:' - outside'. p1 := [ Transcript crShow: Processor activeProcess; show: ' - middle'. p2 := [ [ Transcript crShow: Processor activeProcess; show: ' - inside'. 1 second wait. ] ifCurtailed: [ Transcript crShow: Processor activeProcess; show: ' - curtailed' . 2 seconds wait ] ] fork. 3 second wait. ] newProcess priority: 41. p1 resume. p2 terminate. ==> a Process(304957184) in nil - outside a Process(146580480) in nil - middle a Process(417340928) in nil - inside a Process(304957184) in nil - curtailed ...why does the curtailed block execute in outside thread rather than the middle thread which still exists? Also interesting is that if the curtailed code contains a wait, it blocks the whole UI. cheers -ben btw, I added... Process>>printOn: aStream super printOn: aStream. aStream nextPutAll: '(' , self hash printString , ') in '. suspendedContext printOn: aStream

Feb. 22, 2016

Re: [Pharo-users] [Pharo-dev] Who is using Pharo Launcher and for what

by Damien Cassou

Tudor Girba <tudor(a)tudorgirba.com> writes: > I use it for writing documentation and blog posts. what is the relationship between Pharo Launcher and your documentation and blog posts? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Feb. 22, 2016

Re: [Pharo-users] Smalltalkhub scheduled maintenance today (February, 22nd)

by Christophe Demarey

Smalltalkhub is now back on line! Le 22 fÃ©vr. 2016 Ã 10:59, Christophe Demarey a Ã©crit : > Hello, > > Smalltalk will be down today (february, 22nd) from 12:30 to 13:30 (french local time). > IT will add storage to the root partition (last maintenance finally did not take place). > > Regards, > Christophe

Feb. 22, 2016

Smalltalkhub scheduled maintenance today (February, 22nd)

by Christophe Demarey

Hello, Smalltalk will be down today (february, 22nd) from 12:30 to 13:30 (french local time). IT will add storage to the root partition (last maintenance finally did not take place). Regards, Christophe

Feb. 22, 2016

Re: [Pharo-users] how to import a grammar file into Pharo

by Jen D'Souza

Many thanks! On Sun, Feb 21, 2016 at 4:01 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 21/02/16 22:22, Jen D'Souza wrote: > >> I'd really appreciate if someone could guide me through importing >> PetitIsland.st (http://mucca.inf.usi.ch/source-code.html) into Pharo and >> parsing a text file containing a mix of code and natural language with >> the resulting parser. >> > > Island parsing is now a standard part of the moose image. That is probably > the easiest download to work with. Migrating the other parts of mucca can > be somewhat more work. The web application part of it probably translates > well as it looks like a standard Seaside application. Glorp is available, > I'm not aware of MetaDB, TwoFlower is a simple web browser. In Pharo we > used to have Scamper, but I don't know if that still runs. PetitJava is > loaded in Moose, PetitSTrace should be easy to port. Miller2 is somewhat > larger and might be tightly coupled to VW code. > > Stephan > > > >

Feb. 22, 2016