Bnoerj XNA Libraries

UPDATED WIKI: Bnoerj.Locales

Bjoern — Tue, 01 Apr 2008 08:38:17 GMT

Bnoerj.Locales Current release

This library provides support for localized keyboard layouts, a text input service and a supporting text renderer.

Locales, their keyboard layout and the font are defined at compile time through a simple XML file:

<Locale Name="en-US">
    <Font Name="Verdana" />
</Locale>

The locales name corresponds to the accepted values for the CultureInfo constuctor.
The fonts name is the friendly name of the font to import.

The Locale class holds the keyboard layout and the supporting font texture.

To use the Locale class in a game, simply instantiate a LocaleService. The LocaleService will automatically load the definiton corresponding to the users current locale and fallback to en-US, if the users locale is not supported.

The TextInputService provides a simple interface for text input, applying application defined keyboard delay and repeat speeds.

The TextRenderer class implements text drawing, mimicing the TextRenderer of .NET 2.0.

UPDATED WIKI: Home

Bjoern — Tue, 01 Apr 2008 08:37:57 GMT

Project Description
The Bnoerj XNA Libraries consist of the Bnoerj.Locale and Bnoerj.Audio projects. Bnoerj.Locales provides services to use different, localized keyboard layouts for text input and to render text entered with these. Bnoerj.Audio is a code compatible replace for he Microsoft.Xna.Framework.Audio namespace to provide XACT3 access to Windows based games.

List of libraries

UPDATED WIKI: Bnoerj.Audio

Bjoern — Tue, 01 Apr 2008 08:37:14 GMT

Bnoerj.Audio Current release

This library is a code compatible replacement for the Micrsoft.Xna.Framework.Audio namespace to give Windows based XNA games access to the new XACT3 engine. The advantage of XACT3 over XACT2 is the ability to use WMA compression on Windows, resulting in smaller xwb and hence smaller distributions.

How to use Bnoerj.Audio

First off all, you need the March 2008 release of the DirectX SDK to get the XACT3 tools.

To use Bnoerj.Audio in your Windows XNA Game Studio game the only code changes are:

1. Reference the Bnoerj.Audio.dll assembly
2. Replace all using Microsoft.XNA.Framework.Audio with using Bnoerj.Audio, e.g.

#if XBOX
using Microsoft.XNA.Framework.Audio
#else
using Bnoerj.Audio
#endif

XAP Convertion

You can use the Xapper.exe to convert your XACT2 projects to the XACT3. The command line arguments are the same as for XactBld3.exe and each compression preset that defines XMA compression will be changed to use WMA compression on Windows.

Another way to build the XACT3 runtime binary files from your existing xap project(s) is to open and edit them in XACT3.exe and manually add the WMA compression for the Windows target. Once the compression preset(s) have been updated you might want to save the xap file using a different name (e.g. MyProject.xap3) to not break the build of your Xbox 360 project. To generate the runtime xgs, xsb and xwb files you can either use the XACT3 GUI or the command line tool xact3bld.exe, e.g. "XactBld3.exe /L X:HEADER /WINDOWS MyProject.xap3 ." (without the quotes) to build the binaries into the current directory (ignoring the output directories defined in the xap file itself).

In both cases the binaries can then be used inside the games content project instead of the xap file.

UPDATED WIKI: Bnoerj.Audio

Bjoern — Tue, 01 Apr 2008 08:36:35 GMT

Bnoerj.Audio

This library is a code compatible replacement for the Micrsoft.Xna.Framework.Audio namespace to give Windows based XNA games access to the new XACT3 engine. The advantage of XACT3 over XACT2 is the ability to use WMA compression on Windows, resulting in smaller xwb and hence smaller distributions.

How to use Bnoerj.Audio

First off all, you need the March 2008 release of the DirectX SDK to get the XACT3 tools.

Then download the current release of Bnoerj.Audio.

To use Bnoerj.Audio in your Windows XNA Game Studio game the only code changes are:

1. Reference the Bnoerj.Audio.dll assembly
2. Replace all using Microsoft.XNA.Framework.Audio with using Bnoerj.Audio, e.g.

#if XBOX
using Microsoft.XNA.Framework.Audio
#else
using Bnoerj.Audio
#endif

Source code checked in

Bjoern — Tue, 01 Apr 2008 08:21:33 GMT

Added Xapper.exe overview to the Howto

UPDATED WIKI: Home

Bjoern — Tue, 01 Apr 2008 08:17:00 GMT

UPDATED WIKI: Bnoerj.Audio

Bjoern — Tue, 01 Apr 2008 08:16:36 GMT

Bnoerj.Audio

This library is a code compatible replacement for the Micrsoft.Xna.Framework.Audio namespace to give Windows based XNA games access to the new XACT3 engine. The advantage of XACT3 over XACT2 is the ability to use WMA compression on Windows, resulting in smaller xwb and hence smaller distributions.

How to use Bnoerj.Audio

First off all, you need the March 2008 release of the DirectX SDK to get the XACT3 tools.

To use Bnoerj.Audio in your Windows XNA Game Studio game the only code changes are:

1. Reference the Bnoerj.Audio.dll assembly
2. Replace all using Microsoft.XNA.Framework.Audio with using Bnoerj.Audio, e.g.

#if XBOX
using Microsoft.XNA.Framework.Audio
#else
using Bnoerj.Audio
#endif

UPDATED WIKI: Home

Bjoern — Tue, 01 Apr 2008 08:03:33 GMT

CREATED RELEASE: Bnoerj.Audio v1 (Apr 01, 2008)

Tue, 01 Apr 2008 07:57:26 GMT

Initial release of the Bnoerj.Audio project, providing the XACT3 code compatible replacement for the Microsoft.Xna.Framework.Audio namespace and the compile sample and XAP convertion tool.

RELEASED: Bnoerj.Audio v1 (Apr 01, 2008)

Tue, 01 Apr 2008 07:57:26 GMT

Initial release of the Bnoerj.Audio project, providing the XACT3 code compatible replacement for the Microsoft.Xna.Framework.Audio namespace and the compile sample and XAP convertion tool.

Source code checked in

Bjoern — Tue, 01 Apr 2008 07:38:10 GMT

Initial check in

COMMENTED ISSUE: Multiple character keys pressed simultaneosly not handled correctly

Bjoern — Sun, 03 Jun 2007 11:34:46 GMT

When I type a number like "12", my <1> key usually stays pressed when I start pressing the <2> key. Windows then ignores <1> and treats <2> as the only key pressed. Your library seems to handle that case in a way that does not make sense: 1: When I press <1> a "1" is produced. OK. 2: When I press down <2> a second "1" is produced. Bad. 3: When I let go <2> a third "1" is produced. Bad. You can repeat steps 2 and 3 as often as you like as long as you keep <1> pressed. Comments: ** Comment from web user: Bjoern **

Fixed in change set #4473.

Source code checked in

Bjoern — Sun, 03 Jun 2007 11:33:45 GMT

Fixed issue with simultaneous key presses not being processed correctly (see work item #1141)

COMMENTED ISSUE: Caps Lock is ignored

Bjoern — Sun, 03 Jun 2007 02:09:56 GMT

The component does not handle the Caps Lock key. Characters entered when Caps is locked are still lower case. Comments: ** Comment from web user: Bjoern **

Fixed in change set 4449.

Source code checked in

Bjoern — Sun, 03 Jun 2007 02:08:52 GMT

Fixed caps lock not locked (see work item #1113)

COMMENTED ISSUE: Caps Lock is ignored

SealedSun — Tue, 29 May 2007 20:00:43 GMT

The component does not handle the Caps Lock key. Characters entered when Caps is locked are still lower case. Comments: ** Comment from web user: SealedSun **

mine (de-CH) being one of those...

COMMENTED ISSUE: Caps Lock is ignored

Bjoern — Tue, 29 May 2007 19:19:24 GMT

The component does not handle the Caps Lock key. Characters entered when Caps is locked are still lower case. Comments: ** Comment from web user: Bjoern **

This is sort of By Design, e.g. I did not add it because I hate caps lock; yes, I know that I am ingnorant to the keyboard layouts that use caps lock as another sift state here...

CREATED ISSUE: Multiple character keys pressed simultaneosly not handled correctly

SealedSun — Tue, 29 May 2007 17:40:10 GMT

CREATED ISSUE: Caps Lock is ignored

SealedSun — Tue, 29 May 2007 15:14:30 GMT

The component does not handle the Caps Lock key. Characters entered when Caps is locked are still lower case.

COMMENTED ISSUE: locale definition files missing in source release

Bjoern — Tue, 29 May 2007 01:18:26 GMT

The source release does not contain the *.locale files. Comments: ** Comment from web user: Bjoern **

The latest Locales.zip of [release:3980] contains the content files.