- Pharo-users - lists.pharo.org

Change Playground title based on the name of the first pane
by Peter UhnÃ¡k April 28, 2016

April 28, 2016

Hi, would it be possible to change the Playground title when the first page changed? I know I can change the title through the top right corner, but just a double click might be more useful. Plus there could be some automatic naming pattern, because it would be nice to still see that it is playgroundâ¦ for example I tend to name them: "PL @ custom name". Thanks, Peter

1 0

ModificationTime
by Valentin Ryckewaert April 27, 2016

April 27, 2016

Hi everyone, I don't understand what is the meaning of this method, could someone help me about it plz? modificationTime: aResolvable "Resolve the argument, and answer true if the result refers to a directory, false if it refers to a file or doesn't exist." ^ store modificationTime: (self resolve: aResolvable)

3 3

build for BuildingUIWithSpec
by Peter UhnÃ¡k April 27, 2016

April 27, 2016

Is there a build job for BuildingUIWithSpec? Peter

2 1

UDBCSQLite3Row data accessor.
by Offray Vladimir Luna CÃ¡rdenas April 27, 2016

April 27, 2016

Hi all, I have been using UDBCSQLite3 by Torsten and is pretty stable and in good shape. I have a little suggestion for adding the accessors #data on UDBCSQLite3Row. Its pretty handy for several queries. Is it fine this mail or need I to report this suggestion elsewhere? Thanks, Offray

2 2

[ANN] Genetic Algorithm is available from the Catalog
by Alexandre Bergel April 27, 2016

April 27, 2016

Hi! I did a bit of programmingâ¦ A genetic algorithm is available from the Catalog. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

5 5

1st CFP: SLE 2016 (9th ACM SIGPLAN International Conference on Software Language Engineering)
by Andrei Chis April 26, 2016

April 26, 2016

**Call for Papers** ======================================================================== 9th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2016) Oct 31-Nov 1, 2016, Amsterdam, Netherlands (Co-located with SPLASH 2016) General chair: Tijs van der Storm, CWI, Netherlands Program co-chairs: DÃ¡niel Varro, Budapest University of Technology and Economics, Hungary Emilie Balland, Sensational AG, Switzerland http://conf.researchr.org/track/sle-2016/sle-2016-papers http://www.sleconf.org/2016/ Follow us on twitter: https://twitter.com/sleconf ======================================================================== Software Language Engineering (SLE) is the application of systematic, disciplined, and measurable approaches to the development, use, deployment, and maintenance of software languages. The term "software language" is used broadly, and includes: general-purpose programming languages; domain-specific languages (e.g. BPMN, Simulink, Modelica); modeling and metamodeling languages (e.g. SysML and UML); data models and ontologies (e.g. XML-based and OWL-based languages and vocabularies). ### Important Dates Fri 17 Jun 2016 - Abstract Submission Fri 24 Jun 2016 - Paper Submission Fri 26 Aug 2016 - Notification Fri 2 Sep 2016 - Artifact submission Fri 16 Sep 2016 - Artifact notification Fri 16 Sep 2016 - Camera ready deadline Mon 31 Oct 09:00 - Tue 1 Nov 18:00 2016 Conference ### Topics of Interest SLE aims to be broad-minded and inclusive about relevance and scope. We solicit high-quality contributions in areas ranging from theoretical and conceptual contributions to tools, techniques, and frameworks in the domain of language engineering. Topics relevant to SLE cover generic aspects of software languages development rather than aspects of engineering a specific language. In particular, SLE is interested in principled engineering approaches and techniques in the following areas: * Language Design and Implementation * Approaches and methodologies for language design * Static semantics (e.g., design rules, well-formedness constraints) * Techniques for behavioral / executable semantics * Generative approaches (incl. code synthesis, compilation) * Meta-languages, meta-tools, language workbenches * Language Validation * Verification and formal methods for languages * Testing techniques for languages * Simulation techniques for languages * Language Integration * Coordination between of heterogeneous languages and tools * Mappings between languages (incl. transformation languages) * Traceability between languages * Deployment of languages to different platforms * Language Maintenance * Software language reuse * Language evolution * Language families and variability * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools * User studies evaluating usability * Performance benchmarks * Industrial applications ### Types of Submissions * **Research papers**: These should report a substantial research contribution to SLE or successful application of SLE techniques or both. Full paper submissions must not exceed 12 pages excluding bibliography (in ACM SIGPLAN conference style (http://www.sigplan.org/Resources/Author/)) * **Tool papers**: Because of SLEâs interest in tools, we seek papers that present software tools related to the field of SLE. Selection criteria include originality of the tool, its innovative aspects, and relevance to SLE. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must provide a tool description of 4 pages in SIGPLAN proceedings style (see above), with 1 optional additional page for bibliographic references, and a demonstration outline including screenshots of up to 4 pages. Tool demonstrations must have the keywords "Tool Demo" or âTool Demonstrationâ in the title. The 4-page tool description will, if the demonstration is accepted, be published in the proceedings. The 4-page demonstration outline will be used by the program committee only for evaluating the submission. ### Artifact evaluation Authors of accepted papers at SLE 2016 are encouraged to submit their experiment results used for underpinning research statements to an artifact evaluation process carried out in early September 2016. This submission is voluntary and will not influence the final decision regarding the papers. Papers that go through the Artifact Evaluation process successfully receive a seal of approval printed on the first page of the paper in the proceedings. Authors of papers with accepted artifacts are encouraged to make these materials publicly available upon publication of the proceedings, by including them as "source materials" in the ACM Digital Library. ### Publications All submitted papers will be reviewed by at least three members of the program committee. All accepted papers, including tool papers will be published in ACM Digital Library. Authors of distinguished papers from the conference will be invited to revise and submit extended versions of their papers for a Journal special issue. ### Awards * Distinguished paper. Award for most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * Distinguished reviewer. Award for distinguished reviewer, as determined by the PC chairs using feedback from the authors. ### Program Committee Emilie Balland (co-chair), Sensational AG (SUI) Daniel Varro (co-chair), BME (HUN) Anya Helene Bagge, Univ. Bergen (NOR) Ruth Breu, Univ. Innsbruck (AUT) Jordi Cabot, Univ. Oberta de Catalunya (ESP) Marsha Chechik, Univ. Toronto (CAN) Marcus Denker, INRIA (FRA) Davide Di Ruscio, Univ. LâAquila (ITA) Martin Erwig, Oregon State Univ. (USA) Bernd Fischer, Stellenbosch University (RSA) Sebastian Gerard, CEA (FRA) Jeremy Gibbons, Oxford Univ. (UK) Holger Giese, Hasso Plattner Inst. (GER) Martin Gogolla, Univ. Bremen (GER) Jeff Gray, Univ. Alabama (USA) Esther Guerra, Autonomous Univ. of Madrid (ESP) Gorel Hedin, Lund Univ. (SWE) Michael Homer, Victoria Univ. Wellington (NZL) Dimitris Kolovos, Univ. York (UK) Ralf LÃ¤mmel, Univ. Koblenz (GER) Julia Lawall, LIP6 (FRA) Tihamer Levendovszky, Microsoft (USA) Heather Miller, EPFL (SUI) Pierre-Etienne Moreau, Loria (FRA) GÃ¼nter Mussbacher, McGill Univ. (CAN) Bruno Oliveira, Univ. of Hong Kong (HKG) Terence Parr, Univ. San Francisco (USA) IstvÃ¡n RÃ¡th, IncQuery Labs (HUN) Julia Rubin, MIT (USA) Bernhard Schatz, Fortiss (GER) Sibylle Schupp, Univ. Hamburg (GER) Anthony Sloane, Macquarie Univ. (AUS) Emma SÃ¶derberg, Google (USA) Eugene Syriani, Univ. MontrÃ©al (CAN) Gabi Taentzer, Univ. Marburg (GER) Eric Van Wyk, Univ. Minnesota (USA) Hans Vangheluwe, Univ. Antwerp (BEL) Jurgen Vinju, CWI (NED) Guido Wachsmuth, TU Delft (NED) Eric Walkingshaw, Oregon State Univ. (USA) Andrzej WÄsowski, ITU (DEN) Manuel Wimmer, TU Wien (AUT) Tian Zhang, Nanjing Univ. (CHN)

1 0

Re: [Pharo-users] ensureCreateFile
by Valentin Ryckewaert April 26, 2016

April 26, 2016

Hi ! I made this if it's ok for you i'll post it on fogbugs : AbstractFileReference createFile "Create if necessary a file for the receiver. If the parent does not exist return an exception" self parent ensureCreateDirectory. self writeStream close. createDirectory "Verifies that the directory does not exist and only creates if necessary. Do not remove files contained if they exist.If the parents does not exist return an exception" self parent exists ifFalse:[self error:'The parent directory does not exist']. ^ self resolve ensureCreateDirectory ensureCreateFile "Create if necessary a file for the receiver. If the parent does not exist creates it" self parent ensureCreateDirectory. self writeStream close. ensureCreateDirectory "Verifies that the directory does not exist and only creates if necessary. Do not remove files contained if they exist.If the parents folder does not exist create it" ^ self resolve ensureCreateDirectory 2016-04-26 10:34 GMT+02:00 Valentin Ryckewaert < valentin.ryckewaert(a)gmail.com>: > Hi ! > > I made this if it's ok for you i'll post it on fogbugs : > > AbstractFileReference > createFile > "Create if necessary a file for the receiver. If the parent does not exist > return an exception" > self parent ensureCreateDirectory. > self writeStream close. > createDirectory > "Verifies that the directory does not exist and only creates if necessary. > Do not remove files contained if they exist.If the parents does not exist > return an exception" > self parent exists ifFalse:[self error:'The parent directory does not > exist']. > ^ self resolve ensureCreateDirectory > ensureCreateFile > "Create if necessary a file for the receiver. If the parent does not exist > creates it" > self parent ensureCreateDirectory. > self writeStream close. > ensureCreateDirectory "Verifies that the directory does not exist and only > creates if necessary. Do not remove files contained if they exist.If the > parents folder does not exist create it" ^ self resolve > ensureCreateDirectory > > > 2016-04-25 16:28 GMT+02:00 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> oui moi aussi >> je me demandais si on devait introduire une autre methode mais en fait >> le nouveau comportement est compatible donc je le ferais. >> >> >> On 25 Apr 2016, at 13:58, Valentin Ryckewaert < >> valentin.ryckewaert(a)gmail.com> wrote: >> >> Tu en penses quoi toi ? >> Je trouve Ã§a illogique que ensureCreate ne signifie pas la meme chose >> pour un dossier ou pour un fichier. >> >> ---------- Forwarded message ---------- >> From: Valentin Ryckewaert <valentin.ryckewaert(a)gmail.com> >> Date: 2016-04-22 10:11 GMT+02:00 >> Subject: Re: [Pharo-users] ensureCreateFile >> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> >> >> For me ensureCreateFolder is made to be sure the folder is created, if >> you make '/home/a/b/c/d' with a b c d not existing it will create all of >> them. >> ensureCreateFile should do the same thing no ? >> >> 2016-04-21 13:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >> >>> because it's like this >>> >>> ensureCreateFolder : create the folder structure if necessary >>> ensureCreateFile : create the file if necessary >>> >>> I really don't see any gain from changing existing behavior and >>> introducing potential problems. >>> If I ask for file to be created, I don't expect that the system will >>> suddenly start creating folders, that's a unintentional side effect. >>> If you need it for your convenience, then it's dead-easy to implement >>> without breaking existing stuff. >>> >>> >>> On Thu, Apr 21, 2016 at 10:35 AM, Denis Kudriashov <dionisiydk(a)gmail.com >>> > wrote: >>> >>>> >>>> 2016-04-21 9:55 GMT+02:00 Valentin Ryckewaert < >>>> valentin.ryckewaert(a)gmail.com>: >>>> >>>>> Yes but why ensureCreateFile then ? >>>>> Why don't we juste create a message createFile as there is >>>>> createFolder ? >>>>> createFolder : create the folder >>>>> createFile : create the file >>>>> >>>>> ensureCreateFolder : create the folder and its parents if necessary >>>>> ensureCreateFile : create the file and its parents if necessary >>>>> >>>> >>>> +1 >>>> >>> >>> >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> 03 59 57 78 50 >> 03 59 35 86 16 >> >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >> >

5 10

Dawn Theme on Pharo 4.0
by Siemen Baader April 25, 2016

April 25, 2016

Hi all, has anybody had luck using Sebastian's Dawn Theme [1] on Pharo 4.0? The instructions on github are for Pharo 3.0 - what would I do to make it work on my 4.0 image? thanks, Siemen 1: https://github.com/sebastianconcept/Pharo3DawnTheme -- View this message in context: http://forum.world.st/Dawn-Theme-on-Pharo-4-0-tp4889541.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

5 9

[ANN] Arff generator for Pharo
by Julien Delplanque April 25, 2016

April 25, 2016

Hello everyone, For a university project in ''Datamining and Datawarehousing'', I have to convert data stored as text files in different formats to the Weka[1] ARFF format[2]. I did it with Pharo of course! :) So, I wrote this little project [3] to share what I have done with you, just in case someone else needs to export data from Pharo objects to an ARFF string for further analysis with Weka. Cheers, Julien Links: [1] Weka's website: http://www.cs.waikato.ac.nz/ml/weka/ [2] ARFF format spec: https://weka.wikispaces.com/ARFF [3] Arff generator for Pharo: https://github.com/juliendelplanque/Arff

3 4

Using FFI: MessagetNotUnderstood:InterfaceDev class>>fficall:module
by mathias arnaud nkeumo tsombeng April 25, 2016

April 25, 2016

Dear All, Am try to call a libpcap library using FFI in pharo and am getting the following error: MessagetNotUnderstood:InterfaceDev class>>fficall:module Am working with pharo 4 also I have issue with pharo 5 on unbuntu after runing the pharo launher i create an image of pharo 5 but when i try to run pharo 5 it does not work. Am try to work with UFFI and on many documentation they are advicing me pharo 5 for UFFI Best Regards, A. Tsombeng

3 3