January 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PNG in Artefact

by olivier auverlot

In fact, the PNG is converted to JPEG image before to be included in the PDF file. But the conversion process doesn't support transparency and sets a black background. I think that is a limitation in the JPEG writer but someone have perhaps an idea to fix it. Olivier ;-) 2015-01-11 21:11 GMT+01:00 Torsten Bergmann <astares(a)gmx.de>: > > JPEG supports is degrading. Less and less good support. > > > > Le 11/1/15 18:04, Torsten Bergmann a Ã©crit : > > >>> I improved Artefact this morning and added the support for PNG > files. It's now possible to use PDFPngElement to include a PNG > (untransparent) in a PDF file produced by Artefact. > > > Nice, what is the reason only untransparent PNGs work? > > Thanks - but that was not my question. PNG graphics format can - but must > not > include transparency. When I understand the mail correct only > non-transparent > PNG images are supported with the new addition. > > That's why I ask about transparent PNG. > > Bye > T. > >

Jan. 11, 2015

Re: [Pharo-dev] [squeak-dev] OSProcess stdErr issue on Windows

by David T. Lewis

On Sun, Jan 11, 2015 at 03:07:59PM -0500, David T. Lewis wrote: > On Sun, Jan 11, 2015 at 02:42:01PM -0500, David T. Lewis wrote: > > > > I copied ConfigurationOfOSProcess-ThierryGoubier.33 to the OSProcess > > repository. An update to ConfigurationOfOSProcess will be needed to > > get the latest version (Thierry, can you do this?). > > > > For Squeak, no ConfigurationOfOSProcess is needed, just use the latest > > version (with SqueakMap, or currently it OSProcess-dtl.93 in the repo). > > > > Pharo should also use the latest version if possible, although the > > Metacello configurations are needed to make things work on various older > > Pharo versions. The versions for a current spec would be: > > > > OSProcess-Base-dtl.46 > > OSProcess-Unix-dtl.20 > > OSProcess-Win32-dtl.12 > > OSProcess-Mac-dtl.2 > > OSProcess-OS2-dtl.2 > > OSProcess-RiscOS-dtl.2 > > OSProcess-AIO-dtl.8 > > Tests-OSProcess-dtl.21 > > > > Oops, sorry. That should be OSProcess-Tests-dtl.12, not Tests-OSProcess-dtl.21. Sorry to keep replying to myself, but I noticed some missing test updates from the main OSProcess package, so now it is OSProcess-Tests-dtl.13. Dave

Jan. 11, 2015

Re: [Pharo-dev] PNG in Artefact

by Torsten Bergmann

> JPEG supports is degrading. Less and less good support. > > Le 11/1/15 18:04, Torsten Bergmann a Ã©crit : > >>> I improved Artefact this morning and added the support for PNG files. It's now possible to use PDFPngElement to include a PNG (untransparent) in a PDF file produced by Artefact. > > Nice, what is the reason only untransparent PNGs work? Thanks - but that was not my question. PNG graphics format can - but must not include transparency. When I understand the mail correct only non-transparent PNG images are supported with the new addition. That's why I ask about transparent PNG. Bye T.

Jan. 11, 2015

GT tool request

by stepharo

Hi I found the blue rectangle morph painful because it blocks me when I want to freely edit expression and result. Would it be possible that when I type enter the blue rectangle text is paste in the pane below its expression. Right now I have to copy and paste explictly and it not working. I hate so much this broken interaction.... Example (20@200) printString get blue rectangle press copy parentheses got hilighlited no idea why then I press enter to go to the next line (my selection vanished of course because the magic things selected everything automatically) and I can paste the result and start to edit it. I sincerly hope that GT guys will understand and modify it because right now this is a show stopper to me. It breaks so badly interaction with texts. Stef

Jan. 11, 2015

Re: [Pharo-dev] Woden on Windows?

by Torsten Bergmann

Stef wrote > You need to load latest version of OSWindow from what ronie told me. Thanks, will try

Jan. 11, 2015

Re: [Pharo-dev] [squeak-dev] OSProcess stdErr issue on Windows

by David T. Lewis

On Sun, Jan 11, 2015 at 02:42:01PM -0500, David T. Lewis wrote: > > I copied ConfigurationOfOSProcess-ThierryGoubier.33 to the OSProcess > repository. An update to ConfigurationOfOSProcess will be needed to > get the latest version (Thierry, can you do this?). > > For Squeak, no ConfigurationOfOSProcess is needed, just use the latest > version (with SqueakMap, or currently it OSProcess-dtl.93 in the repo). > > Pharo should also use the latest version if possible, although the > Metacello configurations are needed to make things work on various older > Pharo versions. The versions for a current spec would be: > > OSProcess-Base-dtl.46 > OSProcess-Unix-dtl.20 > OSProcess-Win32-dtl.12 > OSProcess-Mac-dtl.2 > OSProcess-OS2-dtl.2 > OSProcess-RiscOS-dtl.2 > OSProcess-AIO-dtl.8 > Tests-OSProcess-dtl.21 > Oops, sorry. That should be OSProcess-Tests-dtl.12, not Tests-OSProcess-dtl.21. Dave

Jan. 11, 2015

Re: [Pharo-dev] CI nesting of XMLWriter >> writeWith:

by stepharo

I do not know I just created the configuration for XMLWriter. Stef Le 11/1/15 16:10, Ben Coman a Ã©crit : > I am having a look at some failing tests for CIXMLPublisherTest. This > uses XMLWriter, which I haven't used before, so I'm looking for > confirmation of the semantics I've guessed for #writeWith:. It seems > that #writeWith: should not be nested. Since... > > xmlWriter := XMLWriter new. > xmlWriter writeWith: [ :writer | > writer > tag: 'report' > with: [ > writer tag: 'name' with: 'TestName - Report'. > xmlWriter writeWith: [ :writer2 | > writer2 tag: 'finality' with: 'succeed' > ] > ] > ] > > ...produces an error "CollectionIsEmpty: an OrderedCollection() is empty" > > This pattern is the cause of 4 of the 8 tests for CIXMLPublisherTest > to fail. In this case CIXMLPublisher >> publishValidationResult: does > a #writeWith: then calls #publishSuccess: which does another #writeWith: . > > That example was done on top of... > $ wget > https://ci.inria.fr/pharo/job/Pharo-4.0-Issue-Tracker-Image/736/artifact/Ph… > $ unzip *zip > $ wget --quiet -O - get.pharo.org/vmLatest > <http://get.pharo.org/vmLatest> | bash > $ ./pharo-ui *.image > > I have logged https://pharo.fogbugz.com/default.asp?14708 > > cheers -ben

Jan. 11, 2015

Re: [Pharo-dev] Woden on Windows?

by stepharo

You need to load latest version of OSWindow from what ronie told me. Le 11/1/15 18:06, Torsten Bergmann a Ã©crit : > Hi, > > is woden 3D engine for Pharo working out of the box with Pharo 4 and > latest VM on Windows? As OSWindow is already integrated I do not know > if the load script still fits. Wanted to ask first. > What is required to load? > > If so can we have a config in the config browser for easy access? > > Thx > T. > >

Jan. 11, 2015

Re: [Pharo-dev] PNG in Artefact

by stepharo

JPEG supports is degrading. Less and less good support. Le 11/1/15 18:04, Torsten Bergmann a Ã©crit : >>> I improved Artefact this morning and added the support for PNG files. It's now possible to use PDFPngElement to include a PNG (untransparent) in a PDF file produced by Artefact. > Nice, what is the reason only untransparent PNGs work? > > Thx > T. > > >

Jan. 11, 2015

Re: [Pharo-dev] [squeak-dev] OSProcess stdErr issue on Windows

by David T. Lewis

Thanks Ben, On Sun, Jan 11, 2015 at 12:36:14PM +0800, Ben Coman wrote: > On Windows 7, trying to execute a non-existent program as follows... > OSProcess command: 'notepadXX.exe' > > ...causes an MNU in ExternalWindowsOSProcess>>value. This is due to writing > to stderr where "self initialStdErr" returns nil, seemingly due to > ExternalWindowsOSProcess missing the #initialize and #setDefaults of E > xternalUnixOSProcess. I made the change to prevent this error, and committed it to the OSProcess repository. > > Now I understand that stderr is problematic in general on Windows. > The following statements... > OSProcess thisOSProcess stdErr nextPutAll: 'test'. > FileStream stderr nextPutAll: 'test'. > > ...both work fine on OSX, but fail on Windows with the error > "FileWriteError: File stderr is closed" > The result is the same on both Pharo 4 and Squeak 4.5. > (Squeak also brings up a bottom message bar saying... "# To disable: F2 -> > 'debug options' -> 'show console on errors' WARNING: Manufactured file > handle detected!") A word of explanation is in order here. There is a handle registry in the Windows support code for FilePlugin that was added specifically to prevent use of "manufactured" file handles. I think that the idea was enhance security, although in practice the only effect is to prevent OSProcess from attaching to pipes and stdio streams. A workaround would be to provide an external FilePlugin dll with the handle registry disabled. > > Pharo has a workaround for the general issue by creating a disk file > named 'stderr' > as follows... > FileStream class >> standardIOStreamNamed: moniker forWrite: forWrite > self flag: #todo. "This is an ugly hack, while waiting for a real fix for > windows. There several problems with this approach, but it allow us to run > tests, etc." > Smalltalk os isWin32 > ifTrue: [ > [ ^ MultiByteFileStream forceNewFileNamed: moniker asString ] > on: CannotDeleteFileException do: [ > "HACK: if the image is opened a second time windows barks about the already > opened locked file" > ^ MultiByteFileStream forceNewFileNamed: moniker asString, '_', (Random new > nextInt: SmallInteger maxVal) asString ]]. > > So to address the MNU for OSProcess? > 1. wrap the "self initialStdErr" with an #ifNil: check > 2. Squeak adopt the Pharo workaround, then lean on that to define > #initialize and #setDefaults for ExternalWindowsOSProcess > 3. real fix for stderr (outside of OSProcess?) > 4. wont fix > 5. other? > > > Note that this is not a burning issue for me. I am just cleaning out old > issues that I logged in the Pharo bug tracker. If the answer if (4.) I'll > just close the issue [1]. I did #1, and hopefully that will take care of the issue. > > > For both Squeak and Pharo, I > loaded ConfigurationOfOSProcess-ThierryGoubier.33 from... > MCHttpRepository > location: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo40/main' > (Perhaps someone with access can copy that to the main repo) > I copied ConfigurationOfOSProcess-ThierryGoubier.33 to the OSProcess repository. An update to ConfigurationOfOSProcess will be needed to get the latest version (Thierry, can you do this?). For Squeak, no ConfigurationOfOSProcess is needed, just use the latest version (with SqueakMap, or currently it OSProcess-dtl.93 in the repo). Pharo should also use the latest version if possible, although the Metacello configurations are needed to make things work on various older Pharo versions. The versions for a current spec would be: OSProcess-Base-dtl.46 OSProcess-Unix-dtl.20 OSProcess-Win32-dtl.12 OSProcess-Mac-dtl.2 OSProcess-OS2-dtl.2 OSProcess-RiscOS-dtl.2 OSProcess-AIO-dtl.8 Tests-OSProcess-dtl.21 > > cheers -ben > > [1] https://pharo.fogbugz.com/default.asp?11615 Thanks a lot for reporting this! Dave

Jan. 11, 2015