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

Re: [Pharo-project] Again: Basic Questions about NativeBoost

by Luc Fabresse

Hi, In Pharo 2.0 (perhaps not the latest one), NBFFICallbackTests -> 10 run, 7 passes, 3 expected failures so I would say that NB supports some callbacks ;-) Cheers, #Luc 2012/8/28 drush66 <davorin.rusevljan(a)gmail.com> > Does NB support writing callbacks in smalltalk that can be called by > external > library? > > > > ----- > http://www.cloud208.com/ > -- > View this message in context: > http://forum.world.st/Again-Basic-Questions-about-NativeBoost-tp4645447p464… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Aug. 28, 2012

Re: [Pharo-project] Why it takes much more time to load stuff in 2.0 comparing to 1.4?

by Camillo Bruni

run it in the profiler and compare the results. I am very interested int he results :P On 2012-08-28, at 04:06, Igor Stasenko <siguctua(a)gmail.com> wrote: > I was checking how ConfigurationOfNativeBoost behaves on 1.4 > and i noticed that it loads like 3-5 times faster comparing to 2.0.. > > and i refusing to believe this is because of different network latency, > because most time which it spends during loading in 2.0 is showing > "compiling / installing" > progress but not "downloading". > > -- > Best regards, > Igor Stasenko. >

Aug. 28, 2012

Re: [Pharo-project] Who broke UTF8TextConverter?

by Henrik Sperre Johansen

On 28.08.2012 14:35, Igor Stasenko wrote: > or it was like that from the birth?? > > arrrrgghhhh... > > | stream | > stream := WriteStream on: (ByteArray new: 100). > > UTF8TextConverter new nextPut: (Character value: 129 ) toStream: stream. > > stream contents > #[129] > > This is WRONG! RTFM, about utf8 encoding, please! :) > > --------- > > nextPut: aCharacter toStream: aStream > | leadingChar nBytes mask shift ucs2code | > aStream isBinary ifTrue: [^aCharacter storeBinaryOn: aStream]. > > in my case, stream is binary, so it goes directly to #storeBinaryOn: > > storeBinaryOn: aStream > "Store the receiver on a binary (file) stream" > value < 256 > ifTrue:[aStream basicNextPut: value] > ifFalse:[aStream nextInt32Put: value]. > > This is not even close to UTF8. > If character code is less than 256, it will store a single byte (wtf?), > and if more than that, it will store 32-bit integer value in > big-endian order (wtf raisedToPower: 2).. > > i wonder , for what purpose we actually having this code path? this > stuff is completely useless. > according to implementation of storeBinaryOn: > there's no way how you can read the same character value back. > because it can be 1 byte or 4 bytes.. but you simply cannot determine which one. > this is one of the reasons we using utf8 encoding, btw ;) > It's been this way from the start. You want to sanely encode to in-memory bytearrays, use the Zn converters. You want to conveniently switch between putting binary and encoded contents to a filestream (and do so efficiently), use the TextConverters. Cheers, Henry

Aug. 28, 2012

Re: [Pharo-project] Who broke UTF8TextConverter?

by Mariano Martinez Peck

igor, maybe this is related to http://code.google.com/p/pharo/issues/detail?id=6565 ? On Tue, Aug 28, 2012 at 2:35 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > or it was like that from the birth?? > > arrrrgghhhh... > > | stream | > stream := WriteStream on: (ByteArray new: 100). > > UTF8TextConverter new nextPut: (Character value: 129 ) toStream: stream. > > stream contents > #[129] > > This is WRONG! RTFM, about utf8 encoding, please! :) > > --------- > > nextPut: aCharacter toStream: aStream > | leadingChar nBytes mask shift ucs2code | > aStream isBinary ifTrue: [^aCharacter storeBinaryOn: aStream]. > > in my case, stream is binary, so it goes directly to #storeBinaryOn: > > storeBinaryOn: aStream > "Store the receiver on a binary (file) stream" > value < 256 > ifTrue:[aStream basicNextPut: value] > ifFalse:[aStream nextInt32Put: value]. > > This is not even close to UTF8. > If character code is less than 256, it will store a single byte (wtf?), > and if more than that, it will store 32-bit integer value in > big-endian order (wtf raisedToPower: 2).. > > i wonder , for what purpose we actually having this code path? this > stuff is completely useless. > according to implementation of storeBinaryOn: > there's no way how you can read the same character value back. > because it can be 1 byte or 4 bytes.. but you simply cannot determine > which one. > this is one of the reasons we using utf8 encoding, btw ;) > > -- > Best regards, > Igor Stasenko. > > -- Mariano http://marianopeck.wordpress.com

Aug. 28, 2012

[Pharo-project] Who broke UTF8TextConverter?

by Igor Stasenko

or it was like that from the birth?? arrrrgghhhh... | stream | stream := WriteStream on: (ByteArray new: 100). UTF8TextConverter new nextPut: (Character value: 129 ) toStream: stream. stream contents #[129] This is WRONG! RTFM, about utf8 encoding, please! :) --------- nextPut: aCharacter toStream: aStream | leadingChar nBytes mask shift ucs2code | aStream isBinary ifTrue: [^aCharacter storeBinaryOn: aStream]. in my case, stream is binary, so it goes directly to #storeBinaryOn: storeBinaryOn: aStream "Store the receiver on a binary (file) stream" value < 256 ifTrue:[aStream basicNextPut: value] ifFalse:[aStream nextInt32Put: value]. This is not even close to UTF8. If character code is less than 256, it will store a single byte (wtf?), and if more than that, it will store 32-bit integer value in big-endian order (wtf raisedToPower: 2).. i wonder , for what purpose we actually having this code path? this stuff is completely useless. according to implementation of storeBinaryOn: there's no way how you can read the same character value back. because it can be 1 byte or 4 bytes.. but you simply cannot determine which one. this is one of the reasons we using utf8 encoding, btw ;) -- Best regards, Igor Stasenko.

Aug. 28, 2012

Re: [Pharo-project] Again: Basic Questions about NativeBoost

by drush66

Does NB support writing callbacks in smalltalk that can be called by external library? ----- http://www.cloud208.com/ -- View this message in context: http://forum.world.st/Again-Basic-Questions-about-NativeBoost-tp4645447p464… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 28, 2012

[Pharo-project] RPackage question

by Goubier Thierry

If I'm up to date with Pharo 2.0, PackageInfo is gone and RPackage is replacing it, right ? I'm trying to get the AltBrowser to work with RPackage... At the moment, RPackage seems to be organized in the following way. If there are the following Monticello packages : RPackage-Core RPackage-Tests RPackage-SystemIntegration Then, when querying the RPackage organizer, I get the following 4 packages : RPackage RPackage-Core RPackage-Tests RPackage-SystemIntegration In RPackage, I find 3 tags : RPackage-Core RPackage-Tests RPackage-SystemIntegration In RPackage-Core, RPackage-Tests, RPackage-SystemIntegration, I have a single tag, but apparently, by exploring each RPackage info, all the original package references (class definitions, methods etc...), with all that duplicated in RPackage. However, if I query RPackageOrganizer, all classes definitions in RPackage-Core, RPackage-Tests, RPackage-SystemIntegration are reported as belonging to RPackage. Is that expected ? Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Aug. 28, 2012

Re: [Pharo-project] Small Spec / Announcement question.

by Benjamin

No :) That's a mistake :) I think that all registration should be weak Ben On Aug 28, 2012, at 11:07 AM, Goubier Thierry wrote: > Is there a reason for the use or lack of weak in whenChanged for NewValueHolder ? > > NewValueHolder>>whenChanged:do: > announcer weak on:do: > NewValueHolder>>whenChangedSend:to: > announcer on:send:to: > > Thanks, > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Aug. 28, 2012

[Pharo-project] Small Spec / Announcement question.

by Goubier Thierry

Is there a reason for the use or lack of weak in whenChanged for NewValueHolder ? NewValueHolder>>whenChanged:do: announcer weak on:do: NewValueHolder>>whenChangedSend:to: announcer on:send:to: Thanks, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Aug. 28, 2012

Re: [Pharo-project] [ANN] NativeBoost v 1.3

by Igor Stasenko

On 28 August 2012 08:48, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > It works for most parts. There are few examples I will send in a note that > is broken. > > viz: AthensSurfaceExamples >> #exampleStrokeRect should probably in its > subclass AthensCairoSurfaceExamples > > * #exampleDrawText.. and believe other Text drawing expect FreeTypeFont only > as asserted ... but are sent StrikeFont.. > > * AthensTestRenderTest >> #testWindowRender fails as the PluggableTextMorph >>> initialize has a an empty text #setText: '' call.. > this is what i do, when i get something working, i have a small "doits" which then eventually turned into methods like above. some of them became obsolete as project evolves.. and need to be changed/cleaned up. Certainly, i need to do a pass on it to keep things clean and free from confusion. > Need to go down lot more.. and play with it.. seems really neat for external > module callout.. > > Great stuff, need to get down to bottom of it.. incentive enough to re-learn > the necessary bits about assembly lang. Will look at integrating this > permanently with my works till it fails to live up as stable.. > Cannot parse. You want to integrate it till it fails? :) > > BTW: is it extensible to ARM..? I believe so.. also for Raspberry kind of > kits.. > > Long way off to try that out.. but just interested in knowing.. > All of the code is in image, at our disposal. So, it is doable, of course. The only question is who is willing to do that and invest his/her time on it. :) -- Best regards, Igor Stasenko.

Aug. 28, 2012