chandanlog(3C): Releasing OpenGrok 0.3 - Subversion and a new GUI

22 Feb 2006 Releasing OpenGrok 0.3 - Subversion and a new GUI

Another release of OpenGrok - a wicked fast source browser, made possible due to many contributions of Trond Norbye, a new member of OpenGrok team.

Changes in this release include

Support for Subversion
A cscope like GUI for search.
A GUI wizard for creating or updating search index.
New option that supports webapps with different context URLs.
Better display of matched context
Following the tradition of last release, there is a new CSS style sheet with offwhite theme.

You can download the source and binaries from http://www.opensolaris.org/os/project/opengrok/ or run pkgadd -d http://www.opensolaris.org/os/project/opengrok/files/osolopengrok.pkg to install it in /opt/OSOLopengrok. It installs a link to opengrok.jar in /usr/local/bin. You can launch the GUI by running the command

$ opengrok

I have also mirrored the Story of Opengrok and OpenGrok Internals on the project page

Link | Comments [12]

Comments:

Chandan, duuuude! This is incredibly cool. Now I just need to get my various source trees hooked in and I'll be all set on the path to programming happiness.

Posted by James McPherson on February 22, 2006 at 05:28 PM PST #

how does it cope with branches in history? the "demo install" on opensolaris.org is quite linear.

I'm asking because I'm considering a history parser for monotone, and there, branches are the norm, not the exception.

Posted by Patrick Mauritz on February 23, 2006 at 02:19 AM PST #

Keeping a linear history is considered a good practice. Solaris development policy discourages branches in revision log. OpenGrok shows a chronological list of file changes, branches are evident only by the revision number. like 2.1, 2.1.1, 2.2 ..

Posted by Chandan on February 23, 2006 at 11:03 AM PST #

keeping a linear history is a necessity for tools that can't cope with branches properly.

other than that, it has great benefits to have diverging histories: you can break away from mainline, work, update your branch with new mainline stuff (thus ensuring that your changes still fit in), eventually merge back. of course, you could flatten your branch into a single commit to mainline, but you lose quite a bit of information that way - you can look up _why_ a certain change was done.

there are some history viewer for monotone out there, look at http://linux.softpedia.com/screenshots/Monotone-viz_1.png for a small piece of monotone's history.

well, for me that means, that opengrok is probably not a suitable frontend for monotone repositories.

thanks anyway, both for the reply and for the tool - it's still highly usable for cvs and the like

Posted by Patrick Mauritz on February 24, 2006 at 06:48 AM PST #

Dont jump to a conclusion so early :-), both SCCS and CVS support extensive branching, and OpenGrok handles them - just that there is no graph display (yet)

Does Monotone have a CLI log command? If so in what order does it show log comments? If you write a MonotoneHistoryReader, it just has to give out log comments in that order. A real advantage if you have a Monotone support is that you can search through history comments.

Posted by Chandan on February 24, 2006 at 08:09 AM PST #

Can you please put some normal-size screenshots instead of this thumbinals. I would like to see if this software is worth installing before I start playing with java etc.

Posted by confused on February 25, 2006 at 04:25 AM PST #

click on the tumbnail where you can see bigger image or see the live deployment at < ahref="http://cvs.opensolaris.org/">http://cvs.opensolaris.org/

Posted by Chandan on February 25, 2006 at 09:46 AM PST #

Way cool! And one of the Norbye brothers! Does this mean we also get NEdit support (I forget who of them once upon a time did the NEdit/WorkShop integration)?

Posted by 84.73.58.231 on February 27, 2006 at 12:26 PM PST #

The editor in the screenshot is nedit. Set the Preferences --> Editor --> Custom to

nc +%d %s

and it works like a charm!

Posted by Chandan on February 27, 2006 at 01:05 PM PST #

How does one use the HistoryGuru to analyze versioned files? I can't seem to find any documentation on how one would do it, your other documentation is of top quality!

Posted by John F on November 06, 2006 at 11:42 PM PST #

There are HistoryReaders for each versioning system, which provide a Reader interface, that is fed to analyzers.

Posted by Chandan on November 07, 2006 at 01:04 AM PST #

So, if i use the provided run.sh or use opengrok.jar, will the HistoryReader tell that it is a CVS/RCS file and analyze it correctly?

Posted by John F on November 07, 2006 at 09:26 AM PST #