Ok, then it’s my fault probably. I have Epicea but it should be concerned only about method/class changes. Also DFlow is installed but not running, maybe it’s erecting stuff anyway.
Uko
On 01 Jun 2014, at 18:38, Andrei Chis <chisvasileandrei(a)gmail.com> wrote:
> I had a look in your image and indeed the workspace is quite slow.
> However, if I copied the same input to a new fresh moose image and it works fast.
>
> It seems that somehow styling takes a lot of time in your image. Are you using some kind of
> instrumentation?
>
>
> Cheers,
> Andrei
>
>
> On Sun, Jun 1, 2014 at 1:46 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:
> Hi Andrei,
>
> this is the image https://space.zeo.net/g/4xxns. It contains inspector with a lot of code. For me it’s responding slow.
>
> Uko
>
>
>
> On 01 Jun 2014, at 17:07, Andrei Chis <chisvasileandrei(a)gmail.com> wrote:
>
>> Hi Yuriy,
>>
>> That's strange. Rubric should be very fast. If you look at the examples from RubLipsumBasicExample even text with almost 1800 lines works flawlessly.
>> If it's so slow there should be a problem in the way in which we integrated rubric into glamour. Do you have an example where I can reproduce this problem. I just copied a huge amount of text into an inspector/workspace but still cannot reproduce the slowness.
>>
>> Cheers,
>> Andrei
>>
>>
>> On Sun, Jun 1, 2014 at 1:10 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:
>> Hi, I thought my image is lagging, but it happens only in rubric. Yes, probably having 1794 characters in a method is not good, but when you are scripting Code City stuff, sometimes your experiments get large :). Again, sorry for that harsh characteristics, but typing characters and waiting 2 secs for them to appear is a bit upsetting :).
>>
>> Uko
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
Hi,
zooming in Roassal was always a sensitive topic for me, and now it seems to get better API in Roassal2. There are still some things that I don’t understand. Eg. when I send #translateTo:, #translateBy: and related things like #focusOnCenter to TRCamera, nothing happens (at least in GTInspector view). Is there a specific way to use it? Or it’s still work in progress?
Cheers!
Uko
Hi,
I am playing with a new look for Moose. I started from the logo and the
goal is to provide a more dynamic feeling to it. Here is a draft.
It is based on the same philosophy as the current logo (see
http://www.tudorgirba.com/blog/moose-and-the-analysis-story)
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I’m trying to port rectangle packing layout to roassal 2. And one problem that I’ve encountered was that element now do not understand #bounds. I’ve replaced all #bounds usages with #encompassingRectangle, but in the end layout is broken anyway. Before I start to dig down, maybe there are known changes that can impact layouts?
Uko
Hi,
Is there a way to get (semi)transparent blocks in CodeCity? I've tried using Color with alpha, but it doesn't seem to work.
Uko
Sent from my iPhone
Hi everyone,
now there is a dark theme for Pharo that I was waiting for a long time. Is it hard to make Moose-related tools be compatible with it? First thing that I noticed is GTInspector background:
Cheers
Uko
Hi, I thought my image is lagging, but it happens only in rubric. Yes, probably having 1794 characters in a method is not good, but when you are scripting Code City stuff, sometimes your experiments get large :). Again, sorry for that harsh characteristics, but typing characters and waiting 2 secs for them to appear is a bit upsetting :).
Uko
Hi!
It has been very quiet these last few days? Are you busy working on cool projects? What is the name of it? What does it do?
I start. We are working on:
- a paper on Roassal 3d for ESUG. It will describe some cool visualizations, including a code city-like. Together with Ronie, Milton and Francisco
- additional interactions for roassal2, in particular avoiding collision between elements. This is useful when nodes are dynamically added to a canvas. With Juraj
- on a new IDE based on Roassal. You may have seen the video "browsing your code as a Disneyland ride" we are pushing this very hard. With Juraj
- Inti for Pharo, a very nice and interactive view for code profiling. Milton is the main architect
- many other cool stuff, such as event profiling, code metrics, Roassal book. People from Brazil are deeply involved in this
Yes, we are actively preparing our trip for ESUG :)
What do you work on these days?
Alexandre
Hi!
It has been quiet these days on the mailing list.
We are happy to release a new video:
https://www.facebook.com/ObjectProfile/posts/639419506144650
The video is about visualizing software dependencies.
Happy day to you all!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
yeah, but where?
looks like a roassal problem, not a pharo one.
Redirecting to moose list :)
Esteban
On 17 May 2014, at 10:24, volkert(a)nivoba.de wrote:
>
> Am 01.05.2014 13:07, schrieb Alexandre Bergel:
>>> Yes yes yes ... it works. I quickly jumped through some examples. Roassal2 looks so nice. Thank you.
>> Let me know how it goes. Documentation is missing, but we have many many examples…
>> The chapter in Deep into Pharo (www.deepintopharo.com) contains a documentation about Roassal1 and the Mondrian builder, written on top of the core of Roassal.
>>
>> Roassal2 is largely compatible with Roassal1. When it is not, then small changes have to be made.
>>
>> Alexandre
>>
> today i started with a fresh pharo 3.0 image (#30848) und loaded roassal2 (following the video tutorial). But when
> selecting the example and evalution menu i got a "MessageNotUnderstood: ByteString>>replaceAllRegex:with:".
> Something is broken here.
>
> BW,
> Volkert
>
Hi,
I tried to build a graph in glamour. It works very well, but the
numerotation of x-axis is not correct.
There are an example follow:
| b |
b := GLMTabulator new.
b column: #first.
b column: #second.
b transmit to: #first; andShow: [ :a |
a list
display: (1 to: 20);
yourself
].
b transmit from: #first; to: #second; andShow: [ :a |
a roassal2 painting: [ :view :input |
| bg |
bg := GET2Line new view: view; data: (input to: 30).
bg y: [ :x | x * x. ].
bg build
]
].
b openOn:42.
Thanks
--
*ATREVI D. Fabrice *
*Master en Informatique A l'Institut de la Francophonie pour l'Informatique
(IFI/Hanoï)*
Here is an early preview of what we are working on...
https://vimeo.com/96091089
To be announced at ESUG...
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
As you know, the moose team is full of passionated and happy people willing to analyze software.
We have great platforms to carry out analysis that are robust enough to compete with state-of-the-Art software analysis platforms out there.
It would be great to have software to feed our wonderful tools. There are 123 873 packages on Smalltalkhub (!). Can we have easily access to them? I mean, a big big big .zip file would be fantastic with all the public software.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
For the past few months I've been distracted by working on Issues for
Pharo 3.0 Beta. Now that it is almost released, its time for me to
return to packaging my masters project for release (it was good to have
the break after handing everything in). I wrote my project on top of
Moose 4.7-Development and I have modification against some of the
packages. Some of these are not worth merging into the current HEAD
since I'll be migrating to GraphET and Roassal2. However it would be
good to have them somewhere I can reference them for a Configuration of
a working system before I do that migration. It would be useful for them
to be in their main repositories rather than trying to work out
something else.
Can I get access to upload to the EyeSee, Glamour, Magritte and Roassal
repositories?
Here is a summary of what I would upload, compared to Moose47 and latest
versions:
* EyeSee had extension Dictionary class >> keys:values: that hardcoded a
reference to 'Dictionary' preventing use by subclasses that I had. So I
change that reference to 'self'.
Latest EyeSee-Core-VincentBlondeau.110
Moose47 EyeSee-Core-AndreHora.100
LEKtrek01 EyeSee-Core-BenComan.101
* I added two features to Magritte:
* MADropDownListMorph
* MASeparatorMorph
Latest Magritte-Morph-SeanDeNigris.86
Moose47 Magritte-Morph-NickAger.63
LEKtrek01 Magritte-Morph-BenComan.66
* I introduced #newView: to Glamour-Roassal so that #painting: could
receive a raw ROView rather than only ROMondrianBuilder. I believe
similar functionality ended up being integrated into the mainline later
on, but there are too many other changes for me to catch up for the 0.1
release.
Latest Glamour-Morphic-Renderer-AndreiChis.239
Moose47 Glamour-Morphic-Renderer -TudorGirba.183
LEKtrek01 Glamour-Morphic-Renderer -BenComan.181
Latest Glamour-Roassal-Presentations-TudorGirba.20
Moose47 Glamour-Roassal-Presentations-TudorGirba.8
LEKtrek01 Glamour-Roassal-Presentations-BenComan.10
Latest Glamour-Tests-Roassal-TudorGirba.6
Moose47 Glamour-Tests-Roassal-TudorGirba.4
LEKtrek01 Glamour-Tests-Roassal-BenComan.5
* I ended up a long way behind with Roassal. I added several features
that I think some made their way into the mainline, but I just didn't
keep up:
* adjust popup position
* added selections
* drag multiple items at a time
* work with ROView in Glamour
* keypress modifiers shift/control/alt
Latest Roassal-AlexandreBergel.757
Moose47 Roassal-AlexandreBergel.476
LEKtrek01 Roassal-BenComan.396
Latest RoassalMorphic-AlexandreBergel.170
Moose47 RoassalMorphic-VanessaPena.111
LEKtrek01 RoassalMorphic-BenComan.81
cheers -ben
Hi everyone,
we all have seen how cool CodeCity can the visualisation be on example of Pharo3 changes. But my question is: can we make platform to be somehow wider than the “wall” inside of it? Because in my case colour of a platform may not be the same as all the nodes on the wall and it’s hard to understand if it’s the platform that is red or the nodes at the bottom of the wall.
I’ve tried to do "wallLayout outerGap: 5 asCCPoint”, and it gives the desired result, but then walls also start to float above platforms.
I’d be thankful for any suggestion.
Uko
You might want to take a look at DeprecationFinder (on smalltalkhub).
You could make a data structure representing all missing dependencies for a package, so you can create independent models for all versions of packages. If you can reason about multiple versions of packages you calculate which versions can (not) work together based on class/method signatures.
To do this over something as large as Moose, you currently need to create deltas or at least a structure more memory efficient than Famix, otherwise you'll run out of memory. I'm looking forward to a 64 bit image+vm
Stephan
Hi guys.
I’ve encountered an error that occurs when we are displaying for example dict in GTInspector. There is very nice functionality which sorts items according to one column
column: 'Key'
evaluated: [:each | GTObjectPrinter new asTruncatedTextFrom: each key ]
sortedBy: [:x :y | x > y ];
but not all objects know how to respond to #>.
Any ideas how to solve this in a mic way?
Uko
Hi all,
I have two questions :
how to load Moose in Pharo 1.0?
then how can I make in a programmatic way a MooseModel with packages that I chose in Pharo 1.0?
cheers,
------------------------------------
Hayatou
Ok, with some more configuration massage, some parts of it actually work.
The dependency on Magritte-Seaside was missing.
It still depends on Mondrian...
Stephan
Dory wrote:
>Pretty cool. Did you by any chance run it locally to see if it actually works?
Nah, no need if the tests run ;)
The tests don't tell you:
- need to load Zinc-Seaside
- need to load JQueryUI
Then you get to see something. WATableTag>border: is still missing,
I don't know where to get that.
Stephna