- Moose-dev - INF Mailman

by Alexandre Bergel

Hi! I am experiencing a situation which is either unintuitive or reflects a bug. Consider the following script -=-=-=-=-=-=-=-=-= | browser | browser := GLMFinder new. browser text act: [:prez :v | v inspect ] on: $i entitled: 'Inspect'. browser openOn: 'hello world' -=-=-=-=-=-=-=-=-= If start to type in it, and trigger the action, an inspector on the string 'hello world' is open, no matter what I typed. Is there anything obvious that I do not see? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 10 months

2
5
0 0

Issue 700 in moose-technology: Hover in Glamour

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Medium Component-Glamour New issue 700 by alexandr...(a)gmail.com: Hover in Glamour http://code.google.com/p/moose-technology/issues/detail?id=700 #hover is not yet supported by the rendering. Please open a ticket, because this is an old to do that should not be difficult to do. Cheers, Doru On 5 Sep 2011, at 21:56, Alexandre Bergel wrote: Hi! Just wondering whether #hover is supported in Glamour. Apparently not, but I just want to be sure. Cheers, Alexandre

13 years, 10 months

1
0
0 0

Hover in Glamour

by Alexandre Bergel

Hi! Just wondering whether #hover is supported in Glamour. Apparently not, but I just want to be sure. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 10 months

2
2
0 0

Re: [Pharo-project] data set

by Tudor Girba

Thanks everyone for the suggestions. I will try to look into them. Cheers, Doru On 5 Sep 2011, at 07:04, Lukas Renggli wrote: > Stanford has many large graph-like datasets to download: social > networks, web graphs, peer-to-peer networks, shopping networks, road > networks, wikipedia networks, etc. > > http://snap.stanford.edu/data/ > > Lukas > > On 5 September 2011 06:24, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> I've used as an example of datamining a dataset about car accidents we got >> from here http://www.nhtsa.gov/NASS . >> >> Hope it helps :) >> Guille >> >> On Sun, Sep 4, 2011 at 11:58 PM, Hernán Morales Durand >> <hernan.morales(a)gmail.com> wrote: >>> >>> 2011/9/4 Tudor Girba <tudor(a)tudorgirba.com>: >>>> Hi, >>>> >>>> Thanks, but I am looking for data sets that contained graphs of entities >>>> with properties, rather then numbers. >>>> >>> >>> Oh, that was just the top of the iceberg, look at cellular interaction >>> networks like protein-protein interactions, relations between genes >>> and QTLs, phylogenetic trees, gene ontology classifications, etc. >>> probably they have more "properties" and relationships than you ever >>> imagined. Check for example >>> http://www.nature.com/msb/journal/v3/n1/fig_tab/msb4100166_F2.html or >>> the one from the Human Interactome here >>> http://www.blog.republicofmath.com/archives/2005, or >>> http://www.biomedcentral.com/content/supplementary/1471-2164-9-96-s6.jpeg >>> for Gene Ontology "objects". Also PubMed have thousands of related >>> papers about real case studies. >>> >>>> To give an idea, an example would be a set of persons that have multiple >>>> properties, such as age or function, and have various kinds of relationships >>>> with other persons. Ideally, it should be something containing some more >>>> than 5-10 types of entities. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 5 Sep 2011, at 02:51, Hernán Morales Durand wrote: >>>> >>>>> Hi Tudor, >>>>> >>>>> I don't know if you want few data sets or many ones, but for each case >>>>> I found "Selecting genes with dissimilar discrimination strength for >>>>> sample class prediction", report case studies in two real cancer >>>>> microarray datasets (CAR and LUNG) for gene expression profiling. The >>>>> Lymphoma case study in humans contains 30 case study genes, you may >>>>> read about it in "Examples and Applications of Fuzzy Measure >>>>> Similarity Using GO Terms". In general you can find many case studies >>>>> from SNP data experiments doing all kind of predictions, for example >>>>> from protein structure prediction studies that use LiveBench data sets >>>>> (http://en.wikipedia.org/wiki/LiveBench), search for "Consensus fold >>>>> recognition by predicting model quality". >>>>> If you need more or something more specific just ask :) >>>>> Cheers, >>>>> >>>>> Hernán >>>>> >>>>> 2011/9/4 Tudor Girba <tudor(a)tudorgirba.com>: >>>>>> Hi, >>>>>> >>>>>> To show how Moose can support the analysis of various data sets, I am >>>>>> looking for a case study containing a complex data structure that does not >>>>>> represent a software system, and a set of questions associated with it. >>>>>> Ideally, the data should be freely available and it should contain a set of >>>>>> entities with various properties and various relationships with other >>>>>> entities. >>>>>> >>>>>> Anyone has any idea regarding such a case study? >>>>>> >>>>>> Cheers, >>>>>> Doru >>>>>> >>>>>> -- >>>>>> www.tudorgirba.com >>>>>> >>>>>> "There are no old things, there are only old ways of looking at them." >>>>>> >>>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every successful trip needs a suitable vehicle." >>>> >>> >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > -- www.tudorgirba.com "Reasonable is what we are accustomed with."

13 years, 10 months

1
0
0 0

Issue 699 in moose-technology: Glamour presentations should be easily extensible

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-Glamour Milestone-4.6 New issue 699 by tudor.gi...(a)gmail.com: Glamour presentations should be easily extensible http://code.google.com/p/moose-technology/issues/detail?id=699 Currently, scripting Glamour presentations relies solely on direct setters to the presentations. This makes it hard to create presentations that rely on composite structures. A simple way to provide an extension mechanism would be to implement a with: method: GLMPresentation>>with: aBlock ^ aBlock value: self We could use it like this: composite text with: [:textPresentation | textPresentation ... ]

13 years, 10 months

1
1
0 0

Re: Issue 106 in moose-technology: Disable the default Smalltalk shortcuts from the Text Morphic widget in Glamour

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Milestone-4.4 Comment #5 on issue 106 by tudor.gi...(a)gmail.com: Disable the default Smalltalk shortcuts from the Text Morphic widget in Glamour http://code.google.com/p/moose-technology/issues/detail?id=106 (No comment was entered for this change.)

13 years, 10 months

1
3
0 0

Issue 655 in moose-technology: export a moose model raise an error

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 655 by cy.delau...(a)gmail.com: export a moose model raise an error http://code.google.com/p/moose-technology/issues/detail?id=655 Try to import a smalltalk model in moose. Right click on the model and 'export to mse' . at the end of the export you will get: MessageNotUnderstood: receiver of "sender" is nil I think it is related this issue : http://code.google.com/p/moose-technology/issues/detail?id=635 At the end of the export there is a notification signaling that the export succeed. The new way announcements are dealing now with exception signals lead to those kind of behavior

13 years, 10 months

1
6
0 0

Issue 694 in moose-technology: Should be able to 'do it' in text presentations

by moose-technology＠googlecode.com

Status: Started Owner: damien.c...(a)gmail.com CC: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour New issue 694 by damien.c...(a)gmail.com: Should be able to 'do it' in text presentations http://code.google.com/p/moose-technology/issues/detail?id=694 In Glamour, it is not possible to select a piece of text and "do it". Steps to reproduce: 1- GLMBasicExamples open 2- Select one example 3- Select 'Source code' 4- Type 'self' somewhere and print it It should print 'GLMBasicExamples' and not 'nil' as it currently does.

13 years, 10 months

1
5
0 0

Support for Hismo?

by Alexandre Bergel

Hi! Is there a support for Hismo? I would like to monitor my programming activities. I would like to know how many new methods I modified when I commit on squeaksource for example. Can Moose help for this? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 10 months

2
2
0 0

Glamour is not loadable in Pharo 1.4

by Alexandre Bergel

Any plan to make this happen? Apparently, a dependency on RB is missing. I do not know how critical this dependency is actually. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 10 months

2
1
0 0

[ANN] glamorous inspector

by Tudor Girba

Hi, I am happy to announce the first release of the Glamorous Inspector, a new browser for inspecting objects based on Glamour. More information, including a demo and screenshots, can be found here: http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk To download it follow the instructions from: http://www.moosetechnology.org/tools/glamoroustoolkit You can use it by: 1. "GTInspector openOn: someObject", or 2. "GTInspector registerToolsOn: Smalltalk tools" and then use CMD+I (explore) Please let your opinion be heard :) Cheers, Doru p.s. Have fun at ESUG :) -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

13 years, 10 months

3
6
0 0

major repackaging planned

by Tudor Girba

Hi, For the next major version of Moose, we need to rethink the packaging of Moose. To rethink this, we first need to have a common understanding of the structure of Moose. For this, please read the short description of Moose from here: http://www.themoosebook.org/book/introduction/nutshell In particular, I want to start distinguishing clearly between several types of components: . Importers: -- These have the responsibility of importing data into models -- Examples: SmalltalkImporter, MSE . Analyses -- they do something specific with data -- Examples: metrics, system complexity, dependency browser ... . Meta-Models: -- they define the structure of data -- Examples: FAMIX, Hismo, ... . Engines -- they are meta-tools with which we control the analysis flow -- Examples: Moose-Core, PetitParser, Fame, Mondrian, Glamour, Magritte Then of course, there will be various kinds of flavors. For example: MooseFinder is both an engine (because it is generic and can be contextualized in several ways) and an analysis (because it is built on top of an engine). After we settle on a larger picture, I want to have clearly named configurations for each subpart. Then it will be clearer where people should put the extensions (because currently we all define the extensions in the same package) Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

13 years, 10 months

5
20
0 0

Re: [Pharo-project] Bug or feature? XMLElement>>allElementsDo:

by Tudor Girba

Indeed, it should be named withAllElementsDo: to be consistent with Smalltalk naming, and then it would exactly what the name says :) Doru On 30 Aug 2011, at 07:51, Max Leske wrote: > … and maybe it should be renamed to #withAllElementsDo: ? > > > On 30.08.2011, at 00:01, Levente Uzonyi wrote: > >> On Mon, 29 Aug 2011, Nicolas Anquetil wrote: >> >>> In XML-Parser-Nodes we have: >>> >>> XMLNodeWithElements >>> XMLDocument >>> XMLElement >>> >>> A document is composed of elements that can hold recursively other elements >>> >>> XMLNodeWithElements implements (in protocol enumerating) >>> allElementsDo: aBlock >>> "Descend depth-first visiting each element with aBlock." >>> >>> self hasElements >>> ifTrue: [self elementsDo: [:each | each allElementsDo: aBlock]] >>> >>> Looks perfectly normal to me >>> But then: >>> >>> XMLElement implements (in protocol searching !) >>> allElementsDo: aBlock >>> "See superclass version." >>> >>> aBlock value: self. >>> >>> super allElementsDo: aBlock. >>> >>> which means that >>> anXMLElement allElementsDo: [...] >>> runs first on itself and then on its elements ?!? >>> Seems counter intuitive to me. >>> >>> Should I remove this? >> >> IMHO you shouldn't, because it is enumerating the whole tree, which is exactly what I'd expect from this method. But the method should be recategorized. >> >> >> Levente >> >>> >>> nicolas >>> >>> >> > > -- www.tudorgirba.com "Live like you mean it."

13 years, 10 months

1
0
0 0

Bug or feature? XMLElement>>allElementsDo:

by Nicolas Anquetil

In XML-Parser-Nodes we have: XMLNodeWithElements XMLDocument XMLElement A document is composed of elements that can hold recursively other elements XMLNodeWithElements implements (in protocol enumerating) allElementsDo: aBlock "Descend depth-first visiting each element with aBlock." self hasElements ifTrue: [self elementsDo: [:each | each allElementsDo: aBlock]] Looks perfectly normal to me But then: XMLElement implements (in protocol searching !) allElementsDo: aBlock "See superclass version." aBlock value: self. super allElementsDo: aBlock. which means that anXMLElement allElementsDo: [...] runs first on itself and then on its elements ?!? Seems counter intuitive to me. Should I remove this? nicolas nicolas

13 years, 10 months

2
1
0 0

Fan out.metric computation

by pascal.vollmer＠nexgo.de

Hi, I try to use Moose to get the fan out-metric computed for a small Smalltalk project. In order to have type inference I checked "Compute type of attributes (using Roel Typer)" when importing my project. Unfortunately I do not understand what "Select a strategy to compute invocation candidates" says. I left this as it is set by default ("Use the standard CandidateListOperation"). The same is true for "Choose an importer". Now, I look at a certain class C which is interesting for me. "InvokedClasses in C" shows several classes to which C does not send a message. What can I do about that? 1) Is there a possibility to "help" Roel Typer manually when automatic type inference is not feasible? 2) What about the approach of Alexandre Bergel shown at ESUG 2011. Can I try it? Kind regards, Pascal Pascal Vollmer Email: pascal.vollmer(a)ieee.org Arcor empfiehlt: Mal über die Karriere nachdenken! Wissenswertes und Nützliches finden Sie hierzu unter http://www.arcor.de/content/finanzen_job/job_karriere/bewerbung_karriere/ra…

13 years, 10 months

2
1
0 0

A quick primer on Moose Hapax basics (Moose-Algos-InformationRetrieval)

by Simon Denier

Hi all Since I'm in the process of discovering/evaluating the Moose tools in Moose-Algos-InformationRetrieval, I thought it would be a good idea to put together a small tutorial about what can be done and how to use it. http://www.moosetechnology.org/tools/moosealgos/vocabulary These tools are built primarily for vocabulary analysis of any document and corpus of documents. There are basic yet allow one to extract interesting information. Of course comments are welcomed. Notice that this does not contain the full Hapax tool suite. The port of Hapax to Pharo is here http://www.squeaksource.com/Hapax.html but development is halted and will not continue unless a specific need arises (first things first, tests need to be written) -- Simon Denier

13 years, 10 months

4
3
0 0

Re: Sparse Matrix in Moose/Pharo

by Alberto Bacchelli

I am trying the one in Hapax (e.g., SparseRowMatrix) but it doesn't look so sparse to me… Maybe I am doing something wrong. In any case, at least the data structure for the Yale format shouldn't be too hard to write. I'll keep you posted about it. On Aug 25, 2011, at 11:29 AM, Tudor Girba wrote: > I am not aware of it, but it would be a great addition. We had one in VW, but I think you know that one already. > > Doru > > > On 25 Aug 2011, at 11:20, Alberto Bacchelli wrote: > >> Hi all, >> >> Is there any library for _seriously_ handling/storing sparse matrices >> in Pharo/Moose? >> >> >> I was thinking about something like >> http://en.wikipedia.org/wiki/Sparse_matrix#Yale_format >> >> Thanks. >> >> Alberto >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "Every thing should have the right to be different." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

13 years, 10 months

5
4
0 0

Problems with checkout of Py2mse

by Nelli Kaiser

Hi everyone, I am a newbie here and for one of my projects I need Py2mse. I found the intruction how to checkout this parser ( http://www.moosetechnology.org/tools/retired/py2mse) but I did not make it. Can anyone please tell me exactly how I can download it - I mean: which lines should I enter in my subversion client? Your assistance would be greatly appreciated!! Thanks, Nelli

13 years, 10 months

3
4
0 0

Issue 697 in moose-technology: FAMIX should provide TypeAlias for modeling typedef in C

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.6 New issue 697 by tudor.gi...(a)gmail.com: FAMIX should provide TypeAlias for modeling typedef in C http://code.google.com/p/moose-technology/issues/detail?id=697 I C we can provide another name for an existing type: typedef struct var newtype; Essentially, this acts like a type alias. This should be captured by FAMIX-C.

13 years, 10 months

1
1
0 0

Sparse Matrix in Moose/Pharo

by Alberto Bacchelli

Hi all, Is there any library for _seriously_ handling/storing sparse matrices in Pharo/Moose? I was thinking about something like http://en.wikipedia.org/wiki/Sparse_matrix#Yale_format Thanks. Alberto

13 years, 10 months

2
1
0 0

mondrian easel based on glamour

by Tudor Girba

Hi, I have implemented a Mondrian Easel based on Glamour. It is available in the latest Glamour-Tools. I attached here a screenshot. You can spawn it via something like: GLMMondrianEasel openOn: {#classes -> Collection allSubclasses} The only thing it does not offer is completion, but this is because it is not yet supported by Glamour. Alex, I know you implemented it for the Easel. Would you have time to look into having it in Glamour as well? Cheers, Doru -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

13 years, 10 months

3
2
0 0

Issue 536 in moose-technology: inFusion should export parentScope instead of container in Function

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 536 by tudor.gi...(a)gmail.com: inFusion should export parentScope instead of container in Function http://code.google.com/p/moose-technology/issues/detail?id=536 currently it exports container, but it should be parentScope

13 years, 10 months

1
1
0 0

Issue 537 in moose-technology: inFusion should export explicit sourceAnchor for Function

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 537 by tudor.gi...(a)gmail.com: inFusion should export explicit sourceAnchor for Function http://code.google.com/p/moose-technology/issues/detail?id=537 Currently, it exports sourceAnchor as a string like this: (FAMIX.Function (sourceAnchor 'path') ...) It should be (FAMIX.FileAnchor (id: 1) ...) (FAMIX.Function (sourceAnchor (ref: 1)))

13 years, 10 months

1
1
0 0

Issue 544 in moose-technology: inFusion should point the C++ source text to the implementation, not definition

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 544 by tudor.gi...(a)gmail.com: inFusion should point the C++ source text to the implementation, not definition http://code.google.com/p/moose-technology/issues/detail?id=544 Currently, the source anchor for a c/c++ class or methods points to the definition in the header. It should point to the implementation from the c/cpp file.

13 years, 10 months

1
1
0 0

Issue 695 in moose-technology: Mondrian Easel should be based on Glamour

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour 4.6 New issue 695 by tudor.gi...(a)gmail.com: Mondrian Easel should be based on Glamour http://code.google.com/p/moose-technology/issues/detail?id=695 We should offer a Mondrian Easel based on Glamour.

13 years, 10 months

1
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev