Moose-dev June 2014

moose-dev@list.inf.unibe.ch

38 participants
138 discussions

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

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

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

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

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

9 years, 10 months

snapshotCello and remooseReloader: ConfigurationOfMoose

by stepharo

9 years, 10 months

did snapshotcello worked on ConfigurationOfMoose?

by Stéphane Ducasse

Hi doru did you succeed to snapshotcello worked on ConfigurationOfMoose? Stef

9 years, 10 months

Roassal 3d Job

by Alexandre Bergel

Hi! Yuriy has set a jenkins job for Roassal 3d > https://ci.inria.fr/moose/job/Roassal3d/ Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 10 months

Event handling in CodeCity

by Yuriy Tymchuk

Hi, as far as I understand at the moment we can only react to node being selected or unselected. I wander if it won't be able to announce events like left click, right click, hover and so on. I think that it will be interesting to be able to hover over an entity and see it's name somewhere. If the idea is fine, where should I look to implement it? Uko Sent from my iPhone

9 years, 10 months

Handling uniform values in Normalizers

by Yuriy Tymchuk

Hi, I encountered a problem in CodeCite that arises when you are using ColorNormalizer and all values are the same (so you cannot scale anything). Is there a standard way to handle that, or I need implement something myself? Uko

9 years, 10 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev June 2014