May 2014 - Moose-dev - INF Mailman

Re: Issue 995 in moose-technology: Roassal does not export the full PNG / SVG

by moose-technology＠googlecode.com

Updates: Summary: Roassal does not export the full PNG / SVG Comment #6 on issue 995 by tu...(a)tudorgirba.com: Roassal does not export the full PNG / SVG http://code.google.com/p/moose-technology/issues/detail?id=995 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 2 months

1
6
0 / 0

Issue 1067 in moose-technology: MoosePanel panes showing group should be sorted

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1067 by james.fo...(a)gemtalksystems.com: MoosePanel panes showing group should be sorted http://code.google.com/p/moose-technology/issues/detail?id=1067 I can resort them by executing a Smalltalk expression, but the default order should be meaningful rather than random. * Type-Enhancement * Component-MoosePanel -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 2 months

1
3
0 / 0

Issue 1069 in moose-technology: Use self notExistentMetricValue instead of -1 in some metrics of MooseEntities

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1069 by v.blonde...(a)gmail.com: Use self notExistentMetricValue instead of -1 in some metrics of MooseEntities http://code.google.com/p/moose-technology/issues/detail?id=1069 Describe the problem: what do you get? what do you expect? FAMIXBehaviouralEntity, FAMIXType, FAMIXFileAnchor and FAMIXSourceTextAnchor define metrics where -1 is used instead of self notExistentMetricValue. Additional information: platform, context which may impact the problem Moose 5.0 Please fill in the labels with the following information: * Type-Enhancement * Component-Moose-Core -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 2 months

1
2
0 / 0

Issue 1039 in moose-technology: Glamour layout clipping bug

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1039 by ssadams....(a)gmail.com: Glamour layout clipping bug http://code.google.com/p/moose-technology/issues/detail?id=1039 When sizing a presentation row, I noticed the bottom pane extends below the top window bounds and is clipped. browser := GLMTabulator new. browser row:#textField size:30; row: #listField. browser transmit to:#textField; andShow:[:a| a text display:[:x| 'Hello Doru!']]. browser transmit to:#listField; andShow:[:a| a list display:[:x| 1to:200]]. browser openOn: 123 Additional information: platform, context which may impact the problem Pharo 2.0 ConfigurationOfGlamour-TudorGirba.123 * Type-Defect * Component-Glamour -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 2 months

1
3
0 / 0

Issue 757 in moose-technology: Smalltalk completion appears at absolute coordinates, instead of relative ones in Finder

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour New issue 757 by tudor.gi...(a)gmail.com: Smalltalk completion appears at absolute coordinates, instead of relative ones in Finder http://code.google.com/p/moose-technology/issues/detail?id=757 Try this: GLMFinder new show: [:a | a smalltalkCode ]; openOn: ''. and then type "1 as". You will see that the completion appears in the top right of the world, instead of the top right of the text pane. This only happens in the finder, and it is likely due to some problems of transforming coordinates.

9 years, 2 months

2
3
0 / 0

Issue 1037 in moose-technology: Missing context menu in GTDebugger code editor

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium New issue 1037 by kurs....(a)gmail.com: Missing context menu in GTDebugger code editor http://code.google.com/p/moose-technology/issues/detail?id=1037 I really miss the context menu in the gt debugger code editor. It is not consistent with standard editor menu it is not consistent with the browse/inspect context menu in the bottom part of the debugger. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 3 months

1
4
0 / 0

Dark-theme compatibility :)

by Yuriy Tymchuk

Hi everyone, now there is a dark theme for Pharo that I was waiting for a long time. Is it hard to make Moose-related tools be compatible with it? First thing that I noticed is GTInspector background: Cheers Uko

9 years, 3 months

6
21
0 / 0

What are you working on?

by Alexandre Bergel

Hi! It has been very quiet these last few days? Are you busy working on cool projects? What is the name of it? What does it do? I start. We are working on: - a paper on Roassal 3d for ESUG. It will describe some cool visualizations, including a code city-like. Together with Ronie, Milton and Francisco - additional interactions for roassal2, in particular avoiding collision between elements. This is useful when nodes are dynamically added to a canvas. With Juraj - on a new IDE based on Roassal. You may have seen the video "browsing your code as a Disneyland ride" we are pushing this very hard. With Juraj - Inti for Pharo, a very nice and interactive view for code profiling. Milton is the main architect - many other cool stuff, such as event profiling, code metrics, Roassal book. People from Brazil are deeply involved in this Yes, we are actively preparing our trip for ESUG :) What do you work on these days? Alexandre

9 years, 3 months

3
4
0 / 0

Video on GraphBuilder

by Alexandre Bergel

Hi! It has been quiet these days on the mailing list. We are happy to release a new video: https://www.facebook.com/ObjectProfile/posts/639419506144650 The video is about visualizing software dependencies. Happy day to you all! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 4 months

2
1
0 / 0

Re: [Pharo-dev] Pharo 3.0 / Roassal2 / Ubuntu

by Esteban Lorenzano

yeah, but where? looks like a roassal problem, not a pharo one. Redirecting to moose list :) Esteban On 17 May 2014, at 10:24, volkert(a)nivoba.de wrote: > > Am 01.05.2014 13:07, schrieb Alexandre Bergel: >>> Yes yes yes ... it works. I quickly jumped through some examples. Roassal2 looks so nice. Thank you. >> Let me know how it goes. Documentation is missing, but we have many many examples… >> The chapter in Deep into Pharo (www.deepintopharo.com) contains a documentation about Roassal1 and the Mondrian builder, written on top of the core of Roassal. >> >> Roassal2 is largely compatible with Roassal1. When it is not, then small changes have to be made. >> >> Alexandre >> > today i started with a fresh pharo 3.0 image (#30848) und loaded roassal2 (following the video tutorial). But when > selecting the example and evalution menu i got a "MessageNotUnderstood: ByteString>>replaceAllRegex:with:". > Something is broken here. > > BW, > Volkert >

9 years, 4 months

4
7
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev May 2014