Monday, May 17, 2010

Free Good Post-it like program for Windows

Stickies by Tom Revell is a good option. It's not open source but it is free.

It has a lot of features. Here's what I like about it.
1. Colors are available
2. You can set alarms
3. Free
4. Check boxes

The one thing I don't like about it is it is not open source, but that's not a deal breaker.

Thursday, May 13, 2010

WPF/XAML mapping to custom assemblies and clases in less than 60 seconds

You can map XML namespaces to assemblies using a series of tokens within an xmlns prefix declaration, similar to how the standard WPF and XAML-intrinsics XAML namespaces are mapped to prefixes.

The syntax takes the following possible named tokens and following values:

clr-namespace: The CLR namespace declared within the assembly that contains the public types to expose as elements.

assembly= The assembly that contains some or all of the referenced CLR namespace. This value is typically just the name of the assembly, not the path, and does not include the extension (such as .dll or .exe). The path to that assembly must be established as a project reference in the project file that contains the XAML you are trying to map. In order to incorporate versioning and strong-name signing, the assembly value can be a string as defined by AssemblyName, rather than the simple string name.

Note that the character separating the clr-namespace token from its value is a colon (:) whereas the character separating the assembly token from its value is an equals sign (=). The character to use between these two tokens is a semicolon. Also, do not include any whitespace anywhere in the declaration.

Got that?
Taken from here.

Wednesday, May 12, 2010

more MSDN WPF mind-bending docs

Adorners receive input events just like any other FrameworkElement. Because an adorner always has a higher z-order than the element it adorns, the adorner receives input events (such as Drop or MouseMove) that may be intended for the underlying adorned element. An adorner can listen for certain input events and pass these on to the underlying adorned element by re-raising the event.

At some point, the repetition of adorn makes my head spin.

adorn, adorn, adorn, adorn, adorn.


See original documentation here.

Monday, May 10, 2010

WPF WTF on MSDN part 1

My mind went blank after reading the following:

For instance, the underlying attached event Mouse.MouseDown can more easily be handled on any given UIElement by using MouseDown on that UIElement rather than dealing with attached event syntax either in XAML or code. The attached event serves a purpose in the architecture because it allows for future expansion of input devices. The hypothetical device would only need to raise Mouse.MouseDown in order to simulate mouse input, and would not need to derive from Mouse to do so. However, this scenario involves code handling of the events, and XAML handling of the attached event is not relevant to this scenario.

from here.

Anyone care to explain this one?