- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] strange Zinc JPEG bug

by stepharo

Le 24/5/16 Ã 19:50, Henrik Nergaard a Ã©crit : > > Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? > > Any bug found in the standard image regardless of project should be > reported on fogbugz, no? > Yes I imgaine that there is zinc project there else we should create one. > > but this works just fineâ¦ > > If I do: > > /| imageStream |/ > > // > > /imageStream := (ZnEasy get: > 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') > contents readStream./ > > // > > /JPEGReadWriter formFromStream: imageStream./ > > It will give me an error âimage format not recognizedâ. > > ImageReadWriter chooses to use PluginBasedJPEGReadWriter instead of > JPEGReadWriter (ImageReadWriter >>#readerClassFromStream: ). > > So perhaps #getJpeg: should use the PluginBasedJPEGReadWriter or have > a fallback on error trying once more by using ( > > /JPEGReadWriter formFromStream: theStream /) ? > > Best regards, > > Henrik > > *From:*Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *On Behalf > Of *Peter UhnÃ¡k > *Sent:* Tuesday, May 24, 2016 6:37 PM > *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> > *Subject:* [Pharo-dev] strange Zinc JPEG bug > > Hi, > > Offray discovered a strange Zinc bug when reading a JPEG. > > Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? > > This fails on "marker D0 cannot be handled" > > image := ZnEasy getJpeg: > 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…'. > > World backgroundImage: image layout: #scaled. > > but this works just fine > > image := (ImageReadWriter formFromStream: (ZnEasy get: > 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') > contents readStream). > > World > > backgroundImage: image > > layout: #scaled. > > Peter >

May 25, 2016

about ensureCreateFile

by stepharo

I would like to move on on this one: https://pharo.fogbugz.com/f/cases/18084/FileReference-EnsureCreateFile I'm in favor of the change. But I'm all ears. Stef

May 25, 2016

Re: [Pharo-dev] slice/merge conflict with package AST-FFI-Pharo50Compatibility

by Nicolai Hess

2016-05-24 23:51 GMT+02:00 Henrik Nergaard <henrik.nergaard(a)uia.no>: > When trying to load the Slice for 17696 from pharo60Inbox I get: > âMessageNotUnderstood: receiver of "dependencies" is nilâ when it tries to > load AST-FFI-Pharo50Compatibility. > > > > I think you need to reset the package cache/folder? > > You might also I need to do the slice again (without loading the > previous), and ensure that the author set when uploading the slice is not > the same as similar slices in the repo so it will not create dependencies > of it ( ie before creating the slice do: âAuthor fullname: â_NicolaiHessâ > Thanks, I think cleaning the package cache folder did the trick. It seems to work now. > > > Best regards, > > Henrik > > > > *From:* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *On Behalf > Of *Nicolai Hess > *Sent:* Tuesday, May 24, 2016 11:38 PM > *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> > *Subject:* [Pharo-dev] slice/merge conflict with package > AST-FFI-Pharo50Compatibility > > > > I need help with issues > 17696 > <https://pharo.fogbugz.com/f/cases/17696/RBParser-should-not-allow-variable-…> > RBParser should not allow variable names for pragma arguments > 17994 > <https://pharo.fogbugz.com/f/cases/17994/RBParserNode-allowed-primitive-prag…> > RBParserNode: allowed primitive pragma definition can not compile > > for both issues I created a slice that will modify methods from package > AST-FFI-Pharo50Compatibility, but merging this slices shows a merge > conflict. > > I don't know what is wrong or how I could solve this. > > any help appreciated. > > nicolai >

May 24, 2016

Re: [Pharo-dev] slice/merge conflict with package AST-FFI-Pharo50Compatibility

by Henrik Nergaard

When trying to load the Slice for 17696 from pharo60Inbox I get: âMessageNotUnderstood: receiver of "dependencies" is nilâ when it tries to load AST-FFI-Pharo50Compatibility. I think you need to reset the package cache/folder? You might also I need to do the slice again (without loading the previous), and ensure that the author set when uploading the slice is not the same as similar slices in the repo so it will not create dependencies of it ( ie before creating the slice do: âAuthor fullname: â_NicolaiHessâ Best regards, Henrik From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Nicolai Hess Sent: Tuesday, May 24, 2016 11:38 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: [Pharo-dev] slice/merge conflict with package AST-FFI-Pharo50Compatibility I need help with issues 17696<https://pharo.fogbugz.com/f/cases/17696/RBParser-should-not-allow-variable-…> RBParser should not allow variable names for pragma arguments 17994<https://pharo.fogbugz.com/f/cases/17994/RBParserNode-allowed-primitive-prag…> RBParserNode: allowed primitive pragma definition can not compile for both issues I created a slice that will modify methods from package AST-FFI-Pharo50Compatibility, but merging this slices shows a merge conflict. I don't know what is wrong or how I could solve this. any help appreciated. nicolai

May 24, 2016

slice/merge conflict with package AST-FFI-Pharo50Compatibility

by Nicolai Hess

I need help with issues 17696 <https://pharo.fogbugz.com/f/cases/17696/RBParser-should-not-allow-variable-…> RBParser should not allow variable names for pragma arguments 17994 <https://pharo.fogbugz.com/f/cases/17994/RBParserNode-allowed-primitive-prag…> RBParserNode: allowed primitive pragma definition can not compile for both issues I created a slice that will modify methods from package AST-FFI-Pharo50Compatibility, but merging this slices shows a merge conflict. I don't know what is wrong or how I could solve this. any help appreciated. nicolai

May 24, 2016

Re: [Pharo-dev] Screenshot of Pharo 64 bits

by Dimitris Chloupis

You guys are awesome, amazing work , thank you so much for making this reality :) On Tue, May 24, 2016 at 7:06 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thanks a lot! > > Doru > > > > On May 24, 2016, at 3:25 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > > > > Today I helped Esteban porting the 32 to 64 bits bootstrap to Pharo. It > looks like we have a Pharo 64 bits image on 64 bits VM running on Mac & > Linux. > > > > Here is the wonderful screenshot showing the amazing result: > > > > <Screen Shot 2016-05-24 at 3.19.23 PM.png> > > -- > www.tudorgirba.com > www.feenk.com > > "Some battles are better lost than fought." > > > > > >

May 24, 2016

Re: [Pharo-dev] strange Zinc JPEG bug

by Sven Van Caekenberghe

> On 24 May 2016, at 20:11, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > On Tue, May 24, 2016 at 7:50 PM, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? > > Any bug found in the standard image regardless of project should be reported on fogbugz, no? > > > Ah, good point. > > > > > but this works just fineâ¦ > > If I do: > > > > | imageStream | > > > > imageStream := (ZnEasy get: 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') contents readStream. > > > > JPEGReadWriter formFromStream: imageStream. > > > > It will give me an error âimage format not recognizedâ. > > > > ImageReadWriter chooses to use PluginBasedJPEGReadWriter instead of JPEGReadWriter (ImageReadWriter >>#readerClassFromStream: ). > > > > So perhaps #getJpeg: should use the PluginBasedJPEGReadWriter or have a fallback on error trying once more by using ( > > JPEGReadWriter formFromStream: theStream ) ? > > > What's the difference? Why do we have two clasees for reading JPEGs? > > Peter One is implemented in pure Pharo code, the other is plugin based, C code calling a library, and is much faster (and presumable more capable in handling weird cases). I always assumed the fastest one was used automatically, but apparently not. This works: PluginBasedJPEGReadWriter formFromStream: (ZnEasy get: 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') entity readStream. I'll have to look into this. Sven

May 24, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60033 Home: https://github.com/pharo-project/pharo-core

May 24, 2016

Re: [Pharo-dev] strange Zinc JPEG bug

by Peter UhnÃ¡k

On Tue, May 24, 2016 at 7:50 PM, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? > > Any bug found in the standard image regardless of project should be > reported on fogbugz, no? > Ah, good point. > > > but this works just fineâ¦ > > If I do: > > > > *| imageStream |* > > > > *imageStream := (ZnEasy get: > 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir… > <http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…>') > contents readStream.* > > > > *JPEGReadWriter formFromStream: imageStream.* > > > > It will give me an error âimage format not recognizedâ. > > > > ImageReadWriter chooses to use PluginBasedJPEGReadWriter instead of > JPEGReadWriter (ImageReadWriter >>#readerClassFromStream: ). > > > > So perhaps #getJpeg: should use the PluginBasedJPEGReadWriter or have a > fallback on error trying once more by using ( > > *JPEGReadWriter formFromStream: theStream *) ? > What's the difference? Why do we have two clasees for reading JPEGs? Peter

May 24, 2016

Re: [Pharo-dev] strange Zinc JPEG bug

by Henrik Nergaard

Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? Any bug found in the standard image regardless of project should be reported on fogbugz, no? but this works just fineâ¦ If I do: | imageStream | imageStream := (ZnEasy get: 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') contents readStream. JPEGReadWriter formFromStream: imageStream. It will give me an error âimage format not recognizedâ. ImageReadWriter chooses to use PluginBasedJPEGReadWriter instead of JPEGReadWriter (ImageReadWriter >>#readerClassFromStream: ). So perhaps #getJpeg: should use the PluginBasedJPEGReadWriter or have a fallback on error trying once more by using ( JPEGReadWriter formFromStream: theStream ) ? Best regards, Henrik From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Peter UhnÃ¡k Sent: Tuesday, May 24, 2016 6:37 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: [Pharo-dev] strange Zinc JPEG bug Hi, Offray discovered a strange Zinc bug when reading a JPEG. Not sure where to report zinc bugsâ¦ fogzbugz? or is it a separate project? This fails on "marker D0 cannot be handled" image := ZnEasy getJpeg: 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…'. World backgroundImage: image layout: #scaled. but this works just fine image := (ImageReadWriter formFromStream: (ZnEasy get: 'http://orig13.deviantart.net/e8d3/f/2013/092/a/3/glados_s_activation_by_fir…') contents readStream). World backgroundImage: image layout: #scaled. Peter

May 24, 2016