Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

Broken examples (GLMExamplesBrowser) issue 16111

by Nicolai Hess

I think some examples in GLMExamplesBrowser In Pharo5.0 are broken. see fogbugz issue "16111 Collections being passed as a whole into blocks, instead of each individual object" The confusion about "display-block" and "format-block" is sorted out, so we could close the issue. But it seems the examples "Updateable browser" "Validating presentation" are broken (and maybe the Magritte example, but I don't know where it is).

9 years, 2 months

Syntax highlighting is missing in Playground and examples

by Alexandre Bergel

Hi! I see there is a great battle involving Rubric and all its friends is taking place. When I browse an example, I do not have the syntax highlighting. I am using the last version of Moose. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 2 months

Problem when debugging

by Alexandre Bergel

Hi! I have apparently some problem when I debug some methods. See the attached screenshot. I can share the image if necessary. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 3 months

Mailing list address change?

by Blondeau Vincent

Hi, I just wanted to know why the address of the mailing list changed from moose-dev(a)iam.unibe.ch<mailto:moose-dev@iam.unibe.ch> to moose-dev(a)list.inf.unibe.ch<mailto:moose-dev@list.inf.unibe.ch>. Which one should be used? Thanks in advance, Vincent ________________________________ Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

9 years, 3 months

PetitSQL fix

by stephan

Name: ConfigurationOfPetitSQLParser-StephanEggermont.28 Author: StephanEggermont Time: 11 October 2015, 2:05:48.838156 pm UUID: c6bd1590-d850-4a25-9f75-b22b42c73944 Ancestors: ConfigurationOfPetitSQLParser-AndreiChis.27 Fix symbolic version to use the right baseline in Pharo5

9 years, 3 months

Missing mcz versions

by Stephan Eggermont

Projects that load packages using Metacello, tend not to look in Pharo50 and Pharo50Inbox for new versions of those packages. I noticed the Rubric version in Moose 6 to be significantly behind the one in Pharo 5... Can we automatically copy back the inbox/integrator version to its repo? Stephan

9 years, 3 months

HashTable version fix

by stephan

Name: ConfigurationOfHashTable-StephanEggermont.13 Author: StephanEggermont Time: 10 October 2015, 9:03:03.070153 pm UUID: 6b5ec7a8-d07e-4672-94c9-748750e30a78 Ancestors: ConfigurationOfHashTable-StephanEggermont.12 #stable needs to be 2.0 for Pharo 5

9 years, 3 months

pharo5 and ConfigurationOfMagritteGlamourForPharo40

by Andrei Chis

Hi, In the latest moose image ConfigurationOfMagritteGlamourForPharo40 hides the latest versions for some packages. For example it loads Glamour-Morphic-Renderer.issue_1126-SeanDeNigris.325 instead of the latest version Glamour-Morphic-Renderer-MarcusDenker.326. Did something changed these days? Cheers, Andrei

9 years, 3 months

Magritte updates

by stephan

Name: ConfigurationOfMagritte3-StephanEggermont.118 Author: StephanEggermont Time: 10 October 2015, 9:09:24.252164 pm UUID: 5d39ab33-c062-4754-ad55-4feb4b59199d Ancestors: ConfigurationOfMagritte3-StephanEggermont.117 Update Grease to stable version #'release1.2' is version 3.5.0 Name: ConfigurationOfMagritte3-StephanEggermont.117 Author: StephanEggermont Time: 10 October 2015, 5:56:07.098168 pm UUID: e61105b7-4521-4428-9881-795f10251beb Ancestors: ConfigurationOfMagritte3-SeanDeNigris.116 In place change: block with MagritteGlamourForPharo40 only for Pharo 4.

9 years, 3 months

stackedVerticallyArrangement vs. two separate panes

by Sean P. DeNigris

I want to have two presentations stacked vertically, which present different aspects of the same object. I used `a stackedVerticallyArrangement`, but I want them to be a) different initial sizes and b) have a draggable splitter in between, but this doesn't seem possible. So my questions are: 1. Do I need to use two separate panes? 2. What is the use case for #stackedVerticallyArrangement? I.e. how does it differ from using two panes? Thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/stackedVerticallyArrangement-vs-two-separate-panes-tp… Sent from the Moose mailing list archive at Nabble.com.

9 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev