- Esug-list - lists.esug.org

[ANN] Moose 4.7

by Tudor Girba

We are happy to announce the Moose Suite version 4.7: http://moosetechnology.org/download What is new: • Integration of the Roassal visualization engine • New PetitParser browser with integrated refactorings • Improved Glamorous Toolkit for Pharo including the Glamorous Inspector and Debugger • Several features in Glamour including Watcher support (similar to OS X preview) • Significant improvements in FAMIX • Improved external VerveineJ parser for Java • Based on Pharo 1.4 A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… Have fun, The Moose Team

March 3, 2013

Release of the Pharo consortium web site

by Stéphane Ducasse

Hi guys After some efforts, we are proud to announce the consortium around Pharo. http://consortium.pharo.org With such consortium, companies and academic partners will be able to collaborate and sustain the development of the Pharo environment and ecosystem. Today we announce the release of the beta version of the official consortium website. Invest in your future, participate to the consortium! Our goal is to be able to pay a couple of full-time engineers to build a bright future for everyone. Thanks Esteban for the effort, lusy for the design, and our first members: Inria, VMWare, yesplan, 2denker, madEnvironment, BetaNine, Versus for their trust We wish you a lot of business and success! The Pharo Team

March 1, 2013

Re: [Esug-list] Join ESUG for GSOC 2013

by Damien Cassou

Dear Malintha, On Wed, Feb 27, 2013 at 9:24 PM, Malintha Adikari <malintha.adikari(a)hotmail.com> wrote: > Thank you Damien for the reply. I would like to start with developing > documentation tool for smalltalk classes. For that I want to understand the > supportive of the smalltalk classes for a documentation tool. Are they > developed with that kind of supportive manner (annotations ect.. ) . Where > can I find the example codes for the reference. I don't really understand your question. Keep it simple. Just use the class comment, the class name, the methods name, the method comments, and the method parameters. You may want to have a look at Pharo by Example first or Squeak by Example. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 28, 2013

Re: [Esug-list] Join ESUG for GSOC 2013

by Malintha Adikari

Hi, Thank you Damien for the reply. I would like to start with developing documentation tool for smalltalk classes. For that I want to understand the supportive of the smalltalk classes for a documentation tool. Are they developed with that kind of supportive manner (annotations ect.. ) . Where can I find the example codes for the reference. Thank you, Malintha Adikari > From: damien.cassou(a)gmail.com > Date: Wed, 27 Feb 2013 08:03:20 +0100 > Subject: Re: [Esug-list] Join ESUG for GSOC 2013 > To: malintha.adikari(a)hotmail.com > CC: esug-list(a)lists.esug.org; carla.griggio(a)gmail.com; janko.mivsek(a)eranova.si > > Dear Malintha, > > On Tue, Feb 26, 2013 at 12:37 PM, Malintha Adikari > <malintha.adikari(a)hotmail.com> wrote: > > I am final year computer engineering undergraduate from University of > > Peradeniya. I would like to join ESUG for GSOC 2013. I am interesting about > > your organization & projects. Could you please tell me more details about > > the available projects if any > > > thank you for your interest. I don't know if there will be ESUG > projects this year for GSOC, maybe others will have more information. > If you want to have a chance to get selected in case we would have > projects, I advise you to start with these little exercises: > > - implement in Pharo/Smalltalk a double-linked list using a > test-driven-development (TDD) approach; > - implement a tool that takes any Smalltalk class as input and > produces HTML with the documentation of the class (instance variables, > class comment) and its methods (parameters, method comment). That's > just like a small javadoc tool. > > Don't hesitate to ask for help: > > - on stackoverflow.com (with tags #smalltalk, #squeak, #pharo...) > - on mailing lists (see Squeak and Pharo websites) > - on IRC (see Squeak and Pharo websites) > > > Best, > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill

Feb. 27, 2013

Re: [Esug-list] Join ESUG for GSOC 2013

by Damien Cassou

Dear Malintha, On Tue, Feb 26, 2013 at 12:37 PM, Malintha Adikari <malintha.adikari(a)hotmail.com> wrote: > I am final year computer engineering undergraduate from University of > Peradeniya. I would like to join ESUG for GSOC 2013. I am interesting about > your organization & projects. Could you please tell me more details about > the available projects if any thank you for your interest. I don't know if there will be ESUG projects this year for GSOC, maybe others will have more information. If you want to have a chance to get selected in case we would have projects, I advise you to start with these little exercises: - implement in Pharo/Smalltalk a double-linked list using a test-driven-development (TDD) approach; - implement a tool that takes any Smalltalk class as input and produces HTML with the documentation of the class (instance variables, class comment) and its methods (parameters, method comment). That's just like a small javadoc tool. Don't hesitate to ask for help: - on stackoverflow.com (with tags #smalltalk, #squeak, #pharo...) - on mailing lists (see Squeak and Pharo websites) - on IRC (see Squeak and Pharo websites) Best, -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 27, 2013

Call for papers for Dyla'13: 7th Workshop on Dynamic Languages and Applications @ ECOOP

by Alexandre Bergel

Dyla'13, 7th Workshop on Dynamic Languages and Applications Colocated with ECOOP, ECMFA and ECSA 1–5 July, Montpellier, France http://rmod.lille.inria.fr/web/pier/Events/Dyla13 !! Important dates - Submission deadline: April 19th - Notification: mid-May - Workshop: July 1st - Ecoop early registration: mid-May !! Abstract The advent of Java and C# has been a major breakthrough in the adoption of some important object-oriented language characteristics. This breakthrough turned academic features like interfaces, garbage collection, and meta-programming into technologies generally accepted by industry. Nevertheless, the massive adoption of these languages now also gives rise to a growing awareness of their limitations. A number of reactions from industry testify this: invokedynamic bytecode instruction has been included in latest Java virtual machine release; the dynamic language runtime (DLR) is gaining popularity; C# adopted dynamic as a valid static type. Gartner prognoses further growth (http://blogs.gartner.com/mark_driver/2008/12/10) of dynamic languages. Researchers and practitioners struggle with static type systems, overly complex abstract grammars, simplistic concurrency mechanisms, limited reflection capabilities, and the absence of higher-order language constructs such as delegation, closures and continuations. Dynamic languages such as Ruby, Python, JavaScript and Lua are a step forward in addressing these problems while getting more and more popular. Making these languages mainstream requires practitioners to look back and pick mechanisms up in existing dynamic languages such as Lisp, Scheme, Smalltalk and Self. Practitioners also need to further explore discover new dynamic approaches in the context of new challenging fields such as pervasive computing. The goal of this workshop is to act as a forum where practitioners can discuss new advances in the design, implementation and application of dynamically typed languages that, sometimes radically, diverge from the statically typed class-based mainstream. Another objective is to discuss new as well as older "forgotten" languages and features in this context. Topics of interest include, but are not limited to: - programming language extensions - programming environment extensions - executing environments - static and dynamic analyses - optional type-checking - meta-object protocols - reserve engineering - domain-specific languages/tooling - testing environments - live programming !! Targeted audience The expected audience of this workshop is practitioners and researchers sharing the same interest in dynamically typed languages. Lua, Python, Ruby, Scheme and Smalltalk are gaining a significant popularity both in industry and academia. Nevertheless, each community has the tendency to only look at what it produces. Broadening the scope of each community is the goal of the workshop. To achieve this goal we will form a PC with leading persons from all languages mentioned above, fostering participation from all targeted communities. !! Workshop Format and Submission Information The workshop will have a demo-oriented style. The idea is to allow participants to demonstrate new and interesting features and discuss what they feel is relevant for the dynamic-language community. To participate to the workshop, you can either - submit (before __April 19th 2013__) an article (ACM Tighter Alternate style http://www.acm.org/sigs/publications/proceedings-templates) describing your presentation and/or tool. Articles whose length ranges from 2 to 15 pages will be carefully reviewed by a program committee including but not limited to the organizers. Each accepted paper will be presented for 20 to 30 minutes and be published to the ACM Digital Library (at the option of each author) and the workshop's web site. The submission website is http://www.easychair.org/conferences/?conf=dyla2013. - or give a 10-minute lightning demo of your work. A dedicated session will be allocated for this, provided there is ample time available. A session on pair programming is also planned. People will then get a chance to share their technologies by interacting with other participants. !! Program committee - Carl Friedrich Bolz, Heinrich-Heine-Universität Düsseldorf, Germany (http://cfbolz.de) - Camillo Bruni, Inria Lille-Nord Europe, France (http://rmod.lille.inria.fr/web/pier/team/bruni) - Adrian Kuhn, University of British Columbia, Canada (https://www.cs.ubc.ca/people/adrian-kuhn) - Lukas Renggli, Google, Switzerland (http://www.lukas-renggli.ch/) - Juan Pablo Sandoval Alcocer, University of Chile (http://users.dcc.uchile.cl/~jsandova/) - Bastian Steinert, Hasso-Plattner-Institute, Germany (http://www.bastiansteinert.org) - Veronica Uquillas Gomez, Vrije Universiteit Brussel, Belgium (http://soft.vub.ac.be/~vuquilla/) - Simon Urli, University of Nice-Sophia Antipolis, France (http://www.simonurli.fr/) - Didier Verna, EPITA Research and Development Laboratory, France (http://www.lrde.epita.fr/~didier) - the 4 workshop organizers !! Workshop Organizers - Alexandre Bergel (http://bergel.eu) - Damien Cassou (http://damiencassou.seasidehosting.st) - Jorge Ressia (http://www.jorgeressia.com) - Serge Stinckwich (http://www.doesnotunderstand.org) !! News feed Follow us on twitter: http://twitter.com/dyla2013 For further information: http://rmod.lille.inria.fr/web/pier/Events/Dyla13 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 26, 2013

Join ESUG for GSOC 2013

by Malintha Adikari

Hi, I am final year computer engineering undergraduate from University of Peradeniya. I would like to join ESUG for GSOC 2013. I am interesting about your organization & projects. Could you please tell me more details about the available projects if any Thanks & regards, Malintha Adikari

Feb. 26, 2013

[JOB][Research] 16 month Postdoc "Architectural Design Exploration"

by Marcus Denker

Architectural Design Exploration ================================ About Inria and the job ----------------------- Inria, with its academic, institutional and industrial partners, is commited to major research and innovation projects in the field of computational sciences. The institute disseminates across France thanks to its eight research centres. The Inria Lille - Nord Europe research centre, inaugurated in 2008, employs 357 people, including 250 scientists, in its seventeen research teams. Recognised for its significant contribution to the social and economic development of the Nord - Pas-de-Calais region, the Inria Lille - Nord Europe research centre promotes a policy of close cooperation with major businesses and small enterprises. By encouraging synergies between researchers and industrial partners, Inria contributes to the transfer of skills and expertise in computational technologies and provides access to top-level European and international research in order to support innovation and businesses, particularly in the region of Lille. Whether designing innovative software for business or logistics, modelling living cells or fusion plasma, or developing medical simulators or interfaces to facilitate human-computer interaction, our research opens up new possibilities that can revolutionise common practice and contribute to a better understanding of the natural phenomena which surround us. The postdoc is hosted by Team-Project RMoD. The goal of RMoD is to support remodularization of object-oriented applications. This objective is tackled from two complementary perspectives: reengineering and modularity constructs for programming languages. In the reengineering perspective we will propose new analyses to understand and restructure existing large applications (specialized package metrics, adapted visualizations, layer identification) on top of Moose [Duca08a], [Bhat12b]. http://rmod.lille.inria.fr/web/ Mission -------- Changes in the architecture may occur during the entire lifecycle of a system. Some of them might only affect local parts of a system, while others have more systemic impact. In general, we distinguish three types of approaches for handling change systematically, listed in an order of increasing severity: - Refactoring. They correspond to improvements and concern only certain components and connectors. They do not alter the offered functionality of the system. - Renovating. Sometimes, parts of the architecture are in such a bad condition that refactoring cannot work anymore. In such contexts, renovating the architecture – by restoring its fundamental principles or refreshing essential components – may be the better choice. Renovating also deals with only parts of the system. - Re-architecting. When an architecture is subject to significant changes, refactoring or renovating may not suffice. This might be the case if for example the technology platform is to be replaced by a new one, if there is a large change in business scope, or if the architecture is in such a bad shape that errors keep emerging. In such cases, re-architecting is required. The re-architecting process usually analyzes the existing architecture (e.g., using a SWOT analysis) and results in a new architecture by: a) reusing those components worthwhile to keep, b) modifying some of the existing components (refactoring) and c) re-building the rest of the components (renovating).[Ieee13] Because software engineers do not have a full understanding of the complete source code, each kind of changes may solve some problems (e.g. reduce some cycle between package), while creating new problems (e.g. creating new cycles). In this situation it would be profitable to have a tool that allows to test a possible new configuration (refactored, renovated or re-architectured) of the source code to see if the abstract property one wishes to improve, first actually improved, and second, did not improve at the expense of another equally important one. For this several alternatives new configurations have to be considered. In the RMoD team, we developed Orion [Lava10b], a tool that uses models as abstract representations of the program and enables the definition of several possible alternative versions of this program. Each version differentiates from the others by a set of refactoring operations. Currently, once an adequate version is selected, the user has to manually perform the operations on the code. Job offer description ---------------------- In this postdoc, we would like to enhance Orion in order to automatically generate code or modify the existing one once a version is chosen. Thus, it would be possible to study various alternatives of possible refactoring or restructuring of an existing program, using metrics [Abde12a], [Mord12b] or some other means [Hema12] to check the improvement in the "quality" of the code, and then ask the tool to perform the changes of the selected final solution onto the source code. The used metamodel enables a representation where code details are abstracted. A new metamodel for example AST metamodel, representing code will be introduced and the links between the two models will have to be maintained. Skills and profile -------------------- The candidate should : - hold a PhD degree in Computer Science - be fluent in English (French is an advantage but not required) - be knowledgeable in the domains of Software Engineering, maintenance, code analysis - have good programming skills in Smalltalk or be able to acquire them in a short amount of time Benefits --------- - Possibility of French courses - Help for housing - Participation for transportation - Scientific Resident card and help for husband/wife visa Additional information ----------------------- - Duration : 16 months - Salary: 2 620,84 € gross/month - Monthly salary after taxes : around 2 138€ (medical insurance included). - Before applying, please contact the scientist advisor: nicolas.anquetil(a)inria.fr - For the first selections, please apply before March 2013, 22nd Security and defense procedure ------------------------------- In the interests of protecting its scientific and technological assets, Inria is a restricted-access establishment. Consequently, it follows special regulations for welcoming any person who wishes to work with the institute. The final acceptance of each candidate thus depends on applying this security and defense procedure. More information: http://rmod.lille.inria.fr/web/pier/blog/2013-02-22-2

Feb. 25, 2013

[ANN] Minecraft Bindings

by Bert Freudenberg

I'm happy to announce my Smalltalk bindings for "Minecraft: Pi Edition": Find out more at http://croquetweak.blogspot.com/2013/02/smalltalk-bindings-for-minecraft-pi… - Bert -

Feb. 25, 2013

[JOB][Research] Postdoc position: IDEs

by Marcus Denker

Infrastructure for new generation IDEs ===================================== About Inria and the job ----------------------- Inria, with its academic, institutional and industrial partners, is commited to major research and innovation projects in the field of computational sciences. The institute disseminates across France thanks to its eight research centres. The Inria Lille - Nord Europe research centre, inaugurated in 2008, employs 357 people, including 250 scientists, in its seventeen research teams. Recognised for its significant contribution to the social and economic development of the Nord - Pas-de-Calais region, the Inria Lille - Nord Europe research centre promotes a policy of close cooperation with major businesses and small enterprises. By encouraging synergies between researchers and industrial partners, Inria contributes to the transfer of skills and expertise in computational technologies and provides access to top-level European and international research in order to support innovation and businesses, particularly in the region of Lille. Whether designing innovative software for business or logistics, modelling living cells or fusion plasma, or developing medical simulators or interfaces to facilitate human-computer interaction, our research opens up new possibilities that can revolutionise common practice and contribute to a better understanding of the natural phenomena which surround us. The goal of the RMoD research team at Inria Lille is to support re-modularization of object-oriented applications. This objective is tackled from two complementary perspectives: reengineering and modularity constructs for programming languages. For more information on RMOD, see http://rmod.lille.inria.fr Mission ------- The objectives will be to reconsider and develop a new infrastructure to build new and modern IDEs. The goal of this postdoc is to help the RMOD team rethinking the infrastructure of Pharo from the point of view of its user interface and interaction foundation as well as code navigation. The following topics will be analysed and rethought : - Alternate models of event handling - Decomposing responsibilities of event handler and dispatchers. - Alternative ways to navigate code - Queries to access code elements - Smart handling of coding contexts - Management of window plague - Support for contextual refactorings and automated code transformation. Skills and profile ------------------ - English - Pharo: http://www.pharo.org - User interface design, Vector graphics - IDE design and user interactions Benefits --------- - Possibility of French courses - Help for housing - Participation for transportation - Scientific Resident card and help for husband/wife visa Additional information ----------------------- - Duration : 16 months - Salary: 2 620,84 € gross/month - Monthly salary after taxes : around 2 138 € (medical insurance included) - For the first selections, please apply before March 2013, 22nd. - Before applying, please contact the scientist advisor: stephane.ducasse(a)inria.fr - More information: http://rmod.lille.inria.fr/web/pier/blog/2013-02-22 Security and defense procedure ------------------------------ In the interests of protecting its scientific and technological assets, Inria is a restricted-access establishment. Consequently, it follows special regulations for welcoming any person who wishes to work with the institute. The final acceptance of each candidate thus depends on applying this security and defense procedure.

Feb. 24, 2013