Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

What do we use from XMLSupport?
by Stéphane Ducasse 26 Feb '13

26 Feb '13

Hi guys I do not like the configurationOfXMLSupport because it introduces references to project using XML and I think that it makes little sense and leads to more complex configuration. I ported XMLWriter to SmalltalkHub and now I'm considering creating XMLParser with the parsing aspects of XMLSupport. I do not want to manage SIXX, Pastell: they should have their own projects and configurations! I could create a project, configuration… for Pastell for example. Do you know know what Moose really needs? Stef

3 2

these projs are still residing in SS
by Usman Bhatti 26 Feb '13

26 Feb '13

Stef, These are the moose-related projects that are still hosted on SS, so if you can move these to SThub it will be great. These are not part of core-default baseline but still these are loaded in the current version of Moose. http://www.squeaksource.com/dsm http://www.squeaksource.com/SmallDude http://www.squeaksource.com/Kumpel http://www.squeaksource.com/Metanool tx, Usman

1 0

Fwd: [Pharo-users] [JOB][Research] 16 month Postdoc "Architectural Design Exploration"
by Tudor Girba 25 Feb '13

25 Feb '13

---------- Forwarded message ---------- From: Marcus Denker <marcus.denker(a)inria.fr> Date: Mon, Feb 25, 2013 at 10:41 AM Subject: [Pharo-users] [JOB][Research] 16 month Postdoc "Architectural Design Exploration" To: "Pharo-project(a)lists.gforge.inria.fr Development" < Pharo-project(a)lists.gforge.inria.fr>, A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> Cc: The general-purpose Squeak developers list < squeak-dev(a)lists.squeakfoundation.org> 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 -- www.tudorgirba.com "Every thing has its own flow"

1 0

Carrack?
by Alexandre Bergel 25 Feb '13

25 Feb '13

Hi! What Carrack is about? I guess it is related to Moose, but http://www.squeaksource.com/Carrack.html does not say much... The abstract of Fabrizo says it is an inferencer for dependencies. Maybe a short explanation, and even better, a very short example in the squeaksource and the moose website would be great... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 2

Moose loaded on Pharo 2.0
by Nicolas Anquetil 22 Feb '13

22 Feb '13

tests are red :-) (not that much because we only took Moose-Ttests*) 1005 run, 969 passes, 0 skipped, 1 expected failures, 13 failures, 22 errors, 0 unexpected passes nicolas -- Nicolas Anquetil -- RMod research team (Inria)

1 0

glamour moved
by Usman Bhatti 22 Feb '13

22 Feb '13

I moved glamour to STHub - config updated to create a baseline for pharo1.4 pointing to STHub for as many packages as possible (roassal, Metacello, BDD is still in SS) - loaded the baseline in 1.4 pharo...all tests green... - created a baseline for pharo 2.0...loaded in 2.0 and ran tests, here are the results: 357 run, 246 passes, 0 skipped, 12 expected failures, 0 failures, 99 errors, 0 unexpected passes - I wanted to define #stable and #development but since these are already defined with specific version info, I didn't modify these. Doru, can you have look for the definition of symbolic versions?

1 0

glamour in the course of being migrated
by Tudor Girba 22 Feb '13

22 Feb '13

Hi, I started to migrate Glamour to SmalltalkHub. Cheers, Doru -- www.tudorgirba.com "Some battles are better lost than fought."

4 19

Jenkins build became unstable: moose-latest-dev #1287
by address not configured yet 21 Feb '13

21 Feb '13

See <http://localhost:8020/job/moose-latest-dev/1287/>

2 2

Fwd: [Pharo-project] Time Series in Smalltalk
by stephane ducasse 21 Feb '13

21 Feb '13

I thought that we had something like that in Moose. Begin forwarded message: > From: Serge Stinckwich <serge.stinckwich(a)gmail.com> > Subject: [Pharo-project] Time Series in Smalltalk > Date: February 20, 2013 10:28:10 PM GMT+01:00 > To: Pharo Development <pharo-project(a)lists.gforge.inria.fr> > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > Hi all, > > I'm looking for a time series library available in Smalltalk. > Something like Python Time Series Analysis : http://pytseries.sourceforge.net/ > or > Pandas: http://pandas.pydata.org/ > > Thank you. > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ >

1 0

config of moose on SThub
by Usman Bhatti 21 Feb '13

21 Feb '13

I sent this mail yesterday but strangely no received it, so here it is again. With Nicolas, we have created a first baseline of Moose based on the projects in STHub. The baseline baseline47STHub: corresponds to the old core-default baseline. Loading the baseline on 1.4 works fine, here are the test results: 998 run, 991 passes, 1 expected failures, 6 failures, 0 errors, 0 unexpected passes For each proj moved to SThub, we have tried to define two symbolic versions: #stable: a specific version of a proj at the time of move to STHub #bleedingEdge: load the latest packages of a proj.

4 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev