10 Dec
2017
10 Dec
'17
11:55 a.m.
2017-12-10 7:34 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>om>:
Hi,
Thanks for the report.
I see that you are on Windows 8.1. We only tested on Windows 10.
How did you install this on windows 10 ?
I tried to load the code in a 6.1 image as described on the github page:
Metacello new
baseline: 'GToolkit';
repository: 'github://feenkcom/gtoolkit/src';
load.
But it now runs since two hours without finishing it.
After I excluded the pharo image from the windows defender antivirus check,
it seems to need less cpu time.
But it is still not finished.
I will restart the installation with the antivirus deactivated from the
start and see how long it will take.
Can you tell me how you installed the code?
Cheers,
Doru
On Dec 10, 2017, at 7:30 AM, Hernán Morales
Durand <
hernan.morales(a)gmail.com> wrote:
Hi Tudor,
VM just crashed here after click in Bloc examples -> any item ->
Connected
(Bloc)
Attached crash.dmp
Cheers,
Hernán
2017-12-09 4:14 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>om>:
Hi,
We are happy to announce GT Mondrian, a graph visualization engine built
on top of
Bloc.
It is similar to the original Mondrian and the Mondrian from Roassal,
but it is
different in that it is built directly out of Bloc elements. This
is interesting because it allows us to combine typical widgets with
visualizations. The other interesting thing about it is that it validates
the design of Bloc: right now, the implementation has 509 lines of code
(excluding graph-specific layouts). The goal is to make visualization a
first class citizen and an integral part of the IDE.
The key ingredient that made this happen is that Bloc can now treat
graph layouts,
such as tree or force based, behave under the same rules as
typical widget layouts, such as grid or flow. The challenge comes from the
fact that a graph layout depends on the notion of edges between elements,
and we did not want to have elements know about edges in the core of Bloc.
The solution was to split the typical edge implementation in graph
visualization
libraries into two distinct concepts:
• Line is an element that draws the
connections.
• Edge defines constraints imposed by connections between elements.
Thus, edges form constraints, and constraints are what layouts deal
with. That is
one reason why elements in bloc have the ability of defining
layout-specific constraints. Using this, we can nicely define edges between
elements as a plugin to Bloc, but still be able to connect arbitrary
elements. What's more, it turns out that we need constraints for other
layouts as well. For example, an element in a grid layout might specify the
span.
The API of GT Mondrian is similar to the one from Roassal, but there are
a few
differences as well. These are described in the Pillar documentation
available in the GitHub repo.
The best way to experience GT Mondrian and its documentation is to load
the
GToolkit as described here:
https://github.com/feenkcom/gtoolkit
If you download the GT code through Iceberg, the documentation can be
experienced
live by inspecting:
'./pharo-local/iceberg/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar'
asFileReference
<mondrian-doc.png>
Cheers,
The feenk team
--
www.tudorgirba.com
www.feenk.com
"Quality cannot be an afterthought."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
<crash.dmp>_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
--
www.tudorgirba.com
www.feenk.com
"One cannot do more than one can do."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev