Hi, A student of mine worked on a petit javascript parser. The tags covered are not that much but you might like to take a look. The project is called PetitJSParser http://www.squeaksource.com/@RFTiNHNPPC2NVeeI/kidwMQO9 Cheers, Fabrizio 2012/3/21 Norbert Hartl <norbert(a)hartl.name>

On Mar 21, 2012, at 7:41 AM, Tudor Girba wrote: Yes :) Doing software analysis. Research and commercially (i hope) software analysis, for other kinds of analysis. reality." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On 21 mrt 2012, at 07:41, Tudor Girba wrote: Diego and I use Moose for data conversion from an old Cobol system to a modern ERP system. We use glamour, mondrian, and eyesee to create a 'daily visualization'. The fast feedback it allows is crucial for us to keep the customer "steering" the conversion. We can show her what we do and do not understand, and it allows her to prioritize. We build a custom parser for the parts of the cobol files we were interested in. In hindsight, using petitparser for that would have been a better decision. We added a simple seaside application to allow multiple people to make corrections to the data. Stephan Eggermont _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

wrote:

Diego would it be possible to see one of your daily visualization? Just curious to see how visualization can help people understanding what we are doing. Stef On Mar 21, 2012, at 5:41 PM, Stephan Eggermont wrote: for interested decision. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

wrote:

using for research. We have a small presentation of Moose with a slide saying that: 1- have an idea 2- implement it in 5min. with moose 3- publish the results The 5 min. are a bit understated, but this is what we do. In my case, mainly metrics computation nicolas On 21/03/12 07:41, Tudor Girba wrote: ______________________________**_________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/**mailman/listinfo/moose-dev<https://www.iam.un…

Hi! Yes, we are using moose at the university of chile. Moose is central in a lecture I give on software quality during one semester. We research with moose. Currently we are improving dependencies of a model by running unit tests. I am principally developing and maintening Mondrian. A new visualization engine, called Roassal, will be soon released. roassal supports better interactions. Moose is also the core of a number of industrial proposals I submitted. We will see how it goes... Cheers, Alexandre Le 21 mars 2012 à 01:41, Tudor Girba &lt;tudor(a)tudorgirba.com&gt; a écrit : software analysis, for other kinds of analysis. reality." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Have you ever consider doing a screencast, in order to explain how do you those tools? On Thu, Mar 22, 2012 at 10:51 AM, Alexandre Bergel &lt;alexandre.bergel(a)me.com&gt; wrote: Hi! Yes, we are using moose at the university of chile. Moose is central in a lecture I give on software quality during one semester. We research with moose. Currently we are improving dependencies of a model by running unit tests. I am principally developing and maintening Mondrian. A new visualization engine, called Roassal, will be soon released. roassal supports better interactions. Moose is also the core of a number of industrial proposals I submitted. We will see how it goes... Cheers, Alexandre Le 21 mars 2012 à 01:41, Tudor Girba &lt;tudor(a)tudorgirba.com&gt; a écrit : _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

For the thesis of my Master of Engineering Technology (Electric Power Systems) I am using Moose to implement the IEC 61970 Common Information Model [1] as part of the emerging requirements for Electric Smart Grids. This is the international standard for the exchange of electric power model information between power utilities to facilitate co-ordinated operations across the interconnected electric power network. The standards committee overseeing IEC 61970 subscribes to the OMG Model Driven Architecture and maintains the standard as a UML model consisting of about 800 classes. I am hoping to produce a tool useful for exploring this model and as well as providing a basis for building electric power applications. I was attracted to implementing this using the Connectors application on Squeak, and was then drawn to Pharo for its more business focus, and now to Moose for its integration of the applications above Pharo that I have gradually discovered to be most useful - which for me so far are the trifecta of Glamour, Magritte and Mondrian. I had been trying to make use the FAME meta-model stuff but the UML related stuff appears to have been dropped and I could not determine a path forward to using it as I required.

[1] http://en.wikipedia.org/wiki/Common_Information_Model_%28electricity%29 [2] http://www.nist.gov/public_affairs/releases/upload/smartgrid_interoperabili… This project arose to fill a need for tools to work with the emerging standards for the electric power industry. As an overview of the general need in this area, I have pulled some extracts from [2]... "Under the Energy Independence and Security Act of 2007 (EISA), the National Institute of Standards and Technology (NIST) is assigned the “primary responsibility to coordinate development of a framework that includes protocols and model standards for information management to achieve interoperability of Smart Grid devices and systems…” There is an urgent need to establish protocols and standards for the Smart Grid. In May 2009, U.S. Secretary of Commerce Gary Locke and U.S. Secretary of Energy Steven Chu chaired a meeting of nearly 70 executives from the power, information technology, and other industries at which these executives expressed their organizations’ commitment to support the plan established by NIST to meet its EISA responsibility. " "This document [2] was drafted through an open public process that engaged the broad spectrum of Smart Grid stakeholder communities and the general public. Input was provided through three public workshops, in April, May and August 2009, in which more than 1,500 individuals representing hundreds of organizations participated. Through the NIST workshops, NIST determined that many potentially useful standards will require revision or enhancement before they can be implemented to address Smart Grid requirements. In addition, stakeholders identified gaps requiring entirely new standards to be developed. In all, a total of 70 such gaps or related issues were identified. Of these, NIST selected 15 for which resolution is most urgently needed to support one or more of the Smart Grid priority areas." [BTC: Half of these Priority Action Plans refer to the IEC 61850, 61970, 61968 standards of IEC Technical Committee 57. ] <moz-screenshot-14.jpg> "A recent forecast projects that the U.S. market for Smart Grid-related equipment, devices, information and communication technologies, and other hardware, software, and services will double between 2009 and 2014—to nearly $43 billion. Over the same span, the global market is projected to grow to more than $171 billion, an increase of almost 150 percent." regards, Ben Tudor Girba wrote: _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev