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
Name: GT-Debugger-StephaneDucasse.200
Author: StephaneDucasse
Time: 26 June 2014, 9:10:31.768055 am
UUID: 4e20dcfb-724e-4293-a6dd-4452bf73b3c4
Ancestors: GT-Debugger-TudorGirba.199
remove register assubclassresponsibility because it breaks completely
the toolRegistry.
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!
Workspace registerToolsOn: SmalltalkImage current tools
Then why the theme 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
In Pharo 30 it is fully working. In Moose well you can trash your image.
So to get a chance to be productive in moose we have a special quizz to
solve first.
Stef
So I'm trying to unload GT-Playground from moose and
I love it
SmalltalkImage current resetTools freezes my image.
And after you want that people like Igor spend time fixing problems in
the Moose image.....
In fact
SmalltalkImage current resetTools freezes my image even without
underloading GT-Playground.
I think that Moose is decaying sadly.
How can I get the old debugger interface? Because I go much faster with it?
Stef
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
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
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
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
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
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
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
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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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
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
Hi,
if it possible to change colour of CodeCity visualisation while it’s running? In particular I just need to re-run normaliser or a block, and not re-assign color value to a shape.
Uko
Can we make the configuration work for Pharo4? Because I think that it should work for now, but the configuration is just missing. All we need is to add something like:
spec for: #'pharo4.x' version: '0.2-baseline’.
to development version.
Uko
I really wish this is fixed :-(
Hard to make convincing publicity for Roassal…
I am writing the text using:
-=-=-=-=-=-=-=-=-=-=-=-=
drawOn: athensCanvas
athensCanvas pathTransform restoreAfter: [
"Draw the label centered on the position"
athensCanvas pathTransform
translateBy: self position asIntegerPoint;
rotateByDegrees: angle value;
translateBy: ((self notRotatedWidth value / -2) @ (self notRotatedHeight value / 2)) asIntegerPoint;
translateBy: (0 @ font descent negated) asIntegerPoint.
athensCanvas setFont: font.
athensCanvas setPaint: color.
athensCanvas drawString: text
].
-=-=-=-=-=-=-=-=-=-=-=-=
the font variable is set using the following method:
-=-=-=-=-=-=-=-=-=-=-=-=
getFontForSize: aNumber
^ LogicalFont familyName: StandardFonts defaultFont familyName pointSize: aNumber
-=-=-=-=-=-=-=-=-=-=-=-=
Is there something I am missing?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.