Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

Start a nNew thread

test

by stepharo

10 years, 6 months

Can we get playground not hidding the old workspace?

by stepharo

Hi guys Can we get playground not hidding the old workspace? The textselection is awfull. Why do we sacrifice what is working in Pharo? Some keybindings are not working, registerToolsOn: registry "Add ourselves to registry. See [Smalltalk tools]" "self registerToolsOn: Smalltalk tools" registry register: self as: #playground SmalltalkImage current resetTools is broken on Moose :( Great! Then why the syntax highlithging does not support correctly the display of incomplete class names and selector? I will really consider to ask the rmod team to make its own Moose build with decent default because this is each time the same story instead of having the time to fix a problem (snapshotcello is not working with latest moose then I lose times to fix the system to work as good as the default pharo). Stef

10 years, 6 months

tyring to unload Playground breaks Moose :(

by Stéphane Ducasse

So now I’m stuck. I really start to hate this situation. Stef

10 years, 6 months

Inti demo

by milton mamani

Hi, I've been working on Inti, you can watch a simple demo of this. https://vimeo.com/98760520 Best regards, Milton

10 years, 6 months

Moose debugger/inspector error

by Juraj Kubelka

Hi, I have regularly a problem when exploring things in debugger/inspector. It raise an error. Here is the captured video: https://dl.dropboxusercontent.com/u/710942/pharo/moose-debugger-error.mov It says errorSubscriptBounds: for MethodContext>>tempAt: Is it known error? Can I avoid it? Thanks, Juraj

10 years, 6 months

why playground does not support the default text selection?

by Stéphane Ducasse

normally we can select an expression just by clicking on the start or end of a string. With playground it does not work and this is annoying. Stef

10 years, 6 months

snapshotcello ConfigurationOfMoose problems

by Stéphane Ducasse

Hi guys Snapshotcello and MooseReloader fails on ((ConfigurationOfMoose project version: #development) ignoreImage: true; record) It takes ages. Can somebody confirm that this is the same problem? Stef

10 years, 6 months

Polygon shape in Roassal 2

by Natalia Tymchuk

Hello, everyone. I'm working on a builder for Voronoi diagram. Is there something which can help me to build the polygon shape for the element in Roassal 2 ? Thank you. Best regards, Natalia

10 years, 6 months

CodeCity and Roassal3d

by Yuriy Tymchuk

My dear friends, this may be an ugly question, but why CodeCity and Roassal3d are not cooperating. Maybe I’m just not able to see the significant differences, but for me as 3rd person it seems that Roassal3d is missing concrete functionality, like CodeCity’s awesome builder, and CodeCity is missing event handling, translucent colors, etc… Maybe we can merge efforts? Uko

10 years, 6 months

Re: did snapshotcello worked on ConfigurationOfMoose?

by Stephan Eggermont

Snapshotcello is currently only partially useable for managing Moose versions. It provides a snapshot of the loaded versions of all packages, but doesn't know to which groups & projects they belong. By flattening that data, further development becomes practically impossible. We notice that when bug fixes no longer get propagated, or the number of snapshots gets impractically large. A new snapshot would be needed for each fix in each of the dependencies. I consider storing snapshots in a configuration not a good idea. A flattened snapshot is fine for producing a reproducible load, and is valuable as a separate object. In Seaside we noticed that referring to versions as #stable and #development is not enough, we need to make explicit that it is the stable #release3 #release3.0 or #release3.1. Bugs are fixed in those releases, and no APIs are changed in 3.0/3.1. Referring to #stable of Seaside in your configuration is a potential bug, as it will lead to a different version, with a different API, getting loaded when Seaside 3.2 is released. I expect most projects will be better off separating bug fixes from feature development. Stephan

10 years, 6 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