Hi,
If you want to install GToolkit (the project that contains GTInspector,
GTPlayground and GTDebugger) in your image, you can follow one of the
options as described here:
http://www.humane-assessment.com/blog/installing-gtoolkit
If you give it a try, please let us know how it works for you.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hello,
Is there any particular reason for GLMRoassal2Presentation working with
RTView instead of RTMondrianViewBuilder i.e. in the painting block, we get
RTView object instead of the builder.
I am asking this question because the predecessor, GLMRoassalPresentation,
used to work with ROMondrianViewBuilder. Now, when we'll move our
visualizations to work with Roassal2 in Glamour we'll have to make major
modifications to the source code because the level of details with RTView
and RTMondrianViewBuilder is not the same.
Usman
Hi everybody,
I am using PetitParser a lot and had implemented some little tools that
help me for writing or generating grammars. I put two of the most useful in
the project PetitParserExtension (
http://smalltalkhub.com/#!/~Moose/PetitParserExtensions).
the first one is useful when you generate grammars with lots of rules:
A PPExtendedCompositeParser offers you a new way to create rules. Just
define your rule as a method in the #rules protocol and it will be managed
exactly like rules in PPCompositeParser.
You will not have the limitation of 256 rules due to the instance variables
limit but you will need to refer to your rule with the method #rule: in any
other rule using it.
You can mix PPCompositeParser and PPExtendedCompositeParser way to define
rules.
the second one is cool for token identification because it creates a parser
that will parse in a time depending on token length and not the number of
different tokens.
A PPMultiStringParser is a tool able to create a really effective parser on
a huge collection of Strings. This parser will match any string in this
collection, and the longest one if two are matchable (( PPMultiStringParser
on: #('tin' 'tintin')) parse: 'tintin' will match 'tintin' and not just
'tin')
If someone else has implemented some tools around PetitParser, it will be
great to put those all together so feel free to commit your tools in this
project and to improve mines.
--
*Guillaume Larcheveque*
I wonder if this is a minor demonstration opportunity for Moose
refactoring tools...
"Neovim is a major overhaul of the vim editor to provide better
scripting, cleaner support for plugins and integration with modern
graphical interfaces. Modernising the large and complex codebase of Vim
is a formidable task, but the developer has a clear plan, and has
already begun work
http://news-beta.slashdot.org/story/14/03/22/147222/neovim-rebuilding-vim-f…http://neovim.org/
cheers -ben
Hello,
Is it possible to do popup views in Roassal 2 as we could do
with ROPopupView?
I didn't find any example related to this in Roassal 2.
tx,
Usman
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1016 by usman.bh...(a)gmail.com: PNG Export is not clean (example
EyeSee charts)
http://code.google.com/p/moose-technology/issues/detail?id=1016
See the attached screenshot, it seems that the export is not clean. The
diagram export is correct but the labels seem to be superimposed. The
problem might be coming from Pharo but I dont know how to reproduce it in
there.
Attachments:
EyeSee-2013-11-25-1506.png 5.9 KB
--
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
Well downloaded the newst Moosse and lates Pharo VM from here:
http://www.moosetechnology.org/download/5.0
Loading ConfigurationOfODBC from:
MCSqueaksourceRepository
location: 'http://squeaksource.com/ODBC'
user: ''
password: ''
Now in a workspace just type:
ConfigurationOfODBC load.
After a while I get an backtrace. which points to
ExternalClass class initialize
initialize
"ExternalObject initialize"
Smalltalk addToStartUpList: self after: ShortRunArray.
Yes ShortRunArray, is not there any more (that is known) but, just
removing it give the following Error
ffiPrintString: aString
"FFITestLibrary ffiPrintString: 'Hello'"
<cdecl: char'>' expected -> * 'ffiPrintString' (char *) module:'SqueakFFIPrims'>
^self externalCallFailed
And that's it.
Now where's the bug, in the VM in the image or where else?
Regards
Friedrich
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1047 by usman.bh...(a)gmail.com: Moose-on-Moose job in jenkins
failing
http://code.google.com/p/moose-technology/issues/detail?id=1047
The job Moose-on-moose is failing in Jenkins probably because output file
does not have the correct format. We launched the rules report on a moose
image with:
OnMooseReport importAndExportAsHudsonTests
And it succeeded. Currently, the job is disabled.
--
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
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium Component-MooseTools Component-DSM
New issue 1057 by anne.et...(a)gmail.com: DSM in MoosePanel without the name
of the entities
http://code.google.com/p/moose-technology/issues/detail?id=1057
In the MoosePanel, when right clicking on Package or Namespace, there is
the possibility to get various DSM. However, we can't do nothing with it,
since the name of the involved entities are not present. It could be nice
that at least when mouse over, the name of the involved entities appears.
Please fill in the labels with the following information:
* Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other
* Component-XXX
--
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
Hi all,
When I ran into trouble with the configurations again, I decided I needed a better tool. Metaceller is nice now, but not good enough. So I started working on a new version.
During my tests I stumbled on the configurationOfNewDebugger. This is the output it produces: (colors are missing).
0.2-baseline
Author:
Status: somethingLoaded
Imported versions: #()
DebuggerActions
Assuming version DebuggerActions-AndreiChis.69 is the correct version.
DebuggerModel
Assuming version DebuggerModel-AndreiChis.82 is the correct version.
DebuggerModel-Tests
No valid repository for self DebuggerModel-Tests.
Expected this package in one of the following repostories: spec
repository: 'http://www.smalltalkhub.com/mc/Pharo/Debugger/main'
DebuggerFilters
Assuming version DebuggerFilters-AndreiChis.2 is the correct version.
DebuggerFilters-Tests
No valid repository for self DebuggerFilters-Tests.
Expected this package in one of the following repostories: spec
repository: 'http://www.smalltalkhub.com/mc/Pharo/Debugger/main'
DebuggerExtensions
Assuming version DebuggerExtensions-AndreiChis.6 is the correct version.
default
Core
Spec-Debugger
Assuming version Spec-Debugger-AndreiChis.188 is the correct version.
Core-Tests
UI
But as you can see: this configuration does not load at the moment, because some of the packages are simply not there in the repositories.
Cheers,
Diego
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1055 by v.blonde...(a)gmail.com: Can't inspect instances variables
in debugger by the ALT+i command
http://code.google.com/p/moose-technology/issues/detail?id=1055
Describe the problem: what do you get? what do you expect?
When you try to inspect a instance variable in the debugger by the ALT+i
shortcut, you get a DNU :
MessageNotUnderstood: receiver of ""cull:cull:"" is nil
In the method:
GLMSmalltalkCodeModel>>bindingOf: aSymbol
^ bindingsStrategy cull: self variableBindings cull: aSymbol
The IV bindingsStrategy is nil.
How to reproduce the problem: step by step if necessary
Debug:
| temp |
temp := { 1 . 2 } asSet.
temp add: 3.
And go into the add: method and try to inspect array in the method source
Additional information: platform, context which may impact the problem
Moose 5.0 - W7
Please fill in the labels with the following information:
* Type-Defect
* Component-GT
--
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
Hi Max,
I am happy you want to give these tools a try :).
The tools do not install themselves automatically because I think it is not
a good practice to tie code loading with installation. To setup the Moose
image, we actually have a command line handler that allows you to simply
trigger this from the CI job:
./pharo $JOB_NAME.image mooseimagesetup --signature=$BUILD_URL
You can also trigger from the image:
MooseImageSetupCommandLineHandler activateWith: (CommandLineArguments
withArguments: {})
This installs the theme, the fonts, preferences and the GToolkit
playground, inspector and debugger.
However, for developing in Pharo, you do not need all of Moose, and almost
certainly do not need the Moose Finder. You likely only need the GToolkit.
spec project: 'GToolkit' with: [
spec
className: 'ConfigurationOfGToolkit';
version: #development;
file: 'ConfigurationOfGToolkit';
repository: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main' ].
To install the tools, you have to install them manually at the moment - but
I will create a command line handler for that soon:
GTPlayground registerToolsOn: Smalltalk tools.
GTInspector registerToolsOn: Smalltalk tools.
GTGenericStackDebugger registerToolsOn: Smalltalk tools.
GTGenericStackDebugger registerExtraToolsOn: Smalltalk tools.
"GTPPDebugger registerToolsOn: Smalltalk tools." "only if you need it for
PetitParser"
GTGlamourDebugger registerToolsOn: Smalltalk tools.
ACGlamourDebugger registerToolsOn: Smalltalk tools.
GTSUnitDebugger registerToolsOn: Smalltalk tools.
GTMoldableDebugger enableDebuggerWindowDistinctColor: true
To install the white theme:
GLMWhitespaceTheme defaultSettings: nil; setPreferredWorldBackground;
beCurrent
To install the fonts, you can just do this:
#('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular'
'SourceSansProBold') do: [ :each |
Smalltalk globals
at: each asSymbol
ifAbsent: [
Gofer new
smalltalkhubUser: 'girba' project: 'FreeFonts';
package: each;
load ].
(Smalltalk at: each asSymbol) new install ].
FreeTypeSystemSettings loadFt2Library: true.
FreeTypeFontProvider current updateFromSystem
Let me know how it goes.
Cheers,
Doru
On Wed, Mar 19, 2014 at 8:24 AM, Max Leske <maxleske(a)gmail.com> wrote:
> Hi
>
> I want to use the Moose UI tools for development and since I have a CI job
> for the project I thought I could just load Moose and be done with it. That
> doesn't seem to work however.
>
> I tried loading #development but when I do that I get the FallbackMenu
> instead of the world menu and no new inspectors / browsers. Here are the
> conditions of my build:
> - I want to start my build from a fresh Pharo3 image
> - I only want the Moose UI tools (I don't need any of the parsers etc.)
> - it would be nice if, when I open a built image, the default tools are
> already set to the Moose ones
>
> I know that there is a development Moose build for Pharo3, so I'm a bit
> surprised that I can't just load the configuration...
>
> BTW: this is how I tried to load Moose (maybe I just screwed up the
> configuration):
>
> baseline02: spec
> <version: '0.2-baseline'>
>
> spec for: #common do: [
> spec blessing: #baseline.
>
> spec package: 'LibGit2Bindings' with: [
> spec repository: '
> http://smalltalkhub.com/mc/MaxLeske/LibGit2Bindings/main' ].
>
> spec project: 'Moose' with: [
> spec
> className: 'ConfigurationOfMoose';
> file: 'ConfigurationOfMoose';
> version: #development;
> loads: #(Core UI);
> repository: '
> http://smalltalkhub.com/mc/Moose/Moose/main' ].
>
> spec package: 'Phexample' with: [
> spec repository: '
> http://smalltalkhub.com/mc/Phexample/Phexample/main' ].
>
> spec repository: '
> http://smalltalkhub.com/mc/StefanMarr/LibGit/main'.
> spec package: 'LibGit-Core' with: [
> spec
> requires: #(Phexample LibGit2Bindings
> Moose);
> postLoadDoIt: #postLoadRecompile ]
> ].
>
> I'd appreciate any help (and if nobody helps me Doru will probably kick my
> ass for still not using Moose :p)
>
> Cheers,
> Max
>
--
www.tudorgirba.com
"Every thing has its own flow"
Hi guys,
I started to play with Moose, because I need to analyze some code to detect
some bad smells.
As I used Moose ** a long time ago ** I am bit confused (and also lost)
with the way of using and manipulating the objects in the Moose panel.
Just an example to explain what I need is that:
1- I loaded a package of Pharo (let's say Collections-Sequenceable)
I can see all the information offered by the panel, but I would like to do
is the following:
a) How can I access to the information of the model, for example, to
manipulate the methods of the analyzed classes? In previous versions of
Moose, we could do something like MooseManager currentModel, but I see that
the design has changed drastically, and now I can not see how I can do it.
I need specifically access to the info stored in the model.
b) I see that you are using pragmas to define how we calculate properties
in each source code entity. For example in:
FAMIXMethod
numberOfInvokedMethods
<MSEProperty: #numberOfInvokedMethods type: #Number>
<MSEComment: 'Return a number corresponding to the number of invoked
methods'>
<derived>
^ self privateState propertyAt: #numberOfInvokedMethods ifAbsentPut: [self
invokedMethods size]
I added a new property with the same structure, but when I analyzed again a
previous application, my new property is not appearing in the list of
properties for a method in Moose.
Should I call a special message, or make a class invoke another method to
update the properties used to analyze the application?
I will appreciate a lot your help.
Cheers,
Gabi
Hi guys,
Now regarding Critics Browser, I have some questions.
1) After some reading I understood why you have a manifesto class in some
classes, BUT I do not understand what I should write in #rejectClasses and
in #rejectRules
2) When I used Critics Browser, when showing the results, there is a button
with Save Critics (Pharo 2.0 - but it is the same as in Pharo 3.0).
When I clicked, the message says that this action will modify my manifesto
classes. Choosing YES, I checked but there are no new manifest classes or
even the ones that already exist, have not changed. Am I missing something
in the process?
Cheers,
Gabi
Hi,
I tried to look in the the failing build problem, but I could not solve it.
Somehow the Moose-Tests-Core.xml is incomplete on the build server.
I tried to reproduce the problem locally, but I did not manage with this
code:
MooseTestCommandLineHandler activateWith: (CommandLineArguments
withArguments: {'--junit-xml-output'})
This should be the correspondent of:
./pharo $JOB_NAME.image moosetest --junit-xml-output
Could anyone else try as well?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi folks,
I am Pablo Estefó an ObjectProfile engineer and I will continue the excellent work of Daniel Aviv on Graph-ET (on Roassal2).
I’ve just added the “oblique” labels feature(for Roassal2’s GraphET version only). And the result is something like this:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
| diagram |
diagram := GETDiagramBuilder new.
diagram horizontalBarDiagram
models: #(0.2 0.5 2 0.3 0.51 1);
color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]];
valueAxisLine;
baseAxisLine;
addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5);
addValueDecorator: (GETRotatedLabelDecorator new diagonal numberOfLabels: 5).
diagram open
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
It produces:
If we change the rotated label as diagonal inverted:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
| diagram |
diagram := GETDiagramBuilder new.
diagram horizontalBarDiagram
models: #(0.2 0.5 2 0.3 0.51 1);
color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]];
valueAxisLine;
baseAxisLine;
addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5);
addValueDecorator: (GETRotatedLabelDecorator new diagonalInverted numberOfLabels: 5).
diagram open
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Vertical labels
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
| diagram |
diagram := GETDiagramBuilder new.
diagram horizontalBarDiagram
models: #(0.2 0.5 2 0.3 0.51 1);
color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]];
valueAxisLine;
baseAxisLine;
addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5);
addValueDecorator: (GETVerticalLabelDecorator new numberOfLabels: 5).
diagram open
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Vertical labels
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
| diagram |
diagram := GETDiagramBuilder new.
diagram horizontalBarDiagram
models: #(0.2 0.5 2 0.3 0.51 1);
color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]];
valueAxisLine;
baseAxisLine;
addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5);
addValueDecorator: (GETVerticalLabelDecorator new inverted numberOfLabels: 5).
diagram open
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
I am thinking a succinct way to specify it.
Well, as you can see the axis configuration will get more complex the more options we can provide.
So our next question to drive our development is:
How can we get the richest input in order to interpret it and return the best plot with the minimum configuration input.
I would like to know your opinions to develop a better Graph-ET :-)
Cheers,
Pablo
Hi everybody,
I have created a large FAMIX 3.0 file using InFamix form the wildfly (a.k.a. JBOSS) aplication server.
This file is about 142 MB large with 7 853 171 lines.
Importing that MSE file into Moose 4.9 (with pharo) on Windows and MacOS with 8GB RAM fails due to out of memory.
Is there an easy possibility to increase the the memory of the VM? I have only found some older postings talking about recompiling the VM.
Thank you very much
Thomas
Is it possible to provide objects instead of labels for the widgets in
Merlin? I am particularly thinking about MultiCheckboxesPart so that it is
provided with some objects and it shows their labels. Later, I would like
to get the user selection object instead of a label.
Currently, I only know how to provide labels and once user chooses (e.g. a
checkbox, i only get the selected label) and then I have to keep a
dictionary to determine the corresponding selector. Ideally, we should
provide an object along with a selector to get the labels/other properties
to be displayed.
May be something to take up at the upcoming sprint.
regards,
Usman
Hi!
The Moose image offers much more than offering moose. For example, I have a postdoc working on Astronomy images and she is using the moose image not because of moose, but because of what is shipped with it.
Does something who is not interested in analyzing software may find the moose image useful? The answer is absolutely yes.
What about changing the name of the Moose image into something closer to what it really offer?
Maybe Pharo4Modelling ? PharoModellingEdition?
I think this discussion is important.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
In March we will start our lecture about Pharo and Moose. We will give to each student one or two small projects to work on during the semester. We went through the site http://topics.pharo.org to have some ideas.
Is there anything you would like to see that is not on the topics website?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.