Moose-dev September 2016

moose-dev@list.inf.unibe.ch

20 participants
33 discussions

Re: parentSelectors - <container> pragma
by Blondeau Vincent 19 Sep '16

19 Sep '16

Hi, By searching in Fame, I found the pragma <container>. It is recognized by the metamodel in FM3PropertyDescription but not used (excepted for Fame itself in FM3PropertyDescription>>mmClass). I think we have a usage with Moose query to use it. However, I don't understand why it is not used for FAMIX. Cheers, Vincent > -----Message d'origine----- > De : Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] De la part de > Tudor Girba > Envoyé : dimanche 18 septembre 2016 15:33 > À : Moose-related development > Objet : [Moose-dev] Re: parentSelectors > > Hi, > > > On Sep 18, 2016, at 3:29 PM, Blondeau Vincent > <vincent.blondeau(a)worldline.com> wrote: > > > > > > ________________________________________ > > De : Moose-dev [moose-dev-bounces(a)list.inf.unibe.ch] de la part de > > Tudor Girba [tudor(a)tudorgirba.com] Date d'envoi : dimanche 18 > > septembre 2016 15:17 À : Moose-related development Objet : [Moose- > dev] > > Re: parentSelectors > > > > Hi, > > > >> On Sep 18, 2016, at 2:57 PM, Vincent BLONDEAU > <vincent.blondeau(a)polytech-lille.net> wrote: > >> > >> > >> > >> From: Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch] On > >> Behalf Of Tudor Girba > >> Sent: dimanche 18 septembre 2016 11:09 > >> To: Moose-related development > >> Subject: [Moose-dev] parentSelectors > >> > >> Hi, > >> > >> Hi, > >> > >> > >> I just saw that the way the parent selectors are being defined was > changed. In general, please announce deep changes like these on the mailing > list. > >> > >> Indeed, I done it last week and didn’t announced it yet on the mailing list. > >> > >> If I understand correctly, the goal was to make it easier for extensions to > specify the parentSelectors. This is a good goal, but there are two problems > with the current solution: > >> > >> Yes, there was some problems if you extend the FAMIX metamodel with > some classes, as it is done with Orion. The parentSelectors are in fact not > described in the fame metamodel and cannot be used easily in the > subclasses. > >> > >> 1. The parentSelectors should be extensible. Right now, they are defined > in one method returning a collection of strings. Instead, it would be better to > have them described directly in the selector method. For example, we could > have: > >> > >> FAMIXType>>container > >> <MSEProperty: #container type: #FAMIXContainerEntity opposite: > #types> > >> <MSEComment: 'Container entity to which this type belongs to. > Container is a namespace, not a package (Smalltalk).'> > >> <MSEParentProperty> > >> ^container > >> > >> This would also allow us to extend existing classes with annotations that > can be selectors. > >> > >> 2. Right now, the parentSelectors are defined on the instance side as an > MSE property: > >> > >> FAMIXType>>parentSelectors > >> <MSEProperty: #parentSelectors type: #String> > >> <multivalued> > >> ^ #(container parentPackage) > >> > >> This is incorrect given that they describe the type, not the instance. For > example, one consequence is that now we serialize this information (check > MooseModel>>testExport which fails right now). Instead, let’s go for > solution from point 1. > >> > >> What do you think? > >> > >> I agree that this property is a type property. But, in fame we cannot > define such kind of property. To do it, we can: > >> - Don’t use the Fame meta model (previous solution) > >> - Use the instance meta descriptions that are already defined meta > model (current solution bu not the best) > >> - Define some new properties in the metamodel, as you propose. But > in the 2 points suggested, we have to change the MSE importer and the > metamodel to take into account the new pragmas (in “annotation” or in the > selectors by MSEParentProperty). > >> Do you think that is a good idea ? > >> If, we do that, I think the solution in point 1 is better. > >> > >> For the current failing test, we can add <derived>. This way the > >> information will not be serialized > > > > The MSE property is about an instance. So, marking it with <derived> does > not work because we are mixing levels of abstractions. > > > > <I know it is just temporary. > > > > What we want is to make the selector discoverable through reflection. This > is at the level of Pharo code. So, by annotating the concrete property we can > discover them properly and have subclasses know about them. > > > > > > <So you don't think that is should be described in the meta model? and just > use the Pharo reflexion to retrieve the methods? > > I think we only use this in Pharo at runtime, so adding it to the meta-model is > not particularly useful. That is why, let’s keep it simple. > > Cheers, > Doru > > > > > Cheers, > > Vincent > > > > > > Cheers, > > Doru > > > > > >> Cheers, > >> Vincent > >> > >> > >> Cheers, > >> Doru > >> > >> > >> > >> -- > >> www.tudorgirba.com > >> www.feenk.com > >> > >> "It's not how it is, it is how we see it." > >> > >> _______________________________________________ > >> Moose-dev mailing list > >> Moose-dev(a)list.inf.unibe.ch > >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Obvious things are difficult to teach." > > > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > > !!!************************************************************ > ******* > > ****************** "Ce message et les pièces jointes sont > > confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut > également être protégé par le secret professionnel. Si vous recevez ce > message par erreur, merci d'en avertir immédiatement l'expéditeur et de le > détruire. L'intégrité du message ne pouvant être assurée sur Internet, la > responsabilité de Worldline ne pourra être recherchée quant au contenu de > ce message. Bien que les meilleurs efforts soient faits pour maintenir cette > transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à > cet égard et sa responsabilité ne saurait être recherchée pour tout dommage > résultant d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this e-mail > in error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be triggered > for the message content. Although the sender endeavours to maintain a > computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted.!!!" > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > "There are no old things, there are only old ways of looking at them." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev !!!************************************************************************************* "Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

1 0

parentSelectors
by Tudor Girba 18 Sep '16

18 Sep '16

Hi, I just saw that the way the parent selectors are being defined was changed. In general, please announce deep changes like these on the mailing list. If I understand correctly, the goal was to make it easier for extensions to specify the parentSelectors. This is a good goal, but there are two problems with the current solution: 1. The parentSelectors should be extensible. Right now, they are defined in one method returning a collection of strings. Instead, it would be better to have them described directly in the selector method. For example, we could have: FAMIXType>>container <MSEProperty: #container type: #FAMIXContainerEntity opposite: #types> <MSEComment: 'Container entity to which this type belongs to. Container is a namespace, not a package (Smalltalk).'> <MSEParentProperty> ^container This would also allow us to extend existing classes with annotations that can be selectors. 2. Right now, the parentSelectors are defined on the instance side as an MSE property: FAMIXType>>parentSelectors <MSEProperty: #parentSelectors type: #String> <multivalued> ^ #(container parentPackage) This is incorrect given that they describe the type, not the instance. For example, one consequence is that now we serialize this information (check MooseModel>>testExport which fails right now). Instead, let’s go for solution from point 1. What do you think? Cheers, Doru -- www.tudorgirba.com www.feenk.com "It's not how it is, it is how we see it."

4 6

GT-InspectorExtensions-CoreRoassal dependency problem
by Hernán Morales Durand 17 Sep '16

17 Sep '16

Hi. I am using Pharo 5.0 and installing a Metacello config which is loading Roassal2 (stable). At some loading step a Warning dialog raises which is preventing unattended automatization of whole installation. This is the message: This package depends on the following classes: CPDiverging CPQualitative CPSequential You must resolve these dependencies before you will be able to load these definitions: CPDiverging>>#gtExampleColorPalette CPDiverging>>#gtInspectorPreviewIn: CPQualitative>>#gtExampleColorPalette CPQualitative>>#gtInspectorPreviewIn: CPSequential>>#gtExampleColorPalette CPSequential>>#gtInspectorPreviewIn: The package loaded at that point is GT-InspectorExtensions- CoreRoassal-TudorGirba.44 Any hints? Hernán

3 6

Robust way to fit RTBox around variable text
by Cris Fuhrman 16 Sep '16

16 Sep '16

Hello, I'd like to visualize a graph where the nodes are boxes and they have text inside. The boxes should grow or shrink horizontally so the text doesn't go outside the box. I saw the answer at http://forum.world.st/Roassal2-Label-width-td4847887.html which led me to a solution. However, I've commented the "not robust" part below, since it's passing by "lbl" which I suspect could change. ~~~~~~~~~~~~~~~~ | b label el | b := RTView new. el := RTBox new elementOn: 'hello world'. label := RTLabeled new center. b add: el. el @ label. "not robust" el width: label lbl width. el height: label lbl height. b ~~~~~~~~~~~~~~~~~~~~~~ [image: Inline image 1] I found the unit tests for RTLabel (RTLabelTest) and I found another solution, but maybe it's equally fragile? ~~~~~~~~~~~~~~~~~~~~~~~~~ | text b lblBox lblForCalc dummyElement | text := 'Text inside the box'. b := RTView new. lblBox := (RTBox new elementOn: text) + RTLabel. lblForCalc := RTLabel new text: text. dummyElement := RTElement new. lblBox height: (lblForCalc heightFor: dummyElement). lblBox width: (lblForCalc widthFor: dummyElement). b add: lblBox. b ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [image: Inline image 2] I'd love to get some feedback on these approaches. Maybe there's a simpler robust way? Thanks!

2 3

How to use Hismo?
by Alexandre Bergel 16 Sep '16

16 Sep '16

Hi! Is there a tutorial on how to use Hismo? If I have several model, how can I add them in a HismoModel? How to create such a model by the way? Cheers, Alexandre

3 4

Looking for a webpage on moosetechnology.org
by Blondeau Vincent 16 Sep '16

16 Sep '16

Hi, I am looking for http://www.moosetechnology.org/tools/Orion. This page was available in the old website version, but vanished with the new one. Does someone still have the source code of the webpage? Or, can someone put the page in the new website? BTW, there are others documentation pages that are missing like the moose algo one... Thanks in advance, Cheers, Vincent !!!************************************************************************************* "Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

4 4

[ann] pillar support in gtinspector
by Tudor Girba 15 Sep '16

15 Sep '16

Hi, I updated the Pillar support in GTInspector. Some of the extensions already exist in the default Pillar #development version. If you want to play with the full support, you can load it like this: Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; package: 'PetitAnalyzer'; package: 'PetitIndent'; package: 'PetitIslands'; smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'GT-InspectorExtensions-Pillar'; load Then you can just inspect a book folder and you get this: I did not integrate this in the main Pillar yet because this is an older implementation based on a limited island parser. As now Pillar has a full parser based on PetitParser, the next step is to move the highlighting logic to use this parser instead of the island parser. From my measurements, the speed of the two parsers is about the same, so from a user perspective there will be not much changes. It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

4 5

TRCanvas canvas/surface
by Nicolai Hess 14 Sep '16

14 Sep '16

During debugging the Athens-Crash I found something strange about TRCanvas (not responsible for the crash) 1. TRCanvas canvas instance variable is not a AthensCairoCanvas at all but an AthensCairoSurface 2. the canvas resp. surface is initialized with TRCanvas initial extent but a change on TRCanvas extent does not change the surfaces extent 3. Is this canvas resp. surface actually used ? Do we only need it to manage some external resources (path/ image forms) ? Can it be removed or at least renamed to something different. regards nicolai

4 4

parentBehaviouralEntity is nil for Java local variable declared in static block (FAMIXLocalVariable)
by Fuhrmanator 13 Sep '16

13 Sep '16

Here's another anomaly I found in my reasoning about Java interfaces through MSE files. In the example with ArgoUML 0.28.1 there's a class called ConfigurationFactory.java that declares a local variable in a static block: static { ... IConfigurationFactory newFactory = null; ... } Within MOOSE, the FAMIXLocalVariable "newFactory" shows up in the structuresWithDeclaredTypes for the FAMIXClass "IConfigurationFactory". However, its parentBehaviouralEntity is nil. Is this because static blocks in Java don't map to behavioural entities in FAMIX? I'm trying to understand the nil case, as it doesn't happen with all FAMIXLocalVariables. The problem is obviously that I can't find the dependency on the interface in this case. In the stated example, there's also a private static final Attribute, so the MOOSE dependency comes through that in the end (it's a redundant dependency). But I'm guessing there could be some cases where a dependency via local variable used in a static block might not always be stored in an Attribute. Any ideas on how to work around this? Possibly related: https://github.com/moosetechnology/moose/issues/785 -- View this message in context: http://forum.world.st/parentBehaviouralEntity-is-nil-for-Java-local-variabl… Sent from the Moose mailing list archive at Nabble.com.

3 4

Java interfaces and clientTypes
by Fuhrmanator 12 Sep '16

12 Sep '16

[Apologies to the moderator(s) for trying to post this via email with the wrong address. ] I have Moose 6.0 and I've used jdt2famix 1.0.2 to generate an MSE file. I'm trying to use Moose to reason about clients of Java interfaces. I would like to find any classes that depend on an interface by any means. I thought using clientTypes was the right thing, except it doesn't work the way I expect in a simple case. For the interface in my example, clientTypes only returns the class that is an implementation of the interface (which makes sense, as they depend on it) but not the client class that uses it via a private static reference (which, to me, doesn't make sense). For more information, I am able find the client of the interface via structuresWithDeclaredType, so I'm pretty sure it's not information missing in the MSE file (not a jdt2famix bug). Based on the simple example below, shouldn't clientTypes for ITest return ClassAClient and ConcreteImplementationA rather than just ConcreteImplementationA? // ITest.java public interface ITest { } // ConcreteImplementationA.java public class ConcreteImplementationA implements ITest { } // ClassAClient.java public class ClassAClient { private static ITest theTest; public static void main(String arg[]) { theTest = new ConcreteImplementationA(); } } -- View this message in context: http://forum.world.st/Java-interfaces-and-clientTypes-tp4915115.html Sent from the Moose mailing list archive at Nabble.com.

4 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev September 2016