November 2017 - Pharo-users

FileReference>>#moveTo: across filesystems

by Claudio Corrodi

Hi all, Manuel Leuenberger and I ran into an issue with the FileReference>>#moveTo: method last week. On my system, I have "/" and "/home" in two different partitions/file systems. If I do something like the following, Pharo complains with a PrimitiveFailed signal: '/tmp/aFile.txt' asFileReference moveTo: '/home/claudio/aFile.txt' asFileReference I do not know how this is implemented exactly, but assume that the "rename" syscall is used (on Linux systems, that is), which does not work across file systems. The issue does not arise if I moveTo: inside the same filesystem. Is this expected behaviour? It is not obvious (to me) that FileReference>>#moveTo: requires source and target to be on the same filesystem. It would therefore make more sense to me if there were a fallback that copies and deletes if two filesystems are involved (much like "mv" behaves). What do you think? Cheers, Claudio

Nov. 13, 2017

Re: [Pharo-users] I18n in pharo

by Hilaire

Ok, got it. Le 12/11/2017 Ã 13:04, Stephane Ducasse a Ã©critÂ : > Yes. Morph and Polymorph as well as Athens but Sparta offers a similar > API. So conversion should be easy. > And Bloc opens a lot of possibilities. Bloc is the result of around 4 > years of effort understanding the domain > and comparing solutions. -- Dr. Geo http://drgeo.eu

Nov. 13, 2017

Re: [Pharo-users] Embedded PDF viewer?

by Offray Vladimir Luna CÃ¡rdenas

On 13/11/17 06:59, Ben Coman wrote: > "Live programming PDF documents" seems like a catchy meme that the > broader community may find intriguing.Â Â > > Really, I'm just curious about what might be possible and can only > discover that by walking the way. Certainly I would be interested in that catchy meme. Please keep us updated and keep also the good work. Thanks, Offray

Nov. 13, 2017

Re: [Pharo-users] Open Debugger, Save and Quit

by Sean P. DeNigris

Tim Mackinnon wrote > you can override this and Fuel out the debug context to a file Thanks, Tim! I do know about that, but I was thinking/hoping that maybe there was a way to keep the debug context alive without fueling outâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 13, 2017

Re: [Pharo-users] Embedded PDF viewer?

by Sean P. DeNigris

Ben Coman wrote > I've wanted PDF rendering inside Pharo for *years* and finally got a > sniff of a solid possibility - so I'm chasing it down. It might not pan > out like I imagine, but "Live programming PDF documents" seems like a > catchy meme that the broader community may find intriguing. Go, go, go!! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 13, 2017

Re: [Pharo-users] NeoJSON. Allowing null or an object

by Juraj Kubelka

Hi, I have just found the answer for the reader: -=-=-=- rectangleJson := '{ "origin" : null, "corner" : null }'. (NeoJSONReader on: rectangleJson readStream) mapInstVarsFor: Point; for: Point do: [ :mapping | mapping allowNil ]; for: Rectangle do: [ :mapping | (mapping mapInstVar: #origin) valueSchema: Point. (mapping mapInstVar: #corner) valueSchema: Point ]; nextAs: Rectangle. -=-=-=- I have an impression that there is a bug in the writer. While the following example works: -=-=-=- String streamContents: [ :stream | (NeoJSONWriter on: stream) for: Point do: [ :mapping | mapping mapAllInstVars. mapping allowNil ]; for: Rectangle do: [ :mapping | (mapping mapInstVar: #origin) valueSchema: Point. (mapping mapInstVar: #corner) valueSchema: Point ]; nextPut: Rectangle new ]. -=-=-=- the following example does not work: -=-=-=- String streamContents: [ :stream | (NeoJSONWriter on: stream) for: Point do: [ :mapping | mapping mapAllInstVars. mapping allowNil ]; for: Rectangle do: [ :mapping | (mapping mapInstVar: #origin) valueSchema: Point. (mapping mapInstVar: #corner) valueSchema: Point ]; writeNil: true; nextPut: Rectangle new ]. -=-=-=- What do you think? Juraj > On Nov 13, 2017, at 12:50, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi, > > Please, how should I modify the mapping to be able to parse the following example? > > -=-=-=- > rectangleJson := '{ > "origin" : null, > "corner" : null > }'. > > (NeoJSONReader on: rectangleJson readStream) > mapInstVarsFor: Point; > for: Rectangle do: [ :mapping | > (mapping mapInstVar: #origin) valueSchema: Point. > (mapping mapInstVar: #corner) valueSchema: Point ]; > nextAs: Rectangle. > -=-=-=- > > I receive from a server JSON messages including null values. > Can we say use Point value schema or null? How? > > In the documentation I can see the example: > > -=-=-=- > String streamContents: [ :stream | > (NeoJSONWriter on: stream) > mapAllInstVarsFor: Point; > writeNil: true; > nextPut: Point new ]. > -=-=-=- > that produces {"x":null,"y":null} > > But I do not see how to apply this for the following example: > -=-=-=- > String streamContents: [ :stream | > (NeoJSONWriter on: stream) > mapAllInstVarsFor: Point; > for: Rectangle do: [ :mapping | > (mapping mapInstVar: #origin) valueSchema: Point. > (mapping mapInstVar: #corner) valueSchema: Point ]; > writeNil: true; > nextPut: Rectangle new ]. > -=-=-=- > > Thanks, > Juraj > >

Nov. 13, 2017

NeoJSON. Allowing null or an object

by Juraj Kubelka

Hi, Please, how should I modify the mapping to be able to parse the following example? -=-=-=- rectangleJson := '{ "origin" : null, "corner" : null }'. (NeoJSONReader on: rectangleJson readStream) mapInstVarsFor: Point; for: Rectangle do: [ :mapping | (mapping mapInstVar: #origin) valueSchema: Point. (mapping mapInstVar: #corner) valueSchema: Point ]; nextAs: Rectangle. -=-=-=- I receive from a server JSON messages including null values. Can we say use Point value schema or null? How? In the documentation I can see the example: -=-=-=- String streamContents: [ :stream | (NeoJSONWriter on: stream) mapAllInstVarsFor: Point; writeNil: true; nextPut: Point new ]. -=-=-=- that produces {"x":null,"y":null} But I do not see how to apply this for the following example: -=-=-=- String streamContents: [ :stream | (NeoJSONWriter on: stream) mapAllInstVarsFor: Point; for: Rectangle do: [ :mapping | (mapping mapInstVar: #origin) valueSchema: Point. (mapping mapInstVar: #corner) valueSchema: Point ]; writeNil: true; nextPut: Rectangle new ]. -=-=-=- Thanks, Juraj

Nov. 13, 2017

Re: [Pharo-users] Open Debugger, Save and Quit

by Sven Van Caekenberghe

I do something similar, in my WAHtmlHaltAndErrorHandler subclass fuelOutException: exception | filename context | filename := 't3-seaside-exception-{1}.fuel' format: { ZTimestamp now format: '20010203T160506' }. context := exception signalerContext. [ FuelOutStackDebugAction serializeTestFailureContext: context toFileNamed: filename ] on: Error do: [ ] But like Tim says, it works via a .fuel file, it does not change the image state. You then open the .fuel file in a similar image. > On 13 Nov 2017, at 15:48, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi Sean - not sure if this is exactly what you are after, but there is a method in the debugger that is invoked when you need to debug, you can override this and Fuel out the debug context to a file (or I guess even a variable in the image if you are also saving the image when it gets an error). When the the image relaunches in a headful state you could check if that file exists (or variable is not null) and then open a debugger on the Fueled back in state? > > Marianoâs article gave me all of the hints for doing something like this for PharoLamda - (although I am reading the file from S3 and then creating the debugger in a different image) - but I could imagine you doing this for what you want? > > If you need specific code I can dig it out for you tonight. > > Tim > >> On 12 Nov 2017, at 23:15, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> Sean P. DeNigris wrote >>> In a headless image, I'd like to do the following: if there's any error, >>> arrange to have a debugger open on the next (headful) launch, and then >>> save >>> and quit. >> >> Bump :) I can't believe no one knows how to do this! >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >

Nov. 13, 2017

Re: [Pharo-users] Open Debugger, Save and Quit

by Tim Mackinnon

Hi Sean - not sure if this is exactly what you are after, but there is a method in the debugger that is invoked when you need to debug, you can override this and Fuel out the debug context to a file (or I guess even a variable in the image if you are also saving the image when it gets an error). When the the image relaunches in a headful state you could check if that file exists (or variable is not null) and then open a debugger on the Fueled back in state? Marianoâs article gave me all of the hints for doing something like this for PharoLamda - (although I am reading the file from S3 and then creating the debugger in a different image) - but I could imagine you doing this for what you want? If you need specific code I can dig it out for you tonight. Tim > On 12 Nov 2017, at 23:15, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sean P. DeNigris wrote >> In a headless image, I'd like to do the following: if there's any error, >> arrange to have a debugger open on the next (headful) launch, and then >> save >> and quit. > > Bump :) I can't believe no one knows how to do this! > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Nov. 13, 2017

Re: [Pharo-users] Peeking at a stream

by Prof. Andrew P. Black

> On 2 Nov 2017, at 10:10 , Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > My first hunch is that you don't want to change PositionableStream. Because it works on collections and files (because of inheritance). But not on other kind of streams that are not part of the hierarchy, such as sockets. And we are cleaning that part. > > Instead, some time ago Sven produced a really nice hierarchy of stream decorators. Check the package: > > Zinc-Character-Encoding-Core > > There you have > > ZnBufferedReadStream > > That implements buffering in an orthogonal way. Maybe it makes more sense to put such method there? > I wanted this to be something light-weight. I really donât want to have to wrap my stream in a decorator before peeking ahead. Because Iâm doing this in SmaCC, I implemented #explore: (thatâs the name I chose) in SmaCCLineNumberStream. But I think that the general solution is to put this method in a Trait, so that it can be combined into any stream, whether or not that stream inherits from PositionableStream. There are probably other methods that could go in such a trait too. Actually, the idea of resetting a stream to a prior position is much less general, and easier to implement, then general positionability. Over the weekend I posted an issue that discusses positioning a MultiButeFileStream â thatâs a good example. Here is my implementation â really simple. ``` explore: aBlock "evaluate aBlock with this stream as argument. When done, reset my position to the current position." | savedPosition | savedPosition := self position. [ ^ aBlock value: self ] ensure: [ self position: savedPosition ] ``` Andrew

Nov. 13, 2017