Two Pc’s, Two Monitors, One Mouse, One Keyboard, One Input Director!

I have always had a rough time swapping between keyboards for my laptop and desktop until now. Thanks to Input Director (http://www.inputdirector.com/)  I can use one keyboard and one mouse to control both. No extra Hardware needed! The mouse will scroll through all three of my monitors and I really love the cursor wraparound feature. Ok enough with the infomercial check it out for your self if you are interested! It’s FREE!

Input Director

Input Director is a Windows application that lets you control multiple Windows systems using the keyboard/mouse attached to one computer. It is designed for folks who have two (or more) computers set up at home and find themselves regularly sliding from one system to the other (and wearing out the carpet in the process!). With Input Director, you can share a single keyboard/mouse across a set of systems. You switch which system receives the input either by hotkey or by moving the cursor so that it transitions from one screen to the other (in a very similar fashion to a multi-monitor setup). The idea being that you can position the monitors from two or more systems in a row and use a shared keyboard/mouse to control all of them.

Input Director also supports a “shared” clipboard, in which you can copy data onto the clipboard on one system, transition across to another and paste.

Input Director requires Windows 2000 (Service Pack 4), Windows XP (Service Pack 2), Windows 2003 or Windows Vista. The systems must be networked.

 


Continuous Integration 101

What is Continuous Integration?

Continuous integration describes a set of software engineering practices that speed up the delivery of software by decreasing integration times. (http://en.wikipedia.org/wiki/Continuous_Integration)

Continuous integration advantages:

  • When unit tests fail, or a bug is discovered, developers might revert the codebase back to a bug-free state, without wasting time debugging.
  • Integration problems are detected and fixed continuously – no last minute hiatus before release dates;
  • Early warning of broken/incompatible code;
  • Early warning of conflicting changes;
  • Immediate unit testing of all changes;
  • Constant availability of a “current” build for testing, demo, or release purposes;
  • The immediate impact of checking in incomplete or broken code acts as an incentive to developers to learn to work more incrementally with shorter feedback cycles.

Microsofts Team Build.

Here’s a diargram from Microsoft of an overview of Team Build..

ms181710_vs_bigbldarchovrviewen-usvs_90

To Be Continued…