version control system

DateControl 3.8
DateControl is such a real and useful basic control plugin tool that is designed to enable users to create a Date-picker. more>>
DateControl 3.8 is such a real and useful basic control plugin tool that is designed to enable users to create a Date-picker.
The Control is displayed according to control panel date settings, or in exclusive mm.dd.yyyy, exclusive dd.mm.yyyy or exclusive SQL format mode. "NULL" dates or what some would call no selection is supported. The control uses Native Windows control on Windows systems and native
Enhancements:
- Made adjustments so that font sizes work correctly with REALbasic 2009r4.
- MacFontSize, WinFontSize and LinuxFontSize properties now have the type Single instead of Integer.
- Added a WinTextUnit property.
- Added a LinuxTextUnit property.
- Windows fonts can now be nailed down to normal size pixels.
Requirements:
- MacOS X PPC - (Mach-O)
- MacOS X Universal Binary (Mach-O)
- Win32 - Windows
- Linux x86
- REALbasic 2006r4 or later.
Gerrit 2.0.17
Gerrit offers users a fantastic web based code review system, facilitating online code reviews for projects using the Git version control system. more>> Gerrit 2.0.17 offers users a fantastic web based code review system, facilitating online code reviews for projects using the Git version control system.
- Makes reviews easier by showing changes in a side-by-side display
- Allows inline comments to be added by any reviewer.
- Simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer. This functionality enables a more centralized usage of Git.
Enhancements:
- New Features:
-
- Add 'and '' shortcuts to PatchScreen: The keys 'and '' can be used to navigate to previous and next file in a patch set.
- GERRIT-241 Always show History panel in PatchScreen: The History panel in a patch screen is now always shown, even if there is only one patch set for this file. This permits viewing the number of comments more easily when navigating through files with ']'.
- Add 'Reply' button to comments on diff screen: There is now a 'Reply' button on the last comment, making it easier to create a new comment to reply to a prior comment on the same line. However, Gerrit still does not quote the prior comment when you reply to it.
- GERRIT-228 Apply syntax highlighting when showing file content: Files are now syntax highlighted. The following languages are supported, keyed from common file extensions: C (and friends), Java, Python, Bash, SQL, HTML, XML, CSS, JavaScript, and Makefiles.
- GERRIT-139 Allow mimetype.NAME.safe to enable viewing files: The new configuration option mimetype.NAME.safe can be set to enable unzipped download of a file, for example a Microsoft Word document.
- GERRIT-179 Display images inline for compare if mimetype.image/....: If mimetype.image/TYPE.safe is true images can be viewed inline in order to more easily visually compare them when an image is modified. Primarily useful for viewing icons in an icon library.
- File review status tracking: Per-user green check marks now appear when you view a file. This makes it easier to keep track of which patch set you last looked at, and within a patch set, which files you have looked at, and which ones you have not.
- GERRIT-247 Allow multiple groups to own a project: The owner of a project was moved from the General tab to the Access Rights tab, under a new category called Owner. This permits multiple groups to be designated the Owner of the project (simply grant Owner status to each group).
- Bug Fixes
-
- Permit author Signed-off-by to be optional: If a project requires Signed-off-by tags to appear the author tag is now optional, only the committer/uploader must provide a Signed-off-by tag.
- GERRIT-197 Move 'f' and 'u' navigation to PatchScreen: The 'f' and 'u' keystrokes in a patch screen were disabled when there were no differences to view. This was fixed, they are now always available.
- Remove annoying 'no differences' error dialog
- GERRIT-248 Fix server crash when showing no difference: The "No Differences" error dialog has been removed. Instead the "No Differences" message is displayed in the patch screen. This makes navigation through a pair of patch sets easier with ']' (no dialog stopping to interrupt you when you encounter a file that has not changed and has no comments).
- GERRIT-244 Always enable Save button on comment editors: Some WebKit based browsers (Apple Safari, Google Chrome) didn't always enable the Save button when selecting a word and deleting it from a comment editor. This is a bug in the browser, it doesn't send an event to the Gerrit UI. As a workaround the Save button is now just always enabled.
- GERRIT-206 Permit showing changes to gitlinks (aka submodule poin...: You can now view a change made to a gitlink (aka a submodule path).
- GERRIT-171 Don't crash the submit queue when a change is a criss-...: Instead of crashing on a criss-cross merge case, Gerrit unsubmits the change and attaches a message, like it does when it encounters a path conflict.
- Other Changes
-
- Start 2.0.17 development
- Move 'and '' key bindings to Navigation category
- Use gwtexpui 1.1.2-SNAPSHOT to fix navigation keys
- A few Javadocs and toString() methods for Patch and Pa...
- Merge change 10646
- Include the mime-util library to guess file MIME types
- Merge change 10667
- Added missing access method for accountPatchReviews
- Fix bad upgrade014_015 ALTER TABLE command
- GERRIT-245 Update PatchBrowserPopup when reviewed status is modif...
- Remove DiffCacheContent.isNoDifference
- Fix upgrade014_015 part1 scripts WHERE clause
- Don't allow users to amend commits made by Gerrit Code...
- Fix bad formatting in UnifiedDiffTable appendImgTag
- GERRIT-228 Add google-code-prettify 21-May-2009 version
- GERRIT-228 Load Google prettify JavaScript into client
- Fix formatting errors in PatchScreen
- Remove unused imports
- GERRIT-250 Fix syntax highlighting of multi-line comments
- Use gwtexpui 1.1.2
MacMercurial 1.3.3
Free program that will help you ease the most common Mercurial operations. MacMercurial is a graphic user interface wrapper for the Mercurial version control system more>> Free program that will help you ease the most common Mercurial operations.
MacMercurial is a graphic user interface wrapper for the Mercurial version control system. MacMercurial goal is to ease the most common Mercurial operations and not to completely replace command line use of Mercurial.
Enhancements
- Fixed a bug in which the repository file failed to record a change in the location of a repository.
- In a status window, the Differences command is not enabled if there are selected items but no item with status M is selected.
Bazaar 1.16 RC1 / 1.15.1
Free and open source application that adapts to the workflows you want to use Bazaar is a distributed version control system available under the GPL that reduces barriers to participation in your more>> Free and open source application that adapts to the workflows you want to use
Bazaar is a distributed version control system available under the GPL that reduces barriers to participation in your project.
Bazaar is designed to support Mac OS, GNU/Linux, UNIX, Windows. In summary, Bazaar gives you fast, distributed revision control that "Just Works", supporting renames of directories and files smoothly.
Bazaar is designed to maximise the level of community participation in your project.
Bazaar branches can be published on any web server, and uploaded over sftp, ftp, or rsync. If you want the fastest possible network performance, there is a smart server.
Bazaar supports flexible work models: centralized like cvs or svn, commit offline, enforced code review when desired, and automatic regression testing.
Decentralized revision control systems give people the ability to collaborate more efficiently over the internet using the bazaar development model and have many other advantages.
When you use Bazaar, you can commit to your own local branches of your favourite free software projects without needing special permission.
Main features:
Good performance:
- Bazaar status in a tree of 5,000 files takes just 0.5 seconds, so almost every open source project can get the advanced features of Bazaar without slowing down its developers. Bazaar is robust in the face of radical tree restructuring, saving you time when it comes to merging from your community.
Safe with your data:
- There have not been any data loss bugs in a Bazaar release in the past two years. Bazaar has a huge test suite that ensures that new file formats can be tested automatically. The development process follows best practice with code review of all core and community code landings.
Friendly:
- Bazaar "Just Works" (which is why the Ubuntu team chose it for their project). Bazaar has a natural feel, you can publish your code on any web server or use a custom server for performance. Bazaar has perfect support for renaming files AND directories, which means you can unleash your community and merge efficiently even from contributors who are radically restructuring the tree.
Free:
- Bazaar is available under the GPL v2 or later.
Easy to integrate:
- Bazaar is designed as a Python API with a plugin system, so it is easy to embed in your tools and projects and easy to extend or integrate with existing infrastructure. Whether you are managing your development, or keeping track of configuration files, or building a new content management system, Bazaar is a great choice if you like to work in Python.
System requirements:
-
Enhancements
Compatibility Breaks:
- Display prompt on stderr (instead of stdout) when querying users so that the output of commands can be safely redirected. (Vincent Ladeuil, #376582)
New Features:
- A new repository format 2a has been added. This is a beta release of the the brisbane-core (aka group-compress) project. This format now suitable for wider testing by advanced users willing to deal with some bugs. We would appreciate test reports, either positive or negative. Format 2a is substantially smaller and faster for many operations on many trees. This format or an updated version will become the default in bzr 2.0.
- This is a rich-root format, so this repository format can be used with bzr-svn. Bazaar branches in previous non-rich-root formats can be converted (including by merge, push and pull) to format 2a, but not vice versa. We recommend upgrading previous development formats to 2a.
- Upgrading to this format can take considerable time because it expands and more concisely repacks the full history.
- If you use stacked branches, you must upgrade the stacked branches before the stacked-on branches. (See )
- --development7-rich-root is a new dev format, similar to --dev6 but using a Revision serializer using bencode rather than XML. (Jelmer Vernooij, John Arbash Meinel)
- mail_client=claws now supports --body (and message body hooks). Also uses configured from address. (Barry Warsaw)
Improvements:
- --development6-rich-root can now stack. (Modulo some smart-server bugs with stacking and non default formats.) (John Arbash Meinel, #373455)
- --development6-rich-root delays generating a delta index for the first object inserted into a group. This has a beneficial impact on bzr commit since each committed texts goes to its own group. For committing a 90MB file, it drops peak memory by about 200MB, and speeds up commit from 7s => 4s. (John Arbash Meinel)
- Numerous operations are now faster for huge projects, i.e. those with a large number of files and/or a large number of revisions, particularly when the latest development format is used. These operations (and improvements on OpenOffice.org) include: branch in a shared repository (2X faster), branch --no-tree (100X faster), diff (2X faster), tags (70X faster) (Ian Clatworthy)
- Pyrex version of bencode support. This provides optimized support for both encoding and decoding, and is now found at bzrlib.bencode. bzrlib.utils.bencode is now deprecated. (Alexander Belchenko, Jelmer Vernooij, John Arbash Meinel)
Bug Fixes:
- Bazaar can now pass attachment files to the mutt email client. (Edwin Grubbs, #384158)
- Better message in bzr add output suggesting using bzr ignored to see which files can also be added. (Jason Spashett, #76616)
- bzr pull -r 123 from a stacked branch on a smart server no longer fails. Also, the Branch.revision_history() API now works in the same situation. (Andrew Bennetts, #380314)
- bzr serve on Windows no longer displays a traceback simply because a TCP client disconnected. (Andrew Bennetts)
- Clarify the rules for locking and fallback repositories. Fix bugs in how RemoteRepository was handling fallbacks along with the _real_repository. (Andrew Bennetts, John Arbash Meinel, #375496)
- Fix a small bug with fetching revisions w/ ghosts into a new stacked branch. Not often triggered, because it required ghosts to be part of the fetched revisions, not in the stacked-on ancestry. (John Arbash Meinel)
- Fix status and commit to work with content filtered trees, addressing numerous bad bugs with line-ending support. (Ian Clatworthy, #362030)
- Fix problem of "directory not empty" when contending for a lock over sftp. (Martin Pool, #340352)
- Fix rule handling so that eol is optional, not mandatory. (Ian Clatworthy, #379370)
- Pushing a new stacked branch to a 1.15 smart server was broken due to a bug in the BzrDirFormat.initialize_ex smart verb. This is fixed in 1.16, but required changes to the network protocol, so the BzrDirFormat.initialize_ex verb has been removed and replaced with a corrected BzrDirFormat.initialize_ex_1.16 verb. 1.15 clients will still work with a 1.16 server as they will fallback to slower (and bug-free) methods. (Jonathan Lange, Robert Collins, Andrew Bennetts, #385132)
- Reconcile can now deal with text revisions that originated in revisions that are ghosts. (Jelmer Vernooij, #336749)
- Support cloning of branches with ghosts in the left hand side history. (Jelmer Vernooij, #248540)
- The bzr diff now catches OSError from osutils.rmtree and logs a helpful message to the trace file, unless the temp directory really was removed (which would be very strange). Since the diff operation has succeeded from the users perspective, no output is written to stderr or stdout. (Maritza Mendez, #363837)
- Translate errors received from a smart server in response to a BzrDirFormat.initialize or BzrDirFormat.initialize_ex request. This was causing tracebacks even for mundane errors like PermissionDenied. (Andrew Bennetts, #381329)
Documentation:
- Added directory structure and started translation of docs in Russian. (Alexey Shtokalo, Alexander Iljin, Alexander Belchenko, Dmitry Vasiliev, Volodymyr Kotulskyi)
API Changes:
- Added osutils.parent_directories(). (Ian Clatworthy)
- bzrlib.progress.ProgressBar, ChildProgress, DotsProgressBar, TTYProgressBar and child_progress are now deprecated; use ui_factory.nested_progress_bar instead. (Martin Pool)
- graph.StackedParentsProvider is now a public API, replacing graph._StackedParentsProvider. The api is now considered stable and ready for external users. (Gary van der Merwe)
- bzrlib.user_encoding is deprecated in favor of get_user_encoding. (Alexander Belchenko)
- TreeTransformBase no longer assumes that limbo is provided via disk. DiskTreeTransform now provides disk functionality. (Aaron Bentley)
Internals:
- Remove weave.py script for accessing internals of old weave-format repositories. (Martin Pool)
Testing:
- The number of cores is now correctly detected on OSX. (John Szakmeister)
- The number of cores is also detected on Solaris and win32. (Vincent Ladeuil)
- The number of cores is also detected on FreeBSD. (Matthew Fuller)
License:GPL
epicstcl 2.0
epicstcl - Tcl/Tk support for the EPICS control system along with EPICS aware megawidgets. epicstcl is a software solution that comes with Tcl/Tk support for the EPICS control system but also with more>> epicstcl - Tcl/Tk support for the EPICS control system along with EPICS aware megawidgets.
epicstcl is a software solution that comes with Tcl/Tk support for the EPICS control system but also with EPICS aware megawidgets.
Enhancements
- Use CChannelVariable derived from CTCLVariable so that
- epics linked variables are bi-directional.
- Formally set release level to 1.2
- Manage duplicate channel definitions by using reference counted
- channels.
Ditz 0.5
Simple, light-weight distributed issue tracker designed to work with distributed version control systems more>> Simple, light-weight distributed issue tracker designed to work with distributed version control systems
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like darcs and git. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format.
This directory is kept under version control, alongside project code. Changes in issue state is handled by version control like code change: merged with changes from other developers, included as part of a commit, conflict-resolved in the standard manner, etc.
Ditz provides a simple, console-based interface for creating and updating the issue database file, and some rudimentary HTML generation capabilities for producing world-readable status pages. It offers no central public method of bug submission.
System requirements:
- Trollop 1.7 or later
Volume Tiny 1.0
Free Yahoo! volume widget for your Mac more>> Free Yahoo! volume widget for your Mac
Volume tiny is a free Yahoo! widget that will let you manage the Macs volume and, when you double-clicking, it will show the systems Volume Control window.
System requirements:
- Yahoo! Widget Engine
Device Control Device 0.14
Remote telescope client program compatible with the INDI standard more>> Remote telescope client program compatible with the INDI standard
Device Control Device is a client program compatible with the INDI standard (see http://indi.sourceforge.net) for remote telescope and device control. Device Control Device is writen in Python and uses the GTK in order to display the GUI.
System requirements:
- Internet Connection
Volume Control 1.0
Free Yahoo! volume control widget for your Mac more>> Free Yahoo! volume control widget for your Mac
Volume Control is a free Yahoo! widget that will allow you to easily control your volume! This light-weight Widget allows you to adjust and mute your computers volume with a simple mouse scroll or click of a button. You can even set the volume sensitivity.
System requirements:
-
Enhancements
- This initial version provides mouse-scroll volume adjustments, up and down volume buttons, a mute button, and in-volume click changes.
Knob Control 1.0.2
Free Yahoo! volume widget for your Mac more>> Free Yahoo! volume widget for your Mac
Knob Control is a free Yahoo! widget that features an analog volume knob.
System requirements:
-
Enhancements
- Change marker position.
Java Remote Control 2.1b
View and control a remote desktop over TCP/IP more>> View and control a remote desktop over TCP/IP
Java Remote Control is a free and simple application to allow remote viewing of a desktop and control of the mouse and keyboard of the remote machine
Developed purely in Java, the Java Remote Control application should run on any machine with a JVM 1.2 or above installed.
Java Remote Control has been tested on Mac OS X (on a Mac Mini), Windows XP, Windows 98, Suse Linux and Red Hat Linux.
System requirements:
- Java
Ikiwiki 3.10
A free and open source wiki compiler more>>
Major Features:
- Uses a real RCS:
- Rather than implement its own system for storing page histories etc, ikiwiki uses a real Revision Control System. This isn't (just) because we're lazy, it's because a real RCS is a good thing to have, and there are advantages to using one that are not possible with a standard wiki.
- Instead of editing pages in a stupid web form, you can use vim and commit changes via Subversion, git, or any of a number of other Revision Control Systems.
- ikiwiki can be run from a post-commit hook to update your wiki immediately whenever you commit a change using the RCS.
- Note that ikiwiki does not require a RCS to function. If you want to run a simple wiki without page history, it can do that too.
- A wiki compiler:
- ikiwiki is a wiki compiler; it builds a static website for your wiki, and updates it as pages are edited. It is fast and smart about updating a wiki, it only builds pages that have changed (and tracks things like creation of new pages and links that can indirectly cause a page to need a rebuild)
- Supports many markup languages:
- By default, pages in the wiki are written using the MarkDown format. Any page with a filename ending in ".mdwn" is converted from markdown to html by ikiwiki. Markdown understands text formatted as it would be in an email, and is quite smart about converting it to html. The only additional markup provided by ikiwiki on top of regular markdown is the WikiLink and the directive.
- If you prefer to use some other markup language, ikiwiki allows others to easily be added by plugins. For example it also supports traditional WikiText formatted pages, pages written as pure HTML, or pages written in reStructuredText or Textile.
- ikiwiki also supports files of any other type, including plain text, images, etc. These are not converted to wiki pages, they are just copied unchanged by ikiwiki as it builds your wiki. So you can check in an image, program, or other special file and link to it from your wiki pages.
- Blogging:
- You can turn any page in the wiki into a blog. Pages matching a specified PageSpec will be displayed as a weblog within the blog page. And RSS or Atom feeds can be generated to follow the blog.
- Ikiwiki's own TODO, news, and plugins pages are good examples of some of the flexible ways that this can be used. There is also an example blog set up that you can copy into your own wiki.
- Ikiwiki can also aggregate external blogs, feeding them into the wiki. This can be used to create a Planet type site that aggregates interesting feeds.
- You can also mix blogging with podcasting by dropping audio files where they will be picked up like blog posts. This will work for any files that you would care to syndicate.
- Valid html and css:
- ikiwiki aims to produce valid XHTML 1.0. ikiwiki generates html using templates, and uses css, so you can change the look and layout of all pages in any way you would like.
- Plugins:
- Plugins can be used to add additional features to ikiwiki. The interface is quite flexible, allowing plugins to implement additional markup languages, register directives, provide a RCS backend, hook into CGI mode, and much more. Most of ikiwiki's features are actually provided by plugins.
- The standard language for ikiwiki plugins is perl, but ikiwiki also supports external plugins: Standalone programs that can be written in any language and communicate with ikiwiki using XML RPC.
- utf8:
- After rather a lot of fiddling, we think that ikiwiki correctly and fully supports utf8 everywhere.
- Other features:
- Tags: You can tag pages and use these tags in various ways. Tags will show up in the ways you'd expect, like at the bottom of pages, in blogs, and in RSS and Atom feeds.
- SubPages: Arbitrarily deep hierarchies of pages with fairly simple and useful LinkingRules
- BackLinks: Automatically included on pages. Rather faster than eg MoinMoin and always there to help with navigation.
- Smart merging and conflict resolution in your web browser
- Editing pages in a web browser: Nearly the definition of a wiki, although perhaps ikiwiki challenges how much of that web gunk a wiki really needs. These features are optional and can be enabled by enabling CGI and a Revision Control System.
- User registration: Can optionally be configured to allow only registered users to edit pages.
- Discussion pages: Thanks to subpages, every page can easily and automatically have a /Discussion subpage. By default, these links are included in the templates for each page
- Edit controls: Wiki admins can lock pages so that only other admins can edit them. Or a wiki can be set up to allow anyone to edit Discussion pages, but only registered users to edit other pages. These are just two possibilities, since page edit controls can be changed via plugins.

Icarus Camera Control 20090425
Camera control software for Nikon D80 and other PTP cameras. more>>
This program allows users of PTP cameras to remote control the camera, i.e. for tethered capture. It is intended as a replacement for vendor supplied camera control software that performs badly on portable computers.
This is open source software, not closed shareware. Easy-to-install bundles are available, or you can retrieve the source and build yourself.
Nikon Camera Control Pro 2.5
Nikon Camera Control Pro is one of the most salutary programs that can enable simplified remote control of many Nikon digital SLR functions from a personal computer, and includes advanced features such as Viewer that provide substantial improvements in operation. more>> <<less
QuickVolume 0.1
Free Yahoo! volume control widget for your Mac more>> Free Yahoo! volume control widget for your Mac
QuickVolume is a Yahoo! widget for adjusting the volume quick and easily. Very practical in those situations when you dont have any hardware sound control.
System requirements:
- Yahoo! Widget Engine