Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Call for Participation in the Smalltalk Devroom at FOSDEM 2012.
by Stephan Eggermont 07 Dec '11

07 Dec '11

Call for Participation in the Smalltalk Devroom at FOSDEM 2012. "A devroom for the Pharo, Squeak, GST, Etoilé, Seaside, Moose Smalltalk projects. Smalltalk environments offer a very high development productivity, unmatched by their successors. Come do some pair programming with us and experience the advantages of a real OO environment." The meetup will take place Sunday, February 5, 2012, from 9AM until 5PM, room AW1.126. This room has 72 seats, a VGA video projector and wireless internet. More information will be available later. Proposals on content and format are welcome. People interested in running a session should announce that on the smalltalk-devroom mailing list, with the following information: - Their name - The project they are associated with - A short bio, to be put on the website along with their speaker name - (optionally) a picture of themselves - The title of their session (which will go on the website and in the booklet) - A abstract describing the session in further detail. - The desired length of the session. - The desired time slot in which they want to hold the session. Suggested values for the duration are 55min, 25min, 6m40 (Pecha Kucha). The desired time slot is meant to help you prevent conflicts with other dev rooms in which you might have a talk or your travel arrangements. The deadline for submissions is December 31, 23:00 GMT+1. Discussion takes place on the smalltalk-devroom(a)lists.fosdem.org mailing list. Please subscribe if you are interested: https://lists.fosdem.org/listinfo/smalltalk-devroom The local VUB/ULB Smalltalkers have been asked to organize a sprint/BSUG meeting on Saturday Februari 4. Devroom related URLs: http://www.pharo-project.org http://www.squeak.org/ http://etoileos.com/ http://www.seaside.st/ http://smalltalk.gnu.org/ Please distribute

1 0

Fwd: Build failed in Jenkins: moose-latest-dev #735
by Tudor Girba 07 Dec '11

07 Dec '11

Hi Lukas, I saw that you worked on the Petit refactorings. This is cool, but you seem to have committed a wrong superclass: AnObsoleteRefactoring subclass: #PPGrammarRefactoring Do you have time to fix it? Cheers, Doru Begin forwarded message: > From: admin(a)moosetechnology.org > Subject: Build failed in Jenkins: moose-latest-dev #735 > Date: 7 December 2011 22:13:31 CET > To: tudor(a)tudorgirba.com, simon.denier(a)gmail.com, cy.delaunay(a)gmail.com, alexandre(a)bergel.eu, stephane.ducasse(a)inria.fr, jannik.laval(a)gmail.com > > See <http://hudson.moosetechnology.org/job/moose-latest-dev/735/> > > ------------------------------------------ > Started by timer > [workspace] $ /bin/sh -xe /tmp/hudson2362877769901627270.sh > + rm -rf <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose> <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose-tests> <http://hudson.moosetechnology.org/job/moose-latest-dev/735/artifact/moose_s…> > + /srv/hudson.moosetechnology.org/builder/build.sh -i Pharo-1.3 -s moose -s glamorous-theme -s glamorous-toolkit -s moose-clean -s cleanupforrelease -o moose > build.sh: error loading code (/srv/pharo/coglinux2382/squeak) > > *** Warning: Warning: This package depends on the following classes: > AnObsoleteRefactoring > You must resolve these dependencies before you will be able to load these definitions: > PPDefineProdcutionRefactoring > PPDefineProdcutionRefactoring>>checkSource > PPDefineProdcutionRefactoring>>preconditions > PPDefineProdcutionRefactoring>>setSource: > PPDefineProdcutionRefactoring>>sourceRewriter > PPDefineProdcutionRefactoring>>transform > PPGrammarRefactoring > PPGrammarRefactoring>>preconditions > PPGrammarRefactoring>>rootClass > PPGrammarRefactoring>>setClass: > PPRemoveProdcutionRefactoring > PPRemoveProdcutionRefactoring>>preconditions > PPRemoveProdcutionRefactoring>>setProduction: > PPRemoveProdcutionRefactoring>>transform > PPRenameProdcutionRefactoring > PPRenameProdcutionRefactoring>>setNewProduction: > PPRenameProdcutionRefactoring>>setOldProduction: > PPRenameProdcutionRefactoring>>transform > > Recording test results > Archiving artifacts > -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

2 2

Latent Semantic Indexing in Moose?
by Alexandre Bergel 07 Dec '11

07 Dec '11

Hi! Is this supported? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 3

weird cursor behavior by copy/pasting stuff
by Fabrizio Perin 07 Dec '11

07 Dec '11

Hi all, I just download the last Moose build from the server and i notice a weird cursor behavior: If i copy/paste something either in a workspace or into a code browser i find the cursor at the beginning of the pasted code intend of at the end. Is it a Moose related problem? Is it a new pharo feature? Or my image is possessed by the devil? Thanks for any help. Cheers, Fabrizio

2 1

date property
by Nicolas Anquetil 07 Dec '11

07 Dec '11

what would be the pragma to describe a date property in the meta-model? birthDate <MSEProperty: #birthDate type: #???> Number? (representing the date as a timestamp?) nicolas

2 4

wrapping mondrian drawing
by Usman Bhatti 07 Dec '11

07 Dec '11

I am looking for a method which allows wrapping mondrian drawings. That is, the nodes are draw to a certain width (the width of the mondrian window) and whatever comes next, is drawn on the following line. The purpose is to avoid the need to scroll the window. thanx Usman

3 3

integrating sql support
by Tudor Girba 07 Dec '11

07 Dec '11

Hi, Over the past couple of weeks, Fabrizio did a cool job at detaching his work around SQL into PetitSQLite (for parsing) and Famix-SQLite (for importing and modeling). I already used the parsing in a project and it worked nicely on quite complex SQL statements. We will add this to the default Moose configuration. It's a really nice addition. Cheers, Doru p.s. For those that want to have fun with optimizing the grammar, it is still a bit slow so it's a cool case study :) -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

2 1

Issue 760 in moose-technology: UndefinedObject(Object)>>doesNotUnderstand: #attributeKeyFrom:
by moose-technology＠googlecode.com 06 Dec '11

06 Dec '11

Status: New Owner: usman.bh...(a)gmail.com Labels: Type-Defect Priority-Medium New issue 760 by usman.bh...(a)gmail.com: UndefinedObject(Object)>>doesNotUnderstand: #attributeKeyFrom: http://code.google.com/p/moose-technology/issues/detail?id=760 Menssana dashboard reference values cannot be set because message not understood error occurs. The message appears before setting the value. Sometimes, the dialogue for setting the values does appear, but it crashes when a value is entered. how to produce: Right click on an item in Menssana dashboard, click set reference value.

1 1

Issue 756 in moose-technology: Glamour: errors when updating panels
by moose-technology＠googlecode.com 06 Dec '11

06 Dec '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 756 by vuqui...(a)gmail.com: Glamour: errors when updating panels http://code.google.com/p/moose-technology/issues/detail?id=756 * Type-Defect * Component-Mondrian After modifying the data on one panel I update several other panels, that are not necessarily connected together. The data is correctly updated, but not the presentations. Based on the example below: #when: in the second list does not react. * If you start with an empty collection, the list does not appear (ok), then if you add an element the list does not appear either. * if you start with some elements, the list is there, but after removing all the elements the list does not disappear, and instead you have a SubscriptOutOfBounds error because of a tab index Example to reproduce the problem: | browser collection | collection := GLMAnnouncingCollection new. collection add: 1. browser := GLMTabulator new. browser column: #automatic; column: #menu. browser act: [:b | b entity add: (b entity size + 1) ] entitled: 'Add an item in the collection'. browser act: [:b | b entity removeLast ] entitled: 'Remove last item from the collection'. browser act: [:b | b update ] entitled: 'Update complete browser'. browser transmit to: #automatic; andShow: [ :a | a title: 'Updated automatically'. a stackedArrangement. a list title: [:x | 'List: ', x size printString ]; shouldValidate: true; updateOn: GLMItemAdded from: #yourself; updateOn: GLMItemRemoved from: #yourself ]. browser transmit to: #menu; andShow: [ :a | a title: 'Updated via menu'. a list title: 'List'; when:[ :e| e size > 0 ]; act: [:p | p update ] entitled: 'Update'. a text title: 'Text'; act: [:p | p update] entitled: 'Update'. ]. browser openOn: collection

1 3

Issue 645 in moose-technology: we should keep the current selected tab in the moose panel
by moose-technology＠googlecode.com 06 Dec '11

06 Dec '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 645 by cy.delau...(a)gmail.com: we should keep the current selected tab in the moose panel http://code.google.com/p/moose-technology/issues/detail?id=645 In the moose finder, If I click on an entity, I have a new pane that open on the right. In this new pane, if I select any tab, this one should stay selected when I click on other entities

1 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev