- Moose-dev - INF Mailman

by Usman Bhatti

I am looking for a Java Exporter for Moose. Earlier I had tried IPlasma but I am getting some problems in its interface so I cannot use it. I also tried J2Moose but the format generated by the tool is not accepted by moose. Is there a Java exporter for moose that is compatible with the current MSE file format? thanx in advance, Usman

15 years, 6 months

7
14
0 0

MSE File Parser

by Arif Iftikhar

While loading MSE File in Moose i get the error attached. If i proceed it loads 0 entities in moose.Is there any special version of moose for such mse file. -- Thanks & Regards Arif Iftikhar

15 years, 6 months

2
1
0 0

Re: Problem generating a mse with infusion

by Tudor Girba

Hi Simon, It works fine on my computer. I am also using 7.2.6, but I did not update the JVM. Cheers, Doru On 26 Dec 2009, at 13:04, Simon Denier wrote: > > On 26 déc. 2009, at 12:13, Tudor Girba wrote: > >> Hi Simon, >> >> Strange, that should not happen. I would need to see the sources to >> debug this. > > > Here you go. It compiles against Java 6 on Mac Os platform, but I > didnt install the latest release. > > Also I used infusion 7.2.6 > > > <GecoSrc0.5.25.zip> > > >> >> Cheers, >> Doru >> >> >> On 26 Dec 2009, at 11:49, Simon Denier wrote: >> >>> Hi all >>> >>> I'm trying to generate a mse file for a java project with infusion. >>> >>> It stops somewhere with this error: >>> Writing the MSE file for the path: /Users/deniersi/workspace/GecO/ >>> src >>> --Export started-- >>> MSE file generation aborted! >>> >>> which does not give much help. >>> >>> Last lines in the mse describe beginning of a method >>> >>> (FAMIX.Method (id: 4318) >>> (sourceAnchor (ref: 9706)) >>> (parentType (ref: 3)) >>> >>> ref 9706 is '_unknown_path\_unknown_file' >>> >>> Any idea about how to debug? >>> >>> -- >>> Simon >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> >> "It's not what we do that matters most, it's how we do it." >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > Simon > > > -- www.tudorgirba.com "Be rather willing to give than demanding to get."

15 years, 6 months

5
4
0 0

.MSE file generation

by Arif Iftikhar

How to generate MSE file for Java code in eclipse. -- Thanks & Regards Arif Iftikhar

15 years, 6 months

2
1
0 0

4.0 beta 4

by Tudor Girba

Hi, Moose Suite 4.0 beta 4 is now available for download: http://moosetechnology.org/download Among others, it also deals with the PrimitiveTypes exported by inFusion. Cheers, Doru -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

15 years, 6 months

2
1
0 0

Please remove "Software Cartographer" from Moose page

by Adrian Kuhn

Hi Doru, please remove "Software Cartographer" from Moose page. It never integrated with Moose at all. http://www.moosetechnology.org/tools/vw/softwarecartographer thanks, AA

15 years, 6 months

5
18
0 0

Mondrian health report

by Alexandre Bergel

Since I slightly modified the cacheBounds initialization when translating nodes when adding the features wanted by Marco, I regenerate the mondrian health report. Slightly improvement from the one I sent at the beginning of the month. I discovered an opportunity to gain many % when rendering nodes. I will work on that soon. Report produced on 2009-12-28T13:32:14+00:00 Benchmark ManyNode (simple rendering of nodes) : 100 nodes => 16 ms 200 nodes => 54 ms 300 nodes => 108 ms 400 nodes => 187 ms 500 nodes => 301 ms 600 nodes => 446 ms 700 nodes => 574 ms 800 nodes => 755 ms 900 nodes => 949 ms 1000 nodes => 1148 ms 1600 nodes => 3043 ms Benchmark ManyEdges (simple rendering of edges) : 10 edges => 1 ms 20 edges => 5 ms 30 edges => 13 ms 40 edges => 180 ms 50 edges => 50 ms 60 edges => 79 ms 70 edges => 117 ms 80 edges => 174 ms 90 edges => 256 ms 100 edges => 342 ms 200 edges => 4432 ms 300 edges => 35438 ms 55.08 % of methods are covered Progress from last time: -0.96 % Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 6 months

3
5
0 0

www.moosetechnology.org

by Tudor Girba

Hi, Moose has a new den: http://www.moosetechnology.org/ Most of the content (including the users) was ported from moose.unibe.ch. Here are the main diffs: - The look suffered a minor surgery - I created a small ad-like movie to introduce the logo (embedded on the main page). It does not have sound, but it's a start - The tools were reorganized: those tools that were only available in VW are now under /tools/vw. For the popular tools like codecity, softwarenaut and chronia, we have a forward in /tools (e.g., www.moosetechnology.org/tools/codecity) . - I added http://www.moosetechnology.org/development for development related pages - The publications list is up to date based on scg.bib and uses the latest Citezen implementation by Oscar. At this moment, there is no automatic update, and if you want to get your publications online, please let me know. - http://www.moosetechnology.org/docs/famix/3.0 is generated dynamically from the MSE specification. This will probably grow in the near future to offer a more detailed documentation. - The old moose.unibe.ch redirects to the new page (except for the / resources which are still hosted on macamis.unibe.ch for serving large files) I would like to thank Lukas for all the support he provided to deal with the technical details of redirects and server settings. Cheers, Doru -- www.tudorgirba.com "Live like you mean it."

15 years, 6 months

3
9
0 0

Dialect/Operating System matrix for moose tools

by Norbert Hartl

Hi, I've started to play around with moose a bit. The tools page on the moose site has quite impressive tools to offer. But as soon as I took a pharo image and loaded moose into it I recognized that it is (again) not as easy as I hoped. For a lot of the tools I don't meet the smalltalk dialect requirements and/or I don't meet the operating system requirements. So, is there a matrix where I can see which of the tools are usable in which dialect or operating system? Thanks, Norbert

15 years, 6 months

5
13
0 0

Problem generating a mse with infusion

by Simon Denier

Hi all I'm trying to generate a mse file for a java project with infusion. It stops somewhere with this error: Writing the MSE file for the path: /Users/deniersi/workspace/GecO/src --Export started-- MSE file generation aborted! which does not give much help. Last lines in the mse describe beginning of a method (FAMIX.Method (id: 4318) (sourceAnchor (ref: 9706)) (parentType (ref: 3)) ref 9706 is '_unknown_path\_unknown_file' Any idea about how to debug? -- Simon

15 years, 6 months

2
1
0 0

Missing invocations?

by Alberto Bacchelli

Hi, I still use VisualWorks 7.6nc and FAMIX2.1 to analyze Java systems in Moose. I still have to move to Pharo, sorry... I am trying to find the connections between Java classes of a software system. Besides inheritance (which is perfectly recognized), I would also like to consider other type of relations, such as invocations. Although many invocations are correctly recognized, there is -at least- one case which I cannot extract. For example, if you take ArgoUML 0.28 [0], that I parsed into a MSE file [1] using inFusion 7.2.7, and consider the class org.argouml.application.api.Argo [2], you can find this code: ==== ==== ==== [...] public final class Argo { [...] /** * Key for default startup directory. */ public static final ConfigurationKey KEY_STARTUP_DIR = Configuration.makeKey("default", "user", "dir"); [...] ==== ==== ==== I believe that, between all the invocations done by this Argo class, there should be the invocation to the method "makeKey(String,String,String)" that belongs to the class Configuration. However, if I call "outgoingInvocations" on the FAMIX Class representing the Java class Argo, I cannot get this invocation. It is possible that this problem is not caused by Moose, but by the generation of the MSE file: I manually looked for the Argo class inside the MSE file [1]. I found that it has id = 202. I looked at all the references (idref: 202) to this id. I could find 4 connections to all the methods of this class, many connections to all the attributes of this class, but no reference to this "makeKey" method invocation. Is this problem caused by the fact that the method invocation is in the main body of the class? What happens if such an invocation is to be found inside a class method, is it correctly recognized? Thank you in advance. Ciao, Alberto [0] http://www.inf.usi.ch/phd/bacchelli/research/argouml/2009-03-23-argoUML_0.2… [1] http://www.inf.usi.ch/phd/bacchelli/research/argouml/2009-03-23_argoUML_0.2… [2] http://www.inf.usi.ch/phd/bacchelli/research/argouml/Argo.Java

15 years, 6 months

2
1
0 0

Why could we not make Moose load in a core image?

by Stéphane Ducasse

tried to load moose in pharoCore-rc401 This package depends on the following classes: RBProgramNodeVisitor OBPluggableTextMorphWithShout OBTextMorphWithShout RBVariableNode RBBlockLintRule RBProgramNode You must resolve these dependencies before you will be able to load these definitions: FAMIXMetaModelClassesShouldNotOverrideRule FAMIXMetaModelClassesShouldNotOverrideRule>>checkClass: FAMIXMetaModelClassesShouldNotOverrideRule>>group FAMIXMetaModelClassesShouldNotOverrideRule>>metaModelClasses FAMIXMetaModelClassesShouldNotOverrideRule>>name FAMIXMetaModelClassesShouldNotOverrideRule>>rationale FAMIXMetaModelClassesShouldNotOverrideRule>>selectorsThatShouldNotBeOverriden FAMIXMetaModelClassesShouldOverrideRule FAMIXMetaModelClassesShouldOverrideRule>>checkClass: FAMIXMetaModelClassesShouldOverrideRule>>group FAMIXMetaModelClassesShouldOverrideRule>>metaModelClasses FAMIXMetaModelClassesShouldOverrideRule>>name FAMIXMetaModelClassesShouldOverrideRule>>rationale FAMIXMetaModelClassesShouldOverrideRule>>resultClass FAMIXMetaModelClassesShouldOverrideRule>>selectorsThatShouldBeOverriden FameNameConventionBetweenFM3AndSmalltalkRule FameNameConventionBetweenFM3AndSmalltalkRule>>addClass:toMetaBuilderCollection: FameNameConventionBetweenFM3AndSmalltalkRule>>checkClass: FameNameConventionBetweenFM3AndSmalltalkRule>>group FameNameConventionBetweenFM3AndSmalltalkRule>>name FameNameConventionBetweenFM3AndSmalltalkRule>>rationale FameOppositeAttributeShouldPointBackRule FameOppositeAttributeShouldPointBackRule>>checkMethod: FameOppositeAttributeShouldPointBackRule>>group FameOppositeAttributeShouldPointBackRule>>name FameOppositeAttributeShouldPointBackRule>>rationale FameSuperclassMetaDescribedExistRule FameSuperclassMetaDescribedExistRule>>addClass:toMetaBuilderCollection: FameSuperclassMetaDescribedExistRule>>checkClass: FameSuperclassMetaDescribedExistRule>>group FameSuperclassMetaDescribedExistRule>>name FameSuperclassMetaDescribedExistRule>>rationale MOEaselTextEditor MOEaselTextEditor>>bindingOf: MOEaselTextEditor>>hasBindingOf: MOEaselTextEditor>>hasBindingThatBeginsWith: MOEaselTextEditor>>textMorphClass MOTextMorphWithShout RBProgramNode>>isSuper RBVariableNode>>isSuper SmalltalkMethodVisitor SmalltalkMethodVisitor classSide>>on: SmalltalkMethodVisitor>>acceptAssignmentNode: SmalltalkMethodVisitor>>acceptBlockNode: SmalltalkMethodVisitor>>acceptCascadeNode: SmalltalkMethodVisitor>>acceptMessageNode: SmalltalkMethodVisitor>>acceptMethodNode: SmalltalkMethodVisitor>>acceptReturnNode: SmalltalkMethodVisitor>>acceptSequenceNode: SmalltalkMethodVisitor>>acceptVariableNode: SmalltalkMethodVisitor>>classifyMethodNode: SmalltalkMethodVisitor>>createAccessTo:writing: SmalltalkMethodVisitor>>createReferenceTo: SmalltalkMethodVisitor>>extractCommentsFromNode: SmalltalkMethodVisitor>>importer SmalltalkMethodVisitor>>importer: SmalltalkMethodVisitor>>matchConstant: SmalltalkMethodVisitor>>matchConstructor: SmalltalkMethodVisitor>>matchGetter: SmalltalkMethodVisitor>>matchSetter: SmalltalkMethodVisitor>>methodEntity SmalltalkMethodVisitor>>parseTreeForSource: SmalltalkMethodVisitor>>resolve: SmalltalkMethodVisitor>>resolveInstanceSide: SmalltalkMethodVisitor>>runWith:and: SmalltalkMethodVisitor>>runWithSource:and: SmalltalkMethodVisitor>>visitArgument: SmalltalkMethodVisitor>>visitNode: VisualWorksParseTreeMetricCalculator VisualWorksParseTreeMetricCalculator>>acceptAssignmentNode: VisualWorksParseTreeMetricCalculator>>acceptBlockNode: VisualWorksParseTreeMetricCalculator>>acceptCascadeNode: VisualWorksParseTreeMetricCalculator>>acceptMessageNode: VisualWorksParseTreeMetricCalculator>>acceptMethodNode: VisualWorksParseTreeMetricCalculator>>acceptSequenceNode: VisualWorksParseTreeMetricCalculator>>classNameFromMethod VisualWorksParseTreeMetricCalculator>>computeCyclomaticNumber: VisualWorksParseTreeMetricCalculator>>countConditionals: VisualWorksParseTreeMetricCalculator>>cyclomaticNumber VisualWorksParseTreeMetricCalculator>>cyclomaticNumber2 VisualWorksParseTreeMetricCalculator>>cyclomaticNumber: VisualWorksParseTreeMetricCalculator>>initialize VisualWorksParseTreeMetricCalculator>>methodBodyOn: VisualWorksParseTreeMetricCalculator>>methodComplexity VisualWorksParseTreeMetricCalculator>>methodComplexity: VisualWorksParseTreeMetricCalculator>>numberOfConditionals VisualWorksParseTreeMetricCalculator>>numberOfConditionals: VisualWorksParseTreeMetricCalculator>>numberOfLinesOfCode VisualWorksParseTreeMetricCalculator>>numberOfLinesOfCode: VisualWorksParseTreeMetricCalculator>>numberOfMessageSends VisualWorksParseTreeMetricCalculator>>numberOfMessageSends: VisualWorksParseTreeMetricCalculator>>numberOfStatements VisualWorksParseTreeMetricCalculator>>numberOfStatements: VisualWorksParseTreeMetricCalculator>>parameterComplexityMultiplier VisualWorksParseTreeMetricCalculator>>parameterComplexityMultiplier: VisualWorksParseTreeMetricCalculator>>processMethod:usingImporter:inModel: VisualWorksParseTreeMetricCalculator>>resetMetricValues VisualWorksParseTreeMetricCalculator>>visitArgument: VisualWorksParseTreeVisitor VisualWorksParseTreeVisitor>>checkThatClassIsStillCorrect VisualWorksParseTreeVisitor>>classNameFromMethod VisualWorksParseTreeVisitor>>compiledMethod VisualWorksParseTreeVisitor>>famixNameFor: VisualWorksParseTreeVisitor>>importer VisualWorksParseTreeVisitor>>importer: VisualWorksParseTreeVisitor>>inModel VisualWorksParseTreeVisitor>>inModel: VisualWorksParseTreeVisitor>>isDirtySuperInMethod:withReceiver: VisualWorksParseTreeVisitor>>isSuperInMethod:withReceiver: VisualWorksParseTreeVisitor>>methodBodyOn: VisualWorksParseTreeVisitor>>methodEntity VisualWorksParseTreeVisitor>>methodEntity: VisualWorksParseTreeVisitor>>processMethod:usingImporter:inModel: VisualWorksParseTreeVisitor>>stClass VisualWorksParseTreeVisitor>>stClass: VisualWorksParseTreeVisitor>>stParseTree Select Proceed to continue, or close this window to cancel the operation.

15 years, 6 months

2
1
0 0

Re: [Moose] moose-dev on Nabble?

by Tudor Girba

Hi Geert, Thanks for the suggestion. I created a Nabble mailing list: http://n3.nabble.com/moose-dev-f97923.html Cheers, Doru On 19 Dec 2009, at 18:22, Geert Claes wrote: > Could you add moose-dev on Nabble for those who prefer to follow > moose online rather than via email? > _______________________________________________ > Moose mailing list > Moose(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose -- www.tudorgirba.com "Every thing has its own flow."

15 years, 6 months

2
3
0 0

FAMIXNamespace question & comment

by Johan Fabry

Hi all, 2 short ones: If I have a FAMIXNamespace, how do I obtain a reference to the model that contains this namespace? FAMIXNamespace has child scopes instead of namespaces, which makes it ugly to define a Glamour tree view on models and their namespaces. I have therefore added the code below, I think it would be a good idea to add that to the core as well. FAMIXNamespace>>allNamespaces ^ self childScopes -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

15 years, 6 months

3
5
0 0

new moose problems

by Adrian Dozsa

Hi all, I've tried today the latest Moose version (the Squeak based one) - http://moose.unibe.ch/resources/download/moose-suite-4_0-beta-2.app.zip I've extracted a famix 3 mse with the latest inFusion (build Dec 21) and tried to import it into Moose. But I get a lot of errors: 'Element ''FAMIX.PrimitiveType'' not found.' and a lot of 'Error(Object)>>doesNotUnderstand: #createInstance' Can somebody help me out here, please. Thanks, Adrian Dozsa

15 years, 6 months

2
1
0 0

MorphTreeMorph>>mouseEnter: broken in Moose

by Oscar Nierstrasz

I get an infinite loop of exceptions in the Moose Finder when I load Moose into the latest Pharo. LazyMorphTreeMorph does not understand keyboardFocusOnMouseDown ... Sleuthing shows: MorphTreeMorph>>mouseEnter: event "Changed to take keyboardFocusOnMouseDown preference into account." super mouseEnter: event. self wantsKeyboardFocus ifFalse: [^self]. self keyboardFocusOnMouseDown ifFalse: [self takeKeyboardFocus] But keyboardFocusOnMouseDown is not implemented anywhere in the system. What gives? Alain, it seems this method comes from you. What gives? I am unsure what to do ... - on

15 years, 6 months

3
2
0 0

Multi selection in the moose finder

by Simon Denier

The current selection schema in the moose finder is annoying: I can select one item, I can shift-select a range of items, but I can not select some items in the list. I guess it's related to something in the morphic tree widget, but what are the plans to solve that? -- Simon

15 years, 6 months

2
1
0 0

New interaction abilities in mondrian

by Alexandre Bergel

Comment of Version Mondrian-Alexandre_Bergel.315 is: -=-=-=-=-=-=-=-=-=-=-=-= -added a reference of the viewRenderer to each announcement. This is useful when a window update is needed - added new interaction methods on MOAnnouncer (highlightWhenOver. highlightWhenOver:, stronghigHlightWhenOver) - Added new examples related to interaction on MOEaselHelp - Added new tests for the interaction - Make nodeForDomainValues more flexible -=-=-=-=-=-=-=-=-=-=-=-= Try the following: -=-=-=-=-=-=-=-=-=-=-=-= | view nodes | view := MOViewRenderer new. view interaction strongHighlightWhenOver: [:v | {v - 1 . v + 1. v + 4 . v - 4}]. view shape rectangle width: 40; height: 30; withText. nodes := view nodes: (1 to: 16). view gridLayout gapSize: 2. view open. -=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 6 months

1
0
0 0

mondrian to file

by Tudor Girba

Hi Alex, I would need to be able to export Mondrian visualizations to files. I somehow recall a discussion in which it was explain how to do it, but I could not find my way. Is it supported? Cheers, Doru -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

15 years, 6 months

3
3
0 0

Mondrian-Alexandre_Bergel.313

by Alexandre Bergel

Several important improvements. From the user perspective: - added a two new buttons, each offering a menu and a help - export options added (png, bmp, gif, jpeg) From the developer point of view: - used Lint to clean the code Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

15 years, 6 months

1
0
0 0

Glamour and Mondrian action

by Laval Jannik

Hi all, Is it possible to add actions in a Mondrian Pane in Glamour ? I would like to add somethink like: ----- browser mondrian title: 'test'; act: [:each | each selection inspect] entitled: 'inspect'; painting:....... ----- But now, it does not work. Is there another way to do it ? Cheers, --- Jannik Laval ---

15 years, 6 months

3
3
0 0

Glamour view update triggering, how?

by Johan Fabry

Hi all, a question: I have a tree on a collection of elements, with the following specification: tags: [:asp | {asp show ifTrue:[MenuIcons smallOkIcon] ifFalse: [MenuIcons smallCancelIcon]}]; act: [:tree | |asp| asp := tree selection. asp show: (asp show not) ] on: $t entitled: 'Toggle On/Off (t)'; Now when the toggle action is performed, the tree should redisplay, as the tag needs to change. (adding a tree update within the act block does not work :-( ) How do I achieve this? Thanks in advance! -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

15 years, 6 months

2
8
0 0

description of FAMIXPrimitiveType seems to not appear in 'MooseModel meta'

by Cyrille Delaunay

Hi, When executing 'FAMIXPrimitiveType asMooseDescription' we get an Error as result. The problem is that FAMIXPrimitiveType is not found in the moose metaRepository . Is it a normal behavior ?

15 years, 6 months

2
1
0 0

Welcome and question!

by Mariano Martinez Peck

Hi folks! I have just subscribed to the mailing list. I have a little question for you. I want to analyze and see a graphic of a graph of objects and the references between them. Note that I want objects, at runtime. Not static, not classes. Is there something in Moose that I can use ? Cheers, Mariano

15 years, 6 months

3
11
0 0

Re: [Metacello] specific problem when loading a nested configuration

by Dale Henrichs

Mariano, Would you be in favor of the abstract class, if the abstract class itself had to be booted into the image? It's just a practical issue for me ... if we can count on the abstract class being preloaded in all dialects, then an abstract class makes sense. If we can count on Metacello being preloaded in some of the dialects, then the ensureMetacello method need only be present for portability to platforms in which Metacello is not preloaded. I don't disagree with the oddity of copy and paste. Earlier versions of Metacello configurations did rely on a superclass, but booting the superclass into the image was problematic. Granted bootstrapping would only be hard in Squeak, but it isn't supposed to be hard! The ensureMetacello method is only there for ease of bootstrapping software that is supposed to make it easy to boostrap software, but can't do the bootstrapping until it is bootstrapped itself:) I just hate the idea of making it harder to share configurations with Squeak... Dale ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | On Fri, Dec 11, 2009 at 8:26 PM, Dale Henrichs | <dale.henrichs(a)gemstone.com>wrote: | | > I wouldn't be entirely opposed to having an abstract configuration | class, | > but I hate to switch the configuration structure in midstream | again... it is | > very nice that a config can be loaded into any old smalltalk image | without | > any prerequisites.... | > | > The #ensureMetacello method should simply load | ConfigurationOfMetacello and | > go from there ... | > | > To require an abstract configuration class, I would want that class | to be | > in the core for Pharo, GemStone and Squeak ... Metacello is already | bundled | > with the core in GemStone so that leaves Squeak ... I really don't | want to | > have to preface all of the install instructions with "Before loading | the | > configuration, make sure that you've done X, Y and Z" | > | > If bootstrapping is the only consideration, I don't think it is | worth | > making the change ... there isn't a lot protocol that I would want | to put | > into the Abstract configuration class ... project instance variable | and | > method ... | > | > If there are enough other arguments for an Abstract configuration | class, | > then it would be good to make the switch sooner rather than later. | > | > Being able to view the configurations using a hierarchy browser is | an | > advantage, but that's more of a tools issue. | > | > As I think about it, most of the advantages that come to mind are | tools | > related. Even bootstrapping is a tools issue of sorts... | > | > What do others think? | > | | The first time I have to create my configuration, when I did the | tutorial, | and I have to copy paste the template I wondered myself why there | wasn't an | abstract configuration class :) | In my opinion, it is easier for the configurations. You put the | ensure | metacello and all those methods that are in the template there and | that's | all. | | So... +1 to have an abstract class for me. | | | > | > Dale | > | > ----- "Tudor Girba" <tudor.girba(a)gmail.com> wrote: | > | > | Oh! I am slightly embarrassed :) | > | | > | I updated ConfigurationOfMooseJEE to use the latest | > | ConfigurationOfMetacello and indeed it works. | > | | > | But I think this basically means that it starts to make sense to | have | > | | > | an abstract configuration in Pharo-Core, because copy paste just | does | > | | > | not scale anymore. | > | | > | Cheers, | > | Doru | > | | > | p.s. Btw, I love the progress bar :) | > | | > | | > | On 11 Dec 2009, at 19:24, Dale Henrichs wrote: | > | | > | > Doru, | > | > | > | > I looked at the #ensureMetacello method ConfigurationOfMooseJEE, | but | > | | > | > didn't notice (the first, second and third time that I looked:) | that | > | | > | > it is using MetacelloConfiguration so latest version isn't | getting a | > | | > | > recent enough version of Metacello ... | > | > | > | > So update the ConfigurationOfMooseJEE class>>ensureMetacello to | boot | > | | > | > with ConfigurationOfMetacello instead of | MetacelloConfiguration... | > | > | > | > Dale | > | > ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | > | > | > | > | Doru, | > | > | | > | > | Things worked fine (well almost fine) with my first try at | > | loading | > | > | MooseJEE ... initialization failed in FSPlatformResolver, | because | > | > | there is no FSUnixResolver, however the | Morphic-MorphTreeWidget | > | is | > | > | being loaded. I used this expression: | > | > | | > | > | Gofer new squeaksource: 'MooseJEE'; addPackage: | > | > | 'ConfigurationOfMooseJEE'; load. | > | > | (Smalltalk at: #ConfigurationOfMooseJEE) perform: | #loadDefault | > | > | | > | > | ... This test was run with 1.0-beta.18 preloaded, so I will | try | > | > again | > | > | with a virgin image... | > | > | | > | > | Dale | > | > | ----- "Tudor Girba" <tudor.girba(a)gmail.com> wrote: | > | > | | > | > | | Hi, | > | > | | | > | > | | A strange problem, that appeared before but was solved at | the | > | > time, | > | > | | > | > | | seems to resurface again in a slightly different context. | > | > | | | > | > | | It is related to the Morphic-MorphTreeWidget from the Momo | > | > | | squeaksource repository. This is needed in Glamour. | > | > | | | > | > | | Glamour is needed in Moose. | > | > | | | > | > | | Now, if you load ConfigurationOfMoose, it all works fine: | > | > | | | > | > | | Gofer new squeaksource: 'Moose'; addPackage: | > | > 'ConfigurationOfMoose'; | > | > | | > | > | | | > | > | | load. | > | > | | (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault | > | > | | | > | > | | However, Moose is needed in MooseJEE. And if you load | > | > | | ConfigurationOfMooseJEE it does not work anymore: | > | > | | | > | > | | Gofer new squeaksource: 'MooseJEE'; addPackage: | > | > | | 'ConfigurationOfMooseJEE'; load. | > | > | | (Smalltalk at: #ConfigurationOfMooseJEE) perform: | #loadDefault | > | > | | | > | > | | If you look in the packages to load, | Morphic-MorphTreeWidget | > | does | > | > | not | > | > | | | > | > | | seem to appear among them in the latter case. | > | > | | | > | > | | I would need help for this one, if someone has time to look | > | into | > | > | that | > | > | | :) | > | > | | | > | > | | Cheers, | > | > | | Doru | > | > | | | > | > | | -- | > | > | | www.tudorgirba.com | > | > | | | > | > | | "The coherence of a trip is given by the clearness of the | > | goal." | > | | > | -- | > | www.tudorgirba.com | > | | > | "Presenting is storytelling." | >

15 years, 6 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev