Moose-dev December 2011

moose-dev@list.inf.unibe.ch

32 participants
167 discussions

by Stéphane Ducasse

Hi apparently the smalltalk importer does not take into account the Pool variables (class variables of a SharedPool subclass and with declared usage in I have to investigate that. Now this is not as simple as for class variables. We have a sharedPool MyPool classVar: Editor LAN.Node poolDictionary: MyPool foo Editor I could either change the class import to check whether the class uses a sharedPool and add their class variables and when I encounter a pool variable usage I have to prefix it with the classPool. Would make sense. I will add an example in the LAN and see if I do not break that many tests. Stef

13 years, 3 months

dynamix and petitsql

by Tudor Girba

Hi, For your information, Dynamix and PetitSQL are now part of ConfigurationOfMoose. Cheers, Doru -- www.tudorgirba.com "Beauty is where we see it."

13 years, 3 months

verveinej and maven

by Tudor Girba

Hi Nicolas, Do you know if it would be possible to get VerveineJ to work with a pre-existing Maven configuration? I know that Eclipse can (I think through a plugin) recognize the Maven configurations and generate/adapt project properties and dependencies based on this. Would it maybe possible to do the same on the VerveineJ side? Cheers, Doru -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."

13 years, 3 months

reworking the petit browser

by Tudor Girba

Hi, I just wanted to let you know that I started to rework the PetitParser browser. There are several things that have changed: - it is modular, currently being formed of 3 distinct browsers. To give them a try (I also attached a couple of screenshots): PPAllParsersBrowser open. PPParserBrowser openOn: PPArithmeticParser. PPParserInspector openOn: PPArithmeticParser new. - it only relies on the Glamour mechanisms without state in the implementation code. This was more of a validation that the engine is expressive enough - it has a slightly different layout - the Mondrian map can be used as a navigation, so clicking on a node will focus the browser on that production. - it uses a tree widget for the debugger so we can scale for large debugging traces What is still to do: - install the associated instance variable for each newly created production. - introduce parser renaming refactoring. This would entail triggering both a method and an instance var rename. - add the possibility to remove a production. This would entail removing a method and the corresponding instance var. - make the morph graph view interactive. - add a new grammar class. - integrate tests for each production. This would involve being able to browse tests associated to a production, run, add and remove them. If these would work, we would have a true IDE and for most parts we would not need the Smalltalk editor for building parsers. But, I could use some help on the todos left, especially on the refactorings. Cheers, Doru -- www.tudorgirba.com "Presenting is storytelling."

13 years, 3 months

FAMIXFunction>>packageScope is missing

by Alexandre Bergel

Hi! We are importing C++ code in Moose and are bumping into problem when using Chef. packageScope is missing on FAMIXFunction. We could have something like: FAMIXFunction>>packageScope ^ self declatedType ifNotNil: [ self declatedType packageScope ] ifNil: [ nil ] Any better idea? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 3 months

Exception Handling in the Moose Distribution Image

by Mircea Filip Lungu

Hi guys, This is a bug report I got from one of my students and replicated by myself: In the Moose 4.6 image downloaded from moosetechnology.org, if I execute the following code | c | c := Collection new. c add: 1. the image seems to freeze, although what I would expect is that SubclassResponsibility exception to be raised. This has been observed on Windows and Mac. Do you know about this? Thanks, M. -- Dr. Mircea Lungu Researcher Software Composition Group University of Bern

13 years, 3 months

Fwd: [Pharo-project] Keymapping & OB conflict (was Re: Chasing Browsers)

by Stéphane Ducasse

So guys will you maintain petitparser? or Moose will stay in 1.3? Stef Begin forwarded message: > From: Lukas Renggli <renggli(a)gmail.com> > Subject: Re: [Pharo-project] Keymapping & OB conflict (was Re: Chasing Browsers) > Date: December 11, 2011 12:33:48 PM GMT+01:00 > To: Pharo-project(a)lists.gforge.inria.fr > Reply-To: Pharo-project(a)lists.gforge.inria.fr > >> - then that OB can be loaded on top of Pharo. Remember we are not against OB we just do not have >> the knowledge to maintain it. So if lukas gets OB working for 1.4 beta then we will probably include in Pharo. >> Now if OB is working for 1.4 only three months after 1.4 is released then we will not include it. > > Yes please, do not wait for me. > > Just to repeat myself: With Pharo 1.4 having uncountable changes in > core parts of the system and with the system including more and more > forked and increasingly incompatible versions of packages (AST, RB, > FS, Shout, Regex, ...) I am unwilling to go through the same pain as > with Pharo 1.3 again. In the current state, I don't see any of the > code I am involved with (including Seaside, Magritte, Pier, OB, > PetitParser, ...) to move forward. I suspect that moving to another > development platform soon causes less pain than to move to adopt the > next Pharo :-( > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

13 years, 3 months

experience with large images?

by jannik.laval

Hi Alex, With the team at Bordeaux, we are working on an implementation to query histories (the tool is named VPraxis). I implement a importer for Smalltalk. For now, I can load histories for a package, for a metacello configuration, from a repository. A first part is build in Pharo (building snapshots from Monticello), and a second part in build with our java software and build the history file. We can export xml, sql or swipl, which allows us to build prolog queries. Here (http://code.google.com/p/harmony/wiki/VPraxis) is a tutorial for the java VPraxis. For Smalltalk, I am working on it. I generated the current Mondrian history in a swipl format, available here: http://dl.dropbox.com/u/7739334/MondrianHistorySwipl.zip An important point is that we do not into account the multiple branches (it is a current work :) ). So, when there are multiple branches, for now, we check were is the merge and we "ignore the multiple branches". Now, for your question, we create a script: http://dl.dropbox.com/u/7739334/mondrianScript.txt Using swi-prolog (http://www.swi-prolog.org/) , you can call, in this script, the method moreN(L, 10). For the package Mondrian-Layout, it returns: L = [id_MOAbstractGraphLayout, id_MOCircleLayout, id_MOSugiyamaLayout]. Which are the three classes that have changed more that 10 times. For now, I am working on packaging all the things together. But if you have some other requests, do not hesitate to ask me :) Cheers, Jannik On Nov 24, 2011, at 14:05 , Alexandre Bergel wrote: > Having a reification in Moose of 100 versions of Mondrian for example :-) > > Just answering the question 'Which classes and methods of Mondrian have changed more than 10 times since the day Mondrian was born?' cannot be easily done without a lot of memory > > Alexandre > > > On 24 Nov 2011, at 03:27, Francois Stephany wrote: > >> I'm wondering: how big is a dataset > 500MB ? I've no idea how big it is. >> Alex, what is your use case (in practice!) for more than 500MB? >> >> On 23/11/11 18:25, Igor Stasenko wrote: >>> It is problematic, and requires different memory management than we >>> currently have. >>> I think if you need really big data sets, then use gemstone, which is >>> developed to deal with that specifically. >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > --- Jannik Laval

13 years, 3 months

EyeSee

by Alexandre Bergel

Hi! I am currently working on a few introductory slides for EyeSee. What ESDiagramTest is for? It is apparently not used and no test methods is defined. I also fixed a couple of methods: - Collection>>openPlot for example was not working. I added an example in ESExample. - #openPlotWith: is cool, but why the two curves are black? Why not having one black and one red? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 3 months

keymapping

by Tudor Girba

Hi Guille, We recently added Keymapping to the Moose distribution (actually part of Glamour), but it seems that it breaks the image in subtle ways: - Ctrl+v and Cmd+v lead to different behaviour - pasting a piece of code leaves the cursor at the beginning of the pasted text Do you happen to have time to look into these? Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

13 years, 3 months

← Newer
1
...
10
11
12
13
14
15
16
17
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev December 2011