November 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Experience makers

by stepharo

Yes > > The projects that I know are using startup actions [1][2]. These are > files that go into ~/Library/Preferences/pharo/ and define what has to > be run on image startup. They areused to âcustomizeâ your image. Yes but there are implicit. There are there but we do not see them and manipulate them if you see what I mean. And there are static. What I want to say also is that this is not the spying framework but the projects people work on. > > Uko > > [1]: https://github.com/RobertoMinelli/DFlow/blob/master/installDFlow.st > [2]: http://smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter > <http://smalltalkhub.com/#%21/%7Edalsat/ShoreLine-Reporter> >

Nov. 4, 2014

Re: [Pharo-dev] WhatsUp from: 2014-11-03 until: 2014-11-16

by stepharo

> Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS - working on a new book with sven and damien - working on success stories for Pharo - working on consortium building > > ### What's next, until 2014-11-16 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - working on a new book with sven and damien - working on success stories for Pharo - working on consortium building :) > > (*) we'll be expecting results by then ;) > >

Nov. 4, 2014

Re: [Pharo-dev] NAtiveBoost error

by stepharo

> Hi Alain, > > This is nice that you are working on a zmq binding for Pharo. > Is it public and on Sthub? +1

Nov. 4, 2014

Re: [Pharo-dev] SmalltalkHub Recent watched events

by Esteban Lorenzano

yepâ¦ I do not have a lot of time so that is in really low priority on my todo list :( Esteban > On 04 Nov 2014, at 09:26, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > This is known bug https://code.google.com/p/smalltalk-hub/issues/detail?id=29 <https://code.google.com/p/smalltalk-hub/issues/detail?id=29> but I don't think anybody is working on it. > > Peter > > On Tue, Nov 4, 2014 at 9:01 AM, Torsten Bergmann <astares(a)gmx.de <mailto:astares@gmx.de>> wrote: > The "Recent watched events" still show no new entries. > Only ones from 2004. Anyone know how to fix this? > > Thanks > T. > > >

Nov. 4, 2014

Re: [Pharo-dev] Internship position at Thales

by Ben Coman

stepharo wrote: > Please distribute and contact eric eric.lepors(a)fr.thalesgroup.com > > Begin forwarded message: > > From: LE PORS Eric <eric.lepors(a)fr.thalesgroup.com> > Subject: Ouverture de sujet de stage Pharo > Date: 3 Nov 2014 11:12:18 GMT+1 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > STAGE : Multi-fenÃªtrage sous Pharo Smalltalk (Logiciel) (H/F) - 1413963 > Stage - Temps plein > Famille professionnelle 06 - R&D : Logiciel > Lieu principal FR-Bretagne-Brest > Organisation Thales France > > Dans le cadre de notre dÃ©veloppement, nous recherchons un(e) : > > STAGE : Multi-fenÃªtrage sous Pharo Smalltalk (Logiciel) â H/F > BasÃ©(e) Ã Brest (29) > > > Contexte : > > Notre entitÃ© dÃ©veloppe rÃ©guliÃ¨rement des maquettes dâinterfaces > homme-machine (IHM) innovantes. Lâinnovation se situe autant au niveau > de lâergonomie quâau niveau du design graphique visuel ou des Ã©lÃ©ments > dâinteraction. Le maquettage est souvent utilisÃ© en sÃ©ance avec les > opÃ©rationnels, dâoÃ¹ lâemploi dâun langage dynamique comme Smalltalk qui > permet la modification rapide (et en sÃ©ance) du code et des Ã©lÃ©ments > dâinteraction. > Le maquettage/prototypage des interfaces Homme-Machine est donc > actuellement rÃ©alisÃ© sous SMOCK, un framework de maquettage dÃ©veloppÃ© en > Smalltalk. Smalltalk Pharo est un excellent candidat pour la plateforme > finale d'exÃ©cution du framework de maquettage/prototypage, cependant, > certaines limitations de Pharo nous empÃªchent de l'utiliser de maniÃ¨re > industrielle. > > > Missions : > > Nous souhaitons expÃ©rimenter un environnement de maquettage sous Pharo, > cependant, cette derniÃ¨re limite lâaffichage des IHM Ã lâintÃ©rieur d'une > seule fenÃªtre de l'OS. Nous souhaitons, en relation avec la communautÃ© > Pharo, dÃ©velopper le multi-fenÃªtrage. Le stagiaire devra implÃ©menter un > mÃ©canisme permettant l'ouverture et gestion de fenÃªtres multiples dans > les OS Windows et Linux Ã minima. Une rÃ©utilisation de code existant > dans la communautÃ© Pharo et une reversion de code en OpenSource est > envisageable. > Le candidat sera l'interlocuteur entre Thales et la communautÃ© Pharo. Le > candidat Ã©valuera diffÃ©rentes solutions de multi- fenÃªtrage sous > diffÃ©rents critÃ¨res (performance, robustesse de la solution, portabilitÃ© > de la solution...). La solution devra anticiper le futur et prÃ©voir > d'afficher des contenus visuels variÃ©s (vidÃ©o, primitives de dessin 2D, > OpenGL...). > > L'objectif sera de dÃ©velopper un prototype IHM multi-fenÃªtres de > dÃ©monstration sur Pharo afin de dÃ©montrer les nouvelles capacitÃ©s et un > aperÃ§u des performances. > > > Formation souhaitÃ©e : Master 2 Pro ou 3Ã¨me annÃ©e d'Ecole d'IngÃ©nieur. > > > Connaissances souhaitÃ©es : > > Le stagiaire devra avoir une connaissance du Smalltalk ou Ãªtre motivÃ© > par lâapprentissage de celui-ci. Il devra ensuite Ãªtre motivÃ© par la > conception dâinterfaces homme machine de nouvelle gÃ©nÃ©ration. > > > PÃ©riode souhaitÃ©e et durÃ©e : Ã partir de janvier 2015 pour une durÃ©e de > 6 mois. > > > > > Au sein de nos Ã©quipes, nous vous offrons : > du challenge, > des opportunitÃ©s de carriÃ¨re, > et des technologies innovantes pour rendre le monde plus sÃ»r. > > Le monde mÃ©rite un bel avenir. > Vous aussi. > > Toutes nos offres sur : https://www.thalesgroup.com/fr/homepage/carrieres > > That is cool. Looking forward to see what comes out of it. translate.google.com.... STAGE: Multi-window in Pharo Smalltalk (Software) Context: Our entity regularly develops models of human-machine interfaces (HMI) innovative. Innovation is both in terms of ergonomics at the level of visual or graphic design elements of interaction. The prototyping is often used in meeting with business, hence the use of a dynamic language like Smalltalk that allows fast (and meeting) code modification and interaction elements. The mockup / prototyping of human-machine interfaces is currently produced in SMOCK, a framework developed in Smalltalk prototyping. Pharo Smalltalk is an excellent candidate for the final execution platform framework of prototyping / prototyping, however, some limitations prevent us from Pharo use industrially. Missions: We want to experiment a prototyping environment under Pharo, however, the latter limit the display of HMI within a single OS window. We wish, in relation to the Pharo community, developing multi-windowing. The intern will implement a mechanism for opening and managing multiple windows in Windows and Linux OS minimum. Reuse of existing code in the Pharo community and a reversion of open source code is possible. The candidate will be the interlocutor between Thales and the Pharo community. Evaluate the different candidate solutions to multi-windows from different criteria (performance, robustness of the solution, the solution of portability ...). The solution should anticipate the future and plan to display (primitive video, 2D drawing, OpenGL ...) different visual content. The objective is to develop a multi-window GUI prototype demonstration Pharo to demonstrate the new capabilities and an overview of the performance. Training required: Master Pro 2 or 3rd year of Engineering School. Knowledge required: The trainee should have knowledge of Smalltalk or be motivated by learning it. It will then be given by the man-machine interface design of new generation. Desired period and duration: from January 2015 for a period of 6 months.

Nov. 4, 2014

Re: [Pharo-dev] NAtiveBoost error

by stepharo

Alain which nativeboost chapter :)? Could you propose a paragraph so that we cover the problem you faced? Stef On 4/11/14 00:44, Alain Rastoul wrote: > Hi Igor, > > Thank you for your answer, it worked perfectly > Looks like I overlooked the nativeboost chapter > .. 10 timesRepeatAfterMe: [self rtfm ] . > And my suggestion about testing nil was stupid, much better to fail soon. > ... I am an ass on this one... > > However, I am struggling on another point you already answered in the > past > in the mailing list to a guy who wanted to use socket.io : > (http://forum.world.st/socket-io-td3891592.html#a3893031) > "Sockets in Pharo are not blocking the whole VM. > What they block is the process which working with concrete socket. But > other processes can still run, while > one waiting data / even from single socket. " > on windows, zmq socket receive is blocking, on linux, not blocking > (hence not working). > As zmq is doing is IO on another thread, I guess there is some side > effect of > socket receive timeout settings somewhere (in the plugin ?) - just a > guess... > Getting socket options shows no difference, but I don't know how it is > done on the vm > side with regards to threads and if the socket is the same (zmq socket > is not the tcp socket)... > And on linux, the equivalent C program of to the smalltalk version > blocks as expected. > > I a mperplexified ... > may be I should look at vm and plugin code (VMMaker package IIRC) ? > Do you have another advice ? > > Thanks you > > Alain > Le 03/11/2014 02:12, Igor Stasenko a Ã©crit : >> NBExternalArray instances cannot be passed directly to functions >> expecting pointers. >> >> use 'myarray address' for arguments. >> >> On 3 November 2014 00:20, Alain Rastoul >> <alf.mmm.cat(a)gmail.com >> <mailto:alf.mmm.cat@gmail.com>> wrote: >> >> Hi, >> >> I have a problem with a nativeboost call, but I don't see what I do >> wrong. >> >> library function prototype is: >> int zmq_getsockopt (void *socket, int option_name, void >> *option_value, size_t *option_len); >> >> my calling method in pharo is: >> zmq_getsockopt: socket option_name: option_name option_value: >> option_value option_len: option_len >> <primitive: #primitiveNativeCall module: #NativeBoostPlugin >> error: errorCode> >> ^self nbCall: #(int zmq_getsockopt (void *socket, int >> option_name, void * option_value, size_t* option_len) ) >> >> when I call it with >> ... >> optionValue := (NBExternalArray ofType: 'int') externalNew: 1. >> optionLen := (NBExternalArray ofType: 'size_t' ) externalNew: 1. >> [ optionValue at: 1 put: 0 . >> optionLen at: 1 put: (NBExternalType sizeOf: 'int') . >> rc := self zmq_getsockopt: socket option_name: option_name >> option_value: optionValue >> option_len: optionLen . >> value := optionValue at: 1 . >> ] ensure: [ optionValue free. >> optionLen free ]. >> ... >> I allways get an exception: "error during FFI call : nil" >> >> >> After stepping in NBFFICallout generation, I found something >> strange, the code >> generation seems not to be called because lastError stays at nil ? >> >> handleFailureIn: aContext nativeCode: aBlock >> lastError := self getErrorFrom: aContext lastError: >> NativeBoost lastError. >> >> >>getErrorFrom: aContext lastError: errorCode >> ... checks pragmas etc >> >>getErrorFrom: aContext lastError: errorCode >> ... lastError := aContext tempAt: method >> numTemps. >> => lastError = nil ??? shouldn't be >> ErrNoNativeCodeInMethod ? >> "install native code and retry the send" >> lastError = ErrNoNativeCodeInMethod >> ifTrue: [ ^ self generateCode: aBlock andRetry: >> aContext ]. >> never gets called ... >> >> "ok, we're out of options, signal an error here" >> ^ self signalError: lastError >> >> Could it be because I use this image on windows and unix ? >> Or because I had an exception at prototype parsing the first time >> because I forgot a ; at the end of the prototype ? >> >> Is my prototype correct or is it the origin of the error ? >> Is there a way to reset the lastError (aContext tempAt: method >> numTemps) ? >> I will try to reset it in debugger but may be there is a cleaner >> way ? >> would it be ok to change the test in handleFailure to >> (lastError = ErrNoNativeCodeInMethod) or:[ lastError isNil ] ? >> (I can open a bug in this case ) >> >> Any idea or comment is welcome >> Thanks in advance >> >> Alain >> >> >> >> >> >> -- >> Best regards, >> Igor Stasenko. > > > >

Nov. 4, 2014

Re: [Pharo-dev] NAtiveBoost error

by Luc Fabresse

Hi Alain, This is nice that you are working on a zmq binding for Pharo. Is it public and on Sthub? Cheers, #Luc 2014-11-04 7:43 GMT+01:00 Alain Rastoul <alf.mmm.cat(a)gmail.com>: > > > Le 04/11/2014 01:32, Igor Stasenko a Ã©crit : > >> What is zmq sockets? Some kind of wrapper library? Then best i can >> advise is to follow its guidelines, since i'm not familiar with it. >> >> Btw, using (NBExternalArray ofType: 'xyz') is highly expensive, >> please read carefully NBExternalArray class comment, which explains all >> details. >> >> > ZeroMQ is an open source asynchronous inter-process communication messaging > library/framework written in c++ > zeromq sockets should not have been called sockets because they are more > 'endpoints' > or something like that in zmq realms, however, it uses tcp sockets in my > tests and > has different behaviours on linux and windows, I suspect > something different about underlying tcp sockets states. > > Thank you for the indication about performance, I will take it into account > My first step is just to make experiments that works > to be comfortable with both nativeboost and zeromq. > This experiment is done with two different pharo vm processes > (the client and the server) started manually, and the same > in C. > This library has nice patterns that makes it very interesting from a > parallel computing perspective > (request/response, publisher/subscriber, push/pull , etc). > The guide is here and is worth looking at http://zguide.zeromq.org/page: > all > I know you will be interested in, it has similarities with your > old hydra project > :) > > > > >

Nov. 4, 2014

Re: [Pharo-dev] SmalltalkHub Recent watched events

by Peter UhnÃ¡k

This is known bug https://code.google.com/p/smalltalk-hub/issues/detail?id=29 but I don't think anybody is working on it. Peter On Tue, Nov 4, 2014 at 9:01 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > The "Recent watched events" still show no new entries. > Only ones from 2004. Anyone know how to fix this? > > Thanks > T. > > >

Nov. 4, 2014

SmalltalkHub Recent watched events

by Torsten Bergmann

The "Recent watched events" still show no new entries. Only ones from 2004. Anyone know how to fix this? Thanks T.

Nov. 4, 2014

Re: [Pharo-dev] Fix 'Search Code' menu item in Nautilus

by Max Leske

Hi Paul, You also need to include the two dependencies of the slice, those need to be uploaded to the inbox too. Cheers, Max > On 04.11.2014, at 06:19, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > Hi - > > The attached slice makes the 'Search Code' menu item in Nautilus work like it did prior to the adoption of Nautilus in Pharo 3. I do not have commit rights to Pharo30Inbox but would submit it there if I did. I have not sent the contributor agreement but will tomorrow. > > > The issue in fogbugz is: > https://pharo.fogbugz.com/f/cases/14382/Fix-Search-Code-refactoring-menu-it… > > > Paul > > <SLICE-Issue-14382-Fix-Search-Code-refactoring-menu-item-in-Nautilus-PaulDeBruicker.1.mcz>

Nov. 4, 2014