Dear Codestrikers, Its has been a very long time, but there is finally a new release (beta) with a stack of new features. You can download it from the usual download section from http://codestriker.sf.net. I'd appreciate it very much if people can download it and give it a try, and let me know of any issues.
The interface for adding comments has changed radically - you need to be using a fairly modern browser, as it is now using XmlHttpRequest to do its work, but the nice thing is it avoids the need for poping up a new browser window. I've attached the full CHANGELOG below. Incidently, the example Codestriker deployment on the SF site has also been updated to this beta release, so you can also look at it there. Again, you can access this from the Codestriker home page. -- Cheers, David Version 1.9.0 * Now using overlib javascript library (http://www.bosrup.com/web/overlib) for formatted "tooltips". When the mouse hovers over a line where a comment has been made, a formatted "tooltip" window appears, which contains the comment text formatted appropriately, with author and date header information bolded. The tooltip is not removed until the mouse is moved off the line. Help text on the create topic and search screens have been modified to use this tooltip library as well as opposed to javascript alert windows. * Comments are now added view an overlib tooltip window, rather than using a separate browser window. This speeds up the reviewing process and keeps the reviewer focussed on a single browser window. * It is now possible to create a comment associated with a specific file, or the topic itself, rather than being associated with a specific line. This allows reviewers to create file-level or topic-level comments. * There are patches available for Bugzilla 2.16 and Bugzilla 2.18 in the bin subdirectory, where the view bug screen is modified to include the "Create a New Codestriker Topic" and "View All" links directly under the "Create a New Attachment" and "View All" links. When a new topic is created via this link, the topic title will be set initially to the bug title, and the bug id field will be set to the id of the bug record. Before applying the patch, the codestriker_url variable must be set to the URL of your Codestriker deployment. * Extra options are now available in the codestriker.conf file in regards to when emails are sent out. It is now possible to control whether emails are sent to the topic author and/or the comment author when new comments are created. Also, there is an option which determines if all reviewers are notified if the topic's state is changed. This is all controlled by the $email_send_options configuration item. From Jason Remillard. * Added RSS support, so that the topic list screen now has an equivalent RSS view. From Jason Remillard. * Optimised database connection code, from Jason Remillard. * Added a "add other reviewers" link next to the Cc: field in the "add comment" screen. This allows the comment author to easily Cc all the other reviewers of the topic, for important comments that needs to be sent to all reviewers. * When creating new topics linked to Bugzilla, also include the topic description field in the Bugzilla comment. * Searching on the bugid and cc fields was not working correctly. This has now been fixed. * On UNIX platforms, missing modules can be fetched and installed automatically using the CPAN module, if required. * Subversion 1.1 has changed it diff format slightly. Parser as been updated, as reported by Martin Apel <[EMAIL PROTECTED]>. * Added integration support for Flyspray bug-tracking system. From Martin Apel. * Fixed text message written to bug-tracking system where the topic author was used instead of the actual user, when the topic state was changed. Found by Jason Remilliard. * Make sure for Win32 deployments, that the PATH environment variable is not zapped. This created issues when launching external programs, such as an SCM program. Since taint-mode is broken under Win32, this isn't an issue. Found by Michael R. Brumm <[EMAIL PROTECTED]>. * Fixed message "Character in 'c' format wrapped in pack at ... Response.pm", as reported by an anonymous user. * 'Readonly' topic states are now specified in codestriker.conf. For installations that add their own topic states, this allows them to have more than one state in which topics can be edited. From Dan Prince <[EMAIL PROTECTED]>. * Subversion topic creation fixes from Michael R. Brumm <[EMAIL PROTECTED]>. If module refers to file, path workaround duplicates the file's name at the end of the file path in the filename field. Starting and ending slash not removed from module name during getDiff. * Modified the Perforce parser to handle file-types that return "xbinary". Also handled Perforce diffs which contain unidiff style '---' and '+++' header lines. From Hope Duryea <[EMAIL PROTECTED]>. ------------------------------------------------------- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click _______________________________________________ Codestriker-user mailing list Codestriker-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/codestriker-user
