« November 2006 | Main | January 2007 »
Ever want Firefox's inline search bar in IE (rather than the pop-up dialog offered in IE?) Here you go:
From IEForge, comes InlineSearch. Download from the product home page here.
CTRL+F to open or close the search bar. (And F3 / Shift+F3 to find the next occurrence.)
It's not a complete replacement, but it is absolutely nicer than the one built into IE 7.
Spotted this ..., you may need to actually go to my web site to play it inline depending on your news reader. It's an old take on a game I recall being called "moon-landing".
When you were a child, did you ever take long driving trips with your family? 20 years ago we didn't have all the electronic toys and such to play with, so we were forced to entertain ourselves via simpler means. One game was to name something that began with each letter of the alphabet. The specific "something" changed, but might have been plants, animals, cities, etc.
So, tonight in a geeky trip home from work, the "something" was programming language keywords.
Here's your challenge:
Using each letter of the alphabet (A-Z), come up with a keyword from a programming language you know. For example, the letter "R" might be "Return." Good luck. I couldn't get two letters. How did you do?
Slick page from CNET that can help determine whether you need to budget for a new PC next year to run Vista (or maybe budget for a few new parts).
My video card, while a 'pro' card, fails same of the gaming requirements of Vista like a Vertex and Pixel shader 3.0.
The CPU test seems whacked though and doesn't seem to handle my Xeon processers correctly.
Here. (Makes it simple to add a WPF/E control to a ASP.NET AJAX enabled web site).
I'm sure the WPF/E demo's are going to be flooding the internet ... but in the mean time, here's one that uses Flickr and Script#:
WPF/E and Script#From John Rayner -- a project template which makes it a bit easier and less impactful to install the WPF/E project templates. The installer that is included with the WPF/E SDK requires extra downloads by default -- which you may not want (or need).
Although it took me 2 minutes to create this morning after searching for 2 minutes -- I thought I'd post this:
(I needed a Color to SolidColorBrush converter so that I could display the actual physical color rather than the name)
public class ColorToBrushConverter : IValueConverter
{
#region IValueConverter Members
public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)
{
if (value is Color)
{
return new SolidColorBrush((Color)value);
}
return null;
}
public object ConvertBack(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)
{
throw new Exception("The method or operation is not implemented.");
}
#endregion
}
Although very simple, it was very useful in this situation:
I have an object with a property of type Color:
public Color Color
{
get { return _color; }
set { _color = value; RaisePropertyChanged("Color"); }
}
I wanted to bind a rectangle with the color rather than just the name of the color:
<Rectangle Fill="{Binding Color, Converter={StaticResource myColorToBrushConverter}}" Width="20" Height="20" />
I created an instance of the converter in the local resources:
<ListView.Resources>
<local:ColorToBrushConverter x:Key="myColorToBrushConverter" />
</ListView.Resources>
And made sure I added the clr namespace to the XAML file:
xmlns:local="clr-namespace:WPFCheckBoxDemo"
And here it is in a simple list:
More on the list and why I was doing this in a later post ...
