October 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Bloc Feedback

by Tudor Girba

Hi Sean, > On Oct 25, 2017, at 2:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Aliaksei Syrel wrote >> I don't understand how you guys find these kind of bugs :D > > We have a talent for destruction ;) > > > Aliaksei Syrel wrote >> Aha, I forgot about it, thanks! At this point BlTextEditElement is only >> used internally by Moldable Editor so I will probably move it away from >> Bloc. > > Ah, okay. IHMO at least a basic editable text morph (and ideally a real > editor morph as well) is essential to people starting to > play/experiment/test Bloc for real. I think there is a misunderstanding. We distinguish between Bloc and Brick: - Bloc offers the basic management of graphical elements (including layouts, measurements, transformation etc) - Brick offers widgets In Bloc, there exists a basic text widget, but the full fledged moldable editor is part of Brick. While it is important to have Bloc as a generic infrastructure, coming from Morphic you just can look at Bloc and Brick as being one. Doru > Aliaksei Syrel wrote >> Thanks for the feedback :) > > Sure! Any thoughts on this: >> 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?â¦ 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> > > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- www.tudorgirba.com www.feenk.com "Being happy is a matter of choice."

Oct. 25, 2017

Re: [Pharo-dev] UnifiedFFI Docs

by Esteban Lorenzano

:) Did you look at this project: https://github.com/estebanlm/libclang-pharo-bindings/ <https://github.com/estebanlm/libclang-pharo-bindings/> ? it was using parseTranslationUnit (no 2)â¦ there you can find how is being used (I just converted it to tonel format, but older versions are in filetree) Esteban > On 24 Oct 2017, at 19:17, Todd Blanchard <tblanchard(a)mac.com> wrote: > > Hey Esteban, > > Now that you have outed yourself as a maintainer of FFI, I have a question. :-) > > I want to call the libclang function: > > /** > * \brief Parse the given source file and the translation unit corresponding > * to that file. > * > * This routine is the main entry point for the Clang C API, providing the > * ability to parse a source file into a translation unit that can then be > * queried by other functions in the API. This routine accepts a set of > * command-line arguments so that the compilation can be configured in the same > * way that the compiler is configured on the command line. > * > * \param CIdx The index object with which the translation unit will be > * associated. > * > * \param source_filename The name of the source file to load, or NULL if the > * source file is included in \c command_line_args. > * > * \param command_line_args The command-line arguments that would be > * passed to the \c clang executable if it were being invoked out-of-process. > * These command-line options will be parsed and will affect how the translation > * unit is parsed. Note that the following options are ignored: '-c', > * '-emit-ast', '-fsyntax-only' (which is the default), and '-o \<output file>'. > * > * \param num_command_line_args The number of command-line arguments in > * \c command_line_args. > * > * \param unsaved_files the files that have not yet been saved to disk > * but may be required for parsing, including the contents of > * those files. The contents and name of these files (as specified by > * CXUnsavedFile) are copied when necessary, so the client only needs to > * guarantee their validity until the call to this function returns. > * > * \param num_unsaved_files the number of unsaved file entries in \p > * unsaved_files. > * > * \param options A bitmask of options that affects how the translation unit > * is managed but not its compilation. This should be a bitwise OR of the > * CXTranslationUnit_XXX flags. > * > * \param[out] out_TU A non-NULL pointer to store the created > * \c CXTranslationUnit, describing the parsed code and containing any > * diagnostics produced by the compiler. > * > * \returns Zero on success, otherwise returns an error code. > */ > enum CXErrorCode > clang_parseTranslationUnit2(CXIndex CIdx, > const char *source_filename, > const char *const *command_line_args, > int num_command_line_args, > struct CXUnsavedFile *unsaved_files, > unsigned num_unsaved_files, > unsigned options, > CXTranslationUnit *out_TU); > > The parts I'm not clear on are turning an array or ordered collection of strings into an argv/argc, turning an array of CXUnsavedFile's (FFIExternalStruct) into an array of pointers and count, and getting data back in an output argument as CXTranslationUnit which is an opaque pointer to a C++ object. > > Any tips on these mappings would be great. I've currently guessed it as: > > clang_parseTranslationUnit__cxIndex: cxIndex source: sourceFile arguments: argv unsavedFiles:unsaved options: opts > > | argc unsaved_files num_unsaved_files options error out_TU | > argc := argv size. > unsaved_files := unsaved ifNil: [ #() ] ifNotNil: [ unsaved ]. > num_unsaved_files := unsaved_files ifNil: [ 0 ] ifNotNil: [unsaved_files size]. > options := opts sum. > > error := self ffiCall: #(CXErrorCode clang_parseTranslationUnit2(CXIndex cxIndex, > String sourceFile, > String *argv, > uint argc, > CXUnsavedFile *unsaved_files, > uint num_unsaved_files, > CXTranslationUnitFlag options, > CXTranslationUnit *out_TU)). > > (error = CXError_Success) ifTrue: [ ^out_TU ]. > self error: error > > Thanks. > > >> 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. 25, 2017

Re: [Pharo-dev] Bloc Feedback

by Sean P. DeNigris

Aliaksei Syrel wrote > I don't understand how you guys find these kind of bugs :D We have a talent for destruction ;) Aliaksei Syrel wrote > Aha, I forgot about it, thanks! At this point BlTextEditElement is only > used internally by Moldable Editor so I will probably move it away from > Bloc. Ah, okay. IHMO at least a basic editable text morph (and ideally a real editor morph as well) is essential to people starting to play/experiment/test Bloc for real. Aliaksei Syrel wrote > Thanks for the feedback :) Sure! Any thoughts on this: > 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?â¦ 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> ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 25, 2017

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

by Sven Van Caekenberghe

> On 25 Oct 2017, at 14:02, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sven Van Caekenberghe-2 wrote >> And here is how to do it in Pharoâ¦ > > It would be great to add something like this to Launcher Yeah, but file readStreamDo: [ :in | sha256 := SHA256 hashStream: in ]. is very slow (done completely in Pharo, large file), so it would need a good progress bar. We would also need a canonical place to get the signatures from (like Marcus explained, best another, secure server). Sven

Oct. 25, 2017

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > And here is how to do it in Pharoâ¦ It would be great to add something like this to Launcher ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 25, 2017

Re: [Pharo-dev] Bloc status

by Juraj Kubelka

Thatâs great it works for you. Be careful that using Metacello baseline script does not update the local GIT repositories to the latest versions. Check my recent post in Moose: http://forum.world.st/RTExampleFactory-is-missing-sourceClass-tp4990173p499… <http://forum.world.st/RTExampleFactory-is-missing-sourceClass-tp4990173p499…> So, check in Iceberg that all GIT repositories are up-to-date. Cheers, Juraj > On Oct 24, 2017, at 19:02, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Juraj Kubelka wrote >> Or you may share repositories among imagesâ¦ kIceRepository >> sharedRepositoriesLocationString > > That was it! It was > {IcebergSharedRepoFolder}/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar > > Now that I can see the presentationsâ¦ Super cool!! Putting more $! in front > of a line -> text auto-shrinks :) > > Two issues: > 1. For the live examples in the Bloc-Pillar tab: "MNU receiver of #gtLiveIn: > is nil" > 2. In the Pillar tab, the headings are unreadable with the dark theme: > <http://forum.world.st/file/t128965/Screenshot_2017-10-24_18.jpeg> > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Oct. 25, 2017

Re: [Pharo-dev] Pharo Process question

by Norbert Hartl

But don't complain for the coming weeks about things not working ;) Norbert > Am 25.10.2017 um 12:16 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Thanks guys. > Let us move to tonel :) > So I have to watch out then before pushing the button ;) > Stef > > > On Wed, Oct 25, 2017 at 10:10 AM, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > > > On Tue, Oct 24, 2017 at 9:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > > > > On 24 Oct 2017, at 21:47, Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > > > > Hi > > > > are the pending PR reevaluated when one PR is integrated? > > Unfortunately not on every integration... We should do it that way but there are some problems with Jenkins allocating space in the master machine. > > Christophe was telling me he would contact the people from jenkins to see if there is a solution for that. > > it was, but Guille disabled it because it was killing the server. > when we jump to tonel we can re-evaluate the problem :) > > Esteban > > > > > Stef > > > > > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13 <tel:+33%206%2052%2070%2066%2013>

Oct. 25, 2017

Re: [Pharo-dev] Pharo Process question

by Stephane Ducasse

Thanks guys. Let us move to tonel :) So I have to watch out then before pushing the button ;) Stef On Wed, Oct 25, 2017 at 10:10 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > > > On Tue, Oct 24, 2017 at 9:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> >> >> > On 24 Oct 2017, at 21:47, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> > >> > Hi >> > >> > are the pending PR reevaluated when one PR is integrated? >> > > Unfortunately not on every integration... We should do it that way but > there are some problems with Jenkins allocating space in the master machine. > > Christophe was telling me he would contact the people from jenkins to see > if there is a solution for that. > >> >> it was, but Guille disabled it because it was killing the server. >> when we jump to tonel we can re-evaluate the problem :) >> >> Esteban >> >> > >> > Stef >> > >> >> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

Oct. 25, 2017

[ANN] LAM Research upgraded to Platinum Membership

by Marcus Denker

The Pharo Consortium is very happy to announce that LAM Research has upgraded to Platinum Member status. About - LAM Research: http://www.lamresearch.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

Oct. 25, 2017

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

by Marcus Denker

>> >>> Would it not be cleaner if the signature was next to the resource ? Like >>> >>> http://files.pharo.org/platform/Pharo6.1-mac.zip.sha256.txt >>> >>> Or is that the next step ? >>> >> >> Already there. But a signature like that is not a guarantee if it is downloaded from the same serverâ¦ especially of that server does not >> use SSLâ¦ >> >> The âstack vectorâ that a checksum protects against is the compromise of a download server, especially untrusted mirrors. For that, >> the checksum needs to come from some other (trusted) source. E.g. normally it is inlined on the download website. >> >> But of course these things are never 100% guarantees, they just make it harder to do bad things. > > Ah, OK, I understand, I just think that a shorter/simpler/easier-to-remember URL for the signature would be better. > I will put them on pharo.org <http://pharo.org/> later, too (in a dedicated directory). And link them from the download page. Marcus

Oct. 25, 2017