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

Re: [Pharo-project] [NativeBoost] Question: zero-based or one-based indexes?

by Marten Feldtmann

Hello Igor, 0-based - because it's oriented towards C structures (and therefore memory oriented). Another way to see this is: it's not an index, its an byte-offset from the beginning of the memory. Therefore I would not name the parameter as something like index, but more like zeroBasedOffset. By the way: VASmalltalk does it the same way. The same problem might occur, when dealing with pointers to array of primitive data types in ByteArray or instances of NBExternalAddress. Even here I would suggest using zero based index structures - though it is contrary to Smalltalk typical 0ne-based array index. In VASmalltalk this situation is zero-based access and the parameter is not a byte index, but a data element index. And an index of "0" returns the start of the array (and the first element). Marten Am 03.09.2012 02:28, schrieb Igor Stasenko: > Hi, there > > > i added a bunch of accessors to ByteArray and NBExternalAddress which > having uniform look: > > nb<type>At: > nb<type>At: put: > > where types are: > > {U}Int<8/16/32/64> > or > Float<32/64> > > the problem is that indexes in ByteArray are 1-based, > but in NBExternalAddress is 0-based. > > And there's already different places in code which following these rules. > But i feel like this should be uniform (so same piece of code can be > used for either bytearrays or external addresses), > to avoid confusion and mistakes. > > i just not sure which one to leave: 1-based or 0-based ? > > From one side, all collections in smalltalk is 1-based.. > but from other side accessing memory at 1-based offset looks also unnatural. > > What you think? >

Sept. 3, 2012

[Pharo-project] A useful set of Smalltalk-like methods for Objective-C

by Oscar E A CallaÃº

Hi all, I just release a useful set of Smalltalk-like methods (eg. collect: or match: ) for Objective-C classes NSArray, NSMutableArray and NSString. I just extends those classes using categories and blocks. I made this, because when programming on Objective-C, I really miss them. You can find those methods on: https://github.com/ocallau/ObjCSmalltalkExtensions They are in an iOS project, but you can use them in OSX too. Of course, they come with a set of unit tests (on GHUnit). I hope these methods can be useful for you, as they are for me. Cheers. Oscar

Sept. 3, 2012

Re: [Pharo-project] Some news about Athens

by Igor Stasenko

http://nvidia.fullviewmedia.com/siggraph2012/ondemand/SS106.html -- Best regards, Igor Stasenko.

Sept. 3, 2012

Re: [Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

by Igor Stasenko

On 3 September 2012 04:34, Lawson English <lenglish5(a)cox.net> wrote: > On 9/2/12 6:32 PM, Igor Stasenko wrote: >> >> Hi, >> >> i was in a mood of making some overhauls.. >> so as result i refurbished a type system a bit.. >> removed all bogus C-like class names , e.g. NBUnsignedIntType ... >> [...] >> >> P.P.S. i would really like some help with testing what i did, >> including writing some more tests to cover type system more >> broadly (now since type names follow certain naming rule, many >> different types can be checked without much coding) > > > I'm working up a set of methods (you've seen a few of them) to demo the > syntax of how to use the assembler. Perhaps that can be used as part of the > testing? Of course they can. Anything which tries to do something without using common code paths is welcome. > > Also, I haven't checked , but are the MMX/SMP instruction sets implemented > yet? > I don't remember. x86 has a lot of instructions. (and poor documentation). > If not, do you have a timeframe for when you might get around to it? My own > intuition is that these are where people will get the most benefit from > using the assembler anyway. > My current interests lying elsewhere.. but hey, if someone needs them feel free to add support in assembler.. Dont wait for me :) -- Best regards, Igor Stasenko.

Sept. 3, 2012

Re: [Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

by Lawson English

On 9/2/12 6:32 PM, Igor Stasenko wrote: > Hi, > > i was in a mood of making some overhauls.. > so as result i refurbished a type system a bit.. > removed all bogus C-like class names , e.g. NBUnsignedIntType ... > [...] > P.P.S. i would really like some help with testing what i did, > including writing some more tests to cover type system more > broadly (now since type names follow certain naming rule, many > different types can be checked without much coding) I'm working up a set of methods (you've seen a few of them) to demo the syntax of how to use the assembler. Perhaps that can be used as part of the testing? Also, I haven't checked , but are the MMX/SMP instruction sets implemented yet? If not, do you have a timeframe for when you might get around to it? My own intuition is that these are where people will get the most benefit from using the assembler anyway. L -- Squeak from the very start (introduction to Squeak and Pharo Smalltalk for the (almost) complete and compleate beginner). https://www.youtube.com/playlist?list=PL6601A198DF14788D&feature=view_all

Sept. 3, 2012

Re: [Pharo-project] Some news about Athens

by Igor Stasenko

ah, yes.. i forgot to say: - no strike fonts for Athens will be supported ever. It is simply unproductive to waste time on that. They will never work correctly, because the format how they stored in image are premultiplied subpixel 3*32-bit bitmaps. And sure thing, Cairo don't have our highly-special blit mode to render them correctly (not saying that they'll work only for 1:1 pixel grid match, and only for LCD displays, and if you offset them even by a fraction of pixel or rotate/scale, i doubt you will be able to read anything). You can draw bitmaps (forms) using Athens.. but they should be a normal RGBA 32-bit ones. -- Best regards, Igor Stasenko.

Sept. 3, 2012

[Pharo-project] Some news about Athens

by Igor Stasenko

I added a text support for Cairo backend.. unfortunately i was unable to force it rendering with subpixel AA, Cairo completely ignoring settings i passing to it (looks like i need to dig into compilation options to enable it) So, following examples contain simple code to draw text on surface: AthensCairoSurfaceExamples drawFontMetrics AthensCairoSurfaceExamples draw2Strings A following one is my current state of endless battle area with Morphic.. AthensTextRenderTest testWindowRender since morphic using absolute coordinate system, i can't make the clipping right no matter how hard i try arghhhh .. These changes are available if you load ConfigurationOfAthens v 1.4 But you might probably will unable to use it anyways ;), because NB-enabled VMs on jenkins are not yet bundled with cairo library.. I will do a pass on VMs this week and let you know when this stuff will be readily available for download and play with. So many things stacked on top of each other.. it is a pain the ass when something on base level breaks. -- Best regards, Igor Stasenko.

Sept. 3, 2012

[Pharo-project] [NativeBoost] 1.4 Bleeeding edge release

by Igor Stasenko

Hi, i was in a mood of making some overhauls.. so as result i refurbished a type system a bit.. removed all bogus C-like class names , e.g. NBUnsignedIntType ... and replaced them with nice and uniform names, like NBUInt32, NBInt16 etc. (thanks Marten Feldtmann for an idea) A uniform type aliases for these types also added: int8 NBInt8 uint8 NBUInt8 int16 NBInt16 uint16 NBUInt16 int32 NBInt32 uint32 NBUInt32 int64 NBInt64 uint64 NBUInt64 the rest of C integer types are actually aliases of the above. And some new features: - finally spent time for implementing support of 64-bit integer types. (strangely over 2 years nobody needed them ;) - added a bunch of uniform accessors to ByteArray and NBExternalAddress. But please avoid heavily depending on using them right now, before we decide whether they should use uniform indexing, or stay 1-based index for byte arrays, but 0-based indexes for external addresses. And if we decide to have them uniform, should they use 1-based or 0-based indexing. May be force with you. P.S. The configuration is freshly-baked, i didn't even checked if it loads cleanly or not.. so, i don't recommend updating it in image with your precious code :) Special instruction to load NB for Stef: Gofer it squeaksource: 'NativeBoost'; package: 'ConfigurationOfNativeBoost'; load. (ConfigurationOfNativeBoost project version: '1.4' ) load P.P.S. i would really like some help with testing what i did, including writing some more tests to cover type system more broadly (now since type names follow certain naming rule, many different types can be checked without much coding) -- Best regards, Igor Stasenko.

Sept. 3, 2012

[Pharo-project] [NativeBoost] Question: zero-based or one-based indexes?

by Igor Stasenko

Hi, there i added a bunch of accessors to ByteArray and NBExternalAddress which having uniform look: nb<type>At: nb<type>At: put: where types are: {U}Int<8/16/32/64> or Float<32/64> the problem is that indexes in ByteArray are 1-based, but in NBExternalAddress is 0-based. And there's already different places in code which following these rules. But i feel like this should be uniform (so same piece of code can be used for either bytearrays or external addresses), to avoid confusion and mistakes. i just not sure which one to leave: 1-based or 0-based ? >From one side, all collections in smalltalk is 1-based.. but from other side accessing memory at 1-based offset looks also unnatural. What you think? -- Best regards, Igor Stasenko.

Sept. 3, 2012

Re: [Pharo-project] Internationalization in Pharo - Updates?

by Gisela Decuzzi

Thanks Hilaire! 2012/9/2 Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> > Gettext work for Pharo. > Check for the collaboractive Pharo book, it is explained. > http://book.pharo-project.org/ > > Hilaire > > > Le 02/09/2012 16:58, Gisela Decuzzi a Ã©crit : > > Hello, I want something of i18n for Pharo 1.4. I want to add english > > support for Loop. > > Searching I found 2 ways rigth now: > > > > * GetText package (ported from eToys), the problem here is that seems > > to be not working in Pharo 1.4 > > * the translate message > > > > The last updates I could find were years ago and I would like to know if > > there is any work related (in progress or done) or if someone with > > experience could point me the path to follow and avoid reinventing the > > wheel. > > > > I would be pleaced to hear any comment, even if this is some pending > > task that needs to be done or a link to a thread I coluldn't find. > > > > Thanks in advance! > > > > > > > >

Sept. 2, 2012