Hi,
I took a bit of time to describe how the GTInspector works, what makes it
different, and to provide hints for several usage scenarios.
http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructed
It's a long post, I know :), but please take a look. As you might know,
this is the default inspector in the Moose image, but it can also be loaded
in a fresh Pharo image.
I am particularly interested in the following:
- if you never used it, and tried it now, what don't you like?
- if you used it, was there anything that you did not know?
- and of course, what do you like about it?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi!
Andrei did an excellent job of what I think could be a big big plus of the debugger in Moose.
Here is an example:
The stack is colored according to what you click. I believe this will ease the navigation and browsing of the runtime stack.
I suggest to not have a setting for this, but have it as a default, else nobody will use it.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
To explain my problem I will take this sample , my parser is a
PPCompositeParser.
ClassOrInterfaceType: ClassType / InterfaceType
ClassType:TypeDeclSpecifier, TypeArgumentsopt
InterfaceType: TypeDeclSpecifier, TypeArgumentsopt
TypeDeclSpecifier: TypeName / ClassOrInterfaceType . Identifier
TypeName: Identifier /TypeName . Identifier
Ok, so Identifier works well, no problem but when I tested
typeDeclSpecifier, I lost the contral of Pharo but I don't know why because
I use a PPCompositeParser. For the moment I use some tricks but I would
like it works normally.
Thanks for your help.
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
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"
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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
