Contribute on Github
Discussion on TeamLiquid

Some of my other projects, including Replay sync utilities, C# replay parsing libraries, and an open-source chat log editor has helped the community in creating more formal streaming presentations and extending out into other applications to expand the community.

Using Starboard in particular, I’ve started extending my reach into Android and iPad development, with a first look into networking to create an application remote control. Look forward to that in the future.

Contribute on Github.
Download the latest version (Direct Link).
Discussion on TeamLiquid

Requires .NET 4.0 Client Profile and a Windows OS. No installation is required, just run the application.

Please try to submit bugs on the Github issues page, otherwise feel free to comment, make requests, and critique to your liking.

SC2Replay-CSharp is an open-source library for assisting developers in parsing information in Starcraft 2 replay files. While a work in progress, it can parse lots of useful information including player, team, match information, and chat logs.

Tested to support replays from 1.1.3-1.3.4, but may work with earlier versions.

Let me emphasize: This is intended for developers.

Releases can be found in the download section on Github, but I recommend compiling the latest version of the code to ensure the most stability with the latest replays.

Please try to submit bugs on the Github issues page, otherwise feel free to comment, make requests, and critique to your liking. Also let me know if you’re using this in a project, I’ll add you to the list!

Download the source on Github

Related thread on TeamLiquid

Starboard is an open-source Starcraft 2 scoreboard for Windows systems. It’s design around simplicity, making the players obvious and providing caster information to the viewers in an easy-to-read interface.

To run, be sure you have .NET 4.0 Client Profile installed. Past that, no installation is necessary, just run the executable and the application will run locally.

To contribute, you can fork the project on Github.

Ascend TV started out co-casting with Thundertoss with Viewer King of the Hills every week as an experiment. After making the right connections and a little sponsorship money from Thundertoss, the King of the Hill expanded to a more professional scene, with Top 200 players fighting it out every week.

Check out Ascend TV at both http://ascendtv.com and http://justin.tv/ascendtv

On the previous site, almost all traffic was directed towards an article for creating a Virtual Keyboard in WPF. Since then, I had reworked the keyboard into a more efficient design, and I have posted the code with an example project for those interested to check out in my Portfolio.

On a side note, Starcraft 2 was recently released as well, so I’ve taken to livestreaming games to help new players, in particular Zerg players, learn how to play the game. I offer commentary and answer questions often through the chat, as well as providing Video on Demand of previous streams. If you’re a PC gamer interested in Starcraft 2, I recommend you take a look.

Thanks for coming to the new site, and feel free to leave any comments if there’s something you’d like to see.

Note: This is an evolution of the virtual keyboard code previously displayed on ascendedguard.com before the redesign.

Since WPF does not directly support simulating keyboard strokes, you have two options:

• Import the SendInput function from a C++ DLL (User32.dll i believe it is)
• Manually write the keyboard’s output using the built-in InputManager

In the example I’m showing here, the end result gives you a simple keyboard control that can be themed from within your DLL, and requires no code. You’ll notice the test program only contains a single line of code, to focus the cursor on the first text box at startup. There are two functions that really do all the work here. In reality, there are only two kind of keys: Normal and Special Function. Normal keys output some kind of text to the screen. Special function keys will do something special, like pressing shift, backspace, or caps lock, where you don’t expect the text on the key to be printed to the screen. The following function, WriteText, uses the current InputManager to write text:

1: /// <summary>

2: /// Handles standard (letter/number) virtual keyboard presses. 

3: /// </summary>

4: private void WriteText(object sender, RoutedEventArgs e)

5: {

6:     // For all normal letters and numbers, we can just grab the letter that was on the key.

7:     string text = ((Button )sender).Content.ToString();

8:

9:     if (this .IsShiftPressed)

10:     {

11:         // Unselect the shift key once a capital letter has been inserted.

12:         this .IsShiftPressed = false ;

13:     }

14:     else if (this .IsCapsLockPressed == false )

15:     {

16:         text = text.ToLower();

17:     }

18:

19:     var textEvent = new TextCompositionEventArgs (Keyboard .PrimaryDevice, new TextComposition (InputManager .Current, Keyboard .FocusedElement, text))

20:                         {

21:                             RoutedEvent = TextInputEvent

22:                         };

23:

24:     InputManager .Current.ProcessInput(textEvent);

25: }

26:

The special keys are, in some ways, simpler, but require special logic. For most keys, you can simply embed the Key that will be pressed within the Tag of each key, and send the appropriate RoutedEvent. For Shift and Caps Lock, though, since we’re handling logic about capitalization in our WriteText method, we simply set appropriate properties in our class:

1: /// <summary> Handles standard (letter/number) virtual keyboard presses. </summary>

2: /// <param name="sender"> Keyboard button sending the event. </param>

3: /// <param name="e"> Event arguments. </param>

4: private void PressSpecialKey(object sender, RoutedEventArgs e)

5: {

6:     Key key = (Key )((Button )sender).Tag;

7:

8:     KeyEventArgs keyEvent = new KeyEventArgs (Keyboard .PrimaryDevice, Keyboard .PrimaryDevice.ActiveSource, 0, key)

9:     {

10:         RoutedEvent = KeyDownEvent

11:     };

12:

13:     InputManager .Current.ProcessInput(keyEvent);

14: }

15:

16: /// <summary> Presses or depresses the shift key when caps lock is not pressed. </summary>

17: /// <param name="sender"> Object sending the event. </param>

18: /// <param name="e"> Event arguments. </param>

19: private void PressShift(object sender, RoutedEventArgs e)

20: {

21:     // No reason to change anything if caps is enabled.

22:     if (this .IsCapsLockPressed == false )

23:     {

24:         this .IsShiftPressed = !IsShiftPressed;

25:     }

26: }

27:

28: /// <summary> Presses or depresses the caps lock key. </summary>

29: /// <param name="sender"> Object sending the event. </param>

30: /// <param name="e"> Event arguments. </param>

31: private void PressCapsLock(object sender, RoutedEventArgs e)

32: {

33:     this .IsCapsLockPressed = !IsCapsLockPressed;

34:

35:     this .IsShiftPressed = false ;

36: }

37:

There are a few limitations with this implementation:

• The virtual keyboard must be embedded on every form you intend to use it on. In some implementations, like single screen input kiosks, this may be desired even. However, it means you can’t just set a window as top-most and use it across your entire application.
• Special characters aren’t included currently, which would be required for fields like “E-mail address”. You can treat this as an exercise to extend functionality of this keyboard.

Download the full source code, including a VS2010 project, here:
Virtual Keyboard Example v.1.0.0.0

You can download a pre-compiled version of the app here:
Pre-compiled VK Example Requires minimum .NET Framework 4.0 Client Profile

Revisions
1.0.0.0 – Initial Version