Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Alexandre Bergel

Hi! I do not see it on: http://www.intooitus.com Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 7 months

Re: [Pharo-users] Creating a custom visualization for analyzing a legacy Delphi application in 15 min.

by Tudor Girba

Nice! Doru On Fri, Sep 11, 2015 at 9:11 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > 15 minutes should be enough to create a custom tool, > helping me gain insight in my problem. > Moose (and Pharo) delivers. > > > https://vimeo.com/139004257 > > Stephan > > A big thank you to the GT & Roassal crew > > > -- www.tudorgirba.com "Every thing has its own flow"

9 years, 7 months

Creating a custom visualization for analyzing a legacy Delphi application in 15 min.

by Stephan Eggermont

15 minutes should be enough to create a custom tool, helping me gain insight in my problem. Moose delivers. https://vimeo.com/139004257 Stephan A big thank you to the GT & Roassal crew

9 years, 7 months

Moose build incomplete

by stephan

In Build 366 a working version of GT-InspectorExtensions-CoreRoassal is missing. That makes it difficult to demo Roassal :) Stephan

9 years, 7 months

dynamic actions not displayed correctly

by Usman Bhatti

When dynamic actions are displayed between two presentations, they are not displayed at all. Here is a snippet to reproduce this problem. I've committed a fix in the Moose51 repo. browser := GLMTabulator new. browser row: #one; row: #two. browser transmit to: #one; andShow: [ :a | a tree display:[ :x| 1 to: x ] ]. browser transmit to: #two; andShow: [ :a | a tree display: #(a b c); filterOn: [ :text :each | each name includesSubstring: text ]; dynamicActions: [ :list | {GLMGenericAction new action: [ ]; title: 'Action'; icon: GLMUIThemeExtraIcons glamorousBrowse; yourself} ]]. ^ browser openOn: 5

9 years, 7 months

roassal problem: ellipse border color does not work

by Tudor Girba

Hi, The ellipse border color does not seem to work. Is this an Athens problem, or just a missing implementation? Could someone take a look? For example: view := RTMondrian new. view shape ellipse borderColor: Color red. view nodes: #( 1 2 3 ). view Produces: [image: Inline image 1] Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

9 years, 7 months

moosetech github

by Usman Bhatti

hi, Could someone please add me to the moosetechnology project in github, I would like to add one or two issues? tx.

9 years, 7 months

[ann] brick on top of bloc - preview

by Tudor Girba

Hi, We are happy to announce the first preview version of Brick, a new widget set created from scratch on top of Bloc. Brick is being developed primarily by Alex Syrel (together with Alain Plantec, Andrei Chis and myself), and the work is sponsored by ESUG. Brick is part of the Glamorous Toolkit effort and will provide the basis for the new versions of the development tools. Brick's goal is to provide a beautiful looking widget set, and the default look is based on material design. The widgets are theme-able. Right now, there exists: - Label - Simple button - Toggle button - Checkbox - Radio button - Window with or without an active title bar that can include various visual actions and info - Menu - Beautiful scrollbars that are thin by default and enlarge when the mouse hovers over it - Scalable list for huge amounts of items with various heights (The list also allows one for embedding text widgets with in place editing) The next immediate target is the creation of a new Pager widget (the widget that is behind the current GTInspector). You can see some screenshots on the official site: http://gt.moosetechnology.org/brick To play with it, you can download a ready-made image: https://ci.inria.fr/moose/job/gtoolkit5/lastSuccessfulBuild/artifact/gtoolk… and, in a Bloc space, you can browse the examples: BrExampleBrowser exampleOpen We would be happy to hear your feedback. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

9 years, 7 months

extending FAMIX meta-model and annotations

by Peter Uhnák

Hi, I'm getting acquainted more with Moose and FAMIX and I am not really sure how to proceed (mostly due to lack of documentation and link rot). What I want to do is add "multiplicity" attribute to FAMIXAttribute. Now I see an option: 1) create a subclass of FAMIXAttribute 2) add a method.. something like FAMIXAttribute>>multiplicity <MSEProperty: #multiplicity type: #MyFAMIXMultiplicity> ^ multiplicity now Moose can generate models from smalltalk source code and I would like to infer this information. For example for types, there is MooseImportingContext>>computeTypeOfAttributes So I'm assuming I would have to do something similar. And finally, if I want to help the importer and actually write that information into the source code, I would have to add another pragma there... something like MyClass>>myAttribute <MSEMultiplicity: '2..*' type: MyType> ^ myAttribute and then modify the smalltalk importer to be able to recognize this and produce MyFAMIXAttribute instead of the default one. Am I on the right track? Should it be done differently? Any pointers appreciated, Peter

9 years, 7 months

rubric presentation and text color attributes

by Usman Bhatti

Hi, There seems to be a problem with simple the rubric presentation in Moose 5.0. TextColor attributes are overridden with default text color from the theme when the morph is created. There is a flag in the morph creation code that says that the code needs reviewing in Pharo 4.0. So removing two lines below after the flag resolve this issue: GLMMorphicRubricTextRenderer>>morph |morph| morph := RubScrolledTextMorph new getSelectionSelector: #primarySelectionInterval; model: textModel; color: Smalltalk ui theme backgroundColor; textFont: StandardFonts defaultFont; yourself. self flag: 'Temporary solution until Moose moves to Pharo 4'. (Smalltalk ui theme class canPerform: #textColor) ifTrue: [ morph textColor: Smalltalk ui theme textColor ]. ^ morph Should I commit a fix removing the flagged lines? Should I create a new branch for the fix?

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