- Moose-dev - INF Mailman

by Veronica Isabel Uquillas Gomez

Hi, When displaying text (e.g. source code) on a popup view, it is all aligned to the left without considering tabs... Stef told that he already fixed this in Morph but using the latest version of Mondrian the problem is still present. What I noticed is that a popup text presents the text correctly. Is some else having the same problem with popup views? Regards, Veronica

13 years, 8 months

2
4
0 0

Tests FMMetaRepositoryFilterTest

by Andre Hora

Hello, Some tests related to FMMetaRepositoryFilterTest are red in the latest-dev, but when running them in my machine they are green. []'s -- Andre Hora

13 years, 8 months

2
3
0 0

only one yellow test

by Tudor Girba

Hi, I fixed most tests. As I said before many of the tests failed because the newly defined properties for metrics were not marked as <derived>. The reason why other tests failed was that when we try to load back a model we need a means to set the value. Because most metrics are lazily computable, we do not have setters and thus, they need to be marked with <derived>. The only yellow test is related to RoelTyper which seems to raise again errors in the latest Pharo 1.3. Anyone wants to take this one? :) 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, 8 months

2
5
0 0

Moose and its configurations

by Alexandre Bergel

Hi! Getting a proper configuration of moose is not easy and probably will not be produced tomorrow. I spent some time with our Metacello Sansei, and we did not fix it. Many cycles from the configuration can be removed by simply removing the dependency on ConfigurationOfMoose. For example, ConfigurationOfDSM, ConfigurationOfKumpel and ConfigurationOfSmallDude explicitly load Moose. Is there a reason for this? Saying that DSM, Kumpel and SmallDude can only be loaded in a Pharo with Moose will simplify the situation in my opinion. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 8 months

2
1
0 0

problems with fuel serializing non-integer numbers

by Tudor Girba

Hi Mariano, hi Martin, As you know, we are using Fuel for serializing objects based on Fame descriptions. We recently added new properties to Fame that contain number values that are not integer (e.g., Float), and now we get the problem that Fuel does not seem to be able to serialize them. To reproduce the problem, you can download the latest moose image and run the FuelMooseTests: http://ci.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/arti… You will see that there are some 44 errors due to looking up values in the dictionary. Could please you take a look and see if the problem is in Fuel or maybe somewhere else? Cheers, Doru -- www.tudorgirba.com "It's not how it is, it is how we see it."

13 years, 8 months

4
12
0 0

morph renderer

by Esteban Lorenzano

Hi Doru, I coded a specific glamour renderer for morphs (bah... I copied a lot from magritte renderer). The objective is make possible to update morphs when an update is triggered, and I think in the future there will be much more advantages to having it as a complete renderer. I'm attaching the change set. Cheers, Esteban

13 years, 8 months

1
0
0 0

moose at smalltalks

by Tudor Girba

Hi, FYI, this year, I will end up at Smalltalks and I will be talking about Humane Assessment, Moose and Glamour. Will any of you be around? Cheers, Doru -- www.tudorgirba.com "One cannot do more than one can do."

13 years, 8 months

4
3
0 0

Issue 729 in moose-technology: inFusion should create default constructors

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 729 by tu...(a)tudorgirba.com: inFusion should create default constructors http://code.google.com/p/moose-technology/issues/detail?id=729 If we have: public class A { public void m() {...} } public class B { public void x() { new A() ... } } We should get an invocation between B::x() and A::A(), where A::A() should be marked as stub.

13 years, 8 months

1
0
0 0

please use a sentence to describe an issue

by Tudor Girba

Hi, Please use a sentence when naming an issue. Some examples: - A bug entry should try to specify what the wrong behavior is: "Hismo and classhistories" ==> "allClassHistories is not instance of HismoClassHistoryGroup" - An enhancement should specify what the intended behavior should be: "span or size for each column in GLMTablePresentation" ==> "GLMTablePresentation should allow us to set the size of each column" Cheers, Doru -- www.tudorgirba.com "It's not how it is, it is how we see it."

13 years, 8 months

2
1
0 0

Issue 727 in moose-technology: Hismo and classhistories

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-High Component-Hismo New issue 727 by alexandr...(a)gmail.com: Hismo and classhistories http://code.google.com/p/moose-technology/issues/detail?id=727 In the MooseModel root I have a number of Smalltalk models. Consider the following script: -=-=-=-=-=-=-=-=-=-=-=-= histories:=MooseModel root allModels asArray. history:=HismoModelHistory new. histories do:[:model| history addLastVersionForMooseModel: model]. history allClassHistories class -=-=-=-=-=-=-=-=-=-=-=-= The script prints HismoHistoryGroup, where I expected HismoClassHistoryGroup. In the Moose panel, I see the item 'All Class Histories'. But inspecting it reveals it is an instance of HismoHistoryGroup.

13 years, 8 months

1
4
0 0

Merlin question

by Alexandre Bergel

Hi! I am building a wizard and I am stopped on something that looks trivial. Consider the following script: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | control firstPane lastPane part1 dropListPart part2 | control := WizardControl new. firstPane := WizardFirstPane new. lastPane := WizardLastPane new. control addPane: firstPane; addPane: lastPane. "First pane: picking the configuration we are interested in" part1 := TextPart new inGroupboxNamed: 'Select the configuration you want to load versions from'. firstPane addPart: part1 associatedTo: #selectedConfiguration. dropListPart := DropListPart new inGroupboxNamed: 'Configurations'; list: self listOfConfigurations; useLatePopulateContents: false; yourself. firstPane row: dropListPart associatedTo: #selectedConfiguration2. "Second pane" part2 := MultiSelectionItemSelectorPart new initialList: ([:input | {input at: #selectedConfiguration2}]). lastPane addPart: part2 associatedTo: #selectedVersions. "Open the controler" control open. ^ control -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= The problem is that I do not know how to initialize the MultiSelectionItemSelectorPart in the second pane since I need the result of what I selected in part1. I tried to inspire myself from the merlin example #itemsSelectorPartUsing: , but without success. So, how part2 can refer to the result selected in part1 ? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 8 months

5
9
0 0

Pimon.Figure in VW

by Usman Bhatti

I am working on porting an FCA library from VW to Pharo. In VW, classes LatticeNode and Lattice inherit from a class: Pimon.Figure. The corresponding classes in pharo, already ported, inherit from ProtoObject. My question: Is there an easy workaround (that is inheriting from a similar class in pharo doing the work of Pimon.Figure) or do I need to rewrite these Lattice and LatticeNode classes? thanx Usman

13 years, 8 months

3
7
0 0

moose build is broken

by Tudor Girba

Hi, For your information, the Moose build is broken apparently due to a mismatch between ConfigurationOfGrease and the image. Any help in this direction would be appreciated. Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

13 years, 8 months

2
4
0 0

Re: Merlin question

by Alexandre Bergel

Hi Cyrille, Thanks for your help. This goes indeed in the right direction, however I have the impression I am now bumping into a bug. Consider the following code: -=-=-= -=-=-= -=-=-= -=-=-= -=-=-= | wizardControl wizardPane1 wizardPane2 itemsSelectorsPart listPart aRenderer | aRenderer := MerlinMorphicWizardRenderer new . wizardControl := WizardControl new. wizardControl renderer: aRenderer. wizardPane1 := WizardFirstPane new. wizardPane2 := WizardLastPane new. itemsSelectorsPart := MultiSelectionItemSelectorPart new initialList: #(item1 item2 item3 item4); yourself. listPart := MultiSelectionItemSelectorPart new initialList: [:requiredInputs | (requiredInputs at: #selectedItems) ]; yourself. wizardPane1 row: itemsSelectorsPart associatedTo: #selectedItems. wizardPane2 row: listPart requiring: {#selectedItems}. wizardControl addPane: wizardPane1; addPane: wizardPane2. wizardControl open. -=-=-= -=-=-= -=-=-= -=-=-= -=-=-= This throws an error. Shall I open an issue? Cheers, Alexandre On 17 Oct 2011, at 14:45, Cyrille Delaunay wrote: > Hello alex, > > 2011/10/17 Alexandre Bergel <alexandre.bergel(a)me.com> > Hi! > > I am building a wizard and I am stopped on something that looks trivial. > Consider the following script: > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > | control firstPane lastPane part1 dropListPart part2 | > control := WizardControl new. > firstPane := WizardFirstPane new. > lastPane := WizardLastPane new. > > control addPane: firstPane; addPane: lastPane. > > "First pane: picking the configuration we are interested in" > part1 := TextPart new inGroupboxNamed: 'Select the configuration you want to load versions from'. > firstPane addPart: part1 associatedTo: #selectedConfiguration. > > dropListPart := DropListPart new > inGroupboxNamed: 'Configurations'; > list: self listOfConfigurations; > useLatePopulateContents: false; > yourself. > firstPane row: dropListPart associatedTo: #selectedConfiguration2. > > "Second pane" > part2 := MultiSelectionItemSelectorPart new initialList: ([:input | {input at: #selectedConfiguration2}]). > lastPane addPart: part2 associatedTo: #selectedVersions. > > I think that here you should specify something like: > > lastPane addPart: part2 associatedTo: #selectedVersions requiring: #selectedConfiguration2. > > Like that the input of the MultiSelectionItemSelectorPart get populated with output of the dropListPart. That means that the line: > > > part2 := MultiSelectionItemSelectorPart new initialList: ([:input | {input at: #selectedConfiguration2}]). > > will work corectly. > Does it answer to your question? > > > "Open the controler" > control open. > ^ control > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > The problem is that I do not know how to initialize the MultiSelectionItemSelectorPart in the second pane since I need the result of what I selected in part1. I tried to inspire myself from the merlin example #itemsSelectorPartUsing: , but without success. > > So, how part2 can refer to the result selected in part1 ? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 8 months

1
0
0 0

Strange behavior on Hismo?

by Alexandre Bergel

Hi! In the MooseModel root I have a number of Smalltalk models. Consider the following script: -=-=-=-=-=-=-=-=-=-=-=-= histories:=MooseModel root allModels asArray. history:=HismoModelHistory new. histories do:[:model| history addLastVersionForMooseModel: model]. history allClassHistories class -=-=-=-=-=-=-=-=-=-=-=-= The script prints HismoHistoryGroup, where I expected HismoClassHistoryGroup. In the Moose panel, I see the item 'All Class Histories'. But inspecting it reveals it is an instance of HismoHistoryGroup. Am I missing something obvious? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 8 months

2
3
0 0

FAMIXAssociation>>SourceAnchor

by Nicolas Anquetil

FAMIXAssociations being SourcedEntities have a 'sourceAnchor' instance variable. However it redefines the method sourceAnchor : ^ self from sourceAnchor I am sure there was some good reason to do this, but to me this is counter intuitive and something should probably be corrected. (in practice I spent from 11pm to 1am yesterday looking for a bug that did not exist :-( ) nicolas

13 years, 8 months

2
2
0 0

Re: petit git log paser

by Fabrizio Perin

That is cool Simon. If you can make it public I will surely play with it :) Cheers, Fabrizio On 17 Oct 2011, at 16:30, Simon Denier wrote: > > On 14 oct. 2011, at 12:47, Fabrizio Perin wrote: > >> Hi, >> I will start to work on a parser to parse git logs. For now i will parer the info generated by "git log --stat". A full diff parser will came later. >> >> If you have any suggestion or comment please ping me. > > > Hi Fabrizio > > Just wanted to tell you that I wrote such a parser this summer, part time because I wanted to learn Petit Parser. However, it's still in the context of my work, so I have to check with my boss whether I can release it in the wild first. > > -- > Simon Denier > > >

13 years, 8 months

1
0
0 0

Re: [Pharo-project] Can this be improved in Glamourous?

by Marcus Denker

On Oct 15, 2011, at 11:13 PM, Stéphane Ducasse wrote: > > On Oct 15, 2011, at 10:58 PM, Tudor Girba wrote: > >> Hi, >> >> On 15 Oct 2011, at 22:36, Mariano Martinez Peck wrote: >> >>> Hi Tudor. Today I wanted to give it a try to 'GT-Inspector' 'GT-Playground' hence I did: >> >> I am happy you decided to give them a try :). But, the Playground is not yet ready :). >> >>> (ConfigurationOfGlamoroust project version: #bleedingEdge) load: #('GT-Inspector' 'GT-Playground' ). >>> >>> In a Pharo 1.3 release. To my surprise, it took like half an hour to install, and it even was broken because it installed a different version of refactoring browser that is not working in 1.3. >> >> This is due to a broken ConfiguraitonOfRB. I would actually be very interested in a fix in this area. > > what is broken? because I spent one full sprint to fix it. the fixed version needs a new Core (13315), while the Full image right now is 13307. The RB between the two is not compatible. We need to fix the Metacello of Shout to load the latest version so we can build a Full image based on 13315, this should solve some of the problems. Marcus -- Marcus Denker -- http://marcusdenker.de

13 years, 8 months

3
3
0 0

Re: [Pharo-project] Can this be improved in Glamourous?

by Marcus Denker

On Oct 16, 2011, at 10:07 PM, Tudor Girba wrote: > Hi, > > If you give me the script, I build one based on the Core. > Husdon does: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. -- Marcus Denker -- http://marcusdenker.de

13 years, 8 months

2
1
0 0

Re: [Pharo-project] Can this be improved in Glamourous?

by Marcus Denker

On Oct 16, 2011, at 10:00 PM, Tudor Girba wrote: > Ok. We did it. Now, the whole Moose is unbuildable :) > > The issue is that it tells us that: > > *** Warning: Warning: You are about to load new versions of the following packages that have unsaved changes in the image. If you continue, you will lose these changes. > > Refactoring-Tests-Core > > > We are loading ConfigurationOfRB stable. We really need to make a version of everytthing based on 13315. Marcus -- Marcus Denker -- http://marcusdenker.de

13 years, 8 months

2
1
0 0

Re: [Pharo-project] Can this be improved in Glamourous?

by Tudor Girba

Hi, Btw, you can download a ready-made image with the GlamorousToolkit from: http://ci.moosetechnology.org/job/glamorous-toolkit-latest-dev/lastSuccessf… Cheers, Doru On 15 Oct 2011, at 23:32, Tudor Girba wrote: > Hi, > > On 15 Oct 2011, at 23:13, Stéphane Ducasse wrote: > >> >> On Oct 15, 2011, at 10:58 PM, Tudor Girba wrote: >> >>> Hi, >>> >>> On 15 Oct 2011, at 22:36, Mariano Martinez Peck wrote: >>> >>>> Hi Tudor. Today I wanted to give it a try to 'GT-Inspector' 'GT-Playground' hence I did: >>> >>> I am happy you decided to give them a try :). But, the Playground is not yet ready :). >>> >>>> (ConfigurationOfGlamoroust project version: #bleedingEdge) load: #('GT-Inspector' 'GT-Playground' ). >>>> >>>> In a Pharo 1.3 release. To my surprise, it took like half an hour to install, and it even was broken because it installed a different version of refactoring browser that is not working in 1.3. >>> >>> This is due to a broken ConfiguraitonOfRB. I would actually be very interested in a fix in this area. >> >> what is broken? because I spent one full sprint to fix it. > > Actually it is not broken. Something else is broken by loading an older version somewhere in the Moose configuration. I did not have time yet. > >>>> So..can I ask.. are all of those projects really needed just for 2 simples things like a cool inspector and a cool workspace? >>>> do you need Nile, Grease, RefactoringBrowser, EyeSee, Magritte ??? >>>> can I somehow just load a minimal core for those things I need ? >>> >>> These projects are loaded by the full default ConfigurationOfGlamour. The ConfigurationOfGlamour offers groups, but the GlamorousToolikt one does not yet. If someone can tell me how to do something like this, I would be happy to accommodate the solution. >> >> in the chapter on metacello groups are explained. I can send you the latest version if you want. > > I know how they work. I was actually referring to the actual code :). It is such a big mess to deal with the explosion of combinations. > > Doru > > >>> Cheers, >>> Doru >>> >>> >>>> Thanks >>>> >>>> linear load : >>>> linear load : baseline-0.1 [ConfigurationOfGlamoroust] >>>> load : ConfigurationOfGlamour >>>> atomic load : baseline-0.1 [ConfigurationOfGlamoroust] >>>> linear load : default [ConfigurationOfGlamour] >>>> load : ConfigurationOfEyeSee >>>> linear load : default [ConfigurationOfGlamour] >>>> load : ConfigurationOfGrease >>>> linear load : default [ConfigurationOfGlamour] >>>> load : ConfigurationOfMondrian >>>> linear load : default [ConfigurationOfGlamour] >>>> load : ConfigurationOfShout >>>> atomic load : default [ConfigurationOfGlamour] >>>> load : CollectionExtensions >>>> load : Glamour-Announcements >>>> load : Glamour-Helpers >>>> load : Glamour-Core >>>> load : Glamour-Presentations >>>> load : Glamour-Browsers >>>> load : Glamour-Tests-Core >>>> load : Glamour-Morphic-Theme >>>> load : Glamour-Examples >>>> load : Glamour-Tools >>>> load : Glamour-Morphic-Widgets >>>> load : Glamour-Morphic-Renderer >>>> load : Glamour-Tests-Morphic >>>> linear load : default [ConfigurationOfMondrian] >>>> load : ConfigurationOfProfStef >>>> linear load : default [ConfigurationOfMondrian] >>>> load : ConfigurationOfHealthReportProducer >>>> linear load : default [ConfigurationOfMondrian] >>>> load : ConfigurationOfShapeST80 >>>> atomic load : default [ConfigurationOfMondrian] >>>> atomic load : 0.2-baseline [ConfigurationOfHealthReportProducer] >>>> load : HealthReportProducer >>>> load : CollectionExtensions >>>> load : Nile-Base >>>> load : Mondrian-ComplexShape >>>> load : Mondrian-Core >>>> load : Mondrian-Layouts >>>> load : Mondrian-Help >>>> load : Mondrian-Easel >>>> load : Mondrian-Pharo-Tests >>>> load : Mondrian-Shapes >>>> load : Mondrian-Events >>>> load : Mondrian-Visitor >>>> load : Mondrian-Util >>>> load : Mondrian-Normalizers >>>> load : Mondrian-Example >>>> load : Mondrian-ShapeVisitor >>>> load : Mondrian-Pharo-Morphic >>>> load : Mondrian-Tests >>>> load : Mondrian-FADELayout >>>> load : Glamour-Mondrian-Presentations >>>> load : Glamour-Tests-Mondrian >>>> atomic load : default [ConfigurationOfEyeSee] >>>> load : EyeSee-Events >>>> load : EyeSee-Axis >>>> load : EyeSee-Tests-Core >>>> load : EyeSee-Support >>>> load : EyeSee-Core >>>> load : Glamour-EyeSee-Presentations >>>> load : Glamour-Tests-EyeSee >>>> linear load : 1.0.6.1 [ConfigurationOfGrease] >>>> load : ConfigurationOfRefactoringBrowser >>>> linear load : 1.0.6.1 [ConfigurationOfGrease] >>>> load : Grease-Slime-lr.13 >>>> load : Magritte-Model >>>> load : Magritte-Pharo-Model >>>> load : Magritte-Morph >>>> load : Glamour-Magritte-Presentations >>>> load : Magritte-Tests-Model >>>> load : GT-Playground >>>> load : GT-Inspector >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every successful trip needs a suitable vehicle." >>> >>> >>> >>> >>> >> >> > > -- > www.tudorgirba.com > > "One cannot do more than one can do." > > > -- www.tudorgirba.com "Obvious things are difficult to teach."

13 years, 8 months

2
1
0 0

working on system announcement...

by Stéphane Ducasse

just that you know I'm improving system announcement and hope to get done with the bug that freezes my image with RPackage. So that I can continue to work on the integration of rpackage. The integration is a pain. Stef

13 years, 8 months

3
3
0 0

Can this be improved in Glamourous?

by Mariano Martinez Peck

Hi Tudor. Today I wanted to give it a try to 'GT-Inspector' 'GT-Playground' hence I did: (ConfigurationOfGlamoroust project version: #bleedingEdge) load: #('GT-Inspector' 'GT-Playground' ). In a Pharo 1.3 release. To my surprise, it took like half an hour to install, and it even was broken because it installed a different version of refactoring browser that is not working in 1.3. So..can I ask.. are all of those projects really needed just for 2 simples things like a cool inspector and a cool workspace? do you need Nile, Grease, RefactoringBrowser, EyeSee, Magritte ??? can I somehow just load a minimal core for those things I need ? Thanks linear load : linear load : baseline-0.1 [ConfigurationOfGlamoroust] load : ConfigurationOfGlamour atomic load : baseline-0.1 [ConfigurationOfGlamoroust] linear load : default [ConfigurationOfGlamour] load : ConfigurationOfEyeSee linear load : default [ConfigurationOfGlamour] load : ConfigurationOfGrease linear load : default [ConfigurationOfGlamour] load : ConfigurationOfMondrian linear load : default [ConfigurationOfGlamour] load : ConfigurationOfShout atomic load : default [ConfigurationOfGlamour] load : CollectionExtensions load : Glamour-Announcements load : Glamour-Helpers load : Glamour-Core load : Glamour-Presentations load : Glamour-Browsers load : Glamour-Tests-Core load : Glamour-Morphic-Theme load : Glamour-Examples load : Glamour-Tools load : Glamour-Morphic-Widgets load : Glamour-Morphic-Renderer load : Glamour-Tests-Morphic linear load : default [ConfigurationOfMondrian] load : ConfigurationOfProfStef linear load : default [ConfigurationOfMondrian] load : ConfigurationOfHealthReportProducer linear load : default [ConfigurationOfMondrian] load : ConfigurationOfShapeST80 atomic load : default [ConfigurationOfMondrian] atomic load : 0.2-baseline [ConfigurationOfHealthReportProducer] load : HealthReportProducer load : CollectionExtensions load : Nile-Base load : Mondrian-ComplexShape load : Mondrian-Core load : Mondrian-Layouts load : Mondrian-Help load : Mondrian-Easel load : Mondrian-Pharo-Tests load : Mondrian-Shapes load : Mondrian-Events load : Mondrian-Visitor load : Mondrian-Util load : Mondrian-Normalizers load : Mondrian-Example load : Mondrian-ShapeVisitor load : Mondrian-Pharo-Morphic load : Mondrian-Tests load : Mondrian-FADELayout load : Glamour-Mondrian-Presentations load : Glamour-Tests-Mondrian atomic load : default [ConfigurationOfEyeSee] load : EyeSee-Events load : EyeSee-Axis load : EyeSee-Tests-Core load : EyeSee-Support load : EyeSee-Core load : Glamour-EyeSee-Presentations load : Glamour-Tests-EyeSee linear load : 1.0.6.1 [ConfigurationOfGrease] load : ConfigurationOfRefactoringBrowser linear load : 1.0.6.1 [ConfigurationOfGrease] load : Grease-Slime-lr.13 load : Magritte-Model load : Magritte-Pharo-Model load : Magritte-Morph load : Glamour-Magritte-Presentations load : Magritte-Tests-Model load : GT-Playground load : GT-Inspector -- Mariano http://marianopeck.wordpress.com

13 years, 8 months

3
2
0 0

Cobol sources

by Andre Hora

Hello, Do we have some MSE generator to analyze Cobol sources? I remember in ESUG people presenting a work related to the analysis of Cobol sources in Moose, but I am not sure if their work is available for us. If we don't have one, do you know a good parser / ast generator to Cobol sources? Just to the case if we want to implement something one day... regards, -- Andre Hora

13 years, 8 months

2
1
0 0

Ladder of Abstraction

by Serge Stinckwich

Hi all, i found this very interesting page: http://worrydream.com/LadderOfAbstraction/ on Twitter. This is something that we could envision in future versions of Mondrian: be able to explore/visualize systems and data in a more interactive way at multiple levels of abstraction. I also like the paragraph at the end "Appendix: Tools & Implementation" with sentences like: "Unfortunately, development environments generally don't support this process." and "Perhaps IDE makers will focus on dynamic exploration instead of static analysis, rich visualization instead of line debugging. Perhaps language theorists will stop messing around with arrows and dependent types, and start inventing languages suitable for interactive development and discovery." The animation in this page are done with the help on an js library called Tangle : http://worrydream.com/Tangle/ One nice idea could be use it from Amber Smalltalk in order to have this kind of exploration and at the same time the IDE suitable to modify algorithms and parameters. Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

13 years, 8 months

3
2
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev