Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Esteban Lorenzano

Hi, I'm having a problem updating labels with glamour. I explain: I have a browser with a "status line" at the bottom, something like this: browser := GLMTabulator new row: #itemDetail; row: #summary size: 18; yourself. then, on #summary: browser transmit to: #summary; andShow: [ :presenter | presenter label updateOn: AnAnnouncement from: [self announcer ]; display: [ self summary ] ]. but the summary is never updated :( I'm doing something wrong, or this is a bug? (if I change #label for #text, it is updated properly). Also... dynamicActions shouldn't be updated, on a presentation update? Now I'm using some "status buttons" (it changes an overlay depending on status), and of course, I would like to update it when something changes... how can I do that? best, Esteban

13 years, 11 months

Re: next steps

by Alexandre Bergel

Cool! Can you try a class blueprint? Alexandre On 3 Jun 2011, at 22:39, Santiago Vidal wrote: > Hi, > I committed the Mondrian extensions to support the HTML/Protovis file generation. It took some time because I had some performances issues whit dragging. Also, I had to use an external library to the tooltips because Protovis only supports basic tooltips in a single line. Owing to these problems some additional files are required to run the generated html (I'm attaching these files). > Currently the visitor only support the generation of graphics with rectangle nodes and edges. Specifically, inner nodes, DistributionMap, and system complexity. (I'm also attaching an example of each one) > I gladly welcome your comments! ;) > Cheers > Santiago > > 2011/5/30 Alexandre Bergel <alexandre.bergel(a)me.com> > Looks good. > Edges now > > Alexandre > > On 30 May 2011, at 16:03, Santiago Vidal wrote: > > > I have changed the implementation. Now you can click and drag the inner nodes. The new file is in the attachment. > > Take care > > Santiago > > > > 2011/5/30 Alexandre Bergel <alexandre.bergel(a)me.com> > > > Currently you can select an inner node but you can't drag it. That is because the position of an inner node is determined by the position of its parent. However, I think that the implementation could be change properly. > > > > Ok, let us know > > > > Alexandre > > > > > > > > 2011/5/30 Tudor Girba <tudor(a)tudorgirba.com> > > > Hi, > > > > > > Looks good. However, I think there is a problem: the inner nodes do drag together with the parent node, but I would also like to be able to interact with the inner nodes (e.g., drag or click). Is this a conceptual problem, or is it simple a missing implementation? > > > > > > Cheers, > > > Doru > > > > > > > > > On 30 May 2011, at 18:22, Santiago Vidal wrote: > > > > > > > Sorry, the tittle is wrong. They are inner nodes. I use this example code: > > > > view nodes: (1 to: 5) forEach: [:each | > > > > view nodes: (1 to: each). > > > > view gridLayout ] > > > > > > > > 2011/5/30 Alexandre Bergel <alexandre.bergel(a)me.com> > > > > Yes, this is what I see. But the image is named inner edges and I do not see any edge. > > > > An edge is a line > > > > > > > > Cheers, > > > > Alexandre > > > > > > > > > > > > On 30 May 2011, at 11:12, Santiago Vidal wrote: > > > > > > > > > You should see this > > > > > <InnerEdges.png> > > > > > > > > > > 2011/5/30 Alexandre Bergel <alexandre.bergel(a)me.com> > > > > > Good start! > > > > > In innerEdgesExampleWithAbsolutePosition.html I do not see any edge. Am I the only one? I use Safari and OSX. > > > > > > > > > > Can you try with _large_ visualization? Try to import the whole Moose and generate the visualizations. > > > > > > > > > > Alexandre > > > > > > > > > > > > > > > On 30 May 2011, at 10:52, Santiago Vidal wrote: > > > > > > > > > > > Hi, > > > > > > I have been working in visualization examples of complexity, inner nodes, and distribution map. I used for these examples the second option that we discuss previously. The examples are in the attachment. > > > > > > Cheers > > > > > > Santiago > > > > > > > > > > > > 2011/5/27 Tudor Girba <tudor(a)tudorgirba.com> > > > > > > Hi, > > > > > > > > > > > > You should go for both options. > > > > > > > > > > > > Start with 2, and for 1, you will create new MondrianLayouts that will only work directly with Protovis. > > > > > > > > > > > > Cheers, > > > > > > Doru > > > > > > > > > > > > > > > > > > On 27 May 2011, at 19:02, Santiago Vidal wrote: > > > > > > > > > > > > > I don't know yet. In principle I'm going to implement the drag & drop behavior. In going to try to make an example using the Mondrian representation for Monday. > > > > > > > > > > > > > > 2011/5/27 Johan Fabry <jfabry(a)dcc.uchile.cl> > > > > > > > > > > > > > > I agree with Alex, but I have a question: how do you plan to handle interactions, more specifically node replacement operations? > > > > > > > > > > > > > > On 27 May 2011, at 12:22, Alexandre Bergel wrote: > > > > > > > > > > > > > > > I feel we should opt for 2). > > > > > > > > We should export the visualization using Protovis, not recoding Mondrian in Protovis. > > > > > > > > > > > > > > > > Alexandre > > > > > > > > > > > > > > > > > > > > > > > > On 27 May 2011, at 12:19, Santiago Vidal wrote: > > > > > > > > > > > > > > > >> Hi, > > > > > > > >> I have been working in the visualization of the inner nodes. In general I have 2 options to work with protovis: > > > > > > > >> • Be independent of the data by means of the use of Protovis Layouts. > > > > > > > >> • Copy the same visualization that is used by Mondrian. That is create a Protovis canvas of the same size that the canvas of Mondrian and place each shape in Protovis in the same location that in the canvas of Mondrian. > > > > > > > >> While the first option is more modifiable than the second, it implies the creation of new layouts when they are needed. > > > > > > > >> The main advantage of the second option is that the generated html file could be interactive (such as the example that I send before). However, it doesn't improve the graphics generated by Mondrian. > > > > > > > >> What do you think is the best option? > > > > > > > >> Cheers > > > > > > > >> Santiago > > > > > > > > > > > > > > -- > > > > > > > Johan Fabry > > > > > > > jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry > > > > > > > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Moose-dev mailing list > > > > > > > Moose-dev(a)iam.unibe.ch > > > > > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Ing. Santiago A. Vidal > > > > > > > ISISTAN Research Institute > > > > > > > UNICEN University > > > > > > > Paraje Arroyo Seco > > > > > > > Campus Universitario > > > > > > > (B7001BBO) Tandil, > > > > > > > Bs. As. - Argentina > > > > > > > Phone: 54 2293 439840 Ext. 42 > > > > > > > Fax: 54 2293 439681 > > > > > > > Email: svidal(a)exa.unicen.edu.ar > > > > > > > http://www.exa.unicen.edu.ar/~svidal > > > > > > > _______________________________________________ > > > > > > > Moose-dev mailing list > > > > > > > Moose-dev(a)iam.unibe.ch > > > > > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > > > > > -- > > > > > > www.tudorgirba.com > > > > > > > > > > > > "Not knowing how to do something is not an argument for how it cannot be done." > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Moose-dev mailing list > > > > > > Moose-dev(a)iam.unibe.ch > > > > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Ing. Santiago A. Vidal > > > > > > ISISTAN Research Institute > > > > > > UNICEN University > > > > > > Paraje Arroyo Seco > > > > > > Campus Universitario > > > > > > (B7001BBO) Tandil, > > > > > > Bs. As. - Argentina > > > > > > Phone: 54 2293 439840 Ext. 42 > > > > > > Fax: 54 2293 439681 > > > > > > Email: svidal(a)exa.unicen.edu.ar > > > > > > http://www.exa.unicen.edu.ar/~svidal > > > > > > <protovisMondrian.zip>_______________________________________________ > > > > > > Moose-dev mailing list > > > > > > Moose-dev(a)iam.unibe.ch > > > > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > > > -- > > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > > Alexandre Bergel http://www.bergel.eu > > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Moose-dev mailing list > > > > > Moose-dev(a)iam.unibe.ch > > > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > > > > > > > > > > > > > -- > > > > > Ing. Santiago A. Vidal > > > > > ISISTAN Research Institute > > > > > UNICEN University > > > > > Paraje Arroyo Seco > > > > > Campus Universitario > > > > > (B7001BBO) Tandil, > > > > > Bs. As. - Argentina > > > > > Phone: 54 2293 439840 Ext. 42 > > > > > Fax: 54 2293 439681 > > > > > Email: svidal(a)exa.unicen.edu.ar > > > > > http://www.exa.unicen.edu.ar/~svidal > > > > > _______________________________________________ > > > > > Moose-dev mailing list > > > > > Moose-dev(a)iam.unibe.ch > > > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > -- > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > Alexandre Bergel http://www.bergel.eu > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Moose-dev mailing list > > > > Moose-dev(a)iam.unibe.ch > > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > > > > > > > > > -- > > > > Ing. Santiago A. Vidal > > > > ISISTAN Research Institute > > > > UNICEN University > > > > Paraje Arroyo Seco > > > > Campus Universitario > > > > (B7001BBO) Tandil, > > > > Bs. As. - Argentina > > > > Phone: 54 2293 439840 Ext. 42 > > > > Fax: 54 2293 439681 > > > > Email: svidal(a)exa.unicen.edu.ar > > > > http://www.exa.unicen.edu.ar/~svidal > > > > _______________________________________________ > > > > Moose-dev mailing list > > > > Moose-dev(a)iam.unibe.ch > > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > -- > > > www.tudorgirba.com > > > > > > "If you interrupt the barber while he is cutting your hair, > > > you will end up with a messy haircut." > > > > > > > > > _______________________________________________ > > > Moose-dev mailing list > > > Moose-dev(a)iam.unibe.ch > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > > > > > -- > > > Ing. Santiago A. Vidal > > > ISISTAN Research Institute > > > UNICEN University > > > Paraje Arroyo Seco > > > Campus Universitario > > > (B7001BBO) Tandil, > > > Bs. As. - Argentina > > > Phone: 54 2293 439840 Ext. 42 > > > Fax: 54 2293 439681 > > > Email: svidal(a)exa.unicen.edu.ar > > > http://www.exa.unicen.edu.ar/~svidal > > > _______________________________________________ > > > Moose-dev mailing list > > > Moose-dev(a)iam.unibe.ch > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > > > -- > > Ing. Santiago A. Vidal > > ISISTAN Research Institute > > UNICEN University > > Paraje Arroyo Seco > > Campus Universitario > > (B7001BBO) Tandil, > > Bs. As. - Argentina > > Phone: 54 2293 439840 Ext. 42 > > Fax: 54 2293 439681 > > Email: svidal(a)exa.unicen.edu.ar > > http://www.exa.unicen.edu.ar/~svidal > > <protovisMondrian.zip>_______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)iam.unibe.ch > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > Ing. Santiago A. Vidal > ISISTAN Research Institute > UNICEN University > Paraje Arroyo Seco > Campus Universitario > (B7001BBO) Tandil, > Bs. As. - Argentina > Phone: 54 2293 439840 Ext. 42 > Fax: 54 2293 439681 > Email: svidal(a)exa.unicen.edu.ar > http://www.exa.unicen.edu.ar/~svidal > <DistributionMap.html><DragWithChildRestriction.js><ex.css><jquery.tipsy.js><jquery-1.4.2.min.js><protovis-r3.2.js><tipsy.css><tipsyBehavior.js><innerNodes.html><SystemComplexity.html>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 11 months

Moose for SAS

by Ross Boylan

Some people suggested trying moose for analysis of SAS programs, and I'm trying to figure out where to start with the meta-modeling. SAS is not object oriented, though parts of it could be imagined to be. The main SAS code contains blocks of statements that begin with DATA or PROC; each block could probably be thought of as a function--to be precise, the application of a function. If I want to make some new models, where do I start? FM3? FAMIX? elsewhere? The 4.0 release announcement says FM3 and FAMIX3 are both implemented in Fame, so maybe start with Fame? I've read some documentation, but I can't tell. My inspiration for the project is understanding how some SAS datasets were produced. I have a system that creates numerous datasets, which feed into later datasets, etc. This is split at least across a couple of program files and it's really too complicated to keep in the brain. If I get ambitious it would also be useful to trace where particular variables came from, in the sense of both datasets and individual expressions. The only thing resembling a SAS parser I've run into (except for SAS, which is closed source) is a Perl module, and it looked relatively primitive. I've been using PetitParser, and at the point I started thinking about what it would parse results into. Thanks for any pointers. Ross Boylan

13 years, 11 months

Moose-groups

by Nicolas Anquetil

When working on eclipse, I discovered the necessity to represents things like plugins or components which are not directly handled in Famix. It is important if we want to be able to deal with real world cases. May be we should consider introducing them as Moose Entities? Or may be not: I used Moose-Groups (of class because one package can be spread over different plugins) and it is not that bad. the main issue, in my case, was that classes don't know to what group they have been assigned... So computing dependencies could be very lengthy. I solved that by creating a dictionary on the side, but maybe we should think on a better solution. And then of course integrate this with all the tools... nicolas

13 years, 11 months

MSE: Dealing with Associations

by Usman Bhatti

I am looking to understand what mse entities are created for associations (except inheritance i.e. invocations, access, refs) in code and how to exactly treat the duplicates. I have seen a reference of it in a bug reported for VerveineJ but I am not sure if this issue has been discussed elsewhere. For example, A a; M() { a = new A(); a = new A(); a.CallAMethod(); a.CallAMethod(); } The above code creates these associations (with Verveinesharp) .. 1. An invocations to A's constructor (duplicate constructor invocation is ignored). 2. A field access to the field a (only one instance is recorded, the others are just ignored). 3. An invocation to CallAMethod (field access is already recorded so this one is not considered). 4. A reference from method M() to type A (Duplicate reference is ignored). Please let me know if there an anomaly. thanx, Usman

13 years, 11 months

moose 4.5

by Tudor Girba

Hi, I would like to release a Moose 4.5 sometime next week. There are several fixes that came in Moose after 4.4, and it would be a pity to wait to integrate them. I would still like to get the tests working on the server, but I do not know how. Can anyone take a look? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow."

13 years, 11 months

verveinej unknown element

by Tudor Girba

Hi, I now got the following error when parsing a proprietary piece of code: Exception in thread "main" ch.akuhn.fame.internal.RepositoryVisitor$UnknownElementError: Unknown element: null found via description: FAMIX.ParameterizedType.arguments at ch.akuhn.fame.internal.RepositoryVisitor.getSerialNumber(RepositoryVisitor.java:141) at ch.akuhn.fame.internal.RepositoryVisitor.acceptElement(RepositoryVisitor.java:100) at ch.akuhn.fame.internal.RepositoryVisitor.acceptVisitor(RepositoryVisitor.java:150) at ch.akuhn.fame.internal.RepositoryVisitor.run(RepositoryVisitor.java:195) at ch.akuhn.fame.Repository.accept(Repository.java:105) at ch.akuhn.fame.Repository.exportMSE(Repository.java:217) I did not know how to isolate this, but it seems to me that the problem is somehow related to FAMIX. Am I right? Cheers, Doru -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

13 years, 11 months

Fwd: [Pharo-project] Report generation? (I need an update)

by Stéphane Ducasse

could be interesting in the future Stef Begin forwarded message: > From: Johan Brichau <johan(a)inceptive.be> > Date: June 8, 2011 7:08:52 PM GMT+02:00 > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Report generation? (I need an update) > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > > On 08 Jun 2011, at 17:37, Esteban Lorenzano wrote: > >> So... my question: >> what do you use to generate reports to clients? >> if pdf generation... which strategy? > > We use Jasper reports: www.jasperforge.org > It's a feature-rich library for generation of any report to about any format you can think of, and it's open source. > > The downside is: it is a Java library but we use http communication between our Seaside app and the jasper application. > In the future, I hope to get my own Javaconnect library (working in Visualworks) rolling completely in Pharo to have native communication from Pharo to Java. > In the meantime, you might try JNIPort since that one has Pharo version already. > > We can try to develop everything in Smalltalk but we will fail to keep up. > > Johan

13 years, 11 months

How to load Moose for Dev?

by Diego Fernandez

Hi all, I'm working with Java code using Verveine as the parser and Moose 4.4. Currently I'm having some problems, and I want to debug them to collaborate with the Moose project. But I'm stuck trying to load the latest version of Moose. I used the instructions from http://www.themoosebook.org/book/internals/development/load but as some people commented previously in the list I got a dependency error with Pharo 1.2.1. What is the best way to load the latest version of Moose? Can I update the image from the Moose 4.4 one-click installation? I have to try with the Pharo dev version? Thanks, Diego PS: The problems that I'm trying to resolve are: - DNUs with the FAMIX model (from the previous comments on the list it seems that some methods needs to be implemented to work with the FAMIX model generated from Java). - When working with a large FAMIX model, Moose crashes (I'm working with MacOSX Leopard 10.5.8, and the one-click Moose 4.4 download). I loaded a medium size Java app, the MSE loads fine, but when I click in the "All famixaccesses" of the Moose Panel the VM crashes.

13 years, 11 months

petit parser - exceeded maximum number of instance variables

by Norbert Hartl

I learned something today. While talking about the maximum number of instance variabes I always thought it is a limit per class. But now I know it is a limit on an object. As I reached 230 instance variables I started to split the parser into two. But now I reached the limit and cannot add instance variables. I need some ideas about how to structure the parser. I think it will be too hard to find parts of the grammar that are distinct so it would be possible to separate them into different classes. Another way would be to access some of the parser via method calls instead of accessing the instVar parsers. So does anybody has some experience in how to structure parsers? thanks, Norbert

13 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev