- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] UnifiedFFI Docs

by Todd Blanchard

https://pharo.fogbugz.com/f/cases/20574/FFITypeArray-annonymousClassCreator… <https://pharo.fogbugz.com/f/cases/20574/FFITypeArray-annonymousClassCreator…> There you go. > On Oct 22, 2017, at 2:42 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > >> On 21 Oct 2017, at 21:15, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Esteban will probably reply to this thread > > yes, I will :) > >> >> >> On Thu, Oct 19, 2017 at 10:34 PM, Todd Blanchard <tblanchard(a)mac.com> wrote: >>> I have found the problem with VoidPointer3 generating accessors. > > can you report that on fogbugz ? > (along with your solution) > > thanks! > Esteban > >>> >>> No idea how to contribute back a fix but this is what I've found. >>> >>> FFITypeArrayType>>annonymousClassCreator >>> ^ String streamContents: [ :stream | >>> stream >>> nextPutAll: '(FFITypeArray ofType: '; >>> print: (self objectClass type isPointer ifTrue: [self externalTypeWithArity >>> printString] ifFalse: ['#',self objectClass type class]); >>> nextPutAll: ' size: '; >>> print: self objectClass numberOfElements; >>> nextPutAll: ')' ] >>> >>> Recalling that we are trying to come up with an accessor that can pull out a >>> void*[3], this produces >>> >>> '(FFITypeArray ofType: #FFIVoid size: 3)' >>> >>> which produces an error as FFIVoid's size is undefined. In general, this >>> will be wrong for any pointer type and will probably get the size >>> calculation wrong. >>> >>> Doing a little digging I find that >>> >>> FFITypeArray>>ofType: aType size: aSize >>> >>> delegates resolution of aType to FFIExternalType>>resolveType:aType and this >>> can take all kinds of different things including the native type name. >>> >>> It would be better if this generated the native name for pointers. >>> >>> (FFITypeArray ofType: 'void*' size: 3) >>> >>> So I changed it to: >>> >>> FFITypeArrayType>>annonymousClassCreator >>> ^ String streamContents: [ :stream | >>> stream >>> nextPutAll: '(FFITypeArray ofType: '; >>> print: (self objectClass type isPointer >>> ifTrue: [self externalTypeWithArity printString] >>> ifFalse: ['#',self objectClass type class]); >>> nextPutAll: ' size: '; >>> print: self objectClass numberOfElements; >>> nextPutAll: ')' ] >>> >>> and this seems to work fine. >>> >>> Onwards... >>> >>> On Oct 19, 2017, at 7:18 AM, Todd Blanchard <tblanchard(a)mac.com> wrote: >>> >>> Thatâs great - itâs been kind of magical but a couple things have changed >>> since you wrote it and some bugs have crept into ffi. >>> >>> Right now Iâm finding the generated accessor for the VoidPointer3 is >>> actually generating a void 3 accessor and that doesnât work. I spent all day >>> yesterday tracking it to the accessor generating code. >>> >>> Sent from the road >>> >>> On Oct 18, 2017, at 22:29, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> >>> >>> On Thu, Oct 19, 2017 at 1:05 AM, Todd Blanchard <tblanchard(a)mac.com> wrote: >>>> >>>> I'm working through Ben's great blog post about playing with libclang and >>>> I am puzzled by something. >>> >>> >>> Thx Todd. Knowing someone is looking at it encourages me to expand it. >>> I'm interested in looking at your specific questions, but it might not be >>> until next week after this stint of long work days. >>> >>> cheers -ben >>> >>> >>>> >>>> >>>> invalidateSessionData >>>> handle atAllPut: 0. >>>> >>>> zero;s out the handle. Cool. However, >>>> >>>> handle isNull >>>> >>>> does not return true despite it being used in the getString method as >>>> >>>> ^ handle isNull >>>> ifTrue: ['external memory invalidated by session restart'] >>>> ifFalse:[LibClang clang_getCString__cxString: self]. >>>> >>>> Looks like there should be an isNull on ByteArray that returns true if all >>>> bytes are zero but it isn't there. Was it dropped for some reason? >>>> >>>> >>>> >>>> On Oct 18, 2017, at 2:58 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> >>>> wrote: >>>> >>>> Sure the documentation could be better, that is definetly important, but >>>> is already good enough and UFFI is a very technical subject much more suited >>>> to a mailing list . Its not physical possible to cover the massive potential >>>> of UFFI. >>>> >>>> On Wed, Oct 18, 2017 at 9:32 AM Stephane Ducasse <stepharo.self(a)gmail.com> >>>> wrote: >>>>> >>>>> Please do not hesitate to do Pull Requests. >>>>> Luc told me that he wants to do a pass on it and Esteban promises that to >>>>> me >>>>> but he is super busy. >>>>> >>>>> Stef >>>>> >>>>> >>>>> On Wed, Oct 18, 2017 at 5:54 AM, Todd Blanchard <tblanchard(a)mac.com> >>>>> wrote: >>>>>> Wonderful! Thanks. >>>>>> >>>>>>> On Oct 17, 2017, at 3:45 PM, stephan <stephan(a)stack.nl> wrote: >>>>>>> >>>>>>> On 17-10-17 23:06, Todd Blanchard wrote: >>>>>>>> Anyone know what happened to this? >>>>>>>> >>>>>>>> https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… >>>>>>> >>>>>>> https://github.com/SquareBracketAssociates/Booklet-uFFI >>>>>>> >>>>>>> has a link to a bintray pdf download >>>>>>> >>>>>>> Stephan >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >>> >> > >

Oct. 24, 2017

Re: [Pharo-dev] Bloc status

by Sean P. DeNigris

Tudor Girba-2 wrote > right now we have three such "real life scenariosâ that you can play with: Are these safe to load in a working image? IOW could one switch back and forth between the standard and experimental toolset? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 24, 2017

Re: [Pharo-dev] Bloc Feedback

by Sean P. DeNigris

Tudor Girba-2 wrote > Thanks for the feedback! But of course! Thanks for pushing Bloc :) IMHO a clean low-level graphics framework is the linchpin to unleash a tremendous amount of creativity in the Pharo community. I have several dream projects that I placed on long-term hold after getting stuck in Morphic quicksand :/ Tudor Girba-2 wrote >> - How would one do e.g. a ticking clock in Bloc? The only possibly >> relevant >> example I see is BlAnimatedCursor. Is that a typical usage? One thing >> that >> I'm not sure how to translate to a BlElement is that the cursor seems to >> be >> responsible for starting and stopping the animation via #activateOn:, >> which >> doesn't exist for an element. How would one prevent an element's >> animation >> from continuing to run after a space was closed? > What do you mean? I guess I mean what is the Bloc version of #step that would enable us to do e.g. Squeak's mouse-eyes-tracking-the-cursor or Lively Kernel's clock: <http://forum.world.st/file/t128965/Chromium5.png> Tudor Girba-2 wrote >> - BlElement has 278 instance-side methods. A frequent battle cry against >> Morphic was the bloated Morph class with 899. Definitely an improvement, >> but >> are we "there yetâ? > What do you mean? Is there a consensus on a maximum number of instance-side methods before a class becomes impossible to understand, and if so where does BlElement fall on that scale? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 24, 2017

Re: [Pharo-dev] [Seaside] [ANN] SeasideTesting recovered from oblivion

by Johan Brichau

I donât know... we maintained SeasideTesting at http://smalltalkhub.com/#!/~Seaside/SeasideTesting/ until we developed Parasol because it just covers some bare-bones html page testing. Forget about JavaScript and css influence on your tests in seaside testing. I think we prefer a slower but accurate testing proces, using Parasol. Johan > On 23 Oct 2017, at 22:22, Jon Paynter <kittle31(a)gmail.com> wrote: > > Great to hear! > > I use this on some older projects, and found the documentation helpful, but also sketchy. Hopefully you can update things. > > Will your resurected version work with Visualworks? > >> On Mon, Oct 23, 2017 at 3:04 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> >> I spend some days last week woking with the guys of AFI (http://afi-sa.fr, yes they also use Pharo in some of their projects) and together we recovered SeasideTesting from Davis Shaffer to be used for their TDD experience. >> >> you can check it out here: https://github.com/Afibre/SeasideTesting >> >> Whatâs SeasideTesting? A package to test Seaside components. >> Why we do not use Parasol? Because it is based on selenium and that makes the process slow. >> Where can I know more? >> - there is some documentation here (for VW, I think): http://www.shaffer-consulting.com/david/Seaside/TestingComponents/TestingCo… >> - some slides here (on squeak): http://esug.org/data/ESUG2005/Wednesday/2005-ESUG-Shaffer.pdf >> but all that is old. Best way is to just install and see the tests, as always, >> >> >> cheers! >> Esteban >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Oct. 23, 2017

Re: [Pharo-dev] [ANN] SeasideTesting recovered from oblivion

by Stephane Ducasse

It will be a good candidate when I will convert the Seaside book to pillar. Tx On Mon, Oct 23, 2017 at 12:04 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > I spend some days last week woking with the guys of AFI (http://afi-sa.fr, > yes they also use Pharo in some of their projects) and together we recovered > SeasideTesting from Davis Shaffer to be used for their TDD experience. > > you can check it out here: https://github.com/Afibre/SeasideTesting > > Whatâs SeasideTesting? A package to test Seaside components. > Why we do not use Parasol? Because it is based on selenium and that makes > the process slow. > Where can I know more? > - there is some documentation here (for VW, I think): > http://www.shaffer-consulting.com/david/Seaside/TestingComponents/TestingCo… > - some slides here (on squeak): > http://esug.org/data/ESUG2005/Wednesday/2005-ESUG-Shaffer.pdf > but all that is old. Best way is to just install and see the tests, as > always, > > > cheers! > Esteban

Oct. 23, 2017

Re: [Pharo-dev] XPath chapter...

by J.F. Rick

Nice! On Sun, Oct 22, 2017 at 11:53 PM HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > I don't know for Pharo development, but I used XPath in Pharo for > getting a textual description of gene ontology terms, for example: > > #('GO:0005623' 'GO:0017071' 'GO:0030680') do: [ : goTerm | > | xPath xmlDoc quickGO | > quickGO := ' > http://www.ebi.ac.uk/QuickGO-Old/GTerm?id={1}&format=oboxml' > format: { goTerm }. > xmlDoc := (XMLDOMParser on: (ZnEasy get: quickGO) contents) > parseDocument. > xPath := XPath for: 'normalize-space(/obo/term/name/text())' in: > xmlDoc. > Transcript show: goTerm; tab; show: xPath; cr ]. > > Here you've got similar code in Perl and Java so you can compare: > > https://www.ebi.ac.uk/QuickGO-Old/clients/download-term.pl > https://www.ebi.ac.uk/QuickGO-Old/clients/DownloadTerm.java > > Best regards, > > HernÃ¡n > > > > 2017-10-21 14:04 GMT-03:00 J.F. Rick <self(a)je77.com>: > > NICE! I was just using XPath for Selenium testing. It is really great for > > that application (commanding a browser like Firefox or Chrome to simulate > > user actions). What are the applications for XPath in Pharo? Unit > testing of > > generating markup? > > > > Cheers, > > > > Jeff > > > > PS After spending significant time with other languages at work, I really > > have an appreciation of how wonderful Pharo is as a development > environment. > >

Oct. 23, 2017

[Pharo 7.0-dev] Build #220: SUCCESS

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #220 was: SUCCESS. Could not extract further issue information from commit message: Should good to me. Like that we can have something symmetrical. Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 23, 2017

[Pharo 7.0-dev] Build #219: SUCCESS

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #219 was: SUCCESS. Could not extract further issue information from commit message: some simple renames of instance variables. Looks good. Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 23, 2017

[Pharo 7.0-dev] Build #218: SUCCESS

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #218 was: SUCCESS. Could not extract further issue information from commit message: 20564-Spec-Core-must-be-Morphic-independent Reviewed with Pavel and this led to some new issues :). To be handled soon. Stef and Pavel Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 23, 2017

Re: [Pharo-dev] PharoLauncher - uninformative Pharo7 template names

by stephan

Anything changed here? Stephan

Oct. 23, 2017