- Moose-dev - INF Mailman

by Nicolas Anquetil

I believe I already said here that I don't like very much the "default" FAMIX metamodel in Moose because it is the union of Smalltalk and Java specificities. For 2 languages it works (more or less), but if we want to add C#, C++, and whatever-else (not talking about non OO languages), it quickly starts to be a huge mess. It would be preferable to have a generic metamodel and specific ones for each languages. But then, we will run into cases where we want to have some kind of multiple inheritance. For example we could want to say that a Java method and a C function are behaviouralEntities with return type and Java methods and Smalltalk methods are behavioural entities with a received (when they are called) and Java method now have two superclasses. So the question arise why Fame does not have multiple inheritance? - no specific reason? - fundamental design decision? - historical reason? nicolas -- Nicolas Anquetil -- RMod research team (Inria)

12 years, 4 months

3
7
0 0

Glamorous Toolkit in the course of being migrated

by Andrei Vasile Chis

Hi, I started to migrate Glamorous Toolkit to SmalltalkHub. It will go in a project named GToolkit in the moose group. Cheers, Andrei

12 years, 4 months

3
4
0 0

creating a reloader script for the latest release

by Usman Bhatti

Hello, I used stef's reloader to determine the packages loaded in the latest 4.7 build from squeaksource and I compared it to the flatVersion47: (corresponding to release 4.7, generated in dec 2012) in configurationOfMoose. There are some packages that are updated in latest moose 4.7 but there are old versions of these packages in flatVersion47:. For example, the version number of FAMIX-Core in flatversion47 is 209 but in the latest 4.7 build, it was 211. I am creating a new script6 that loads the latest stable version of Moose on 1.4, it is important because there are some updates from Roassal and Eyesee that we need. So, it would be good that flatVersion47 points to script6. Here is a list of packages whose version number changed. Package: flatVersion47 version number -> latest-dev version number OSProcess: 73-> 78 Famix-Core: 209-> 211 Famix-File: 38-> 39 Famix-Java: 70-> 71 Famix-Extensions: 244-> 246 PetitAnalyzer: 39-> 40 Glamour-Examples: 252-> 253 Glamour-Morphic-Renderer: 179-> 183 PetitGui: 114-> 116 ConfigurationOfRoassal: 752-> 866 Mondrian-Easel: 42-> 43 ConfigurationOfFuel: 157-> 181 Fuel: 685-> 686 FuelCompatibilityBeforePharo20: 20-> 20 Roassal: 404-> 475 RoassalMorphic: 94-> 111 EyeSee-Tests-Core: 66-> 67 EyeSee-Core: 99-> 100 Moose-Finder: 426-> 427 Moose-MondrianPaintings: 172-> 176 ConfigurationOfMoose: 275-> 278 Usman

12 years, 4 months

2
4
0 0

numberOfLinesOfCode metric for smalltalk uses compiledMethod

by Fabrizio Perin

Hi, the metric numberOfLinesOfCode it doesn't work on an imported moose smalltalk model because it looks for the compiled method version to calculate the actual lines of code. I think we should seriously rethink the entire smalltalk importing and handling phase because it is not possible that only pharo can be imported and analyze: In all the places where a "isSmalltalk" method is invoked, if that means that you are going to look for smalltalk code in the image, we should change it with a method called "isSmalltalkCodeLoaded". This method can be set since the import phase. What do you think? Cheers, Fabrizio PS: I hope I can make the code I wrote to import Smalltalk available ASAP, that could be use as a start to create a image code independent parser/importer :)

12 years, 4 months

3
4
0 0

call for speakers - pharoconf (april 2, 3) / mooseday (april 4) - bern, switzerland

by Tudor Girba

Hi, During April 2-4 we will organize a PharoConf and a MooseDay in Bern, Switzerland. Mark the day and join us. The participation will be free of charge. The conference will focus on interactivity and exchange, and will feature experience report talks, tutorials, show-us-your-project sessions and open discussions. We are looking for speakers: TUTORIAL These sessions will walk the audience through a piece of technology. Target duration: 30min - 60min. Example topics: - ZeroConf continuous integration builds - Building vectorial interfaces with Athens - Building UIs with Spec - New development tools (Fuel/Tanker, Glamorous Debugger, Nautilus ...) - Manipulating databases in Pharo (Riak, MongoDB ...) - Visualizing data (Roassal, EyeSee ...) TALK These sessions expose a topic that is not necessarily technical. Target duration: 30min - 60min. Example topics: - Experience of using Pharo to solve business problems - Experience of using Pharo and Moose to solve various technical problems (not necessarily related to Smalltalk) - Successes in marketing Pharo-based solutions - Future directions for Pharo or Moose SHOW-US-YOUR-PROJECT These sessions will feature short presentations of the projects (7-10 minutes) followed by open-space demos. Example topics: - The Glamorous Debugger - Nautilus - Analysis tools like Softwarenaut or Carrack - Fuel/Tanker - ... Please send us your submissions by email at tudor(a)tudorgirba.com. Cheers, Doru on behalf of the organizers -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

12 years, 4 months

2
1
0 0

Migrating CAnalyzer from SS to SHub/Moose/CAnalyzer

by Stéphane Ducasse

Hi guys I'm currently migrating CAnalyzer from SS to SHub/Moose/CAnalyzer Stef

12 years, 4 months

3
3
0 0

PetitJava status

by Yuriy Tymchuk

Hi everyone. If you remember I'm developing an AST extension for FAMIX and right now I've started to work on Java part. One of the features I have to support is generation of method's AST from the source code on demand. I've found that there is a petit parser implementation for Java and I wander what is it's status and is it wise to spend time on it. Because having a parser in smalltalk is really nice compared to passing a method source text to some external script, reading result from generated file, etc. uko -- View this message in context: http://moose-dev.97923.n3.nabble.com/PetitJava-status-tp4026356.html Sent from the moose-dev mailing list archive at Nabble.com.

12 years, 4 months

3
4
0 0

sourceText method wrong implementation

by Fabrizio Perin

Hi, I have noticed that both FAMIXClass and FAMIXMethod sourceText methods starts with: self mooseModel isSmalltalk I think this is wrong. It should always be: self sourceLanguage isSmalltalk This way if a FAMIX element has a language which is default language for the model you can capture that. Do you agree? Cheers, Fabrizio

12 years, 4 months

2
5
0 0

Parse VisualAge Smalltalk st files (or app as they are called)

by Fabrizio Perin

Hi, I would like to create a Moose model of a VisualAge smalltalk application. I tried to fileout a bunch of applications (which are groups of packages as far as I understood) and the result file .app has naturally a different syntax from pharo st files. Now, the questions are: - Should I customize the PPSmalltalkParser or should I start a parser from scratch? - Did anybody tried to import in moose a smalltalk dilect different from pharo? If yes how did he do that? I just want to understand if I can save time or I should build a whole parser and importer from scratch. Thanks for any suggestion or information. Cheers, Fabriyio (bloodz german kezboard)

12 years, 4 months

5
26
0 0

petitparser tests

by Tudor Girba

Hi, I fixed a couple of tests in PetitParser (they were using the obsolete includesSubString:) and they are now all green in Pharo 2.0. However, some of the PetitSmalltalk-Tests are still red: - There was an issue with a commit from Lukas that went to the old repository and was only partly in the new one (probably due to the confusion around the move to the new repository). I merged the changes. - Still some tests fail, but I did not have a chance to figure it out as to why this happens. Cheers, Doru -- www.tudorgirba.com "Value is always contextual."

12 years, 4 months

2
1
0 0

since moose-algos has been migrated

by stephane ducasse

I will comment it on Squeaksource and put it read only. Stef

12 years, 4 months

2
1
0 0

BlockContext

by Usman Bhatti

Some methods in Moose introduce extension methods on BlockContext. BlockContext has been replaced by BlockClosure. We already have the required moose extension methods in BlockClosure, so I'll remove extension methods on BlockContext so that we do not have warnings while loading Moose on pharo 2.0. For info, the ist of extension categories added by Moose packages on BlockContext: - eyesee-support - moose-core - petitparser-core-converting

12 years, 4 months

3
7
0 0

glamour in pharo 2.0

by Tudor Girba

Hi, I fixed a couple of issues for Pharo 2.0. There are still a couple of things left: - There is error due to Mondrian which freezes the image and it is a bit difficult to debug (see the tests from Glamour-Tests-Mondrian). - There is an error when using PaginatedMorphTreeMorph which influences the setting of list selection from outside (see GLMListMorphicTest>>testUpdateFromModel) Cheers, Doru -- www.tudorgirba.com "Every thing should have the right to be different."

12 years, 4 months

1
0
0 0

[ANN] Moose 4.7

by Tudor Girba

We are happy to announce the Moose Suite version 4.7: http://moosetechnology.org/download What is new: • Integration of the Roassal visualization engine • New PetitParser browser with integrated refactorings • Improved Glamorous Toolkit for Pharo including the Glamorous Inspector and Debugger • Several features in Glamour including Watcher support (similar to OS X preview) • Significant improvements in FAMIX • Improved external VerveineJ parser for Java • Based on Pharo 1.4 A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… Have fun, The Moose Team

12 years, 4 months

1
0
0 0