Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Re: [Metacello] specific problem when loading a nested configuration
by Dale Henrichs 11 Dec '09

11 Dec '09

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? 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."

2 1

Re: [Metacello] specific problem when loading a nested configuration
by Dale Henrichs 11 Dec '09

11 Dec '09

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."

3 2

loading Moose in latest Pharo-Dev
by Johan Brichau 11 Dec '09

11 Dec '09

Hi Moosers, I just loaded Moose in the latest Pharo-Dev using the script on your website but I got a bunch of unloadable definitions: This package depends on the following classes: MorphTreeModel MorphTreeColumn MorphTreeNodeModel I did a proceed and obviously, Moose Finder does not open :-( Can you help me out ? ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

3 6

Re: [Metacello] specific problem when loading a nested configuration
by Dale Henrichs 11 Dec '09

11 Dec '09

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."

1 0

specific problem when loading a nested configuration
by Tudor Girba 11 Dec '09

11 Dec '09

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."

3 4

Glamour default examples hanging Pharo
by Johan Fabry 11 Dec '09

11 Dec '09

Hi, all, something that is a major inconvenience: with todays default configuration of moose, a bunch of glamour basic examples hang Pharo. I submitted a bugreport: http://code.google.com/p/moose-technology/issues/detail?id=258 that uses one case but there are many more. Select something in a list and the image hangs. A bit of a shame, I wanted to play around with Glamour to implement the control panel for AspectMaps, but now I cannot do anything at all :-( -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

3 7

Mondrian-Alexandre_Bergel.302
by Alexandre Bergel 10 Dec '09

10 Dec '09

The comment of this version says: -=-=-=-=-=-=-=-=-=-=-=-= This version contains a number of important refactorings and improvement: - MOGraphElement.children has been renamed into MOGraphElement.nodes - allChildrenDo: -> allNodesDo: - added a method MOGraphElement>>handleException: that handle error. Normally, an image should not freeze when rendering an erroneous Mondrian script. - Bug fixed in MOGraphElement>>elementAt:ifAbsent: This solve the ISSUE #193. A test has been added: MOViewRendererTest>>testEdgeContainsPointWithEdges - recagorization of methods in MOArrowedOrthoVerticalLineShape - Bug fixed in MOLineShape>>containsPoint:for: This solved the ISSUE #249. The problem stems from using CurvedLine. I added a test MOViewRendererTest>>testEdgeContainsPointCurveFitter for this - Added a safeguard in MOAnnouncer>>popupText: All 164 Test methods are green! -=-=-=-=-=-=-=-=-=-=-=-= Doru, I wanted to do a merge with tg.296, but you redefined MOSplineShape>>display:on: and I provide a new version of this method (I refactored some part). Maybe you want to do the merging of this method. I can do it if you want. I am now updating the corresponding issues in code.google.com Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

5 8

[infusion] Importing calls from static context
by Simon Denier 10 Dec '09

10 Dec '09

Hi there the infusion team I would like to know if/how inFusion handles calls in static block in Java. I can not find such invocations in a model. Would it be complicated to add them? I have the following sample: class KeyMapping { static final KeyMapping keyMapping1 = new KeyMapping(KeyEvent.VK_LEFT, KeyEvent.VK_RIGHT, KeyEvent.VK_UP, KeyEvent.VK_SPACE); static final KeyMapping keyMapping2 = new KeyMapping(KeyEvent.VK_X, KeyEvent.VK_V, KeyEvent.VK_D, KeyEvent.VK_ALT); int left, right, thrust, fire; KeyMapping(int k_left, int k_right, int k_thrust, int k_fire) { left = k_left; right = k_right; thrust = k_thrust; fire = k_fire; } } -- Simon

2 1

Review long-term goals / milestones etc
by Simon Denier 07 Dec '09

07 Dec '09

So now that we have discussed a bit more how to use the bug tracker, what about these two other pages. http://code.google.com/p/moose-technology/wiki/improveMooseTaksList http://code.google.com/p/moose-technology/wiki/PhamooseRoadmap They should at least be merged together, cleaned from some items, and some items could be pushed in the issue tracker perhaps. I will create a page describing the HowToIssue. -- Simon

4 6

Re: [Metacello] Re: Branch blessing and lastVersion
by Dale Henrichs 05 Dec '09

05 Dec '09

Stef, I tend to agree, but you want it fairly obvious to the end user that they are wandering onto the bleeding edge when using nano versions:) For example, by default, Metacello would filter out nano versions... Dale ----- "stephane ducasse" <stephane.ducasse(a)gmail.com> wrote: | simon my gut feeling is telling me that four level is too complex. | | Stef | | On Dec 5, 2009, at 5:07 PM, Simon Denier wrote: | | > | > | > Thinking again about the dev process specifically in Moose (not | subprojects such as CAnalyzer, Mondrian...), branches for developer | should be 'nano' releases actually, that is: | > - 4 is a major release of Moose | > - 4.1 is a minor release, but still something consistent | > - 4.2.x should be for release in the main trunk, i.e. mostly dev and | beta version before releasing a minor release (would be 4.2) | > - 4.2.x.y is a branch of one developer (something short-lived, | typically for a task resolution, once finished should be merged in | main trunk) | > | > We could also follow the linux rule: | > - 4.1, 4.1.1, 4.1.1.1 are the dev versions for the future 4.2 stable | releases | > - 4.2, 4.2.1 etc are minor and micro releases but stable, with bug | fixes | > i.e. minor is odd -> dev version, minor is even -> stable version | > This does not mean we work on two versions in parallel (we dont have | the manpower), but it just to help distinguish between dev and stable | versions | > | > I'm just pushing ideas out of my head. Now, with this process, we | have three main requirements for Moose: | > - making it easy for anybody to retrieve (and identify it) the | latest stable version | > - making integration in the main dev trunk the priority (we have | limited resources, so each developer should take care to merge its | changes in the main trunk, and start over from the main trunk for a | new task, NOT always working in the same branches) | > - managing micro/nano releases from each developer | > | > I'm sorry if this feels too complicated and overly complex, it is | not. I'm just playing with different schemas and see what could work | best. | > | > | ----------------------------------------------------------------------------------------------------------------------------- | > Now of course Metacello should not care about conventions (minor, | micro...) of each project. Your proposition seems reasonable and | flexible enough. | > | > But then, how can I ask for a version with a specific blessing? | > | > | > | > On 4 déc. 2009, at 18:48, Dale Henrichs wrote: | > | >> | >> Thinking off the top of my head, would it be work to supply a | pattern of some sort as an arg? Something like: | >> | >> ConfigurationOfXXX project lastVersion: '*.*' | >> | >> Not a real regex (because of the periods would need to be escaped, | but mainly because reading regex for me is like trying to read | russian:). | >> | >> Maybe best is a special purpose character like '#' in addition to | the standard(?) smalltalk patterns '*' and '?': | >> | >> ConfigurationOfXXX project lastVersion: '#.#' ---> matches all | major.minor | >> ConfigurationOfXXX project lastVersion: '1.#' ---> matches all | 1.minor | >> ConfigurationOfXXX project lastVersion: '*' ---> is current | algorithm | >> ConfigurationOfXXX project lastVersion: '*.0' ---> matches | versions with trailing .0 | >> ConfigurationOfXXX project lastVersion: '?.#' ---> matches single | character major.minor | > | > I dont see what is the use of this one? | > | > | > | >> ConfigurationOfXXX project lastVersion: '1.#.3' ---> is invalid | >> | >> This one seems to the right approach ... I can add a #match: method | to MetacelloVersionNumber to implement the pattern matching. | >> | >> What do you think? | >> | >> Dale | >> | >> ----- "Simon Denier" <Simon.Denier(a)inria.fr> wrote: | >> | >> | Suppose I have versions like this: | >> | 1.3.2 #development --> branch by a developer | >> | 1.3.1 #development --> branch by a developer | >> | 1.3 #development --> main trunk, last dev | >> | 1.2 #stable --> main trunk, last stable | >> | | >> | When I perform a ConfigurationOfXXX project lastVersion, I would | like | >> | | >> | to retrieve the config for the last dev version common to | everybody, | >> | | >> | and I would like this to be 1.3, not 1.3.2 which is the work of | one | >> | guy not yet merged in the main trunk. | >> | | >> | Right now, I get 1.3.2 | >> | | >> | Perhaps we could have something like this: | >> | 1.3.2 #branch --> branch by a developer | >> | 1.3.1 #branch --> branch by a developer | >> | 1.3 #development --> main trunk, last dev | >> | 1.2 #stable --> main trunk, last stable | >> | | >> | and branch would be an 'unstable' tag ignored by the loader when | >> | asking for latestVersion or lastVersion (and veryLastVersion | could | >> | retrieve the latest version, be it a branch, dev, or stable). | >> | | >> | I have no special requirements here, I'm just playing with the | idea | >> | and process of how to manage micro releases with Metacello. | >> | | >> | -- | >> | Simon | > | > -- | > Simon | > | > | >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev