July 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] question about UI

by StÃ©phane Ducasse

> hello list. I am thinking develop a business application in pharo. Excellent! > I need information about tools for UI for business applications. for example dolphin has MVP framework for desktop. Yes and its MVP framework is cool. > I prefer browser/desktop enable UI framework. Which are the tools you can recommend? You should have a look at Spec - ben I do not remember where is the tutorial. Benjamin started to rewrite widgets like list. > Perhaps someone has experience with businnes app. Esteban, benjamin. What I suggest is to really ask for feedback in the mailing-list and to be prepared to help also because we are changing the widgets and the tools (and the underlying layers but our time is short). > > TIA > PD: Sorry for my english :) Frankly this is not important. > > > Ing. Pablo Digonzelli > Sofware Solutions > IP Soluciones SRL > > 25 de Mayo 521. Entrepiso A > email: pdigonzelli(a)softsargentina.com > email: pdigonzelli(a)gmail.com > twitter: @pdigonzelli > Tel: 0381 4227378 > Cel: 0381 155982714 >

July 2, 2013

question about UI

by Pablo R. Digonzelli

hello list. I am thinking develop a business application in pharo. I need information about tools for UI for business applications. for example dolphin has MVP framework for desktop. I prefer browser/desktop enable UI framework. Which are the tools you can recommend? Perhaps someone has experience with businnes app. TIA PD: Sorry for my english Ing. Pablo Digonzelli Sofware Solutions IP Soluciones SRL 25 de Mayo 521. Entrepiso A email: pdigonzelli(a)softsargentina.com email: pdigonzelli(a)gmail.com twitter: @pdigonzelli Tel: 0381 4227378 Cel: 0381 155982714

July 2, 2013

Re: [Pharo-dev] [update 3.0] #30239

by StÃ©phane Ducasse

>> >> Anyone ever check these diffs? I see the following: >> > Yes, this is a known bug that needs to be fixed. Yes I hope nicolas has it on its list :). > > Marcus > >

July 2, 2013

Re: [Pharo-dev] Metacello doubt

by Guido Chari

Ok, i will follow the issue on github. Thanks! 2013/7/1 Dale K. Henrichs <dale.henrichs(a)gemtalksystems.com> > Guido, > > I created a test case and it turns out that there _is_ a bug in the bypass > lock logic[1] . I'm going to push out a new version of the Metacello > Preview (1.0.0-beta.32.8) in the next day or so and the bugfix for Issue > #174 will _not_ be included in that release ... > > Dale > > [1] https://github.com/dalehenrich/metacello-work/issues/174 > > ------------------------------ > > *From: *"Guido Chari" <charig(a)gmail.com> > *To: *"Pharo Development List" <pharo-dev(a)lists.pharo.org> > *Sent: *Thursday, June 27, 2013 10:23:33 AM > *Subject: *Re: [Pharo-dev] Metacello doubt > > I'm in. > > > 2013/6/26 Dale K. Henrichs <dale.henrichs(a)gemtalksystems.com> > >> >> >> ------------------------------ >> >> *From: *"Guido Chari" <charig(a)gmail.com> >> *To: *"Pharo Development List" <pharo-dev(a)lists.pharo.org> >> *Sent: *Wednesday, June 26, 2013 2:49:09 PM >> >> *Subject: *Re: [Pharo-dev] Metacello doubt >> >> I understood. Thanks for the answer Dale. The drawback in this case is to >> specify a particular dependency to AsmJit in my configuration. Also, >> perhaps is the right way since i realized i have a particular dependency on >> it. >> >> But this discussion makes me thing a little and so i have a new question. >> >> Form what I (mis) undestand from Metacello, when asking for a >> bleedingEdge version it loads only the baseline that specifies packages and >> then last version of every package specified there. >> >> As in the projects referenced on the baseline there is no need for >> specifying a version, and that's the case of nativeBoost configuration, >> wouldn't it be interesting to have some behavior (i mean i new method for >> loading like loadDeepSymbolic:) that not only load the symbolicVersion of >> the package asked, but also propagate that symbolicVersion (bleedingEdge in >> this case) to all the dependencies that don't specify a concrete version? >> >> Guido. >> >> Guido, >> >> With the Metacello Scripting API[1] I've taken a slightly different tack, >> but I think that it gets you to the same place. >> >> I am a big fan of deterministic loads, but I know that from a practical >> point of view developers need to have a certain amount of control over >> exactly what gets loaded into their DEVELOPMENT environments and they need >> to be able to exert this control without having to resort to editing >> configurations to match their specific requirements. >> >> I have accomplished this by arranging for a Notification to be signalled >> whenever a project is referenced during a load. The developer can use one >> or more of the onUpgrade:, onDowngrade: and onConflict: clauses in their >> load scripts to exert fine control over what happens on a project by >> project basis ... >> >> For your specific use case, I would think that you would want to use the >> `lock` command[2] and specify that you want to `lock` the projects >> (NativeBoost and AsmJit) to the #bleedingEdge version. I don't recall if >> I've got test cases for symbolic versions, but if you are seriously >> interested in taking the Scripting API for a spin, I'd be willing to write >> some additional tests using the #bleedingEdge symbolic version (if not >> already covered) and validate this use case... >> >> I am entering a phase where I will be doing some work on getting FileTree >> and Metacello up to snuff for Pharo3.0 so this would be a good time for me >> to add some test cases in anticipation of having some interested users ... >> >> I haven't released the Scripting API, because I need to have real users >> with real use cases take the API for a spin and validate the API. The >> Scripting API can be loaded into any version of Pharo/Squeak/GemStone and I >> think the Scripting API is (or will be) available in Pharo3.0. >> >> I'm looking forward to getting feedback as to how the API stands up to >> real use ... >> >> So let me know if you are interested in being another Scripting API >> guinea pig:) >> >> Dale >> >> [1] >> https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… >> [2] >> https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… >> >> > >

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… 1 regressions found. Tests.CodeImport.ChunkImportTestCase.testImportAClassCategory

July 2, 2013

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

by Igor Stasenko

On 2 July 2013 16:27, kilon <thekilon(a)yahoo.co.uk> wrote: > 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 > you found very interesting way to pass simple integer to function :) if your function is 'function(int var)' you call it directly: someobject function: 5 x := 10. someobject function: x etc.. > b) function(int* var) > > how I create the variable (pointer) ? > > how I put value in the variable (pointer) ? > pointer = address on memory which holding some value. every time you see '*', it means that function expects pointer. And of course, since that function will write or read from that memory location, it is your responsibility to provide a pointer to valid data, with enough size etc. So, the way how you did for first case, is actually applicable for this case. But it is not necessary to use externally allocated memory. Sometimes you can safely use object memory, e.g.: buffer := ByteArray new: 4. someobject function: buffer. > c) function( &var) > did you meant 'int &var'? because otherwise it is not correct declaration. > 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 ? > this is reference (more from C++).. which in fact just a syntactic sugar, function still expecting pointer (so consider this to be same as *var) > > 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 ? > Of course. It is more convenient to deal with array of typed elements (of type you need), than manually deal with bunch of raw bytes. > > 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. > -- Best regards, Igor Stasenko.

July 2, 2013

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

by Camillo Bruni

On 2013-07-02, at 18:41, GOUBIER Thierry <thierry.goubier(a)cea.fr> wrote: > Thanks Lewis, > > my bad. Everything needed is in there, even examples :) Cool. Now, there is still a problem with utf8 in path names, but I suspect it's inside FileReference. > > Thierry yup :/ https://pharo.fogbugz.com/default.asp?2486#73430

July 2, 2013

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

by Jan Vrany

On 02/07/13 17:41, GOUBIER Thierry wrote: > Thanks Lewis, > > my bad. Everything needed is in there, even examples :) Cool. Now, there is still a problem with utf8 in path names, but I suspect it's inside FileReference. File names as kind of tricky under linux because it is not defined in which encoding the filenames are. The name is just a sequence of bytes. The safe way is check for "system" encoding using nl_langinfo(CODESET) and encode/decode strings passed to and from OS to whatever internal representation is used to store strings. So far this works good on our systems. On Windows its lot easier as pathnames are always encoded in Unicode :-) Cheers, Jan > > Thierry > ________________________________________ > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de David T. Lewis [lewis(a)mail.msen.com] > Date d'envoi : mardi 2 juillet 2013 17:59 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] [PROVENANCE INTERNET] Re: FileSystem Permissions > > Hi Thierry, > > You were right in asking for stat/fstat. The unix stat() call provides the > uid and gid of the file, so those values are provided by primitiveFileStat. > In order to determine if the file is e.g. readable, you need that information > along with the file protection mask (also provided by primitiveFileStat), > and of course you need to know the uid and gid of your VM process, see > primitiveGetUid, primitiveGetGid, primitiveGetEUid and primitiveGetEGid > in UnixOSProcessPlugin. > > There are also some unit tests that show how this works, for example: > > UnixProcessAccessorTestCase>>testIsReadableForUserInGroup > > > I'm not sure if this helps with your original question, but maybe it > will help as a reference. > > Dave > > > On Tue, Jul 02, 2013 at 04:46:25PM +0200, Goubier Thierry wrote: >> 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] #30244

by Esteban Lorenzano

30244 ----- 11114 Missing methods after make Trait use TClass https://pharo.fogbugz.com/f/cases/11114/ Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Traits-EstebanLorenzano.534.d…

July 2, 2013

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

by GOUBIER Thierry

Thanks Lewis, my bad. Everything needed is in there, even examples :) Cool. Now, there is still a problem with utf8 in path names, but I suspect it's inside FileReference. Thierry ________________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de David T. Lewis [lewis(a)mail.msen.com] Date d'envoi : mardi 2 juillet 2013 17:59 Ã : Pharo Development List Objet : Re: [Pharo-dev] [PROVENANCE INTERNET] Re: FileSystem Permissions Hi Thierry, You were right in asking for stat/fstat. The unix stat() call provides the uid and gid of the file, so those values are provided by primitiveFileStat. In order to determine if the file is e.g. readable, you need that information along with the file protection mask (also provided by primitiveFileStat), and of course you need to know the uid and gid of your VM process, see primitiveGetUid, primitiveGetGid, primitiveGetEUid and primitiveGetEGid in UnixOSProcessPlugin. There are also some unit tests that show how this works, for example: UnixProcessAccessorTestCase>>testIsReadableForUserInGroup I'm not sure if this helps with your original question, but maybe it will help as a reference. Dave On Tue, Jul 02, 2013 at 04:46:25PM +0200, Goubier Thierry wrote: > 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