Hi Tudor,
I want to use the double click event in a tree for opening a new window.
couldn't find examples of strongSelection doing something like that... Is this possible?
regards,
Veronica
Hi!
I am wondering whether something has been done in making Moose eat JSP
and Java Servlets code? As far as I know, nothing has been done for
the Pharo version of Moose. Anyone can confirm?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
i was trying to load Glamour into a Pharo1.0-Core image using the configuration of Glamour and i got this dependency message:
This package depends on the following classes:
PluggableShoutMorph
You must resolve these dependencies before you will be able to load these definitions:
GLMPluggableShoutMorph
GLMPluggableShoutMorph>>announcer
GLMPluggableShoutMorph>>selectFrom:to:
Is it normal or is it a bug?
Cheers,
Fabrizio
Hi!
Today with Johan, we were surprised that there is no feature request
template when creating a new issue. Only 'Default report from user'
and 'Default report from developer' are available.
Everybody will be happy if I add a feature request template?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I ported the Name Cloud visualization from VW. It is available on any
group.
MooseGroup>>viewNameCloud
Cheers,
Doru
--
www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting
is the right one."
Hi!
I like the properties tab. However, I feel that the first column (the
name of the properties) deserve to be much wider. Some of the property
names are split over 3 lines.
Cheers,
Alexandre
Hi Niall,
Thanks for your mail. I won't have time to look into this until the
second week of May.
Maybe someone else working on the VW Moose can take a look at that?
Cheers,
Doru
On 21 Apr 2010, at 15:51, Niall Ross wrote:
> Dear Tudor, Philipp et al,
> we are approaching code freeze in the current VW release (after
> which there will be a period of RC testing and the release will be
> out in the second half of the year). We're also interested in using
> Moose to analyse the VW build. We would therefore welcome a version
> of Moose usable in already-released 7.7 (and in our latest builds,
> but I suspect a 7.7-compatible Moose version will run in our latest
> as well).
>
> The current latest version is loaded by MooseConfig 1.28 in the SCG
> repository, which dates from 2008. It loads OK but with 33
> Undeclareds, some of which I'm sure just indicate prereqs needing
> added to the config. The main Moose tool then fails to open looking
> for an icon selector (#horizontalDistribution20x20 missing from the
> ToolbarIconLibrary, and the coverage tool is also looking for a
> subspec) that may indicate a prereq (or might be a postLoad) required.
>
> I expect you could fix these things much more quickly than I, so
> that the latest VW Moose runs in 7.7. I'd be grateful if you would
> have a look at it. Meanwhile I will get you added to the VWDEV
> program so you can see our latest builds, but I suspect that if you
> fix whatever (probably trivial) stuff is needed to map from working
> in VW7.6 to working in VW7.7 that will solve the problem.
>
> (If you find you need any explanation on 7.6-to-7.7 changes that
> affect Moose' running, please post in VWNC and I or others can help.)
>
> Thanking you in advance
> Niall Ross
>
>
--
www.tudorgirba.com
"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."
Hi guys
I loaded the latest version of moose OncifgurationOfMoose loadDefault.
Then I loaded ConfigurationOfCAnalyze loadDefault
then I opened a moose browser and tried to load C files but I got the following error
ensureGlobalVariable: xmlDecl in: caUnit
| variableName xmlVariableName famixVariable |
self assert: [ xmlDecl name == #'decl' ].
and xmlDecl name -> 'decl' and not a symbol
Stef
Hi,
Does it exist a simple way to make vertical text ?
I would like to do something like that:
MORectangleShape new
width: 60; height: 20;
verticalText: [:entity | entity name asString]).
Cheers
---
Jannik Laval
This is what the comment says:
-=-=-=-=-=-=
Did some cleaning. Essentially moved methods from MOGraphElement to
MONode. Many methods were defined in MOGraphElement which cannot be
meaningfuly invoked on a MOEdge.
Move MOQuadTree and MOLayout in Utils
-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
Yesterday Doru gave me some bug reports. I wrote tests that identify
them and subsequently killed the bugs.
If you have encountered some bugs in Mondrian and you haven't reported
them, please report them asap.
I know that Mondrian has seen a decrease in its performances recently.
I am currently working on it. But is there something else ?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Alex,
Mondrian-Alexandre_Bergel.426 is not part of the latest ancestry. Is
this by intent or by mistake?
Cheers,
Doru
--
www.tudorgirba.com
"Speaking louder won't make the point worthier."
hi!
What about adding in FAMIXClass:
withAllSubclasses, allSubclasses, superclasses, withAllSuperclasses,
allSuperclasses
FAMIXClass should be somewhat polymorphic to Behavior.
That would be useful... I can do it.
Any opinion?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi all,
I am trying to make DSM generic.
In the last version of DSM, we can make a DSM based on nodes and edges.
Only the basic DSM works on it (dsm with colors). And I have to debug the interaction of the visualization.
In the package DSMCore, I made a class DSMExample with, for now, 2 examples.
Here is an example:
====
dSMMatrix := DSMMatrix withNodes: #(#1 #2 #3) edges: #(#(#1 #2) #(#2 #1) #(#3 #1)).
view := MOViewRenderer new.
DSMVisualization new
open: dSMMatrix
on: view.
view open
====
We make a DSM with nodes and a collection of edges. An edge is a collection of two elements: the source and the target.
I think I will do a third element to add informations for other DSM.
You can try it, and make comments.
I will pay attention to your idea to have a better generic DSM.
Cheers
---
Jannik Laval
Alex
is it on purpose that the default mondrian configuration of load 17 and that in the metacelloRepository you have 5 or 6 more
recent ones?
It is important to consider that you should publish in Mondrian and copy in metacelloRepository.
MetacelloRepository can disappear tomorrow.
Stef
>> dSMMatrix := DSMMatrix withNodes: #(#1 #2 #3) edges: #(#(#1 #2) #(#2 #1)
>> #(#3 #1)).
Just as a side remark, but I already stumbled several times over code
like the above in Mondrian and Glamour:
#1 " is not valid Smalltalk "
It does not parse with any parser other then the default one in
Pharo/Squeak. Up until a few minutes ago it broke the refactoring
engine badly. Pharo strangely compiles the above expression to the
number 1. So why not just put the number, which also saves you one
character?
1 " is a valid number "
To get a symbol with 1 you need to put the number in quotes:
#'1' " is a valid symbol "
Lukas
--
Lukas Renggli
www.lukas-renggli.ch
Hello,
I'm building a browser with gamour and I use a GLMTablePresentation.
There is a thing I would like to do:
I would like to set a specific name to my GLMTablePresentation colums
according the output value send from another presentation of the browser.
The first intuition I had was to specify the name of the column using a
block:
GLMTablePresentation new
column: [:input | input anyOne class asString].
but we can't do that.
Is it possible to do it in another way?
Hi,
I added the possibility to specify the children of a tree also based
on the level at which the item resides.
An example can be found here:
GLMBasicExamples>>treeWithChildrenByLevel
Stef, this solves a problem of easily showing both categories and
selectors (both being represented by symbols) in the same tree :).
Cheers,
Doru
--
www.tudorgirba.com
"There are no old things, there are only old ways of looking at them."
Hi
I notice that the following classes are not described in Fame. Now they are Group classes, so it's not so important as instances are dynamically created. However, MooseGroup and similar are described. So should we be consistent with the rule?
DudeDuplicationGroup
DudeMultiplicationGroup
FAMIXFileGroup
FAMIXFolderGroup
FAMIXGlobalVariableGroup
FAMIXNamespaceGroup
--
Simon
Hi all,
I have the AspectMaps website in a more or less presentable state. Maybe it would be worthwhile linking to it from the tools page on moosetechnology.org The URL is http://pleiad.cl/aspectmaps
The screencast is very basic right now, I hope to find some time soon to make it more fancy, showing more features and adding voice to explain what is going on.
In any case, comments are always welcome!
--
Johan Fabry
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Dear Alex,
I published a new version including two new line shapes.
Best regards,
Veronica
---------------------------------------------------------------
Name: Mondrian-VeronicaUquillas.422
Author: VeronicaUquillas
Time: 14 April 2010, 10:33:04 am
UUID: 853081bf-6830-48f3-80d2-54aef392b7f6
Ancestors: Mondrian-Alexandre_Bergel.421
Added:
- dashed line shape
- arrowed dashed line shape
Hi!
Where are we with the release? I checked the remaining issues and
closed the one that were fixed or that I cannot reproduce.
I am not expert in Glamour or the lazy group definition, but I would
like to see Moose 4.0 out. How can I help? We can do some remote pair
programming.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Gabi,
Ahh, now I understand. Any entity answers to mooseModel, so you can do:
FAMIXClass>>someMethod
self mooseModel ...
Great that you are using the Pharo version. Just for convenience, you
can find the latest development image here:
http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/…
Please let us know if you have further problems.
Cheers,
Doru
On 12 Apr 2010, at 18:18, Gabriela Arevalo wrote:
> Hi Doru,
>
> Thanxs for answering so quick.
>
> I am attaching an jpg to illustrate my problem :)
>
> If I evaluate MooseModel root, I get an instance of MooseModel that
> contains all the existing models. In the image you see that there
> are two models: Collections and SequenceableCollection, and
> SequeanceableCollection is selected to be the current one of the
> analysis.
>
> How can I access to that model if I am coding any property in a
> class? I checked the entities to know if each entity knows the model
> which belongs to, but it seems not.
>
> In the long past we could do ModelManager uniqueInstance
> currentModel, but now, how do I know that information?
>
> I am using Pharo version. I used the VW version during the weekend,
> but it seems that there are some code broken and I could not manage
> to make it work.
>
> Cheers,
>
> Gabi
>
> 2010/4/12 Tudor Girba <tudor.girba(a)gmail.com>
> Hi Gabi,
>
> Nice to hear from you :).
>
> ModelManager was replaced by just another Model that holds Models.
> To get to it, you do "MooseModel root" and if you want to see
> allModels from there, you do "MooseModel root allModels".
>
> Yes, properties are defined using pragmas.
>
> Which Moose are you using? Pharo or VW?
>
> Cheers,
> Doru
>
>
> On 12 Apr 2010, at 02:11, Gabriela Arevalo wrote:
>
> Hi guys,
>
> I have two basic questions regarding the implementation of Moose
> 1) How do we manage now the currentModel (the selected Model in the
> Moose UI)?
> A long time ago :) :), we have had the ModelManager class and we
> could do ModelManager uniqueInstance currentModel
>
> 2) Properties: I have seen that we are using pragmas from the
> instance side. Is it right? Or are there any other way of specifying
> them?
>
> Cheers,
>
> Gabi
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "Beauty is where we see it."
>
>
>
>
--
www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
Hi guys,
I have two basic questions regarding the implementation of Moose
1) How do we manage now the currentModel (the selected Model in the Moose
UI)?
A long time ago :) :), we have had the ModelManager class and we could do
ModelManager uniqueInstance currentModel
2) Properties: I have seen that we are using pragmas from the instance side.
Is it right? Or are there any other way of specifying them?
Cheers,
Gabi
