What I would love is to bind it with epicea. The users can comment the
files.
What is cool with Epicea is that a change has semantics and a before and
after state.
Finally often you do a change (composed of different modifications) and
that you
do not want to see all the modifications one by one but
Ok I split this method into one in the superclass and one in the superclass.
Side note: The more I think the more I think that epicea entity
commenting entiy should be held
in a separate file ( but I should discuss with Martin).
Now I was in the process to propose to students to build an in image
tools for support the
code review. But having a server is much better. Like that people can
share comment.
Where you tool takes its input?
Stef
Hello,
I had some spare time and I built a prototype web application for comparing
Monticello versions. I developed it using Seaside and Monticello version
diff implementation in Pharo. It was super easy to reuse the classes which
are responsible for downloading, comparing and generating diffs of
Monticello packages. Once again I see how extraordinary it is to have such
open system as Pharo.
I made this web app for my work with students as often I need to compare
their versions of packages across different projects/repositories. For
instance, the package is uploaded to PillarHub-Inbox and I want to compare
and discuss changes against the main repository.
Having this in mind I created a small web app called "Monticello Seaside
Review" (didn't get any better).
You may find an example review here:
http://review.pharocloud.com/msr/review/ehx82xz90kpnm56u9exkrul5q/4
You may also log in to this instance and play with it as it is not really
used so no problem if it crash for some reason :)
The sources of the project can be found here:
http://smalltalkhub.com/#!/~mikefilonov/MonticelloSeasideReview
I would be happy of someone finds the project useful and contributes some
ideas.
Thank you,
Mike
--
View this message in context:
http://forum.world.st/Monticello-review-web-application-tp4803443.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
