Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Re: Configuration for Roassal 3D
by Stephan Eggermont 19 Dec '13

19 Dec '13

Ronie wrote: >It could be due to the changes I made to NBOpenGL. Stephan, do you see an error about bindFramebuffer?. Yep. And NBOpenGL stuff looks outdated. >In that case, we should update the configuration of Roassal 3D to use the latest version of NBOpenGL. Yes, please do. Stephan

3 3

moose day summary
by Tudor Girba 19 Dec '13

19 Dec '13

Hi, I hear the Moose Day was dynamic and interesting. I am happy to see the community is alive. What were the high points? It would be great to get a summary posted somewhere (e.g., here, on the website, on the moose news). Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

1 0

Re: Configuration for Roassal 3D
by Stephan Eggermont 19 Dec '13

19 Dec '13

#stable doesn't work. #bleedingEdge neither Stephan

2 1

Presenting at FOSDEM?
by Stephan Eggermont 19 Dec '13

19 Dec '13

Hi all, Perhaps one or more of the mooseday presentations would be nice at our Fosdem smalltalk devroom. Please let me know. Stephan

1 0

MooseDay on Twitter
by Alexandre Bergel 19 Dec '13

19 Dec '13

It is now running. Find us on Twitter: #moose Schedule: 10h: welcome 10h30: APIEvolutionMiner - Andre Hora 11h: FamixDiff - Nicolas Anquetil 11h30: Orion - Jannik Laval and Anne Etien 12h: Lunch offered by ESUG. 14h: First works on Version - Yuriy Tymchuk 14h30: Roassal - Alexandre Bergel 15h-15h30 break 15h30: GraphET - Alexandre Bergel 16h: Use of GraphET - Serge Stinckwich 16h30: Around tests - Alain Plantec -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

GTDebugger and Glamour easels
by Alexandre Bergel 19 Dec '13

19 Dec '13

Hi! I have spotted an important bug. If I enter the following in the Glamour Roassal easel: view nodes: (1 to: 20). self halt. A debugger is open, but I cannot step in. Apparently the code source is not accessible. This is a major regression... https://code.google.com/p/moose-technology/issues/detail?id=1034 Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

MooseDay schedule
by Anne Etien 18 Dec '13

18 Dec '13

Hi, Please find bellow the schedule of the MooseDay. The idea is really to present works developed on top of (or around) Moose and to have fruitful discussions. So I planned 30 mn per topic, but the schedule is quite flexible. Lot of time is foreseen for discussions. 10h: welcome 10h30: APIEvolutionMiner - Andre Hora 11h: FamixDiff - Nicolas Anquetil 11h30: Orion - Jannik Laval and Anne Etien 12h: Lunch offered by ESUG. 14h: First works on Version - Yuriy Tymchuk 14h30: Roassal - Alexandre Bergel 15h-15h30 break 15h30: GraphET - Alexandre Bergel 16h: Use of GraphET - Serge Stinckwich 16h30: Around tests - Alain Plantec Reminder, the MooseDay will take place in Inria B building room B31. Directions to come can be found there (http://www.inria.fr/en/centre/lille/overview/locations). See you next week in Lille ;o) Anne

6 8

Issue 900 in moose-technology: Glamour-Roassal should be able to work with raw ROView not just ROMondrianBuilder
by moose-technology＠googlecode.com 18 Dec '13

18 Dec '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 900 by benjamin...(a)gmail.com: Glamour-Roassal should be able to work with raw ROView not just ROMondrianBuilder http://code.google.com/p/moose-technology/issues/detail?id=900 Hopefully, I've cracked this. In response to my own query: "Could something like a GLMMorphicRoassalRawRenderer be added to the Glamour-Roassal interface? - which would pass an unencumbered ROView to the paintingBlock. It is not really a Glamour-Roassal interface at the moment, more of a Glamour-Mondrian interface." With the attached slice you can now go... browser transmit to: #graphic andShow: [ :a | a roassal newView: [ ROView new @ RODraggable ] ; painting: [:view :input | view add: ROElement new] ]. After loading you can first try the new & old tests in 'Glamour-Tests-Roassal' then try 'GLMRawRoassalExamplesBrowser open' I surprised myself that I got this far. A few times I hit a brick wall and was going to submit a half done proof-of-concept, but then just kept digging. Apart from hopefully getting integrated, some critical feedback would appreciated. A few points for review... 1. I had considered using #viewPrototype: with an instance to copy, but then I wasn't sure how deep I should copy it to produce a new view. So using a block with newView: seemed the safer path (and it also feels like it opens up some interesting possibilities, even if I can't think what they are at the moment) 2. I noticed that GLMRoassalPresentation>>renderOn: had a flag 'This should be the responsibility of the view'. This method was one that I previously copied and modified for GLMRoassalRawPresentation in my "Interactive Roassal" experiment. There I removed the calls to #applyLayout and #populateMenuOn since these were MNU for ROView (which had replaced ROMondrianViewBuilder). This time I pushed these two calls into ROMondrianViewBuilder>>preOpen, where ROView>>preOpen is left empty. I'm note sure I'm happy with #preOpen as a name but it was the best I could come up with, since I also refactored ROMondrianViewBuilder>>open to use it. 3. GLMMorphicRoassalRenderer>>render: had hardcoded reference to #stack with "ROMorph on: view stack" so I pushed the required difference into ROMondrianBuilder>>newMorph and ROView>>newMorph. 4. GLMMorphicRoassalRenderer>>actOnPresentationUpdate had hardcoded use of #stack in "setView: aView stack" so I pushed that into ROMondrianViewBuilder>>onMorph: and ROView>>onMorph: 5. GLMMorphicRoassalRenderer>>actOnPresentationUpdate had hardcoded ROMondrianViewBuilder so I modified this to use the block passed to GLMRoassalPresentation>>newView: . 6. I copied GLMRoassalMorphicTest to GLMRawRoassalMorphicTest with required modifications. 7. I copied GLMRoassalExamplesBrowser to GLMRawRoassalExamplesBrowser with required modifications.

5 18

Build failed in Jenkins: moose-5.0 #372
by admin＠moosetechnology.org 18 Dec '13

18 Dec '13

1 0

Jenkins build became unstable: moose-5.0 #360
by admin＠moosetechnology.org 18 Dec '13

18 Dec '13

See <https://ci.inria.fr/moose/job/moose-5.0/360/>

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev