September 2017 - Pharo-users

Pharo 7 license question

by Jimmie Houchin

Hello, Pharo 7 to my understanding fundamentally changes Pharo. It is my understanding that Pharo 7 starts with a core Pharo kernel and like many languages out there, imports or adds code from a variety of external sources to the image being built. With that understanding, I am curious if that would allow for inclusion of a specific library/module to be licensed as GPL? And it not affect the other code in the composed image? I am a big believer in the MIT/BSD license and not a big fan of the GPL. However, there is software out there that I have avoided looking at the source code or attempting to port it to Pharo because it is GPL. I would sincerely love if I could now port such a library and license it under the GPL as required, and it not affect any other code outside of that specific library. I am not a lawyer. Nor do I know any lawyers. Is is possible for someone to get a reasonably definitive answer on this question? I am sure I am not the only one who has had this desire. I am also sure that I am not the only one who will have this question in the future. So it would be nice to have a proper legal response that could possibly be explicitly stated somewhere on the website or on an FAQ or something. Regardless of the answer, yes or no. It does need to be a settled issue for Pharo. That way someone could know if GPL/LGPL or whatever software could be in the catalog. Just wanted to put that out there to the community. I look forward to the answer, should one be or become available. Thanks. Jimmie

Sept. 15, 2017

Re: [Pharo-users] Writing XML

by Jimmie Houchin

I didn't pay attention to this previously. But I just noticed that using #printToFileNamed: preserved the DOM tree's original line ending where as previously I had to insure the the XMLWriter #lineEnding was changed from defaultLineEnding to canonicalLineEnding. The original document used LF and not CR. Overall this was a nice win. It cleaned up my method to save the file and reduced 7 lines to 2. Nice. :) Thanks. Jimmie On 09/15/2017 09:29 AM, monty wrote: > If you want to write a DOM tree to a file, send #printToFileNamed: (or a related message like #canonicallyPrintToFileNamed: or #printToFileNamed:beforeWritingDo:) to the root. See the XMLNode "printing" category for more. This will automatically encode the file with the encoding the XMLDocument>>#encoding attribute specifies (if recognized), and it's portable across Pharo, Squeak, and GemStone. Use #parseFileNamed:/#onFileNamed: to get portable automatic file decoding when parsing. > >> Sent: Wednesday, September 13, 2017 at 1:02 PM >> From: "Jimmie Houchin" <jlhouchin(a)gmail.com> >> To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> >> Subject: [Pharo-users] Writing XML >> >> Hello, >> >> I am attempting to read and write an XML document. >> >> Currently I have parsed the document successfully. I have basic >> navigation and have learned how to modify the XMLDocument. >> >> Now I want to write the modified document back to the file system. >> What I have tried so far is: >> >> writer := XMLWriter new. >> xmldoc document writeXMLOn: writer. >> writer stream. >> f := File openForWriteFileNamed: '/home/jimmie/xmldoc.xml'. >> f nextPutAll: (writer write contents). >> f flush. >> f close. >> >> It does write an xml document to the file system. However, it has >> exploded in size. The original is 28mb and is in UTF-8. The newly >> written file is 112mb and is UTF-32. >> >> I do not know why the change in encoding or how to correct or manually >> set the encoding. >> >> Any help in understanding how to correctly write an XML document that I >> have read and minimally modified would be greatly appreciated. >> >> Thanks. >> >> Jimmie >> >>

Sept. 15, 2017

Re: [Pharo-users] Writing XML

by Jimmie Houchin

Thanks for the reply. I appreciate the education the people on this list provide. I was already doing the XMLDOMParser #onFileNamed: to open the file. It was showing the correct #encoding for the parsed file. It was just the writing of the nearly identical file which was different. I tried as you wrote #printToFileNamed: and it did as you explained. Thanks again. Jimmie On 09/15/2017 09:29 AM, monty wrote: > If you want to write a DOM tree to a file, send #printToFileNamed: (or a related message like #canonicallyPrintToFileNamed: or #printToFileNamed:beforeWritingDo:) to the root. See the XMLNode "printing" category for more. This will automatically encode the file with the encoding the XMLDocument>>#encoding attribute specifies (if recognized), and it's portable across Pharo, Squeak, and GemStone. Use #parseFileNamed:/#onFileNamed: to get portable automatic file decoding when parsing. > >> Sent: Wednesday, September 13, 2017 at 1:02 PM >> From: "Jimmie Houchin" <jlhouchin(a)gmail.com> >> To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> >> Subject: [Pharo-users] Writing XML >> >> Hello, >> >> I am attempting to read and write an XML document. >> >> Currently I have parsed the document successfully. I have basic >> navigation and have learned how to modify the XMLDocument. >> >> Now I want to write the modified document back to the file system. >> What I have tried so far is: >> >> writer := XMLWriter new. >> xmldoc document writeXMLOn: writer. >> writer stream. >> f := File openForWriteFileNamed: '/home/jimmie/xmldoc.xml'. >> f nextPutAll: (writer write contents). >> f flush. >> f close. >> >> It does write an xml document to the file system. However, it has >> exploded in size. The original is 28mb and is in UTF-8. The newly >> written file is 112mb and is UTF-32. >> >> I do not know why the change in encoding or how to correct or manually >> set the encoding. >> >> Any help in understanding how to correctly write an XML document that I >> have read and minimally modified would be greatly appreciated. >> >> Thanks. >> >> Jimmie >> >>

Sept. 15, 2017

Re: [Pharo-users] Usability issues with Calypso

by kmo

You say The current behaviour is trying to be close to single source pane behaviour of old browsers. I think that's a bit of the problem. For me, nautilus is a single source pane browser and it looks like a single source pane browser. Calypso looks like something else - it looks like a typical tabbed editor. So it's behaviour does not march its look. That's what's confusing. I don't know what is the best behaviour for the tabs - but I think I would prefer always manually opening/closing tabs rather than the auto tabs behaviour - that way I would feel more in control. Other people's mileage may vary. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 15, 2017

Re: [Pharo-users] Writing XML

by monty

If you want to write a DOM tree to a file, send #printToFileNamed: (or a related message like #canonicallyPrintToFileNamed: or #printToFileNamed:beforeWritingDo:) to the root. See the XMLNode "printing" category for more. This will automatically encode the file with the encoding the XMLDocument>>#encoding attribute specifies (if recognized), and it's portable across Pharo, Squeak, and GemStone. Use #parseFileNamed:/#onFileNamed: to get portable automatic file decoding when parsing. > Sent: Wednesday, September 13, 2017 at 1:02 PM > From: "Jimmie Houchin" <jlhouchin(a)gmail.com> > To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] Writing XML > > Hello, > > I am attempting to read and write an XML document. > > Currently I have parsed the document successfully. I have basic > navigation and have learned how to modify the XMLDocument. > > Now I want to write the modified document back to the file system. > What I have tried so far is: > > writer := XMLWriter new. > xmldoc document writeXMLOn: writer. > writer stream. > f := File openForWriteFileNamed: '/home/jimmie/xmldoc.xml'. > f nextPutAll: (writer write contents). > f flush. > f close. > > It does write an xml document to the file system. However, it has > exploded in size. The original is 28mb and is in UTF-8. The newly > written file is 112mb and is UTF-32. > > I do not know why the change in encoding or how to correct or manually > set the encoding. > > Any help in understanding how to correctly write an XML document that I > have read and minimally modified would be greatly appreciated. > > Thanks. > > Jimmie > >

Sept. 15, 2017

UFFI problem / doubt

by alvaro piorno

Hi everybody, iÂ´m using UnifiedFFI with Chipmunk2D library . I want to get a pointer to a C Structure (cpBody) and set a position to it. I have a subClass of FFIOpaqueObject to handle pointer. This is the "new " ffiCall : self ffiCall: #(cpBody* cpBodyNew(cpFloat m, cpFloat i)) And this is a "seter" ffiCall: self ffiCall: #( void cpBodySetPosition( self, cpVect vector ) ). I`m not getting any "error" but the position is not updating. I tried the same using Chipmunk directly and it works, so there is a problem with what i have in Pharo. Any suggestion? Thanks in advance. Alvaro Piorno

Sept. 15, 2017

Re: [Pharo-users] PlotMorph on Pharo 6.1

by st＠bestley.co.uk

Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > --001a113fc0fc9da22e05592a9f54 > Content-Type: text/plain; charset="UTF-8" > > Hi mark > > live is chaotic here with two or three meetings in parallel, visitors, > and a lecture to finish > Now I tested. I took a Pharo 6.1 32 bits and loaded PlotMorph from the catalog > It load Stefaneggermont.8 > > Can you tell us how to reproduce your problem? > I get this on both 32 and 64 bit Pharo on OSX 10.12.6 Loaded a new Pharo from https://pharo.org/web/download and removed previous Preferences Then from Calalog Browser Install Stable Version Then get > > > > Fetched -> ConfigurationOfPlotMorph-StephanEggermont.5 --- > > http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main/ --- > > http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main/ > > Loaded -> ConfigurationOfPlotMorph-StephanEggermont.5 --- > > http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main/ --- > > http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main/ > > Loading 1.1 of ConfigurationOfPlotMorph... > > Fetched -> PlotMorph-StephanEggermont.8 --- > > http://smalltalkhub.com/mc/PharoExtras/PlotMorph/main/ --- > > http://smalltalkhub.com/mc/PharoExtras/PlotMorph/main/ > > OCStoreIntoReadOnlyVariableError: Cannot store into > > PlotMorphGrid > > drawGridOn: aCanvas > > | gridColor lighter darker baseColor bounds | > > baseColor := plot baseColor alpha: 1. > > lighter := baseColor twiceLighter. > > darker := baseColor twiceDarker. > > gridColor := (lighter diff: baseColor) > (darker diff: baseColor) > > ifTrue: [ lighter ] > > ifFalse: [ darker ]. > > bounds := plot drawBounds. > > (bounds left to: bounds right by: (self bestStep: bounds width)) > > do: [ :x | > > x := x rounded. > > aCanvas line: x @ bounds top to: x @ bounds bottom color: > > gridColor ]. > > (bounds top to: bounds bottom by: (self bestStep: bounds height)) > > do: [ :y | > > y := y rounded. > > aCanvas line: bounds left @ y to: bounds right @ y color: > > gridColor ] > > OCStoreIntoReadOnlyVariableError: Cannot store into > > PlotMorphGrid > > drawGridOn: aCanvas > > | gridColor lighter darker baseColor bounds | > > baseColor := plot baseColor alpha: 1. > > lighter := baseColor twiceLighter. > > darker := baseColor twiceDarker. > > gridColor := (lighter diff: baseColor) > (darker diff: baseColor) > > ifTrue: [ lighter ] > > ifFalse: [ darker ]. > > bounds := plot drawBounds. > > (bounds left to: bounds right by: (self bestStep: bounds width)) > > do: [ :x | > > x := x rounded. > > aCanvas line: x @ bounds top to: x @ bounds bottom color: > > gridColor ]. > > (bounds top to: bounds bottom by: (self bestStep: bounds height)) > > do: [ :y | > > y := y rounded. > > aCanvas line: bounds left @ y to: bounds right @ y color: > > gridColor ] > > OCStoreIntoReadOnlyVariableError: Cannot store into > > AxesMorph > > drawGridOn: aCanvas > > | gridColor right bottom width height lighter darker baseColor | > > baseColor := self baseColor. > > lighter := baseColor twiceLighter. > > darker := baseColor twiceDarker. > > gridColor := (lighter diff: baseColor) > (darker diff: baseColor) > > ifTrue: [ lighter ] > > ifFalse: [ darker ]. > > right := self bounds width - margin. > > width := self bounds width - (margin * 2). > > bottom := self bounds height - margin. > > height := self bounds height - (margin * 2). > > (margin to: right by: width / 10) > > do: [ :x | > > x := x rounded. > > aCanvas line: x @ margin to: x @ bottom color: gridColor ]. > > (margin to: bottom by: height / 10) > > do: [ :y | > > y := y rounded. > > aCanvas line: margin @ y to: right @ y color: gridColor ] > > OCStoreIntoReadOnlyVariableError: Cannot store into > > AxesMorph > > drawGridOn: aCanvas > > | gridColor right bottom width height lighter darker baseColor | > > baseColor := self baseColor. > > lighter := baseColor twiceLighter. > > darker := baseColor twiceDarker. > > gridColor := (lighter diff: baseColor) > (darker diff: baseColor) > > ifTrue: [ lighter ] > > ifFalse: [ darker ]. > > right := self bounds width - margin. > > width := self bounds width - (margin * 2). > > bottom := self bounds height - margin. > > height := self bounds height - (margin * 2). > > (margin to: right by: width / 10) > > do: [ :x | > > x := x rounded. > > aCanvas line: x @ margin to: x @ bottom color: gridColor ]. > > (margin to: bottom by: height / 10) > > do: [ :y | > > y := y rounded. > > aCanvas line: margin @ y to: right @ y color: gridColor ] > > Loaded -> PlotMorph-StephanEggermont.8 --- > > http://smalltalkhub.com/mc/PharoExtras/PlotMorph/main/ --- cache > > ...finished 1.1 -- Mark

Sept. 15, 2017

Re: [Pharo-users] Gofer loads wrong version?

by Herby VojÄÃk

stephan wrote: > On 12-09-17 21:58, Herby VojÄÃk wrote: >> Bump. >> >> Can you pls help me with how to load proper version / finding what is >> wrong here? >> >> As shown in replies, it loads two versions (eg. it seems it loads >> everything it finds in the repo). >> >> Herby >> >> Herby VojÄÃk wrote: >>> Hello! >>> >>> As I need to load specific version of Glorp with my fix, and I did not >>> find out how to force-override it in my baseline, I tried to load it >>> post-the-baseline via Gofer: >>> >>> (Gofer new smalltalkhubUser: 'DBXTalk' project: 'Glorp') >>> package: 'Glorp'; >>> version: 'Glorp-HerbyVojcik.127'; >>> load. >>> >>> But it actually looks like this: [see attached bogusgofer.png]. >>> >>> OTOH, after the image loads the tests pass and monticello browser looks >>> like this: [see attached mbloaded127.png]. >>> >>> Am I doing something wrong? I am a bit afraid what is actually loaded / >>> if it won't break b/c of inconsistent state. > > No, it is fine. Telling Gofer package: means prepare to load the latest > version, so you give Gofer two versions to load. Thank you, sir. Changed it to: (Gofer new smalltalkhubUser: 'DBXTalk' project: 'Glorp') version: 'Glorp-HerbyVojcik.127'; load. and now it does exactly what I wanted. Herby > https://www.lukas-renggli.ch/blog/gofer > > Stephan

Sept. 14, 2017

Re: [Pharo-users] (no subject)

by Christophe Demarey

> Le 14 sept. 2017 Ã 14:55, stephan <stephan(a)stack.nl> a Ã©crit : > > On 14-09-17 14:25, Christophe Demarey wrote: >> Let us know if everything is fine. > > Downloaded latest 7 64: > Cannot open iceberg, libgit2 can not be found Thanks for the report. I will check that

Sept. 14, 2017

Re: [Pharo-users] (no subject)

by Christophe Demarey

Hi Stephan, > Le 14 sept. 2017 Ã 14:49, stephan <stephan(a)stack.nl> a Ã©crit : > > On 14-09-17 14:25, Christophe Demarey wrote: >> I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ >> It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. >> Let us know if everything is fine. > > - not downloading the sources; What do you mean? For Pharo images < 70, sources file for the current version and the previous version are downloaded with the VM. > - sources now need to be next to the image; For Pharo 7 images, no sources file are dowloaded since they come with the image. > - when you upgrade the vm, you need to replace all those sources files > - default now dark theme, and not easy to switch I think default theme for the Launcher should be the same as the Pharo theme. Would a (Launcher) preference help? > - icons only shown on hover yes, Pharo 6 regression. I had the problem on other UIs. Will see if I can find a fix quickly.

Sept. 14, 2017