> Objects are magical :) Yes, and this is absolutely mind blowing.
Understanding that a mouse click is most of the time an action to inspect is absolutely a step forward. I feel we are still at the very beginning. It would be nice to see how this will evolve over the time... Alexandre > > On Thu, Jun 4, 2015 at 10:04 PM, Peter Uhnák <i.uh...@gmail.com> wrote: > Yeah, this thing. :) > > <2015-06-04_22:02:31.png> > > I mean I knew I could program it, but I was just surprised that it did it > automatically, which is cool :) > > Peter > > > On Thu, Jun 4, 2015 at 9:54 PM, Tudor Girba <tu...@tudorgirba.com> wrote: > You mean that when you click on a node while you inspecting the view you get > a new pane to the right with that object? > > Doru > > On Thu, Jun 4, 2015 at 7:16 PM, Peter Uhnák <i.uh...@gmail.com> wrote: > Omg I just found out that if I click on the node representing an > McVersionInfo it actually opens it in the inspector and I didn't even needed > to implement anything special. > That's really cool! > > Peter > > On Tue, Jun 2, 2015 at 6:59 PM, Alexandre Bergel <alexandre.ber...@me.com> > wrote: > Interesting visualization! Keep going! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Jun 2, 2015, at 10:57 AM, Peter Uhnák <i.uh...@gmail.com> wrote: >> >> On Tue, Jun 2, 2015 at 3:07 PM, Tudor Girba <tu...@tudorgirba.com> wrote: >> Interesting. The dominance tree layout is quite interesting for this use >> case. >> >> There were some upward lines at the bottom of the graph for no apparent >> reason, not sure what was going on there yet, so I'll look into the layout >> when I have more time. >> >> Alternatively you could also use Sugiyama, however either due to the choice >> of heuristics, or some bug it places high priority on last levels which is >> really bad (since it is no longer at proper hierarchical layers). >> >> Peter >> >> >> Doru >> >> On Tue, Jun 2, 2015 at 12:09 PM, Peter Uhnák <i.uh...@gmail.com> wrote: >> HI Offray, >> >> I gave it a quick bash and come up with the following code. It's just a >> prototype and could be greatly simplified. >> >> - MCVersionInfo ancestors for whatever reason returned empty array down the >> line (so its cut off at the end), but I didn't investigate the problem >> - edge building and possibly ancestor retrieval could be simplified with >> builders; I think RTMondrian has methods for it but can't remember exactly >> (agilevisualization mentioned RTGraphBuilder but that has been removed to my >> knowledge) >> >> ~~~~~~~~~~~~~~~ >> mc := MCSmalltalkhubRepository allInstances detect: [ :m | m project = >> 'Roassal2' ]. >> >> root := mc versionInfoFromFileNamed: mc readableFileNames first. >> >> family := Set new. >> retriever := nil. >> retriever := [ :child | >> family add: child. >> child ancestors do: [ :a | retriever value: a ] >> ]. >> retriever value: root. >> obs := family asGroup. >> >> v := RTView new. >> es := RTEllipse new size: 15; color: Color blue; elementsOn: obs. >> v addAll: es. >> >> edges := RTEdge >> buildEdgesFromObjects: obs >> from: #yourself >> toAll: #ancestors >> using: (RTArrowedLine new withShorterDistanceAttachPoint; color: Color >> red) >> scope: es. >> v addAll: edges. >> >> es @ RTDraggable. >> es @ (RTLabelled new text: [ :m | m nameWithout: 'Roassal2' ]). >> >> v @ RTDraggableView. >> v @ RTZoomableView. >> >> RTDominanceTreeLayout new >> verticalGap: 30; >> horizontalGap: 15; >> on: es. >> >> v open >> ~~~~~~~~~~~~~~~~ >> >> >> <2015-06-02_12:04:32.png> >> >> Cheers, >> Peter >> >> >> On Tue, Jun 2, 2015 at 5:39 AM, Offray Vladimir Luna Cárdenas >> <off...@riseup.net> wrote: >> Hi, >> >> On a closer detail, seems that [1] contains the starting point I'm looking >> for. I'll keep you posted and of course any other approach will be listened. >> >> [1] >> https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Roassal/0104-Roassal.html >> >> Cheers, >> >> Offray >> >> >> On 01/06/15 22:04, Offray Vladimir Luna Cárdenas wrote: >> Hi all, >> >> I had asked a similar question before with no much advances, but today I >> made a discovery that can improve the things a lot: how to export timeline >> data as structured JSON [1] (and of course this open the possibility to work >> with it on Pharo). Now I would like to graph the data as a tree with forks, >> merges and dates and authors of commits. I have seen chronia, but seems >> overkill for this feature (and is integrated with CVS only). >> >> [1] >> http://stackoverflow.com/questions/30577090/how-to-export-fossil-scm-timeline-to-another-format/30580043#30580043 >> >> As usual, any pointer on how to get this going will be greatly appreciated >> and I will give feedback to the community on how to do it. >> >> Cheers, >> >> Offray >> >> >> >> >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
