May 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] OSProcess error in 1.3

by GastÃ³n Dall' Oglio

Hi David. I send some days ago a mail reporting "process never is completed" in Windows, and I propose similar steps to reproduce, see: http://forum.world.st/OSProcess-is-process-done-tp4569088p4570740.html Two notes about this previous mail: Two notes about this previous mail: I say "the image hang", but this was when I evaluate #waitForCommand: and obviously is related to that the external process is always marked as running, not just "when I open the image with OSProcess already loaded" how I says. Another, I do OSProcess command: 'cmd.exe /c dir' en windows 7, OSProcess command: 'dir' only work in windows xp. Well, I run this and both result in a always running process and thread: 1) OSProcess command: 'cmd.exe /c dir'. => always running process (although the associated underlying process is complete) 2) OSProcess thisOSProcess restartChildWatcherThread => always running thread. As I says in previous mail, if I unload and load OSProcess package then all begin to work fine. Then, I suspected that was needed rerun some class side initialize code to solve the problem. And yes!!! That is OSProcessAccessor initialize. I added that to ThisOSProcess>>startUp: resuming | aio | (aio := Smalltalk at: #AioEventHandler) ifNotNil: [ aio startUp: resuming ]. *OSProcessAccessor initialize.* self initializeThisOSProcess Regards. 2012/5/2 David T. Lewis <lewis(a)mail.msen.com> > Sean, > > Can you please try two things, in this order, and let me know which > one causes the problem to go away? > > 1) Save your image, exit, and restart. Then try > > (OSProcess command: 'ls') inspect > > and see if it results in a process proxy with run state "complete". > > 2) Restart the child watcher > > OSProcess accessor restartChildWatcherProcess. > (OSProcess command: 'ls') inspect > > and see if it results in a process proxy with run state "complete". > > Thanks, > Dave > > On Tue, May 01, 2012 at 10:22:44PM -0700, Sean P. DeNigris wrote: > > With the latest OSProcess package from SqS, when I save the image, I get: > > > > 2 May 2012 1:20:30 am > > > > VM: Mac OS - intel - 1073 - Croquet Closure Cog VM [CoInterpreter > > VMMaker-oscog-EstebanLorenzano.155] 21.0 > > Image: Pharo1.3 [Latest update: #13320] > > > > UndefinedObject(Object)>>doesNotUnderstand: #wait > > Receiver: nil > > Arguments and temporary variables: > > aMessage: wait > > exception: MessageNotUnderstood: receiver of "wait" > is nil > > resumeValue: nil > > Receiver's instance variables: > > nil > > > > [[event wait. > > processSynchronizationDelay wait. > > self changed: #childProcessStatus] repeat. > > nil] in UnixOSProcessAccessor>>grimReaperProcess > > Receiver: a UnixOSProcessAccessor on pid 22740 > > Arguments and temporary variables: > > event: nil > > processSynchronizationDelay: a Delay(20 msecs) > > Receiver's instance variables: > > dependents: a DependentsArray(a UnixProcess with pid > 22740) > > sessionIdentifier: #[104 195 160 79] > > canObtainSessionIdentifierFromPlugin: true > > hasTestEof: nil > > grimReaper: a Process in > > MorphicUIManager>>openDebuggerOn:context:label:content...etc... > > sigChldSemaphore: nil > > > > Weird... > > > > > > -- > > View this message in context: > http://forum.world.st/OSProcess-error-in-1-3-tp4602389.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

May 3, 2012

Re: [Pharo-project] multiple pharo images

by Camillo Bruni

we envision an archiving facility with nicely named zips. but the artifacts in there will be the same name => otherwise scripting builds gets too annoying On 2012-05-02, at 23:29, Yanni Chiu wrote: > On 02/05/12 5:20 PM, Francisco Garau wrote: >> How about Jenkins putting a build suffix to the images? -- something >> like *Pharo-2.0.build-20040.image* >> >> At the moment, all the build generate files with the same name. > > I prefer to have the same name, otherwise I have to do one of two things: (1) edit the build script of dependent jobs to have the new name, or (2) re-name the image and changes file to match the build script. I suspect that follow on build jobs is the reason for the current naming convention. > >

May 3, 2012

Re: [Pharo-project] PDF4Smalltalk (was: Artefact - a PDF framework)

by Dale Henrichs

Yanni, Getting close:) Martin Kobetic is making progress on Cypress for VW (the project covering cross dialect git)...not quite there yet... Dale ----- Original Message ----- | From: "Yanni Chiu" <yanni(a)rogers.com> | To: pharo-project(a)lists.gforge.inria.fr | Sent: Wednesday, May 2, 2012 2:59:59 PM | Subject: [Pharo-project] PDF4Smalltalk (was: Artefact - a PDF framework) | | On 02/05/12 12:33 PM, Christian Haider wrote: | >> I've not seen the code for PDF4Smalltalk, because I can't figure | >> out how to browse it without VW. | > | > Unfortunately, you can't :-( | | Could you file out the source code (.st or xml) and post a zip file | to | the gitorious site - or, maybe BobN could do it, since he's looking | at a | port to GemStone. It's a bit of a hurdle to download, install, | refresh/update VW skills - just to evaluate some code. (When I first | heard you'd decided on GIT, I briefly thought that Dale's | Montecello/GIT | would let me browse the code easily - maybe this will be true, at | some | future date). | | |

May 2, 2012

Re: [Pharo-project] Artefact - a PDF framework

by GastÃ³n Dall' Oglio

And in the last page of document says: "Next... Port to VA, GS, Pharo, Squeak (easy for Report4PDF, harder for Smalltalk4PDF)" 2012/5/2 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > Sorry, I mean to capabilities of Report4PDF. > > > 2012/5/2 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > >> Hi. >> >> Following the links in Bob blog, I get a pdf document showing >> capabilities of PDF4Smalltalk: >> >> http://www.stic.st/conferences/stic12/stic12-abstracts/pdf4smalltalk-based-… >> >> Regards. >> >> 2012/5/2 Christian Haider <Christian.Haider(a)smalltalked-visuals.com> >> >>> > Von: pharo-project-bounces(a)lists.gforge.inria.fr >>> [mailto:pharo-project- >>> > bounces(a)lists.gforge.inria.fr] Im Auftrag von Yanni Chiu >>> > >>> > On 02/05/12 10:53 AM, Sean P. DeNigris wrote: >>> > > >>> > > Stephan Eggermont wrote >>> > >> >>> > >> Don't you think it would be much less work to port Christian >>> Haider's >>> > >> work to Pharo? >>> > > >>> > > I was thinking the same thing. The usual Smalltalk duplication of >>> > > effort seems to have been taken to new heights with PDF libs ;-) >>> > >>> > I've loaded Artefact, browsed the code, tried the demos. >>> > >>> > I've not seen the code for PDF4Smalltalk, because I can't figure out >>> how to >>> > browse it without VW. >>> >>> Unfortunately, you can't :-( >>> >>> > However, looking at the examples at: >>> > https://gitorious.org/pdf4smalltalk/pages/Examples >>> > I get the (possibly mistaken) impression that the two frameworks do >>> slightly >>> > different things, but the final result is a PDF in both cases. >>> > >>> > Looking at the PDFDemos of Artefact, it's clear how text and tables >>> can be >>> > written. However, looking at the PDF4Smalltalk examples, it looks like >>> you >>> > have to position the text and tables in your own code. Of course, I >>> may be >>> > completely wrong about PDF4Smalltalk, since I've not seen the full >>> code >>> > base. >>> >>> I have not looked at Artefact, but from what I read, these are different >>> things, I guess. >>> PDF4Smalltalk is a system library providing full access to PDF. >>> PDF objects are regular Smalltalk objects which you can read from PDF >>> files or create them with code and write them as PDF. The PDF basics are >>> quite complete and robust (I use it for a few years in production now), >>> but there are also lots of features desired :-) (TrueType fonts and >>> bitmap images to name a few). >>> >>> It deals purely with PDF and does not add any higher concepts like >>> tables and other layouting facilities - in fact not even proper classes >>> for graphics or text... (high on my list when I find time). It is like >>> painting on a canvas: you are completely responsible for the placement >>> of everything. >>> To deal with that, Bob Nemec implemented Report4PDF which uses Seaside >>> like layouting for a report generator. It is done, works and is quite >>> nice! See >>> http://smalltalk-bob.blogspot.de/2012/01/pdf-report-and-law-of-demeter.h >>> tml<http://smalltalk-bob.blogspot.de/2012/01/pdf-report-and-law-of-demeter.html> >>> >>> I'd love if someone would port this to Pharo! I would help with >>> answering questions, but I have not time to do anything substantial in >>> the moment... >>> >>> Cheers, >>> Christian >>> >>> >> >

May 2, 2012

Re: [Pharo-project] One month working for Pharo Consortium

by Cameron Sanders

Excellent & much appreciated! Hard to expect much in one's first month. Don't be too hard on yourself. -Cam On Wed, May 2, 2012 at 4:27 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Hi, > > So, I'm working since one month for Pharo Consortium, and I want to talk a > bit about how is life here, in RMOD headquarters... > > Of course, is obvious to say that, so far, is been a great experience, and > a lot of fun... the team here is great, very capable, focused and always > willing to help (and to hack something, he). > > In one month, I already face a lot of different issues: > > 1) I helped on release 1.4: > - lots of bugfixed and reviews integrated. > - finishing and integrate new ecompletion/ocompletion > - integration of FileSystem > - fixing VM important issues in windows (FFI plugin and command line > options) > > 2) I worked on the new release process, both in defining them and in doing > steps to make it happen (still far from there) > > 3) Tried to took off some pressure from Marcus and Stef shoulders... I > failed miserably in this issue, because they (both of them) are more or > less workaholics and really enjoy what they do, so, take some of their > responsibilities is not to easy :) > > 4) I also made some small steps on the upcoming pharo consortium web site. > > Well, more or less, that's all. Could I make more? Probably, but well, I > was just adapting to a new country, a new language and a new work > environment. In my not-so-good list, my responsibilities includes the > bootstrap of the pharo consortium, and I think that's the biggest missing > in the month work. I will try to fix that next month. > > In my TODO list, now there are: > > -bootstrap consortium site > -make a first iteration on new release process > -make some "experiments" on validating configurations > -tackle issues and integrate them :) > > best, > Esteban > > >

May 2, 2012

Re: [Pharo-project] Artefact - a PDF framework

by GastÃ³n Dall' Oglio

Sorry, I mean to capabilities of Report4PDF. 2012/5/2 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> > Hi. > > Following the links in Bob blog, I get a pdf document showing capabilities > of PDF4Smalltalk: > > http://www.stic.st/conferences/stic12/stic12-abstracts/pdf4smalltalk-based-… > > Regards. > > 2012/5/2 Christian Haider <Christian.Haider(a)smalltalked-visuals.com> > >> > Von: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project- >> > bounces(a)lists.gforge.inria.fr] Im Auftrag von Yanni Chiu >> > >> > On 02/05/12 10:53 AM, Sean P. DeNigris wrote: >> > > >> > > Stephan Eggermont wrote >> > >> >> > >> Don't you think it would be much less work to port Christian >> Haider's >> > >> work to Pharo? >> > > >> > > I was thinking the same thing. The usual Smalltalk duplication of >> > > effort seems to have been taken to new heights with PDF libs ;-) >> > >> > I've loaded Artefact, browsed the code, tried the demos. >> > >> > I've not seen the code for PDF4Smalltalk, because I can't figure out >> how to >> > browse it without VW. >> >> Unfortunately, you can't :-( >> >> > However, looking at the examples at: >> > https://gitorious.org/pdf4smalltalk/pages/Examples >> > I get the (possibly mistaken) impression that the two frameworks do >> slightly >> > different things, but the final result is a PDF in both cases. >> > >> > Looking at the PDFDemos of Artefact, it's clear how text and tables >> can be >> > written. However, looking at the PDF4Smalltalk examples, it looks like >> you >> > have to position the text and tables in your own code. Of course, I >> may be >> > completely wrong about PDF4Smalltalk, since I've not seen the full >> code >> > base. >> >> I have not looked at Artefact, but from what I read, these are different >> things, I guess. >> PDF4Smalltalk is a system library providing full access to PDF. >> PDF objects are regular Smalltalk objects which you can read from PDF >> files or create them with code and write them as PDF. The PDF basics are >> quite complete and robust (I use it for a few years in production now), >> but there are also lots of features desired :-) (TrueType fonts and >> bitmap images to name a few). >> >> It deals purely with PDF and does not add any higher concepts like >> tables and other layouting facilities - in fact not even proper classes >> for graphics or text... (high on my list when I find time). It is like >> painting on a canvas: you are completely responsible for the placement >> of everything. >> To deal with that, Bob Nemec implemented Report4PDF which uses Seaside >> like layouting for a report generator. It is done, works and is quite >> nice! See >> http://smalltalk-bob.blogspot.de/2012/01/pdf-report-and-law-of-demeter.h >> tml<http://smalltalk-bob.blogspot.de/2012/01/pdf-report-and-law-of-demeter.html> >> >> I'd love if someone would port this to Pharo! I would help with >> answering questions, but I have not time to do anything substantial in >> the moment... >> >> Cheers, >> Christian >> >> >

May 2, 2012

Re: [Pharo-project] Artefact - a PDF framework

by GastÃ³n Dall' Oglio

Hi. Following the links in Bob blog, I get a pdf document showing capabilities of PDF4Smalltalk: http://www.stic.st/conferences/stic12/stic12-abstracts/pdf4smalltalk-based-… Regards. 2012/5/2 Christian Haider <Christian.Haider(a)smalltalked-visuals.com> > > Von: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project- > > bounces(a)lists.gforge.inria.fr] Im Auftrag von Yanni Chiu > > > > On 02/05/12 10:53 AM, Sean P. DeNigris wrote: > > > > > > Stephan Eggermont wrote > > >> > > >> Don't you think it would be much less work to port Christian > Haider's > > >> work to Pharo? > > > > > > I was thinking the same thing. The usual Smalltalk duplication of > > > effort seems to have been taken to new heights with PDF libs ;-) > > > > I've loaded Artefact, browsed the code, tried the demos. > > > > I've not seen the code for PDF4Smalltalk, because I can't figure out > how to > > browse it without VW. > > Unfortunately, you can't :-( > > > However, looking at the examples at: > > https://gitorious.org/pdf4smalltalk/pages/Examples > > I get the (possibly mistaken) impression that the two frameworks do > slightly > > different things, but the final result is a PDF in both cases. > > > > Looking at the PDFDemos of Artefact, it's clear how text and tables > can be > > written. However, looking at the PDF4Smalltalk examples, it looks like > you > > have to position the text and tables in your own code. Of course, I > may be > > completely wrong about PDF4Smalltalk, since I've not seen the full > code > > base. > > I have not looked at Artefact, but from what I read, these are different > things, I guess. > PDF4Smalltalk is a system library providing full access to PDF. > PDF objects are regular Smalltalk objects which you can read from PDF > files or create them with code and write them as PDF. The PDF basics are > quite complete and robust (I use it for a few years in production now), > but there are also lots of features desired :-) (TrueType fonts and > bitmap images to name a few). > > It deals purely with PDF and does not add any higher concepts like > tables and other layouting facilities - in fact not even proper classes > for graphics or text... (high on my list when I find time). It is like > painting on a canvas: you are completely responsible for the placement > of everything. > To deal with that, Bob Nemec implemented Report4PDF which uses Seaside > like layouting for a report generator. It is done, works and is quite > nice! See > http://smalltalk-bob.blogspot.de/2012/01/pdf-report-and-law-of-demeter.h > tml > > I'd love if someone would port this to Pharo! I would help with > answering questions, but I have not time to do anything substantial in > the moment... > > Cheers, > Christian > >

May 2, 2012

Re: [Pharo-project] Multiple desktops

by laurent laffont

On Thu, May 3, 2012 at 12:00 AM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > On Wed, May 2, 2012 at 5:31 PM, Henrik Sperre Johansen < > henrik.s.johansen(a)veloxit.no> wrote: > >> On 02.05.2012 15:40, H. Hirzel wrote: >> >>> How come? >>> >>> Maybe I should have chosen 'Multiple desktops' as the subject line. >>> >>> I just downloaded Pharo 1.4 a few days ago and with only one screen I >>> feel quickly limited. >>> >>> How are people dealing with this? >>> >>> Having different desktops for a system is not a uncommon thing at all. >>> >>> --Hannes >>> >> I believe it was integrated into the TilingWindowManager package. >> It should be loadable through the Metacello Configurations Browser in >> 1.4, (Tools -> Configuration Browser), though I ran into a #DNU doing >> that... >> The monticello repository is http://www.squeaksource.com/** >> TilingWindowManager <http://www.squeaksource.com/TilingWindowManager> . >> > > with -> without problems :) > > I've just tried with latest Pharo 1.4 (build #424) and load it using the > Metacello Configuration Browser with problems. Have you tried with a fresh > 1.4 or a custom image ? > > Cheers, > > Laurent > >> > > >

May 2, 2012

Re: [Pharo-project] Multiple desktops

by laurent laffont

On Wed, May 2, 2012 at 5:31 PM, Henrik Sperre Johansen < henrik.s.johansen(a)veloxit.no> wrote: > On 02.05.2012 15:40, H. Hirzel wrote: > >> How come? >> >> Maybe I should have chosen 'Multiple desktops' as the subject line. >> >> I just downloaded Pharo 1.4 a few days ago and with only one screen I >> feel quickly limited. >> >> How are people dealing with this? >> >> Having different desktops for a system is not a uncommon thing at all. >> >> --Hannes >> > I believe it was integrated into the TilingWindowManager package. > It should be loadable through the Metacello Configurations Browser in 1.4, > (Tools -> Configuration Browser), though I ran into a #DNU doing that... > The monticello repository is http://www.squeaksource.com/** > TilingWindowManager <http://www.squeaksource.com/TilingWindowManager> . > I've just tried with latest Pharo 1.4 (build #424) and load it using the Metacello Configuration Browser with problems. Have you tried with a fresh 1.4 or a custom image ? Cheers, Laurent >

May 2, 2012

[Pharo-project] PDF4Smalltalk (was: Artefact - a PDF framework)

by Yanni Chiu

On 02/05/12 12:33 PM, Christian Haider wrote: >> I've not seen the code for PDF4Smalltalk, because I can't figure >> out how to browse it without VW. > > Unfortunately, you can't :-( Could you file out the source code (.st or xml) and post a zip file to the gitorious site - or, maybe BobN could do it, since he's looking at a port to GemStone. It's a bit of a hurdle to download, install, refresh/update VW skills - just to evaluate some code. (When I first heard you'd decided on GIT, I briefly thought that Dale's Montecello/GIT would let me browse the code easily - maybe this will be true, at some future date).

May 2, 2012