- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-project] Understanding NBOpenGL

by kilon

you can have outdated documentation as you can have buggy code and even outdated code. And yes I would not trust a coder to write proper documentation as much I would trust someone who writes documentation to code or fix a bug. Why ? because its all about motivation, thats why. But you know what , its easy to pick , just ask your users what they want. If they dont want me to contribute to wikibooks and instead contribute to tests, comment classes and methods sure ok I will do it. -- View this message in context: http://forum.world.st/Understanding-NBOpenGL-tp4686514p4696881.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 2, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 3 regressions found. FuelTests.FLGlobalTraitSerializationTest.testNotFoundAfterRename Tests.Traits.TraitPureBehaviorTest.testOwnMethodsTakePrecedenceOverTraitsMethods Tests.Traits.TraitPureBehaviorTest.testPropagationWhenTraitCompositionModifications

July 2, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 3 regressions found. FuelTests.FLGlobalTraitSerializationTest.testNotFoundAfterRename Tests.Traits.TraitPureBehaviorTest.testOwnMethodsTakePrecedenceOverTraitsMethods Tests.Traits.TraitPureBehaviorTest.testPropagationWhenTraitCompositionModifications

July 2, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 3 regressions found. FuelTests.FLGlobalTraitSerializationTest.testNotFoundAfterRename Tests.Traits.TraitPureBehaviorTest.testOwnMethodsTakePrecedenceOverTraitsMethods Tests.Traits.TraitPureBehaviorTest.testPropagationWhenTraitCompositionModifications

July 2, 2013

Re: [Pharo-dev] [Pharo-project] Understanding NBOpenGL

by Camillo Bruni

On 2013-07-02, at 16:47, kilon <thekilon(a)yahoo.co.uk> wrote: > Igor one last thing I forgot to ask about b) how I pass the pointer to the > function ? > > Now Camillo , If you guys care about making pharo popular , I mean really > popular you should stop caring what you want or what I want and care more > about what most people want. Democracy sucks but hey thats the way to fame. > I am sorry but I am not buying into the whole argument of self documented > code. Why ? Because I dont trust coders. It's a matter of resources, examples can be executed and run regularly during tests. Which means they work. Documentation, as any other part, rots, but nobody tests it automatically. So keeping external documentation up to date is a significant effort! So you do not trust coders, but you trust people that write documentation? I only trust tests, if tests are green I am happy. Written out documentation is not tested (unless you have a fancy system, which, sadly, we do not have yet). And I think that you can perfectly explain a complex library with step by step examples. Don't get me wrong, I am not against documentation, but I still think it effort put at the wrong place. Just look at Pharo By Example and how much confusion the outdated examples cause...

July 2, 2013

Re: [Pharo-dev] [Pharo-project] Understanding NBOpenGL

by kilon

Igor one last thing I forgot to ask about b) how I pass the pointer to the function ? Now Camillo , If you guys care about making pharo popular , I mean really popular you should stop caring what you want or what I want and care more about what most people want. Democracy sucks but hey thats the way to fame. I am sorry but I am not buying into the whole argument of self documented code. Why ? Because I dont trust coders. I know however for a fact that as you said it "outside" documentation , assuming its a lengthy one, even if its a bad one, is a much safer bet to make sense , especially for a very big library. If the library is very small sure you can deal with it with class comments and method comments and some random examples. But take Nativeboost for example, understanding Nativeboost without outside documentation is just , well crazy. There so many issues to discuss and many concepts to analyse, and if we take into account that people dealing with Nativeboost are not C coders or experienced with C coding then you will have loads of user with a big questionmark on top of their heads. Sure those people should go read a C code, which I do already , but still would I complain if documentation of NB explained those things to me ? Why would I , I am as lazy as the next person. Plus I am a user why should I care about class comments and methods comments, I dont care how the source works I only care how I can use the library the easiest , quickest way possible. Should classes and methods have their comments ? definitely !!! This is open source , its meant to be read , analyzed and modified. Making people life harder is making it more close source. But I dont believe a user of a library would prioritize class / method comments and code example over old-way hardcore documentation. I seriously believe pharo would greatly benefit from a wiki and would help taking it more seriously. Or at least an included documentation tool inside pharo that will make documentation much easier. I mentioned wikibooks because its based on already highly successful popular technology. If you have better recommendation I am open to any ideas. So in short yes I will comment class/methods of Nativeboost and yes I will contribute to wikibooks as well. Camillo Bruni-3 wrote > I like to see people contributing :), maybe you could do some contribution > on the code-side? > > I personally consider well written, executable examples more valuable than > written documentation outside the image. And I think NativeBoost could > benefit from some in-image documentation. > > > On 2013-07-02, at 14:39, kilon < > thekilon@.co > > wrote: >> And I love pharo and what you guys have created , a lot of fun and very >> productive. So yes I will definitely help you out in documenting NB. >> >> Actually my idea was not to publish in a blog. I hate blogs though I have >> one I just find it very non flexible so I was thinking instead wikibooks >> . >> >> http://en.wikibooks.org/wiki/Help:Contributing >> <http://en.wikibooks.org/wiki/Help:Contributing> >> >> I was thinking moving the entire nativeboost docs (pdf/latex) to wiki >> books >> so I make it much easier for everyone can contribute. Wikibooks uses >> Mediawiki which I am familiar with from the blender wiki when I was >> making >> my python book >> >> http://wiki.blender.org/index.php/User:Kilon/Python_book_of_magic >> <http://wiki.blender.org/index.php/User:Kilon/Python_book_of_magic> >> >> Mediawiki is nowhere near as powerful as latex but its way easier to >> learn >> and it literally takes minutes to learn the syntax and you dont need a >> special editor you can do it online directly with minimum syntax. This >> way >> everyone can contribute , it only needs an account. >> >> >> >> StÃ©phane Ducasse wrote >>> I love your questions! >>> When you will get all your anwsers you have to write a blog about it so >>> that we can use that in >>> a chapter so that every body can know how to do it. >>> >>> Just no time to think right now :( sadly >>> >>> Stef >>> >>> On Jul 1, 2013, at 8:40 PM, kilon < >> >>> thekilon@.co >> >>> > wrote: >>> >>>> Thanks Igor , yes I was aware of String Cr because I have done some >>>> googling >>>> around and it did find information on the subject. Apparently it failed >>>> because I had an error in my source. >>>> >>>> So for our next challenge is learning how to fetch data that a pointer >>>> points to. >>>> >>>> in this case I have an array that contains my vertex positions , called >>>> vertexPositions >>>> >>>> vertexPositions >>>> "the positions of vertices to be passed to opengl" >>>> >>>> ^ #( 0.75 0.75 0.0 1.0 >>>> 0.75 -0.75 0.0 1.0 >>>> -0.75 -0.75 0.0 1.0 ) >>>> >>>> so far so good >>>> >>>> so I create a pointer for that array >>>> >>>> vptrsize := (NBExternalType sizeOf: 'float')* self vertexPositions >>>> size. >>>> >>>> and then take that pointer and insert in each position the individual >>>> values >>>> from vertexPositions >>>> >>>> vertexPositions withIndexDo: [:each :i | >>>> "using nbUInt32AtOffset because we know pointer is 4 bytes :) " >>>> vpos nbFloat32AtOffset: (i-1)*(NBExternalType sizeOf: 'float') >>>> put: >>>> each value. >>>> Transcript show: ' I am putting to vpos in index: '; show: i-1; show:' >>>> value: '; show: each value; cr. >>>> ]. >>>> >>>> so far so good. >>>> >>>> now the tricky part is that I have a function that expects that Array , >>>> not >>>> the smalltalk version but the C version we just created >>>> >>>> gl bufferData_target: GL_ARRAY_BUFFER size: vptrsize data: ....... >>>> usage: >>>> GL_STATIC_DRAW. >>>> >>>> where you see the dots is where I should pass the data, in this case >>>> the >>>> C >>>> array >>>> >>>> I could do a vpo nbFloat32AtOffset: but that will return me only the >>>> individual value at the specific point (index) of the array, while I >>>> want >>>> to >>>> pass the entire array. >>>> >>>> So how I do that ? >>>> >>>> I explored NBExternalAdress and I cant find something that would return >>>> an >>>> array. Am I missing something obvious here ? >>>> >>>> NBExternalAdress value , returns the number of the address and not that >>>> data >>>> contained in that address. >>>> >>>> I also see a NBExternalArray but I am not sure if it is what I should >>>> be >>>> using . >>>> >>>> Igor Stasenko wrote >>>>> On 30 June 2013 21:11, kilon < >>>> >>>>> thekilon@.co >>>> >>>>> > wrote: >>>>>> I am not going to post my code here cause it has become too big , you >>>>>> can >>>>>> find it here >>>>>> >>>>>> http://www.smalltalkhub.com/#!/~kilon/GLTutorial >>>>>> <http://www.smalltalkhub.com/#!/~kilon/GLTutorial> >>>>>> >>>>>> I tried adding newlines with String cr to my shaders strings, but >>>>>> apparently >>>>>> opengl is not convinced. It looks like smalltalk cr is not converted >>>>>> to >>>>>> C >>>>>> "\n" newlines. So how I do that ? >>>>>> >>>>> >>>>> simply replace all occurences of >>>>> Character cr >>>>> with >>>>> Character lf >>>>> (or crlf, if it wants that) >>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://forum.world.st/Understanding-NBOpenGL-tp4686514p4696465.html >>>>>> Sent from the Pharo Smalltalk Developers mailing list archive at >>>>>> Nabble.com. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko. >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://forum.world.st/Understanding-NBOpenGL-tp4686514p4696666.html >>>> Sent from the Pharo Smalltalk Developers mailing list archive at >>>> Nabble.com. >>>> >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Understanding-NBOpenGL-tp4686514p4696807.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> -- View this message in context: http://forum.world.st/Understanding-NBOpenGL-tp4686514p4696870.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 2, 2013

Re: [Pharo-dev] [PROVENANCE INTERNET] Re: FileSystem Permissions

by Goubier Thierry

Hi Lewis, we have already this in a way; Pharo provides the permissions as per stat in fact, but probably not the uid/guid of the file which would allow for a real check of the permissions. (that is, the current (wrong) situation is that isReadable returns ownerCanRead, which has a strong chance of being wrong for a directory owned by root, as you can guess) As you can see, I was wrong in asking for stat/fstat... But thanks for the info. Thierry Le 02/07/2013 16:32, David T. Lewis a Ã©crit : > On Tue, Jul 02, 2013 at 04:05:18PM +0200, Camillo Bruni wrote: >> >> On 2013-07-02, at 16:05, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >>> >>> >>> Le 02/07/2013 15:49, Goubier Thierry a ?crit : >>>> Done: >>>> >>>> SLICE-Issue-11102-FileSystemError-Path--root-ThierryGoubier.1 >>>> >>>> In http://ss3.gemstone.com/ss/PharoInbox >>>> >>>> (It's for 2.0 at the moment. I'll try on 3.0 to port the same code). >>> >>> Oh, it has a problem with utf8 :( >> >> and most probably it won't work under OSX. >> >> I think you have to implement these primitives on the different platform specific stores, >> that implies a separate version for win/mac/linux > > Both the concept and the implementation will be different on Windows, > but for Unix and OS X you can use this for reference: > > UnixOSProcessPlugin>>primitiveFileStat > "Call stat(2) to obtain the file protection mask for a file. Answer errno on failure, > or on success answer an array with: UID with: GID with: protectionMask. The > protectionMask is an Array of four integers representing the protection mask, or > answer errno on failure. The protection mask is four Integers, each of which may > be considered an octal digit (0-7), with bit values 4, 2, and 1. The first digit selects > the set user ID (4) and set group ID (2) and save text image (1) attributes. The second > digit selects permissions for the user who owns the file: read (4), write (2), and > execute (1); the third selects permissions for other users in the file's group, with > the same values; and the fourth for other users not in the file's group, with the > same values." > > For example: > > OSProcess accessor fileStat: '/etc/hosts' > > Dave > > > > -- 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

July 2, 2013

[update 3.0] #30242

by Esteban Lorenzano

30242 ----- 11010 The class Trait must use the trait TClass https://pharo.fogbugz.com/f/cases/11010/ (pass 3, final :) ) Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Traits-EstebanLorenzano.528.d…

July 2, 2013

Re: [Pharo-dev] [PROVENANCE INTERNET] Re: FileSystem Permissions

by David T. Lewis

On Tue, Jul 02, 2013 at 04:05:18PM +0200, Camillo Bruni wrote: > > On 2013-07-02, at 16:05, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > > > > > Le 02/07/2013 15:49, Goubier Thierry a ?crit : > >> Done: > >> > >> SLICE-Issue-11102-FileSystemError-Path--root-ThierryGoubier.1 > >> > >> In http://ss3.gemstone.com/ss/PharoInbox > >> > >> (It's for 2.0 at the moment. I'll try on 3.0 to port the same code). > > > > Oh, it has a problem with utf8 :( > > and most probably it won't work under OSX. > > I think you have to implement these primitives on the different platform specific stores, > that implies a separate version for win/mac/linux Both the concept and the implementation will be different on Windows, but for Unix and OS X you can use this for reference: UnixOSProcessPlugin>>primitiveFileStat "Call stat(2) to obtain the file protection mask for a file. Answer errno on failure, or on success answer an array with: UID with: GID with: protectionMask. The protectionMask is an Array of four integers representing the protection mask, or answer errno on failure. The protection mask is four Integers, each of which may be considered an octal digit (0-7), with bit values 4, 2, and 1. The first digit selects the set user ID (4) and set group ID (2) and save text image (1) attributes. The second digit selects permissions for the user who owns the file: read (4), write (2), and execute (1); the third selects permissions for other users in the file's group, with the same values; and the fourth for other users not in the file's group, with the same values." For example: OSProcess accessor fileStat: '/etc/hosts' Dave

July 2, 2013

Re: [Pharo-dev] [Pharo-project] Understanding NBOpenGL

by kilon

Igor got you will try to avoid using #sizeOf: , even for a readability I can replace it with a simple method returning the same thing depending in platform. Now because I am confused lets clarify how the whole things works because I see many errors in my code and clearly I don't understand how Nativeboost works. Note I am a C noob , so excuse me if I say anything stupid here. As far as functions call are concerned I see 3 possible scenariors a ) function(int var). Here the C function expects a simple variable of some type (int in this case) according to what you told me to make such variable I will do var := Nativeboost allocate:( NBExternalType typeof:'int') if I want to pass a value in that variable then I will do var nbInt32AtOffset: 0 put: 6 will call that function with Object function: var b) function(int* var) how I create the variable (pointer) ? how I put value in the variable (pointer) ? c) function( &var) Now I assume I will create a var variable same way as (a) var := Nativeboost allocate:( NBExternalType typeof:'int') but how I pass the address of var to the function ? I read the pdf of nativeboost but It did not clarify those things or simply I did not understand. Thanks on the instructions about NBExternalArray. So the reason of using this object is for convenience ? Igor Stasenko wrote > On 1 July 2013 20:40, kilon < > thekilon@.co > > wrote: >> Thanks Igor , yes I was aware of String Cr because I have done some >> googling >> around and it did find information on the subject. Apparently it failed >> because I had an error in my source. >> >> So for our next challenge is learning how to fetch data that a pointer >> points to. >> >> in this case I have an array that contains my vertex positions , called >> vertexPositions >> >> vertexPositions >> "the positions of vertices to be passed to opengl" >> >> ^ #( 0.75 0.75 0.0 1.0 >> 0.75 -0.75 0.0 1.0 >> -0.75 -0.75 0.0 1.0 ) >> >> so far so good >> >> so I create a pointer for that array >> >> vptrsize := (NBExternalType sizeOf: 'float')* self vertexPositions size. >> >> and then take that pointer and insert in each position the individual >> values >> from vertexPositions >> >> vertexPositions withIndexDo: [:each :i | >> "using nbUInt32AtOffset because we know pointer is 4 bytes :) >> " >> vpos nbFloat32AtOffset: (i-1)*(NBExternalType sizeOf: >> 'float') put: >> each value. >> Transcript show: ' I am putting to vpos in index: '; show: i-1; >> show:' >> value: '; show: each value; cr. >> ]. >> >> so far so good. >> > > just one small advice: do not use #sizeOf: sparingly.. it parsing the > type > and doing full type resolution when you do that. > you can remember the size of the type you need at boot/startup time, > there is no chance > it can change within same session :) > > but of course for demonstration purposes and readability it good. > >> now the tricky part is that I have a function that expects that Array , >> not >> the smalltalk version but the C version we just created >> >> gl bufferData_target: GL_ARRAY_BUFFER size: vptrsize data: ....... >> usage: >> GL_STATIC_DRAW. >> >> where you see the dots is where I should pass the data, in this case the >> C >> array >> >> I could do a vpo nbFloat32AtOffset: but that will return me only the >> individual value at the specific point (index) of the array, while I want >> to >> pass the entire array. >> >> So how I do that ? >> >> I explored NBExternalAdress and I cant find something that would return >> an >> array. Am I missing something obvious here ? >> > > just pass NBExternalAdress instance as argument and you done. > >> NBExternalAdress value , returns the number of the address and not that >> data >> contained in that address. >> >> I also see a NBExternalArray but I am not sure if it is what I should be >> using . >> > > arrayClass := NBExternalArray ofType: 'float'. > array := arrayClass new: 5. "or externalNew:5 , if you want to > allocate it in external memory" > > array at: 1 put: 10.1 "use just like normal Array" > > to pass it to function use: > > self soemFunction: array address. > >> Igor Stasenko wrote >>> On 30 June 2013 21:11, kilon < >> >>> thekilon@.co >> >>> > wrote: >>>> I am not going to post my code here cause it has become too big , you >>>> can >>>> find it here >>>> >>>> http://www.smalltalkhub.com/#!/~kilon/GLTutorial >>>> <http://www.smalltalkhub.com/#!/~kilon/GLTutorial> >>>> >>>> I tried adding newlines with String cr to my shaders strings, but >>>> apparently >>>> opengl is not convinced. It looks like smalltalk cr is not converted to >>>> C >>>> "\n" newlines. So how I do that ? >>>> >>> >>> simply replace all occurences of >>> Character cr >>> with >>> Character lf >>> (or crlf, if it wants that) >>> >>>> -- >>>> View this message in context: >>>> http://forum.world.st/Understanding-NBOpenGL-tp4686514p4696465.html >>>> Sent from the Pharo Smalltalk Developers mailing list archive at >>>> Nabble.com. >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Understanding-NBOpenGL-tp4686514p4696666.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> > > > > -- > Best regards, > Igor Stasenko. -- View this message in context: http://forum.world.st/Understanding-NBOpenGL-tp4686514p4696858.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 2, 2013