April 2016 - Pharo-users - lists.pharo.org

Reminder: CFP - IWST 2016 - International Workshop on Smalltalk Technologies

by jannik laval

[Please accept our apologies if you receive multiple copies of this call] [Please send to interested colleagues / mailing-lists] ************************************************************************************************************ CALL FOR PAPERS IWST16 â International Workshop on Smalltalk Technologies Prague, Czech Republic; August 23th, 2016 http://www.esug.org/wiki/pier/Conferences/2016/International-Workshop-IWST_… ************************************************************************************************************ ------------------- Goals and scopes ------------------- The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. We expect papers of three kinds: - Short position papers describing emerging ideas - Long research papers with deeper description of experiments and of research results. - Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. *We will not enforce any length restriction.* -------------------- Important Dates -------------------- Submission deadline: *May 15th, 2016* Notification deadline: June 20th, 2016 Camera-ready : July 13th, 2016 Workshop : August 23th, 2016 *All accepted papers will be published in ACM DL (To be confirmed)* *Best papers would be extended in an International Journal* ------------------- Topics ------------------- We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: -Aspect-oriented programming, -Design patterns, -Experience reports, -Frameworks, -Implementation, new dialects or languages implemented in Smalltalk, -Interaction with other languages, -Meta-programming and Meta-modeling, -Tools ------------------- Best Paper Award ------------------- To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be illegible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. ------------------- Publication ------------------- Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm. This site also contains links to useful informations on how to write effective submissions. ------------------- Submission ------------------- All submissions must be sent via easychair: https://easychair.org/conferences/?conf=iwst20160 ------------------- Program chairs ------------------- Anne Etien (UniversitÃ© de Lille 1, France) Jannik Laval (UniversitÃ© Lyon 2 LumiÃ¨re, France) -- ~~Jannik Laval~~ Enseignant-chercheur Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me d'Information IUT LumiÃ¨re, UniversitÃ© Lyon LumiÃ¨re laboratoire DISP http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

April 14, 2016

Re: [Pharo-users] Pharo-users Question about the symbols

by stepharo

Good idea! Stef Le 8/4/16 09:49, Cyril Ferlicot Delbecque a Ã©crit : > > On 08/04/2016 09:05, Henrik Nergaard wrote: >> | s1 s2 | >> >> s1 := 1234 asString. >> s2 := 1234 asString. >> >> s1 = s2. "true" >> s1 == s2. "false" >> >> s1 asSymbol = s2 asSymbol. "true" >> s1 asSymbol == s2 asSymbol. "true" >> >> (s1 class allInstances select: [:s | s = s1 ]) size. "2" >> (s1 asSymbol class allInstances select: [:s | s = s1 asSymbol ]) size. "1" >> >> [ #stringA = #stringB ] bench. "26,812,864 per second" >> [ 'StringA' = 'StringB' ] bench. "3,492,987 per second" >> >> Best regards, >> Henrik > Hi Henrik, > > The class comment of Symbol is really not enough. It need improvement. I > think it would be good to add your examples at least in the class comment. >

April 14, 2016

Re: [Pharo-users] [ANN] General WebBrowser package for Pharo4 and Pharo 5 onwards

by stepharo

The documentation is on github under PharoProgress people should issues pull requests Le 14/4/16 01:15, Ben Coman a Ã©crit : > On Wed, Apr 13, 2016 at 10:04 PM, Rob Rothwell <r.j.rothwell(a)gmail.com> wrote: >>> # Usage >>> >>> WebBrowser openOn: 'http://www.pharo.org' >> >> Fantastic...this is a nice example of using UFFI to call a LibC command, and >> since it is just using open(1), you can also do something like: >> >> >> WebBrowser openOn: '/users/rob/desktop/enterprisepharo.pdf' >> >> To generically open a file! >> >> Take care, >> >> Rob > btw, the might be good for the UFFI documentation to list a few > reference projects using it. > cheers -ben > >

April 14, 2016

Re: [Pharo-users] First impressions, was About Box

by stepharo

Le 14/4/16 01:52, Damien Pollet a Ã©crit : > Heh. The last days I've had a look at Coralâ¦ my current goal is to > remove the dependency to PetitParser from the argument parser, and to > re-integrate that with the commandline handler system of the image. > But that's only one partâ¦ Yes it would be really nice. > > On 14 April 2016 at 01:43, Ben Coman <btc(a)openinworld.com > <mailto:btc@openinworld.com>> wrote: > > On Wed, Apr 13, 2016 at 1:51 AM, Alistair Grant > <akgrant0710(a)gmail.com <mailto:akgrant0710@gmail.com>> wrote: > > > * I'm glad that being able to run headless mode is easy, as I'd > like to > > use Pharo for scripting. > > I'm not sure of its status, but Coral was some experiments along > this line... > https://www.youtube.com/watch?v=HLb_rMcNN6k > > > * I'm still getting used to the idea of the entire ST > environment being > > in a single OS window, but at the moment I think I prefer VW's > > approach where each ST window is a OS window, as it makes it > easier to > > work with other applications, e.g. if I want to look at an > email or > > web page while working within ST. > > This will become more possible over time as some native window > management is being moved out of VM into the Image. > > cheers -ben > >

April 14, 2016

Re: [Pharo-users] First impressions, was About Box

by stepharo

Have a look at the chapter about command handler in Deep into Pharo because you have all you need You can script the loading and execution of expressions easily. People like julien, damien at Pharodays started to resume a better DSL for command descriptions. Le 13/4/16 19:48, Alistair Grant a Ã©crit : > On Wed, Apr 13, 2016 at 05:55:22PM +0200, stepharo wrote: >>> I'd be happy to, thanks. Please let me know what I need to do to get >>> involved (and remember that this is my hobby and I don't get as much >>> time as I'd like, so my responses won't always be as fast as we'd like). >> - start to see if you can write the scripts you want. >> - identify missing functionality >> - use OSSubprocess > Sure... > > While the existing "st" handler has some uses, I think it will be a bit > limited as I expect that most of the scripts I would write would end up > being: > > 1. Load required packages > 2. Maybe do some initialisation > 3. Send (basically) a single message to start the real work > > Which means that I have to maintain a separate file that adds little > value. > > As implied above, I'd like the "script" to be distributable as either > one or two files and take advantage of: > > * OO design > * Pharo's excellent development environment > * SUnit > > I've hacked together a quick framework in which a "script" is actually a > a Monticello package. The package name is supplied on the command line > along with some pre-defined options and anything else required by the > script. The package is loaded and a message sent to the class of the > same name. E.g.: > > pharo script.image cliscript WorkedHours Hours.xlsx > > would load ConfigurationOfWorkedHours, load the package, and > send WorkedHours>>runWithHandler: theCliHandler. (The example script > then reads the Hours spreadsheet and calculates the total hours worked). > > Current help text... > >> ./pharo script.image cliscript --help > CliScript enables running "Monticello" scripts. > > The script is identified by its package name. CliScript looks for a > configuration package with the same name in the local package cache, > loads it, and sends the runWithHandler: message to the class with the > same name. > > Command line parameters: > > packageName The package to load and execute. > > Command line options: > > --debug Halt at the start of the message > --log-transcript Redirect transcript output to transcript.log > > > > I haven't had to use OSSubprocess yet, next steps include: > > * Read XSLX spreadsheets instead of having to export to CSV. > The script mostly does date and time calculations, I need to confirm > that they are working properly in Tabular. > * Add logging (I haven't looked for any logging capability yet). > * Ideally, implement the ODS support in the Tabular package (stretch > goal :-)). > > > Thanks! > Alistair > >

April 14, 2016

Re: [Pharo-users] First impressions, was About Box

by Damien Pollet

Heh. The last days I've had a look at Coralâ¦ my current goal is to remove the dependency to PetitParser from the argument parser, and to re-integrate that with the commandline handler system of the image. But that's only one partâ¦ On 14 April 2016 at 01:43, Ben Coman <btc(a)openinworld.com> wrote: > On Wed, Apr 13, 2016 at 1:51 AM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > > > * I'm glad that being able to run headless mode is easy, as I'd like to > > use Pharo for scripting. > > I'm not sure of its status, but Coral was some experiments along this > line... > https://www.youtube.com/watch?v=HLb_rMcNN6k > > > * I'm still getting used to the idea of the entire ST environment being > > in a single OS window, but at the moment I think I prefer VW's > > approach where each ST window is a OS window, as it makes it easier to > > work with other applications, e.g. if I want to look at an email or > > web page while working within ST. > > This will become more possible over time as some native window > management is being moved out of VM into the Image. > > cheers -ben > >

April 13, 2016

Re: [Pharo-users] First impressions, was About Box

by Ben Coman

On Wed, Apr 13, 2016 at 1:51 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > * I'm glad that being able to run headless mode is easy, as I'd like to > use Pharo for scripting. I'm not sure of its status, but Coral was some experiments along this line... https://www.youtube.com/watch?v=HLb_rMcNN6k > * I'm still getting used to the idea of the entire ST environment being > in a single OS window, but at the moment I think I prefer VW's > approach where each ST window is a OS window, as it makes it easier to > work with other applications, e.g. if I want to look at an email or > web page while working within ST. This will become more possible over time as some native window management is being moved out of VM into the Image. cheers -ben

April 13, 2016

Re: [Pharo-users] [Bug - Pharo 5.0] Remove a class but not remove for RPackage

by Ben Coman

On Wed, Apr 13, 2016 at 9:02 PM, Yann Dubois <yann59.dubois(a)gmail.com> wrote: > Hello, > > When I delete a class, a window pop to inform me that some methods use this > class. So I remove the methods because they are not usefull without my class > to removed. > > But when I close the window, the methods stay on the Browser, so I remove > this methods on the Browser. > > Then, I remove an other class and "BOOM" an error appears, the key which > represents my class is not present in the SystemDictionnary (it's normal), > but I can find the key in the RPackage metaclasses. Partly it could be that Browser is not being told to update. If you can reproduce it, try opening a new second Browser before modifying anything more through the first Browser. cheers -ben

April 13, 2016

Re: [Pharo-users] [ANN] General WebBrowser package for Pharo4 and Pharo 5 onwards

by Ben Coman

On Wed, Apr 13, 2016 at 10:04 PM, Rob Rothwell <r.j.rothwell(a)gmail.com> wrote: >> >> # Usage >> >> WebBrowser openOn: 'http://www.pharo.org' > > > Fantastic...this is a nice example of using UFFI to call a LibC command, and > since it is just using open(1), you can also do something like: > > > WebBrowser openOn: '/users/rob/desktop/enterprisepharo.pdf' > > To generically open a file! > > Take care, > > Rob btw, the might be good for the UFFI documentation to list a few reference projects using it. cheers -ben

April 13, 2016

Re: [Pharo-users] FFI return by reference

by Thibault Raffaillac

Hi, I tried lots of ways to pass an array, based on the few examples found here and there. My example is: GLES2Buffer class>>gen: n into: buffers self ffiCall: #(void glGenBuffers(int n, int* buffers)) With buffers := FFIExternalArray newType: 'int' size: n (or FFIExternalArray gcExternalNewType: 'int' size: n), the above signature executes without error, but buffers is not updated, so I guess it is copied beforehand. If I replace int* with FFIExternalArray, the values are written correctly in my array. If I replace int* with ByteArray instead I can use any one of ByteArray/IntegerArray/FloatArray ! Only ShortArray, LongArray and DoubleArray are missing then, but they are not crucial right now. So for example: GLES2Buffer class>>create buffer := IntegerArray new: 1. GLES2Buffer gen: 1 into: buffer. ^self new setHandle: (buffer at: 1) :) Same goes for passing coordinates to OpenGL, just with #(-1 -1 -1 1 1 1 1 -1) asFloatArray. Perfect. Cheers, Thibault > Hi, > > Just checked? contrary to what I believed, strings are passed by copy (not by > reference, as ByteArray)? logical for safety but with penalty on > performance... so yes, using a ByteArray is the correct way to do it. (Or an > external value holder, which is a glorified way for passing a ByteArray, but > this probably do not work fine for ?char*" because I didn?t preview it :P) > > Esteban

April 13, 2016