Hi
I've fixed a big on ROArc, so that it draws well.
And I've
commented and added methods to RORectanglePacking to reduce biggest
nodes, and so on.
try:
Gofer new
smalltalkhubUser:
'MathieuDehouck' project: 'RoassalAlgorithm';
package: 'Roassal-New';
load
| view rawView n b |
rawView := ROView new.
view :=
ROMondrianViewBuilder view: rawView.
"-------------"
"-------------"
b
:= 30.
view shape rectangle
width: [ :cls | cls numberOfVariables *
5 ];
height: #numberOfMethods;
color: (Color r: 0 g: 1 b: 1 ).
view
nodes: TestCase withAllSubclasses.
view nodes do: [ :e | (e width > b
) ifTrue: [ e shapes first color: (Color r: 1 g: 0 b: 1 ) ] ].
view
layout:(( RORectanglePacking new)ratioWidth: 10 height: 10; padding: 4;
logWidthIfMoreThan: b scale: 5).
"-------------"
"-------------"
"Below
is the initiation of the menu and opening the
visualization"
ROEaselMorphic new populateMenuOn: view.
view open.
There are other log... methods, and scale represent the factor to
multiply the logs by. (yes log 10 = 1 and that's pretty small in pixel)
Regards
Mathieu
P.S. The screens have been made with the width and
the height in the same time.
Hi,
The Glamour tests are temporarily red:
https://ci.inria.fr/moose/job/glamour/lastCompletedBuild/testReport/
The reason is that Andrei and I started to work on a couple of new rather
cool features for Glamour. The engine works fine (only the tests require
changes now), and although the changes are quite deep, they are backward
compatible. More details will follow.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
For exporting Moose on the web, we must serialize the Moose's entities in
JSON or XML.
Is a such method already implemented on a FAMIX entity ?
Thanks,
Vincent Blondeau
Hi,
is there any way to request a string from the user with Glamour.
Something equivalent to:
UIManager default request: 'foo'
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill
Hi,
I would more do it the other way around (from large to small):
niceObject := ParseResult new.
result do: [:eachResult | niceObject add: eachResult ]
Cheers,
Doru
On Tue, May 28, 2013 at 2:23 PM, Juan Ignacio Vaccarezza <
juanvaccarezza(a)gmail.com> wrote:
> Doru,
> thanks for the answer.
>
> I'm doing it in the way you suggest.
>
> What I ment by know how to add to the result is the following: (Modifing a
> bit the example you gave me)
>
> a := 'AAA' asParser flatten ==> [:token | ResultSelfAdder new objectToAdd:
> token; selector:#addA ].
> b := 'BBB' asParser flatten ==> [:token | ResultSelfAdder new objectToAdd:
> token; selector:#addB ].
> c := 'CCC' asParser flatten ==> [:token | ResultSelfAdder new objectToAdd:
> token; selector:#addC ].
>
> meaningful := a / b / c.
> other := (meaningful / #newline asParser) negate star flatten.
> log := (meaningful / other) delimitedBy: #newline asParser.
>
> result := log end parse: 'AAA
> AAA
> BBB
> CCC
> AAA
> other text
> CCC
> BBB
> other text'.
>
> niceObject := ParseResult new.
> result do: [:eachResult | eachResult addYourselfTo: niceObject]
>
>
> ResutlSelfAdder>>addYourselfTo: aParseResult
> aParseResult perform: self selector with: self objectToAdd.
>
> I hope is clear now, Im pretty new at asking on mailists, and sometimes I
> forget to add crucial information
> Thanks again for your time!
>
> Juan
>
>
> On Tue, May 28, 2013 at 2:08 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
>
>> Hi,
>>
>> I am not sure what you mean when you say an object that knows how to add
>> to the result. Basically, you would need to build for each production the
>> object and collect the meaningful ones in the outer scope.
>>
>> Here is something that would work for your example:
>>
>> a := 'AAA' asParser ==> [:token | #a].
>> b := 'BBB' asParser ==> [:token | #b].
>> c := 'CCC' asParser ==> [:token | #c].
>> meaningful := a / b / c.
>> other := (meaningful / #newline asParser) negate star flatten.
>> log := (meaningful / other) delimitedBy: #newline asParser.
>>
>> result := log end parse: 'AAA
>> AAA
>> BBB
>> CCC
>> AAA
>> other text
>> CCC
>> BBB
>> other text'.
>> result select: #isSymbol
>>
>> I am CC-ing the moose mailing list because these questions tend to find
>> better answers there.
>>
>> Cheers,
>> Doru
>>
>>
>> On May 27, 2013, at 11:07 PM, Juan Ignacio Vaccarezza <
>> juanvaccarezza(a)gmail.com> wrote:
>>
>> > Hi all,
>> >
>> > First of all thanks for the amazing work and aswers to all. Having said
>> that, the problem:
>> >
>> > I need to parse a log, a model that represents the lo is the following:
>> >
>> > '
>> > AAA
>> > AAA
>> > BBB
>> > Line I don't care which can contain anything that is not AAA BBB or CCC
>> > CCC
>> > AAA
>> > CCC
>> > BBB
>> > Line I don't care which can contain anything that is not AAA BBB or CCC
>> > '
>> >
>> > I manage to write the grammar which parses this, but then I would lilke
>> to have all the log info digested on a result object which behaves
>> something like this:
>> >
>> > resutlObject as size --> 3
>> > resultObject bs size --> 2
>> > restulIbject cs size -->2
>> >
>> > The option that im using now is that individual parsers (meaning the
>> parser for AAA,BBB,CCC,etc) actually retunrs an object that knows how to
>> add themselves to the result and then, I iterate over the parser's array
>> result asking to each object to add itself to the result.
>> >
>> > Is there a better solution?
>> >
>> > Thanks to all,
>> > Juan.
>>
>> --
>> www.tudorgirba.com
>>
>> "It's not how it is, it is how we see it."
>>
>>
>>
>
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I'm looking for something that looks like a GLMAccordionArrangement,
but which allows maximum one selected element at any point. Current, I
can select one element in each accordion subpane.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill
Hi,
I was playing with the MooseFinder to visualize the source of some files
and I found the rendering of the text rather slow. Longer is the file
slower is the rendering. Is there a way to make the visualization of the
source code faster into MooseFinder?
Cheers,
Fabrizio