{"ref":"refs/heads/master","commits":[{"author":{"name":"Van Daele D","email":"2e5f80caa6b032b7fcb100082d5374d5a22d1ac5@hotmail.com"},"url":"https://api.github.com/repos/CPL2011/CPL1/commits/9f54920e705b54adde695fba9baea5acff638055","message":"IMPORTANT!\nSince I decided to centralize the visualization logic the current use of\nVisualisableGraph as a class that extends Graph with the trait Visual seems rather redundant,\nseeing how you wouldn't think of using trait Visual for anything other than VisualisableGraph.\nFor this reason I have created the NEW TRAIT 'Visualisable' this trait is effectively 'class\nVisualisableGraph extends Graph with Visual' pushed into a single trait.\n\nYou use it like this: var visualisableGraph = new Graph with Visualisable (see simulation/Test.scala)\n\nNow, I'd like to get some feedback on this. Pushing all visualization logic into a single trait seems like the most logical choice, but I'll still only feel comfortable with deleting trait Visual and class VisualisableGraph if I get your consent.\n\nIn other news, I added documentation to VisualisableGraph/Visualisable to simplify interaction.","sha":"9f54920e705b54adde695fba9baea5acff638055"}],"head":"9f54920e705b54adde695fba9baea5acff638055","size":1,"push_id":49744804}