5 Mar
2015
5 Mar
'15
7:11 a.m.
Le 4 mars 2015 23:39, "Offray Vladimir Luna Cárdenas" <offray(a)riseup.net>
a
écrit :
affect
the Agile Visualization book. We have used it in some hackathons and
workshops here. Most of the people like the visuals and easiness of the
platform, but having the data taken from the software itself (the classes
and methods in Smalltalk for example) is far from what most people want.
Taking external data from cvs, json, xml, data bases and making it
computable/visualizable is the biggest concern.
Yes, faced that too.
Sqlite is important here as some datasets are in that format.
I've got one with 70K parliament questions for example.
Seeing how Smalltalk or other software looks inside accounts for the roots
of Moose as a software analysis tool, but in my experience, for Agile
Visualization, examples need to be more general and external.
Hi,
El 03/03/15 a las 15:34, stepharo escribió:
[...]
>
> For me Moose can still focus on meta modeling and we could have "agile
> visualization" but for that
> we do not need FAME, FAMIX and all the Moose related business.
>
> What I was suggesting to alex I told him more than a year ago was:
> Build an image with
> Roassal
> CSV
> JSON
> XML
> + some math packages
>
> No need to do that in the Moose Image: no need to have DSM, FCA,
Metrics,
FAME,
MooseModel.
Stef
That would be an image I would be interested in. I don't know how this
Cheers,
Offray
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev