Moose-dev March 2013

moose-dev@list.inf.unibe.ch

28 participants
207 discussions

Start a nNew thread

Jenkins build became unstable: moose-latest-dev-4.8 #125

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/125/>

11 years, 9 months

Issue 921 in moose-technology: TextPresentation should override default shortcuts

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-High Component-Glamour Milestone-4.8 New issue 921 by tu...(a)tudorgirba.com: TextPresentation should override default shortcuts http://code.google.com/p/moose-technology/issues/detail?id=921 For example: composite := GLMCompositePresentation new. composite wrapper show: [ :a | a text act: #inspect on: $d entitled: 'Inspect'; act: #inspect on: $a entitled: 'Inspect'; act: #inspect on: $s entitled: 'Inspect' ]. composite openOn: '123' It works in Pharo 1.4, but not in Pharo 2.0. The reason is due to the hack that worked only in Pharo 1.4. Perhaps we need to properly use Keymapping -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

11 years, 9 months

one-to-one links with FAME

by Usman Bhatti

Hello, Does FAME allow to create one-to-one relationship with automatic update of the back links? So far, I have seen two entities FMMultivalueLink (one-to-many) and FMMultiMultivalueLink (many-to-many) and their examples. I have an elements and its behavior in separate entities and I would like to create and update one-to-one links between these two entities. I haven't found any example in Moose. tx, Usman

11 years, 9 months

pharo and moose

by Haroldo Stenger

hi! I'm totally new to smalltalk, although I've heard of it since a lot of time ago. In my arch linux installation, I've found some dificulties running squeak, so I went into pharo once I've discovered they are two free implementations of smalltalk. Then I wondered myself, How can I do now to put moose into here ? And then I saw that by selecting the proper text in one of the default windows that pharo opens for me, I could have moose (and other subsystems) installed in the image I'm workin on. So I did. I've found myself pretty impressed at the ease by which the subsystems get installed. I started installing one of the web development systems, and I got thru the whole automated process without any problems. Then I evaluated the code that installs moose. It started running, and run a lot without a problem too. But at some point, some missing methods poped up a window in which I'm asked what to do. At the firsts of them, I put 'proceed' (because I wouldn't abandon, nor debug because I woudn't know what to do), and it proceeded. At some later pop up errors, I was offered a fourth option namely 'create', I did, and put the method I was asked to put somewhere in systembase or some similar name (I can be more precise if needed or asked to), then a code that showed a 'to be implemented' dummy method or something, and then again, asked to proceed, and and did this process a number of times, until I realized that there were many of them, and I abadoned. And went here, asking for some kind help of you. I could insist with squeak if that would do better, or go Cuis alternatively (but from what I've read, maybe Cuis would not fit). I've also read that pharo support from moose is in some development phase. Is that true? So if I'm a beginner I should try it until it's ready. I'm interested in moose mainly, and derived from this, in smalltalk and in any of its free versions if they work. Any hint is welcome. cheers Haroldo

11 years, 9 months

pharo 2.0 vs pharo 3.0

by Tudor Girba

Hi, Moose 4.8 works on Pharo 2.0. The only problem I noticed is that CMD+s does not work in the text areas anymore. So, before we start doing major things (such as removing Mondrian, redoing EyeSee on top of Roassal, adding Athens support, adding Traits into FAMIX, or enhancing GToolkit), I have a little proposition. After a bit more testing I would like to release 4.8, and then move Moose 5.0 to Pharo 3.0 as soon as possible. Here is why: - Moose can benefit from enhancements from Pharo, and we can only influence and contribute if we work closely with the Pharo latest version - Moose should offer tools for Pharo development - We are a small community that should work more closely together What do you think? (If you disagree, please also indicate the amount of effort you would like to invest in Moose in the near future) Cheers, Doru -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

11 years, 9 months

moose with athens

by Tudor Girba

Hi, Given that we want to adopt Athens in the near future, I put together a job that builds Athens on top of Moose: https://ci.inria.fr/moose/job/moose-latest-dev-extras/ Expect this experimental image to grow a bit once Bifrost will be ported to 2.0. Cheers, Doru -- www.tudorgirba.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."

11 years, 9 months

Issue 845 in moose-technology: some Roassal layouts broken when nested

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 845 by google....(a)ben.coman.com.au: some Roassal layouts broken when nested http://code.google.com/p/moose-technology/issues/detail?id=845 The application I am developing needs to apply layouts to nested elements. I noticed that some layouts did not work when nested - so I've done a full review of the layout listed in ROMondrianExample>>chooseLayoutOn: as per the attached image. On the left is the non-nested-result and on the right is the nested-result. I have attached the mcz with a slightly modified #chooseLayoutOn: as well as #chooseLayoutNestedOn: for comparison. Attachments: Roassal-BenComan.313.mcz 241 KB ROMondrianExample-chooseLayoutNestedOn.png 127 KB

11 years, 9 months

Did anyone ever look at the slang/c code with Moose?

by Stephan Eggermont

>From lurking at the vm-dev list, it looks like there are quite a lot of problems in the vm that could be solved by doing some humane assessment. Was Moose ever used on the vm? Stephan

11 years, 9 months

migrated...

by Stéphane Ducasse

Hi guys I migrated XMLParser, XMLWriter, Pastell to SmalltalkHub and revisited their complete configurations. Now I will do the same for OPAX. After I will suggest to put OPAX in readonly and to mention it on the squeaksource web site. Stef

11 years, 9 months

improved ci

by Tudor Girba

Hi, Over the past week I worked on strengthening the new Jenkins infrastructure: - created multiple jobs for Moose subprojects like Fame, Glamour or PetitParser. We should continue to create such jobs for all projects. - Made the jobs to react on commits to the respective repositories, and to trigger the full Moose build. Like this we both ensure that every individual project is loadable as standalone, and we ensure that the integration tests are run after every commit. - created shortcuts: ci.moosetechnology.org -> https://ci.inria.fr/moose/ ci.moosetechnology.org//moose-latest-dev.zip -> https://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/arti… Cheers, Doru -- www.tudorgirba.com "To utilize feedback, you first have to acquire it."

11 years, 9 months

← Newer
1
...
8
9
10
11
12
13
14
...
21
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev March 2013