text:
This article started out as a WPF DataGrid demo and a short article explaining how to accomplish basic tasks with the DataGrid. I have been digging into the WPF DataGrid over the past couple of days, and I am pleasantly surprised by what I have found. It is pretty easy to work with, and it produces pretty good results. I put together a demo to document the basic operations that I will need to perform with the DataGrid on an upcoming project, and I thought I would share it with the CodeProject community. In particular, I wanted to share my approach to drawing a drop-line on the grid while a row drag was in process.
As I wrote this article, it emerged that most of the way in which I deal with the DataGrid is driven by the Model-View-ViewModel pattern, and the article ended up being as much about MVVM as about the DataGrid. I think you will find it particularly helpful if you are trying to get a handle on MVVM, although even experienced hands will find the DataGrid discussion to be useful.
The demo app posted with this article gathers "How-To's" in one place for the basic operations of:
As you will see in going through the article, MVVM heavily influences almost every aspect of working with the DataGrid. For many developers, including myself, it is simply the way that WPF is done.
For the demo app, I needed a simple model with no natural order, so I borrowed the family grocery list from last Friday, and I made an object model out of that. It is the sort of list that one might use to perform all of the DataGrid tasks listed above. I haven't included data persistence in the demo, since there are so many ways of doing that. Instead, I create the object model at runtime.
When you start the demo, you will see a grocery list on a DataGrid. The grid has two columns:
Here is how to perform the basic DataGrid operations described above:
And that's about all there is to the demo. As I said initially, it is pretty simple.
The demo is built around the Model-View-ViewModel (MVVM) pattern. I use a fairly conventional implementation of MVVM. There are several different flavors of MVVM in the wild these days, and a lot of the literature on MVVM doesn't make a distinction that I consider to be vital.
Two flavors of MVVM: MVVM evolved from two other patterns, Model-View-Controller (MVC) and Model-View-Presenter (MVP). Both patterns are approaches for moving business and control logic out of a UI (the View). In both, a coordinator class is placed between the UI and the domain model. The coordinator class communicates with the View, and it contains the business and control logic that otherwise would have gone into code-behind in the View.
However similar the two patterns may be, they are not the same. I personally draw the following distinction between the two patterns:
I have a strong personal preference for the MVC flavor of MVVM. I believe that the MVC approach gives me greater flexibility to change the View, without causing unintended consequences in the ViewModel. In other words, I believe it does a better job of promoting Separation of Concerns and isolating the View and the ViewModel from each other, while allowing easy communication between the two. I discuss the subject at greater length in my CodeProject article on MVC, which can be found here.
Accordingly, my ViewModel knows nothing about the View that uses it. The ViewModel is passed to the View by App.xaml.cs as a part of the application bootstrap process:
protected override void OnStartup(StartupEventArgs e)
// Initialize main window and view model
var mainWindow = new MainWindow();
var viewModel = new MainWindowViewModel();
mainWindow.DataContext = viewModel;
The view model is instantiated and set as the DataContext of the main window, which serves as the demo application's View. From there, the XAML can access the properties of the view model using WPF data binding.
In other respects, my implementation of MVVM is pretty simple. The view model is made up of the following classes:
This composition of a view model using a main class, commands, services, and value converters is pretty typical of my MVVM implementations.
The MVVM pattern is designed to facilitate the use of WPF data binding. I don't know if the WPF implementation can be considered Version 3.0 of data binding, but Microsoft absolutely got it right in this version. WPF data binding dramatically simplifies the process of wiring a view to its view model. Just about everything is done as a simple binding:
<toolkit:DataGrid x:Name="MainGrid"
ItemsSource="{Binding GroceryList}"
SelectedItem="{Binding SelectedItem, ...}" />
Even commands are wired up through data binding:
<Button Command="{Binding DeleteItem}" ... />
The process of wiring up a view is simpler and quicker than it is in WinForms. That alone would justify a move to WPF.
View model properties: My own personal style of programming is to group items and to make heavy use of regions to do the grouping. In the demo app, the view model properties are grouped into two different categories, which is pretty typical of my MVVM implementations:
In some projects, I will include a third category of MVVM properties, UtilityProperties. These properties hold flags and other values that the view may need to provide to the view model. I didn't need them in the demo app, so it only has the two types of properties listed above.
In my MVVM implementations, the ViewModel does very little actual work. Instead, it acts as a coordinator object, and it delegates the work to command and service objects. Command objects are a standard element of the MVVM pattern, and again there are a couple of ways of implementing them. In my implementations, I like to put the main logic for each task in a command object. So, my command properties are all ICommand objects, and each is linked to a unique class that implements the ICommand interface.
The real benefit of the ICommand interface is that it provides a convenient framework for maintaining the enabled/disabled status of controls that are displayed in the view. For example, the demo app displays a button that deletes the selected item from the grid. The button is bound to the DeleteItem command property of the view model:
<Button Command="{Binding DeleteItem}" ... >
That property is linked to an ICommand class, DeleteItemCommand.cs. Every ICommand class must implement a CanExecute() method, which determines whether the command can be executed at any given point in time. Here is the DeleteItemCommand.cs implementation of the method:
/// <summary>
/// Whether this command can be executed.
/// </summary>
public bool CanExecute(object parameter)
return (m_ViewModel.SelectedItem != null);
.NET polls this method for all ICommand objects on a regular basis. If the method returns true, .NET enables any control bound to the command. If the method returns false, then .NET disables the bound control. In DeleteItemCommand.cs, the CanExecute() method simply checks the view model's SelectedItem property to see if anything is selected in the grid. If so, the method returns true, and the button is enabled. Otherwise, the method returns false, and the button is disabled automatically by .NET. That's another strong argument in favor of WPF.
Note that DeleteItemCommand.cs holds a reference to its parent view model, in the command's m_ViewModel member variable. This reference was set when the view model initialized its command properties:
private void Initialize()
// Initialize commands
this.DeleteItem = new DeleteItemCommand(this);
The view model instantiates the ICommand objects to which its command properties are linked, and it passes a reference to itself to the constructor of each ICommand class. This reference makes it easy for the command to check view model properties as it carries out its work.
The actual work of an ICommand is performed in its Execute() method. In the demo app, the work is very simple. The Execute() method gets the currently-selected item from the view model and deletes the item:
public void Execute(object parameter)
var selectedItem = m_ViewModel.SelectedItem;
Data properties are pretty straightforward, because they resemble the object properties that we have used in .NET from the beginning. The only twist is the WPF requirement that data properties in the view model raise the PropertyChanged event, so that the view can be updated when a view model property changes.
In the demo app, we fulfill this requirement in two ways. First, we derive the view model from an abstract class, ViewModelBase.cs, that is located in the UtilityClasses folder of the demo app. The class implements the INotifyPropertyChanged interface, a .NET interface that requires implementing classes to provide the PropertyChanged event. The ViewModelBase class also provides a method, RaisePropertyChangedEvent(), to raise the event when a property changes.
Our view model uses simple auto-properties for command properties, like this:
public ICommand DeleteItem { get; set; }
But it uses more elaborate property declarations for its data properties, like this:
public ObservableCollection<GroceryItem> GroceryList
get { return p_GroceryList; }
p_GroceryList = value;
The form of the data property declaration allows us to invoke the RaisePropertyChangedEvent() in the view model base class when a data property changes. That's what keeps the view and the view model in sync with each other.
There are some tasks that are either:
I use service classes, which I treat as part of the view model, for this code. In my MVVM implementations, service classes are generally static.
NHibernate quirkiness: In the demo app, we have one service class, SequencingService.cs. My applications generally use NHibernate for data persistence. I am a big fan of NHibernate; it drastically reduces the time spent on creating code to load objects from a database and save them back. But it does have a few quirks.
One of the things I like best about NHibernate is the fact that it does automatic 'dirty checking'. It will save only objects that have changed, which speeds up data persistence considerably. But for this feature to work, we have to be fairly careful to preserve the identity of the objects we read in from the database. For example, if we reorder a collection we have loaded from a database, NHibernate will consider the reordered collection to be a new collection, and we will lose automatic dirty checking. Fortunately, we can add objects to the collection, and delete objects from it, without losing dirty checking.
But it turns out that NHibernate also has an aversion to the ObservableCollection<T> collection type that MVVM is built upon. To get around this limitation, I created an application that wraps plain vanilla IList<T> objects, which NHibernate likes, in ObservableCollection<T> wrappers, which WPF likes. You can find the application and documentation here.
The demo app included with this article doesn't involve NHibernate, but my upcoming production app, for which the demo app serves as a pilot project, does. In that app, I am going to need to save a sequence number for each object in the collections displayed by the view, so that the objects can be loaded in the correct order the next time they are read in. That turns out to be a fairly simple task.
When we use wrapper objects as described above, then when we drag and drop items in a data grid, it's the wrapper objects that get reordered, not the domain objects. The domain objects remain in their original order in the domain collection. All we need to do is resequence the wrapper collection after a move, an add, or a delete.
The SequencingService class and the ISequencedObject interface: The SequencingService class takes care of that. It has one method, SetCollectionSequence(), which simply runs through the list and renumbers each item according to its current index:
public static ObservableCollection<T> SetCollectionSequence<T>(ObservableCollection<T>
targetCollection) where T : ISequencedObject
// Initialize
var sequenceNumber = 1;
// Resequence
foreach (ISequencedObject sequencedObject in targetCollection)
sequencedObject.SequenceNumber = sequenceNumber;
// Set return value
return targetCollection;
The signature of this method warrants some explanation. In my production application, I will have several collections that will be displayed by the app's views. These collections will not necessarily derive from the same base class, so I have created an interface, ISequencedObject, so that I can pass any of these collections to this service method. The interface file is located in the UtilityClasses folder of the demo app. It contains a single property:
public interface ISequencedObject
int SequenceNumber { get; set; }
As a result, the SetCollectionSequence() method can process any ObservableCollection<T>, so long as the elements of the collection implement the ISequencedObject interface. That is what the where clause at the end of the method signature signifies.
Service classes are frequently invoked from ICommand objects. However, the demo app shows a different reason for using a service class. Resequencing a collection is not triggered by a button or other control. Instead, it is invoked when the grocery list changes. That is, when an item is added to the list, removed from it, or moved within the list. In its Initialize() method, the view model subscribes to the CollectionChanged event of the grocery list:
p_GroceryList.CollectionChanged += OnGroceryListChanged;
When the event fires, an event handler in the view model invokes the sequencing service:
void OnGroceryListChanged(object sender,
System.Collections.Specialized.NotifyCollectionChangedEventArgs e)
// Resequence list
We could have simply placed the resequencing code in the event handler, but in a complex production app, a view model can get cluttered pretty quickly. And in my upcoming app, the code will be called by a number of different view models. Those requirements call for a service class that is accessible by whoever needs it.
Keep in mind that the sequencing service is not required for either the WPF or MVVM. Its need stems from my fairly unique requirements, which stem from using NHibernate with the WPF DataGrid. Nonetheless, even assuming these requirements do not apply to your application, the service class demonstrates one approach to where and how to use services in an MVVM application. It is an approach that has worked very well for me, and I have no hesitation in recommending it for general use.
Value converters are another frequently-used element of the MVVM pattern. WPF generally communicates in terms of strings, and we use value converters to convert object values to their string representations. The classic example of a value converter is a date converter, which might convert a DateTime object, which has a default string representation of "9/20/2009 12:00:00 AM", to a more user-friendly representation, such as "Sunday, September 20".
We don't have any naturally-occurring value conversion needs in the demo app, but we do have a very important use for a value converter nonetheless. The version of the WPF DataGrid included in the Pre-C# 4.0 WPF Toolkit has a fairly subtle, but very nasty bug. If you data bind the DataGrid's SelectedItem property to a view model (as the demo app does), you can no longer use the DataGrid's ability to add a new item to the grid by clicking on the blank row at the bottom of the grid. If you try to add a new item that way, you will get a FormatException with practically no explanation of what happened or where it happened.
Thanks to Nigel Spencer, who documented this bug and provided a clever fix. It seems the problem lies with the value that the DataGrid generates for a new item. The problem can be avoided by using a value converter that simply ignores that return value. That's what the value converter in the demo app does; it is a direct copy of the one suggested by Nigel. You can read more about the bug, and Nigel's solution, here.
Note that we have to declare the value converter in code—see the class file IgnoreNewItemPlaceHolderConverter.cs. But we also need to reference the value converter in the XAML of each window with a DataGrid. In the demo app, we do that in the <Window.Resources> section of the main Window XAML:
<!-- Value Converters -->
<vc:IgnoreNewItemPlaceHolderConverter x:Key="ignoreNewItemPlaceHolderConverter"/>
As you will see below, it is more usual to place resources such as this in a ResourceDictionary, where they are accessible to multiple windows. With that, let's turn to the DataGrid itself.
As I discussed at the outset, there are three DataGrid operations that most applications need to support: adding items to the grid, removing items from it, and moving items up and down in the grid. Before we get to those operations, let's take a look at styling the grid.
Styling the DataGrid: The DataGrid is styled in XAML. In the demo app, we place the style in the <Window.Resources> section of the main Window XAML. But in production apps, it is more usual to place the style in a ResourceDictionary, where it can be shared among several windows. And in a complex application, where grids may be located in many different assemblies, the styles may be placed in a special resource dictionary located in a 'shared resources' assembly. You can read more about that here.
The styling itself is pretty straightforward. The main window contains three styles:
<!-- DataGrid Background -->
<LinearGradientBrush x:Key="BlueLightGradientBrush" StartPoint="0,0" EndPoint="0,1">
<GradientStop Offset="0" Color="#FFEAF3FF"/>
<GradientStop Offset="0.654" Color="#FFC0DEFF"/>
<GradientStop Offset="1" Color="#FFC0D9FB"/>
<!-- DatGrid style -->
<Style TargetType="{x:Type toolkit:DataGrid}">
<Setter Property="Margin" Value="5" />
<Setter Property="Background" Value="{StaticResource BlueLightGradientBrush}" />
<Setter Property="BorderBrush" Value="#FFA6CCF2" />
<Setter Property="RowBackground" Value="White" />
<Setter Property="AlternatingRowBackground" Value="#FDFFD0" />
<Setter Property="HorizontalGridLinesBrush" Value="Transparent" />
<Setter Property="VerticalGridLinesBrush" Value="#FFD3D0" />
<Setter Property="RowHeaderWidth" Value="0" />
<!-- Enable rows as drop targets -->
<Style TargetType="{x:Type toolkit:DataGridRow}">
<Setter Property="AllowDrop" Value="True" />
The first defines a gradient brush that is used as the grid background. The second style defines the appearance of the DataGrid, and it references the first. The third style is used for dragging and dropping items within the DataGrid, and we will discuss it further below.
By and large, the styles are plain-vanilla XAML, and they do not warrant a lengthy discussion here. If you need more explanation, MSDN and most WPF books have pretty good discussions of the subject.
Adding items to the DataGrid: This task is about as simple as it gets. When you click on the blank row at the bottom of a DataGrid, the control creates a new, empty item for you and adds it to its collection. Thanks to the magic of WPF data-binding, the change is automatically propagated to the view model collection to which the DataGrid is bound. In the demo app, that collection is the GroceryList property. As you add an item to the grid, note the sequence numbers in the first column and the item count at the bottom of the window. Both of these values are being taken from the view model property, not from the grid itself.
The DataGrid is bound to the GroceryList property through the grid's ItemsSource property:
<toolkit:DataGrid x:Name="MainGrid" ItemsSource="{Binding
GroceryList}" ...>
The Sequence column of the DataGrid is bound to the SequenceNumber property of each GroceryItem object in the collection:
<toolkit:DataGrid x:Name="MainGrid"
<toolkit:DataGridTextColumn ... Binding="{Binding SequenceNumber}" ... />
In short, all we have to do is set up the data bindings; the DataGrid does the rest of the work for us.
Removing items from the grid: This task requires just a little more work. We have already discussed it above, in connection with the MVVM implementation. The Delete Item button, located in the main window just above the DataGrid, is bound to the DeleteItem command property in the view model. That property is linked to the DeleteItemCommand.cs class, whose Execute() method performs the actual work.
Moving items within the DataGrid: This is about the only task that requires any explanation. The implementation in the demo app, is taken from a code sample published on MSDN by Ben Carter, a member of the WPF development team. The demo app adds drop-lines to Ben's implementation, but otherwise, it is taken straight from his code. When you drag an item to another row within the grid, you will notice a blue line that follows your cursor up and down the grid, indicating where a dropped row will be inserted. I had previously added that feature to a WinForms data grid, and that implementation required some fairly complicated owner-draw code. In WPF, it takes just a couple of lines of simple formatting code. It's just one more reason to love WPF.
No code-behind: Before we get into the specifics of how the drag-and-drop functionality works, take a look at the code in MainWindow.xaml.cs. It appears that I have broken one of the cardinal rules of MVVM:
A view should delegate its work to its view model, rather than relying on code-behind. A well-designed MVVM application has almost no code-behind in its views.
A view should delegate its work to its view model, rather than relying on code-behind. A well-designed MVVM application has almost no code-behind in its views.
Obviously, in the demo app, the main window of the demo app has quite a bit of code-behind. You might well wonder what that is all about.
I am a big believer in the "no-code-behind" principle, and I don't think I have violated that principle in the demo app. The idea behind no-code-behind is to move control and business logic out of the view to a controller or coordinator layer that mediates between a view and the domain model.
Now take another look at the code-behind in the main window. You will notice that all of the code is related to the drag-and-drop functionality of the data grid. That functionality is a display concern, and it is therefore the province of the view. None of the code deals with business logic or control issues. Accordingly, Separation of Concerns is preserved.
In a larger application, with multiple views and numerous data grids, you might want to remove the guts of the code to a service class for all views, which would be invoked by skeletal event handlers in each view. That approach would eliminate duplication and provide a single point of change for updating the code. But in a simple application like the demo app, there is absolutely nothing wrong with placing view-support code of this sort into code-behind.
So as you develop applications using MVVM, take the no-code-behind rule with a grain of salt. If you need to program display logic that cannot be expressed in XAML, then code-behind is a perfectly acceptable place to do it.
Implementing drag-and-drop: The drag-and-drop implementation is really very straightforward. It has three elements. First, we add the events that we need for drag-and-drop to the DataGrid's XAML:
<toolkit:DataGrid ...
These events follow normal .NET conventions for drag-and-drop operations. If you need more explanation, MSDN covers the subject pretty well.
The second group of elements of the drag-and-drop implementation is the event handlers for the events we added in XAML. These event handlers appear in the main window code-behind:
#region Static Methods
private static T FindVisualParent<T>(UIElement element) where T : UIElement
var parent = element;
while (parent != null)
var correctlyTyped = parent as T;
if (correctlyTyped != null)
return correctlyTyped;
parent = VisualTreeHelper.GetParent(parent) as UIElement;
return null;
#region Event Handlers
private void OnMainGridCheckDropTarget(object sender, DragEventArgs e)
var row = FindVisualParent<DataGridRow>(e.OriginalSource as UIElement);
/* If we are over a row that contains a GroceryItem, set
* the drop-line above that row. Otherwise, do nothing. */
// Set the DragDropEffects
if ((row == null) || !(row.Item is GroceryItem))
e.Effects = DragDropEffects.None;
var currentIndex = row.GetIndex();
// Erase old drop-line
if (m_OldRow != null) m_OldRow.BorderThickness = new Thickness(0);
// Draw new drop-line
int direction = (currentIndex - m_OriginalIndex);
if (direction < 0) row.BorderThickness = new Thickness(0, 2, 0, 0);
else if (direction > 0) row.BorderThickness = new Thickness(0, 0, 0, 2);
// Reset old row
m_OldRow = row;
private void OnMainGridDrop(object sender, DragEventArgs e)
e.Effects = DragDropEffects.None;
e.Handled = true;
// Verify that this is a valid drop and then store the drop target
var row = FindVisualParent<DataGridRow>(e.OriginalSource as UIElement);
if (row != null)
m_TargetItem = row.Item as GroceryItem;
if (m_TargetItem != null)
e.Effects = DragDropEffects.Move;
// Erase last drop-line
if (m_OldRow != null) m_OldRow.BorderThickness = new Thickness(0, 0, 0, 0);
private void OnMainGridMouseMove(object sender, MouseEventArgs e)
// Exit if shift key and left mouse button aren't pressed
if (e.LeftButton != MouseButtonState.Pressed) return;
if (Keyboard.Modifiers != ModifierKeys.Shift) return;
/* We use the m_MouseDirection value in the
* OnMainGridCheckDropTarget() event handler. */
// Find the row the mouse button was pressed on
var row = FindVisualParent<DataGridRow>(e.OriginalSource as FrameworkElement);
m_OriginalIndex = row.GetIndex();
// If the row was already selected, begin drag
if ((row != null) && row.IsSelected)
// Get the grocery item represented by the selected row
var selectedItem = (GroceryItem) row.Item;
var finalDropEffect = DragDrop.DoDragDrop
(row, selectedItem, DragDropEffects.Move);
if ((finalDropEffect == DragDropEffects.Move) && (m_TargetItem != null))
/* A drop was accepted. Determine the index of the item being
* dragged and the drop location. If they are different, then
* move the selectedItem to the new location. */
// Move the dragged item to its drop position
var oldIndex = m_ViewModel.GroceryList.IndexOf(selectedItem);
var newIndex = m_ViewModel.GroceryList.IndexOf(m_TargetItem);
if (oldIndex != newIndex) m_ViewModel.GroceryList.Move(oldIndex, newIndex);
m_TargetItem = null;
Again, this code follows the general .NET pattern for drag-and-drop, so we won't discuss it at length.
Implementing a drop-line on the grid: What is worth noting is the implementation of a moving drop-line, which indicates where a dropped row will be inserted. The demo app implements a drop-line by setting either the top or the bottom border of a data row when the cursor enters that row, and then clearing the border when the cursor enters a new row.
When a drop is made, the WPF DataGrid will insert a dropped item either above or below the row under the mouse pointer at the time of the drop, depending on the direction of the drag:
So, the first order of business is to determine the direction of the drag. We get the original row index from the OnMainGridMouseMove() event handler:
private void OnMainGridMouseMove(object sender, MouseEventArgs e)
// Find the row the mouse button was pressed on
var row = FindVisualParent<DataGridRow>(e.OriginalSource as FrameworkElement);
m_OriginalIndex = row.GetIndex();
We store the index in a member variable in the window class. Next, we get the current row index as we drag the row upwards or downwards. We get that from the OnMainGridCheckDropTarget() event handler (see below). Then we compare the two values. If the result is negative, the drag is upward, and we draw a border on the top of the row under the mouse pointer. If the result is positive, the drag is downward, and we draw a border on the bottom of that row.
private void OnMainGridCheckDropTarget(object sender, DragEventArgs e)
var row = FindVisualParent<DataGridRow>(e.OriginalSource as UIElement);
var currentIndex = row.GetIndex();
// Erase old drop-line
if (m_OldRow != null) m_OldRow.BorderThickness = new Thickness(0);
// Draw new drop-line
var direction = (currentIndex - m_OriginalIndex);
if (direction < 0) row.BorderThickness = new Thickness(0, 2, 0, 0);
else if (direction > 0) row.BorderThickness = new Thickness(0, 0, 0, 2);
// Reset old row
m_OldRow = row;
The final element in the drag-and-drop implementation is a grid style that enables the rows of the grid to be used as drop targets:
<Style TargetType="{x:Type toolkit:DataGridRow}">
<Setter Property="AllowDrop" Value="True" />
As with the other elements of the implementation, there is nothing really unique or special here, so we will leave it without further comment.
Remember that the Shift key must be held down during a drag-and-drop operation. The demo implements that feature in the OnMainGridMouseMove() method:
// Exit if shift key and left mouse button aren't pressed
if (e.LeftButton != MouseButtonState.Pressed) return;
if (Keyboard.Modifiers != ModifierKeys.Shift) return;
This feature was added to the demo app to simplify the process of distinguishing between two types of drags:
If the Shift key is pressed, the selected row will be dragged. If the Shift key is not pressed, multiple rows will be selected.
As you can see, basic grid operations are surprisingly easy to implement in the WPF DataGrid. Not even the code for the drop-line is very complicated
As we noted at the beginning of this article, MVVM is a very scalable pattern, lending itself well to simple applications, such as the demo app, and to much more complex, multi-assembly applications. However, that does not mean that MVVM can support complex enterprise applications on its own. As an application grows larger, the essential problem becomes how to partition the application into manageable pieces, and how to integrate those pieces into a single, functioning whole.
I am very enthusiastic about the solution that Microsoft has provided in Composite Application Guidance for WPF, otherwise known as Prism. Prism is an application framework that allows a developer to partition an application into modules, which load into a shell that serves as the main window of an application. Prism uses some very clever mechanisms to allow the modules to communicate with each other and with the shell without becoming tangled up with each other.
As of this writing, Prism is now in Version 2.0. Unlike the earlier Composite Application Block library, Prism is not an all-or-nothing proposition. You can use as much or as little of it as you like. But Prism integrates so well with MVVM, and it is so well designed, that I find myself using just about everything it has to offer. It is definitely the next step to take after you gain a comfort level with MVVM.
And with that, I'll put down my pen. I invite any comments or suggestions you may have for this article; I find that I learn as much from reader comments as I do from writing the article itself. If you haven't spent a lot of time with MVVM, I recommend it to you. And if you haven't yet used the WPF DataGrid, it is a well-designed, easy to use control that integrates well with MVVM. I hope it simplifies your development chores as it has done for me.
This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)
Fantastic!!! Love it!!! Thanks David!!!
public ObservableCollection<Product> lstProduct
get { return SingletonEntities.GetInstance().dc.Products.ToObservableCollection(); }
private Product _SelectedProduct;
public Product SelectedProduct
get { return _SelectedProduct;}
_SelectedProduct = value; RaisePropertyChanged(() => SelectedProduct );
<Grid Grid.Row="0">
<ComboBox Margin="6" ItemsSource="{Binding Path=lstProduct}"
SelectedItem = "{Binding Path=SelectedProduct}" DisplayMemberPath="ProductName"/>
<Grid Grid.Row="0" Grid.Column="1">
<TextBox Margin="6" Text="{Binding SelectedProduct.ProductID}"/>
<DataGrid Margin="6" Name="dgStockProductHistory" ItemsSource="{Binding Path=SelectedProduct}" IsReadOnly="True" AutoGenerateColumns="false" SelectionMode="Single">
<DataGridTextColumn Binding="{Binding ProductID}" Width="*" Header="ID Produit"/>
General News Suggestion Question Bug Answer Joke Praise Rant Admin
Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.


text:
The sordid tale of Lance Armstrong is unfolding right before our eyes across the web, social media and of course TV in addition to pretty much every other channel known to man.
Back in August of this year I wrote an article about Penn State and if their brand had received the death penalty. While obviously different on many fronts, there are some similarities between Penn State and Lance Armstrong when it comes to branding and there's a lesson for all marketers and advertisers.
The opening two paragraphs of the aforementioned Penn State article fit like a glove when overlaid onto the Lance Armstrong saga:
"There are no shortage of definitions for the term "brand equity." You probably have your favorite. This is one of mine, especially in the context of the Penn State brand: "A brand's power derived from the goodwill and name recognition that it has earned over time, which translates into higher sales volume and higher profit margins against competing brands."
The reason I like this particular definition when it is applied to the brand of Penn State is because of words like "goodwill" and "name recognition" and 'earned over time.'"
Just replace "Lance Armstrong" for "Penn State" in the above sentences and there you go.
Mr. Armstrong has most assuredly achieved name recognition earned over time and he obviously has made himself and his brand a lot of money. He of course has also done a lot of good via his Livestrong Foundation.
I happen to think Livestrong is a separate entity all to itself and will continue on in its fight against cancer. In an article on CNN.com a cancer survivor put it perfectly: "The effect he had on the foundation was huge, but they both should be able to stand on their own. The foundation should not be held accountable for his deception."
Separating The Person From The Foundation
But this is not about Livestrong, this is about Lance Armstrong, the personal brand.
Many have said that this whole incident is reminiscent of Tiger Woods' fall from grace of a few years back but according to branding expert David Brier, it's more along the lines of a certain former vice-president.
"Lance's drop from grace is different than Tiger Woods'. It is much more similar to Al Gore's recent hypocritical act of selling his viewer-starved Current TV cable network for $500 million to Al Jazeera," said Brier.
The reason being, according to Brier, is "Lance professed a certain integrity that was part and parcel to 'his brand' as much as Al Gore, patriotism and environmental accountability seemed to be inseparable, until he sold his soul to Al Jazeera."
For his part Brier has an idea where Armstrong and Gore could potentially benefit from a partnership "A possible solution might be for Mr. Armstrong and Mr. Gore to create a new PR consultancy named 'Strong, Arm and Gore' with the slogan of 'Lots of stamina, no matter how hot it gets' which I think sums it up very nicely."
Then there is the issue of "clawbacks" whereby Lance would have to repay some of the millions of dollars he earned via sponsors now that he has admitted to using performance enhancing drugs.
Jeff Kravitz, a partner in the law firm Fox Rothschild LLP, says essentially if it's not broken, don't fix it. "Why publicly open a wound unless the business is hurting? says Kravitz. "Let it lie, let it die."
Kravitz, who also blogs about sports law, thinks Armstrong can recover from a branding perspective "through charity and clarity." He also believes a mea culpa would certainly help "Weasel words do not work, and presenting himself to the public with more sincerity is necessary."
His advice to Armstrong, which would more than likely be contrary to what many lawyers would advise is to "keep it simple, honest and direct" adding that "the legalities will play out better if you tell the truth."
As for brands who are considering establishing a partnership/sponsorship with a professional athlete, Kravitz suggests that it's best for brands to "know the person you are considering working with; check around before you sign someone and remember that long term relationships can work out when you stick with people."
The Future
Obviously this is all very fresh in our collective minds and the dust is far from settled. So trying to predict the future of the Lance Armstrong brand would be pointless.
As Americans we are a very forgiving society. As Kravitz said to me "If Michael Vick can have a second act, so can Mr. Armstrong."
And while I agree with him to a degree, there are extenuating circumstances regarding Lance Armstrong most notably the fact that he was/is an international star - not just in the US but across the world, people know Lance Armstrong. Will those living in other parts of the world be as forgiving as Americans are more apt to be?
Another thing to consider is the fact that Armstrong, in his defiant best, actually sued and won judgments against those who dared question the veracity of his claims. How will society in general look at such a what-we-now-know-to-be terrible act of power and greed?
Will the Lance Armstrong personal brand survive?
I don't know anymore than you do.
But I will be watching, that's for sure.
(Image credit: Getty Images via @daylife)
Named one of the Top 100 Influencers In Social Media (#41) by Social Technology Review and a Top 50 Social Media Blogger by Kred, Steve Olenski is a senior content strategist at Responsys, a leading global provider of on-demand email and cross-channel marketing solutions.

subset: commoncrawl


text:
I'm always pretty honest here. I don't love ASU and, despite being 6'5″, I've only dunked a handful of times. Fastballs don't translate into verticals. And so to get my mind around, and my heart into, re-examining this season – if not that game – I needed some time. A passage of moments to absorb everything that was our (my) last five months. Because my team didn't win and because they were supposed to. Because I watched a season, five months, rest confidently in the hands of Nick Johnson. And then the season didn't quite make it out of his hands. To tell you that I didn't hurt sitting in section 407, row B, seat 4, alongside my brother, would be a Badger faced lie. I hurt, alongside a fan base starving to be in North Texas, watching the most exciting iteration of their team – our Wildcats – fall one point short. Pain.
And in this afternoon there will be departures and returns. Perhaps some coaching changes down the line. New developments that might further dictate our feelings about those five months.
But for now, take a walk with me. Certainly not a run because a run might not let us appreciate things, the actual path. By running, we might get stuck with a singular memory of a ball, in hand, with a backlit backboard, and the wrong score. A run would neglect to recall how we got to Anaheim. So let's walk. Walk to appreciate how we got there and because sometimes it helps to slow things down, make sure that this blog post doesn't become one big :(. Also, my middle name is Walker. Fun fact.
Like any walk, I suppose we'd have to begin by getting off the couch. Of course that's where it all began for me. I was amongst the more than 18,000 streaming a basketball scrimmage on a Saturday afternoon in October. On that day, TJ McConnell played defense. Yes, I was ecstatic to watch a 6'1" Pittsburgher play practice defense. A skill he'd assert 39 more times for my viewing pleasure.
But that was just a practice. We needed, craved, the real thing. And soon thereafter, by a convergence of love, convenience, and coincidence, I celebrated the first two games of the season and my dear friend's wedding. In Tucson. God bless Sunday weddings in November.
Of course the Cal Poly game left something to be desired. The Mustangs (who would eventually win one NCAA tournament game) made eleven three-pointers and raised questions about whether or not the 2012-13 three-point defense was an anomaly or a trend. The Wildcats would go on to allow the 12th lowest percentage of threes in the nation. Opponents would make just 32% of whatever they got.
But Gabe York started, Kaleb Tarczewski grabbed zero rebounds, Jordin Mayes played 4 minutes to turn the ball over 3 times, and the team shot 56% from the line. Was this game foretelling? No, the next game was. An assertion of strength, execution, and we-are-better-than-you up and down the McKale floor.
The tone was set. Arizona would be the most exciting, defense oriented, pace conscious team there could be. At least that's what we wanted. But their mettle was yet to be tested. Not even a win in San Diego meant enough. A stage, The World's Most Famous Arena, was the only place to do it. So they went to Madison Square Garden, forced Jabari Parker into what would be the second worst offensive performance of his collegiate career (by ORtg), and left their scent all over the right coast. Early the following week, Carolina would win in East Lansing.
Four days later, Arizona was the number one team in the country. Back.
What do you think of our walk so far? Months of speculation about whether these Wildcats could shoot, lead, or get over their youthful hump had manifested into the nation's top team. And it was fun. Validation of the previous tribulations that had seemingly set the program back. Number one again.
But this was December. Who cares about rankings – let alone college basketball – in December? The Wildcats had yet to take their toughest trip of the season, a frigid journey to Ann Arbor. I would join them. It become the upset dujour that weekend and perhaps deservedly so. Michigan was a talented squad playing at home. They'd go on to win the B1G and finish a dagger away from their second straight Final Four. Against Arizona, they led for more than 32 minutes. But Arizona won, Brandon Ashley was the best player on the floor during a game featuring countless NBA bound talent, and shit got real. Jim Nantz told me he'd see me in Dallas. I'm serious. The questions weren't about whether the roster could do this or that, tt became, "Are they the best Arizona team, ever?" Jim fucking Nantz, you guys! And oh was it fun.
There were these:
And this:
And more:
There was a game that Washington State scored 7 points in an entire half. They scored just 0.46 points on each of their 54 possessions; twenty-five collective points from a high-major, Division-1 basketball team. That's what Arizona was going to do to you.
And then these guys came up to see me. My team! Their first trip to the Bay Area in two years and I couldn't be more ecstatic. My brother was going to be in town! The Wildcats! What a weekend.
But then it all changed.
The prohibitive favorites, winners of 21 straight and the top team in the land for eight straight weeks (a school record), lost in Berkeley. Sure the score read 58-60 and the court was preemptively rushed. How can an Arizona fan get pissed about that? Irrelevant. It all changed on February 1st when Brandon Ashley broke his foot. At the time, we couldn't really speak of it. The foot failed but the team would not. Adjustments had to be made because there was still season to be played and we had to see Jim in Dallas. We're on a walk here, right? Brandon couldn't walk. It all changed.
And I buried that change, still absorbed by the narrative of January 31st, not February 2nd. Prohibitive favorites and now who knows what? Somberly, we left Haas that night with what felt like a season in flux. A proverbial tipping point. But the season couldn't be buried in one podiatric misfortune. Onward the Wildcats would go. The feeling was buried. The season endured.
Exhibit A was a two-point home win over Oregon. Exhibit B was a hohum dismissal of the Beavers. The next two games would see the Wildcats in three overtimes, escaping with just one win. They lost in Tempe.
It all changed on 2/1 and whatever we buried was soon to bubble up. The aforementioned post-Ashley exhibits were less than encouraging and Colorado's Keg was looming. Arizona had never won in Boulder as members of the Pac-12. Regardless, my buried feelings and tempered expectations flew to Boulder. With a busy mind, it wasn't clear to me what would happen. I should have known better:Colorado didn't record a field goal for the game's first ten minutes and Arizona won by 27. And then they won by 28 and then 13 and again we could believe. We could slip back into Goliath's slippers and feel good in them.
There was a forgettable trip to Oregon before a defensive tour d'force through the MGM Grand Arena. Utah was throttled and Xavier Johnson – who once noted that the Wildcats "weren't that good" – would make just 5 of 21 shots against the Wildcats after that January remark. And this:
Then the Pac-12 championship game – Arizona and UCLA – was every bit the heavy weight battle it was supposed to be. The Pac-12 deserved and needed it. The Bruins punched first, taking it to Arizona's top rated defense like no other team all season. The Wildcats, however, shot back. Raining from beyond the arc before settling into their more typical defensive effort. But when push came to shove – and it did – Jordan Adams hit the biggest shot. UCLA was your 2014 Pac-12 Tournament Champions. He didn't touch the ball.
To this point I haven't mentioned the walk we were on. It had a title, or at least I had one for it, "The Road to Dallas." But this is the hardest part of the walk. The path narrows and the way more treacherous. Sudden death is a possibility. Sudden death is a reality. This is the NCAA tournament. You know all of this and when Arizona's name was called on Sunday, you contemplated how you'd get to San Diego, Anaheim, and Dallas. I did. We toed the waters but never hesitated to jump in. Bring on the challenge.
And a challenge it is. Littered with hyperbolic prose surrounding its uncertainty and glass slippers. Goliaths enter and one exits. But you – we of the red shirts – were behind Goliath. The Wildcats were going to win this whole fucking thing.
And then they didn't.
I had charged down Interstate-5 with my buddy, Jamie – a lifelong Badger, brilliant hoops mind, sports enthusiast, and beer drinker – for Thursday's games. My brother was flying into LA to join. Jamie and I crashed at a friend's Wednesday night, worked from Westwood the morning of, and then invaded the Honda Center. For Jamie, the early game was a breeze. Wisconsin was on to Saturday's game faster than you could say 'On Wisconsin.'
The Wildcats then took Thursday's court and Nick Johnson scored 15 points in the games final 2:45. He made all of the free throws everyone thought the Wildcats would miss to send them packing from this tournament. The dismissal of SDSU evoked little sympathy. Self inflated with a brotastic following dripping with little brotherdom, I couldn't have ushered them out any faster. And they were removed from the game's hallowed event by the right team. The Aztecs gave the West coast a go and the big kids will take it from here. Kthanksbye.
Which of course brings us to Saturday and me next to my brother at the tops of our chairs and lungs. The game itself could be dissected; examined for the minutiae of +/- data, offensive and defensive efficiencies, and probability charts. Ultimately, on the grandest stage where only one advances by any means possible – survival – the Badgers bettered the Wildcats. By one point. It needn't be pretty, you just need to have the extra point.
For Arizona, they didn't have the extra point. That's the hurt stuff.
The kind of stuff that doesn't let you appreciate an Aaron Gordon overtime three-pointer. He of the comically broken shot stepped into a three in the biggest game of his life. Onions. All the game long nothing would fall for the superfrosh. So naturally he grabbed 18 rebounds – nearly a quarter of all available boards in the game – and stuck that three.
It hurts and you maybe don't get to remember when all seemed wrong, when the Arizona offense was operating at a second grade level, why not Jordin Mayes? He was there for the offensive rebound and the lay-in with sixty seconds left. In the three years of data I can access (hoop-math), it's Jordin's only career putback.
That immediate pain might not allow the opportunity to appreciate a moment like TJ McConnell and Nick Johnson hugging at mid-court. I can't finger the exact situation but into a timeout, deep in the contest with the outcome in the balances and punches being thrown back and forth, the Wildcat backcourt embraced in the middle of the Honda Center. It was the kind of scene you expect to see with a Luther Vandross backdrop. Shit, I thought it meant they weren't going to lose.
SPOILER: They did.
I'm late on all of this but I needed to get away from the suddenness of zeros and no more games. As noted I'm honest on here and the flurry of "UCONN!?!?!?!?! REALLY!?!?!?!?" texts into and out of my phone was…abundant? Ubiquitous? Fiery? And all of that heat was promptly followed by an outpouring of everything we couldn't discuss after 2/1. A date we won't forget and can't neglect in reviewing, even appreciating, this season. Goliath down a peg.
Which is the end of our walk. A saunter through five of the most exciting and unique months of fandom I can recall. We felt promising optimism and crippling defeat. I saw triumphant revenge, fierce confidence, and assertions force. We hoped, believed, and hurt. We did it together and that's the overarching importance of sport. 2013-14 was section 407 with my brother; the living room with my best friends; a bar with countless strangers; every arena I entered. In taking this walk, it's my hope that you remember where you were and who you were with for each of the shining moments that were this season.
Those illuminated flashes that define our favorite game are brief because they're shared. If 68 enter and only one leaves, then we have to believe in those shining moments. We can share those and remember when.
The first games begin in November with the promise of a whole season with anticipation for the unexpected and hopeful before us. And then we get caught in a sprint. Running to March in search of the shining moments that just might not come. Everything changed on 2/1 and maybe that's OK? Maybe it's not. It's OK to remember, just don't get stuck in Haas.
And remember this walk, and all the fun you had watching the 2013-14 Arizona Wildcats Men's Basketball team.


text:
Master of Men! The Spider (1991)
A 1981 Kubert School graduate, Timothy Truman is an original artist of both mainstream and independent comic books. He began his career doing backup stories in DC's Sgt. Rock. In the independent scene, Truman introduced the character Grimjack, co-created with John Ostrander in the Starslayer anthology in 1983. The comic was a mixture of pulp fiction and science fiction. His other independent comic was the 1985 series 'Scout', a series set against the background of a post-holocaust United States.
Jonah Hex
Tim Truman continued his career for DC with the revival of the Hawkman character in 'Hawkworld'. The creator's interest in the western genre led him to write, draw and self publish the graphic novel 'Wilderniss'. He continued in this genre with 'Lansdale' and DC's 'Jonah Hex' (both with writer Joe R. Lansdale). With the same writer, Truman created episodes of 'The Lone Ranger' and 'Tonto' for Topp Comics, as well as 'Dead Folks'. He has also done projects for Acclaim Comics ('Turok'), Dark Horse ('Star Wars') and DC ('The Kents').


text:
Over the last few months I have been writing lesson plans for the British Council Teaching English site. Here is a collection of links. All materials are free to use.
Is Slavery a Thing of the Past? [click on the lesson title for lesson plan and materials]
Designed to raise awareness of the UN's World Day against Trafficking in Persons, this lesson begins by asking students to consider what they know about the issue, then takes them through a process of learning more before concluding by asking them about what they have learnt, and how their understanding might have changed.
The lesson involves plenty of speaking, a vocabulary focus, which pre-teaches topic related vocabulary later found in the text, a jigsaw reading and a focus on passives.
The lesson begins by asking students to think of well-known people that they consider to be heroes. It is likely that many of these will be men, so the students then go on to learn about 5 remarkable women in a jigsaw reading activity.
The students discuss these women's achievements, and learn some useful vocabulary for talking about social issues. There is then a focus on relative clauses, before the final task of writing about another female hero, using the vocabulary and relative clauses where appropriate. For a 50-60 minute class the writing stage could be done at home.
Get to know the neighbours [click on the lesson title for lesson plan and materials]
Students are led through a series of activities to create profiles for imaginary characters who live in the same neighbourhood. The lesson then brings these characters together at a neighbourhood party, where students can practice asking and answering simple questions about work, family, hobbies and so on.
As well as developing spoken fluency, there are opportunities to expand vocabulary (personality adjectives) and some useful questions for making small talk.


text:
An enterprising hacking ring has reportedly stolen nude pics and videos from more than 50 female celebrities, including Vanessa Hudgens, Scarlett Johansson and Natalie Portman, and the FBI is on the case. They've also been targeting sports stars and politicians. (Oh, boy.) But who's the mysterious "ringleader?" We've dug up some possible clues.
The infamous Parisian celebrity nude pic blogger DeepAtSea, who recently posted some of these pictures, tells us the person behind the spree is a hacker named "Gook." DeepAtSea was browsing the message board 4chan when he came across Gook boasting about the celebrity hacks. He sent an email to Gook out of "stupid curiosity." "I wanted to know what his motivation [was] and if he knew my blog," DeepAtSea told us in an email. Gook "responded that he didn't know my blog. I asked him if he was afraid to go to jail—he said no."
DeepAtSea says he wants to shoot down speculation that he's in cahoots with the celebrity hacker, stirred up when The Daily wrote about how he had posted the pictures, bragged about being in touch with the hacker, then mysteriously deleted his blog. "I'm just a blogger who loves celebrities… who reposts pictures, mag scans and videos that i find on the net," DeepatSea wrote in a blog post. He told us that he found the nude pictures he posted of The Secret Life of the American Teenager actress Renee Olstead on 4chan, and the pictures of Disney star Vanessa Hudgens on a now-deleted Flickr account named "Sweetmelodies." It seems the hacker is gradually distributing his pictures via the grass roots, rather than selling them to blogs.
As for why DeepatSea disappeared: "if someone like you, is accuse of being a criminal, what would you do?" (DeepatSea is back at a new address.) Anyone know anything about Gook? Who knows which legislators in what stages of undress he's about to unleash on the world. Drop us a line: firstname.lastname@example.com
[Images via Getty]


text:
Defective Medical Devices: Da Vinci Surgical Robot
We Connect You With Experienced Injury Lawyers That Will Fight For You!
If you have been injured by a defective medical device: Da Vinci Surgical Robot, knowing your legal rights can provide both financial relief and peace of mind.
Defective Medical Devices, like the Da Vinci Surgical Robot can cause life-threatening physical injuries and trauma that can include financial damage to victims of negligent drivers. Injured victims must deal with large and unforeseeable medical expenses, loss of wages, pain, suffering and loss of quality of life. Family members also can suffer economic loss, mental anguish and loss of companionship in caring for an injured family member.
We are currently evaluating all defective medical device involving personal injury claims throughout the U. S. Victims of defective medical devices have the right to seek compensation for their injuries, damages, loss of wages, and medical expenses.
Many personal injuries occur due to negligence on the part of one of others involved. When an accident is caused by another party s negligence you are entitled compensation for medical expenses, pain and suffering as well as other damages.
If you or a loved one has been injured by a defective medical device where you feel you may be entitled to compensation, please complete the contact form on the right or call us at 1-888.267.1137 for a free case evaluation. A live personal injury counselor is available to answer your questions 24 hours a day.
Our personal injury lawyers handle all types of accident claims. We also handle every type of personal injury accident claim and motor vehicle accident compensation cases.
TO GET HELP – Our Nationwide Toll Free Injury Helpline Number is 888.267.1137
Time is of the essence when it comes to filing your Personal Injury lawsuit!
All of our experienced personal injury lawyers work on a contingency basis and don t get paid unless you do!
Each State has a strict statute of limitations for you to file your Defective Medical Device lawsuit.
If you or someone you love has suffered a serious injury because of a failed or defective medical device, we can help you explore your full range of recovery options.
Recent Personal Injury Settlements & Verdicts
- $2.6 Million Settlement: Personal Injury Accutane birth defects.
- $2.5 Million Verdict: Personal Injury case involving a surgical error.
- $7.5 Million Settlement: Brain damage after surgery of 7 year-old at Hospital.
- $800,000 Settlement: Infant sustained injury during birth delivery.
- $3 Million Settlement: Cardiology malpractice wrongful death of 45 year old man.
- $1.2 Million Settlement: Man was improperly administered medication causing brain damage.
- $3.1 Million settlement in a product liability/negligence action involving injuries sustain by an infant injured in a shopping cart accident.
- $2.85 Million global settlement of bar fire case, $890,000 to our clients.
- $1.73 Million jury verdict on behalf of iron worker injured in construction site accident.
- $2.1 Million Settlement: Wrongful death Personal Injury hospital's improper discharge of patient.
Personal Injury Facts & Statistics
- There are more than 1 million cases of whiplash reported each year in the U. S.
- Fatal head injuries are responsible for more than 60% of all bicycle fatalities.
- There are over 3 million injuries each year from transportation accidents.
- 2/3 of all bicycle accident reported deaths are from traumatic brain injuries (TBI).
- There were 109 Bicycle accident related deaths in 2009.
- There were 950 Motorcycle crash related traffic deaths in 2009.
- There were 563 Pedestrian related deaths in 2009.
- There were 17,000 truck related accidents reported in 2009.
- There were 90,000 motorcycle related injuries reported in 2009.
- 50,000 bicycle injuries reported each year in the United States.
- 1 million children are injured in bicycle related accidents each year.
- 8,000 boating accidents are reported by the U. S. Coast Guard each year.
- 500,000 truck and commercial vehicles were involved in accidents in 2010.
- The U. S. Department of Transportation reported 33,808 nationwide traffic accident deaths in 2009.
- More than 100,000 motorcycles are involved in crashes each year according to latest data from the NHTSA.
- Motorcyclists are 39 times more likely than passenger car occupants to die in a crash according to NHTSA.
For a Personal Injury lawsuit to be successful, personal injury lawyers have to show that your injury resulted from the negligence of another party. In the case of a Personal Injury lawsuit victims and immediate family members have the right to file a personal injury claim.
Personal Injury Damages
Choosing the right Injury lawyer can mean the difference between getting fair compensation, partial compensation, or no compensation at all.
Need a Personal Injury Lawyer?
If you or a family member has been injured in accident, we can help you start an injury lawsuit against responsible parties.
Our experienced nationwide injury lawyers will help you get just and fair compensation for your injuries.
Call our Injury Toll Free Helpline at 888.267.1137 and get help today!
We can usually tell within a few minutes whether we can help you, and if we can't, maybe direct you to someone who can. We are always accessible by phone, email and online chat.
We are always available to answer your questions with a phone call and will always keep you informed. We will do everything we can to ensure that you receive the highest compensation for your injuries.
If you have a legal question about an injury or wrongful death lawsuit, you don't have to come into our office. Call us, and you'll speak directly to a lawyer, and if a lawyer is not available, your call will be returned as quickly as possible.
Defective Medical Device Lawsuits: Da Vinci Surgical Robot
We Connect You with Injury Claims Lawyers in all 50 States
Choosing the right Injury lawyer can mean the difference between getting fair compensation, partial compensation, or no compensation at all.
Personal Injury Damages: Defective Medical Device
We welcome your questions, and we will to return your calls within 24 hours.
TO GET HELP – Our Nationwide Toll Free Injury Helpline Number is 888.267.1137
24 Hour Call Back Guarantee!
Fill out our free injury case evaluation form and an experienced injury lawyer will call you to immediately start processing your claim at no cost to you.
There is NO CHARGE FOR YOUR CALL OR THE CONSULTATION.
Our goal is to help you get fair and just compensation for your injury, so you can focus on your recovery!


text:
As a true-blue k-fangirl, I have several big k-loves, and I thought it'd be fun to share my love affair with each one with y'all.. Like, how I came upon them, what made me fall for them, why they're so awesome.. You get the idea 😉
These posts are where I do my extended fangirling and spazzing. And share photos (lots of 'em), videos, and various other tidbits about my k-loves.
I have 3 major k-loves, who will each get the spotlight in this on-going series, and then I will move on to more medium-sized k-loves.
Here we go ^^
My Big k-loves:
My biggest k-love of them all: Gong Yoo ❤
Bonus 1: You can join me on my adventure at Gong Yoo's 2013 fanmeet in Tokyo, Gong Yoo Premium Night, here!
Bonus 2: You can find more Gong Yoo goodies here!
And then there's wonderful, delicious Jang Hyuk:
There's also beautiful, beautiful Kim Woo Bin ❤
..And now, the very versatile, oh-so-talented, very beautiful Lee Junho, who's upped and legit stolen my heart:
Bonus! I've got thoughts and screenshots to share, from Junho's fan meeting, Junho The Moment, here!
Medium-Sized k-loves:
In no particular order, my medium-sized k-loves include (but aren't limited to):
The very talented Kim Soo Hyun:
The chameleon-like and very endearing Lee Jong Suk:
The lovely, melty Park Seo Joon:
The talented, beguiling Lee Jun Ki:
The delightfully sweet and charming Hong Jong Hyun:
The very talented, very awesome Hyun Bin:
The fantastically cheeky & talented Lee Seo Jin:
The very talented, very melty Joo Won:
And there's the super talented, spazz-worthy Park Bo Gum ❤


text:
If you are a regular reader of this blog, then you know that my style is pretty much basic. It's all based on my school uniforms from many years ago andon the way my mother dressed me as a young girl.
Ozone Park, Queens, NYC. Easter Sunday. 1959. The checked coat–perhaps this is where my love of classic clothing started. My mother was pregnant. Again. There were four more pregnancies to come.
Plaid. Blazers. Nothing fussy. Timeless. Classic. And fitted.
Plaid. And more plaid!
I prefer a uniform and understated look in my clothing.
blazer, white shirt, jeans = my usual weekend uniform
Flamboyance is not my thing. I'm not a dramatic dresser. Some women of my age group may think I'm boring in my choice of attire—and that's fine because I don't venture out of my comfort zone.
That goes for my choices in cosmetics too. Red lips? They were fine when I was younger, but as I've aged, my lips are not the one feature that has aged to perfection. Cheek color? I love a nice pink but very lightly. And although I love a dark eye, I stick to neutrals.
Contrary to popular belief, red lips do NOT look fabulous on all women. I prefer a more subdued look. I'll keep the red for my nails!
Yeah. I'm a creature of habit.
But something happened recently that made me go out of my comfort zone.
I follow a young woman on Instagram. We started following each other after we were both featured in the Buzzfeed article about Fenty Cosmetics. (Click that link–she's Number 4 and I'm Number 8) Her feed @kate_zilla is great! She's so talented with makeup and her eye looks are absolutely gorgeous.
@kate_zilla you HAVE to check out her eye looks!
Anyway, she offered a collaboration of other Instagrammers to come up with glittery eye looks—glitter shadows had to be used. How could I not pass this up? For me it was a challenge to go out of my comfort zone with makeup. And I did.
However, I did it my way and kept it somewhat neutral. I used shadows that I had on hand that were never used. Here's the look!
On my lids I have a mix of Wet'nWild gold glitter and Too Faced Tigers Eye. I also used Fenty Trophy Wife highlighter and two bareMinerals powder shadows…
The Wet'nWild glitter shadow is so old that I don't even know if it is still in production. It's coloricon C352B, Brass. The photo on the right are the two bareMinerals shadows I used. The top is cultured pearl–a very light pearlized pink. The bottom is True Gold. I used the cultured pearl under my brow bone.
I used Tiger's eye on the corner of my eyes and to line the bottom of my eyes..
I finished off the look with a touch of Trophy Wife on my lids as well!
Some glitter and glitz for the day!
This is a look that'll be used the next time Bonaparte and I go out to dinner!! I'll light up the restaurant!
Honestly, I have to thank Katy for pushing me to out of my comfort zone with this. Earlier this morning I went to the nail salon and everyone said that my face looked very pretty. I'm sure it was because I had a different eye look that just popped out!
My face got a lot of compliments at the nail salon today. And this was taken after I had my lip and chin waxed so the face makeup is a bit wonky!
But that isn't the only way I took a step out of my comfort zone. I purchased an item of clothing that I swore I would never purchase.
It happened when I was perusing the Shein website earlier in the week. In my viewing, I noticed a couple of kimonos. They looked really interesting. Now—I'm not going to say beautiful, because, to me, they truly were items that piqued my interest. Bonaparte's aunt, Danièle wore kimonos and hers were very elegant and she looked chic. The strange thing about this particular article of clothing is that it can look a bit costume-ish if not worn the right way. And I abhor the look of a woman in costume when it isn't either Halloween or a theme party!
This was the first one that caught my eye! And the price of $15 made it more interesting
But I kept going back to this one kimono that was gray (neutral) with designs that were more muted.
I couldn't help myself. I was drawn to this kimono too!
Well, I ended up ordering both–for a grand total (shipping included) of $31.
The gray one was delivered the other day–I'm still waiting for the white printed one.
Worn with a fitted ballet neck tee, this really is a nice look…
This polyester kimono is made in the USA..and although can be machine-washed, I would air dry it!
The one I received– I "modeled" for Bonaparte today. When I explained that I went completely out of my comfort zone with this but liked it, he had nothing but high praise for it.
Actually, I HAD to model it for my husband because my damned selfie-stick broke and he had to snap the pics! I'm loving the way this looks with jeans and metallic heels!
It's out of my comfort zone, but I don't think it is over the top or flamboyant!
What I absolutely love about this kimono is that it'll be perfect during those summer days at the office when the air conditioning is up a bit high, but I won't need a sweater. This is also going to be great for air travel.
I also like the gray color because it'll lend itself so well to wear with black leggings. I think this was a great choice.
What do you think?
Sometimes it's fun to go out of your comfort zone. I'm still a blazer girl but every now and then changing it up can be a good thing!
Today is National Stripes Day! Always a celebration! I'm wearing stripes in a French mode and thinking of my Father-In-Law Dany and Bonaparte's Stepfather Jean. Both loved those striped shirts!
Always inspired by menswear, I'm in my comfort zone in stripes!!
And in keeping with the spirit of classical music, I was listening to Liszt earlier in my car. I'm a sucker for those Hungarian Rhapsodies! Number 6


text:
Desktop Magnifying Glass With Light Table Lamp
₨ 4,799
Buy Desktop Magnifying Glass With Light Table Lamp at Rs.4799/- in Pakistan exclusively at GetNow.pk
- Free Home Delivery All Across Pakistan
- Pay Cash on Delivery 7 Days Return Warranty
- Same Day Delivery in Lahore – Managed by GetNow.pk
- Delivery will be made within maximum 24-48 Hours all over Pakistan after order confirmation.
Contact on Whatsapp
Delivery Options
Free Delivery
above 1500/-
Delivery Time
24 - 48 hours
Return Policy & Warranty
7 days return
No Change of Mind
No Warranty
on this product
Payment Options
Instant order
Cash on Delivery
Mobile Wallet
Easy Paisa/Jazz Cash
There are no reviews yet.
Be the first to review "Desktop Magnifying Glass With Light Table Lamp"
You must be logged in to post a review.


text:
Delaney is working the counter at the Tucson Tamale Company when she hands over a couple of packs of New Delhi and Berkeley tamales. She asks us: "So you like the vegan ones?" Vegan? We don't care about that—we just think they're the best damn tamales we've ever tasted! If Mr. Fantastic set out to re-engineer the tamale, he couldn't match the super-genius of Todd Martin, who has brought true grandeur to the humble and often-neglected tamale. He's put curry, peas and sweet potatoes into the New Delhi; he's put shrimp, roasted corn and tomatoes into the San Carlos; he's even put a hot dog, bacon, onions and tomatoes into the dogmale. Want to go old-school? The green-corn tamales will knock your cape off.
Runners up:
2. Lerua's
2005 E. Broadway Blvd.
Various locations


text:
BETA: This is a new service - your feedback will help us to improve it. Find out more about the beta phase.
Details of this orphan work
These are the known details of this orphan work. If you know who the right holder is for this work, please contact us.
Work details
Thumbnail of still image:
Applicant or licensee name:
King's College, Cambridge
Applicant or licensee country:
United Kingdom
Application number:
Application date:
Status of application:
Licence Expired
Title or short description:
Rupert Brooke standing in the garden at the Old Vicarage, Grantchester, possibly rehearsing for Doctor Faustus.
Full description:One photographic print.
Category:Still visual art
Type of work:
Museum, gallery, library or archive holding the work:
Details and dates of publication, broadcast and/or distribution:
Paul Delany's 'The Neo-Pagans' (1987) and various other relatively modern biographies. The earliest date of publication is not known.
|Free hand outs for live event, exhibition or similar
|Use in a live event, exhibition or similar
|In newsletter, bulletin, e-newsletter or e-bulletin
|In non-commercial promotional material – print and digital
|Digitise and make available on-line, including on social media
|Preservation purposes
|Use on stage or in performance
|Educational purposes – use in learning/ training materials, including e-learning
|Use in thesis/dissertation
|Personal use
Known creators or right holders
Known identifiers
eg International Standard Book Number (ISBN)


text:
Gregg Rosenthal breaks down the six throws that explain Week 9. Marc Sessler alreadyhas broken down the biggest runs.
Just watch Andrew Luck's entire highlight package this week. It's silly. As our home-page editor, Henry Hodgson, notes, Luck converted third downs of 10, 11, 12, 14, 16 and 20 yards against the best third-down defense in the NFL.
My two favorite throws: The 25-yard bullet under extreme pressure to T.Y. Hilton and the play to Reggie Wayne below. Now that's how you ignore the pass rush around you.
Jacquizz Rodgers is an increasingly important third-down weapon for the Atlanta Falcons. I've seen him make defenders miss and break tackles to keep drives alive a lot this year. This missed tackle from Cowboys cornerback Orlando Scandrick is what Dallas' season has been all about. When they have a chance to make a big play, they usually don't.
Prediction: The moment below will be chosen by "NFL Turning Point" this week to define the New York Giants-Pittsburgh Steelers game. It really might be the turning point of the Steelers' season. After their 24-20 win, they're back.
We usually try to spin positive, but Minnesota Vikings quarterback Christian Ponder's struggles for a contending team have become a huge story. He had 58 yards a few weeks ago, struggled against the Tampa Bay Buccaneers and then had 63 yards in a 30-20 loss to the Seattle Seahawks. It is 2012.
Let Doug Martin run wild. Chuck the ball up to Vincent Jackson and Mike Williams. We like this Tampa Bay Buccaneers offensive personality.


text:
Email Generator
Signature Generator converts a text-based e-mail address and creates a picture that can be placed on a web page. Picture contains the email address which can be easily read by a human. Crawlers, which search for e-mail addresses, could not realize such types of emails. Email generator creates an image file which can be read by anyone except robots. Right click on the generated email, choose "Save Image As..." and save the picture to your PC, then upload it to your server.
Each time you post or place your e-mail address a spammer's bot can read it and find you. If your e-mail address is displayed as an image instead of text, special spammers' email harvesting programs would not be able to read it and store email in the spam list.
Email Image Creator could be used to protect your webpages from scanning by robots. Images of email addresses created by E-Mail Generator can be used to replace text email addresses, which you frequently give for public access on your homepage, blog or discussion boards.


text:
Last week, I wrote an item that made what can only be called a highly unflattering assessment of Alabama Senator Jeff Sessions. Sessions touted a study from the General Accounting Office that, he claimed, proved that Obamacare's fiscal assumptions were lies and that the law would increase the deficit. In the item, I argued that the report showed no such thing and was following directed assumptions that its cost containment efforts would fail. I called Sessions a "Wonk McCarthyite," and illustrated his fallacious reasoning with a tongue-in-cheek analogy to my asking the GAO to assume that Sessions were to acquire a nuclear weapon and detonate it in Manhattan, and then touting this report as finding that Sessions was going to murder 4 million people.
Senator Sessions's staff on the Budget Committee has contacted both me and my editor objecting to the item in the most strenuous terms. I have further explored the matter at length and determined that, in my haste, I treated Senator Sessions's claims far too generously. Senator Sessions's combination of ignorance and gross lack of intellectual standards turns out to be even more horrifying than I managed to initially communicate. Calling Sessions a "wonk McCarthyite" implies a level of policy understanding on his part that is wholly unsupported by the facts.
I would first like to concede one point of neglect. The Republican Senate staff objects that my item failed to include a hyperlink to a post by Aaron Carroll, on whose analysis I partly relied. I apologize for the oversight. Sessions's office further contends that Carroll, whom it correctly if incompletely characterizes as "a pediatrician," is not a reliable source on matters of health-care finance. I replied that I consider Carroll, who is also director of the Center for Health Policy and Professionalism Research at Indiana University, and a co-author of the respected health economics blog the Incidental Economist, a reliable source on these matters. We agreed to disagree on this point.
In my haste I also, in addition to forgetting to include the Carroll hyperlink, failed to adequately capture the staggering dishonesty in Sessions's public claims. Sessions claimed that the GAO report demolishes the accounting assumptions of Obamacare:
"The report reveals the dramatic falsehoods that were used to push [the bill] to passage," Sessions said …
"The big taxes increases in the bill come nowhere close to covering the bill's spending. … The big-government crowd in Washington manipulated the numbers to get the financial score they wanted, to get their bill passed and to increase their power and influence."
This is grossly false. The GAO study does not find that the tax increases in Obamacare fail to cover its spending. The study, in fact, does not measure the tax increases at all. It only looks at the costs of the bill, not at the revenue it raises. (As the report says, "Increases in revenue related to PPACA did not affect the long-term assumption for revenue in the Alternative simulation, which assumes that revenues return to the historical average after 2020.") The report assumed, at least in the set of assumptions quoted by Sessions, that all the higher tax in the law disappeared after 2020.
You may be wondering why the report did such an incredibly odd thing. Here is where the unusual dynamics of the situation require some explanation. The Government Accounting Office is a kind of in-house think-tank for Congress and has earned a sterling reputation. Because it is subordinate to Congress, members of Congress can order up reports in order to advance their chosen agenda. And while GAO's analysis is rigorous, Congress can set the parameters of that analysis.
This is the point I was making when I wrote, "the report turns out to be following directions to assume that all of the efforts in the law to control health-care cost inflation fail or are repealed, and the portions that provide coverage are kept in place." The GOP budget staff vigorously objects to this passage in particular. I asked them to send me their request to GAO. Instead, the budget staff sent me GAO's letter to them agreeing to do the report. When I replied that this was GAO's letter to Sessions, rather than Sessions's letter to the GAO, they told me the request had been made verbally and no written record could be found.
I called Susan Irving, the lead author of the GAO report. As you might expect, given the extremely difficult position in which she finds herself, the interview was pretty strange. GAO used two different possible scenarios. The first, which assumed Obamacare is actually carried out as written, shows it would substantially reduce the long-term deficit. But the report also used a second scenario, which GAO has used in the past, making more pessimistic assumptions, such as that future Congresses would pass new laws canceling out the cost-control provisions in the law. The main point of the paper was that its success in controlling costs depended on how well Congress stuck with the cost controls in the law — which is axiomatic, obviously. "There's not much news here," she told me.
But part of that pessimistic scenario also assumed that tax levels would revert to their historic average. Because the law was largely financed through new taxes, this meant it assumed zero effect after 2020 from the taxes in Obamacare. Obviously, since a big part of the law's savings come from new taxes, choosing to ignore the taxes would make it look like it increases the deficit.
Irving repeatedly told me, "This is not a projection." And of course it's not a projection — you can't analyze the effect of a bill on the deficit while ignoring the impact of its biggest source of savings.
What I wanted to know was why GAO used this method — why examine only the costs of the bill and not its net effect on the deficit? GAO's letter to the Republicans on the committee promised the report would be "a general estimate of the effects of the coverage provisions in PPACA." But "the coverage provisions" sounded like it meant just the parts of the bill that expand health-insurance coverage — that is, GAO would measure the cost of covering uninsured people, but not the savings that help pay for it. I asked Irving if this is what "coverage provisions" meant. She told me, "We were asked to look at the coverage expansion." Asked, that is, by the Republican staff.
This didn't really answer the question, so I kept pressing, and she kept offering up the same answer. When I told her this didn't seem to answer the question, she replied, "You have been a reporter long enough to know why I am repeating something verbatim."
In any case, a few things are clear. Sessions' request is not on record, but GAO agreed, in response, to publish a study that would measure the costs of Obamacare but not its net effect on the deficit. The GAO knew this, and then Sessions falsely claimed the study concluded something completely at odds with its actual findings.
In sum, I apologize to my readers, the citizens of Alabama, budget fans, and other concerned citizens for failing in my original post to adequately convey the full paucity of the intellectual standards of the junior senator from Alabama. I hope I have rectified my failure here.
This piece has been updated throughout.


text: For that added protection during those unsure moments, Injen Technology's HYDRO-SHIELD PRE- FILTERS are race proven material manufactured from highly durable polyester. Uniform micron openings allow the filtering of debris .005" or larger. The HYDRO-SHIELD PRE-FILTERS are factory treated using an embedded hydrophobic process, which offers consistent airflow, water repellency and maintains horsepower gains. (Please note that this item is water repellent, not water proof) Snug and secure.


text:
The current Swine Flu pandemic headlines read like those flashing through the intro sequence of a post-apocalyptical movie. Now you can see the cases spreading in real time—as the WHO declares them—in Google Maps. Updated
In case you have not been paying attention to the news during the last few days, there's a pandemia going on. A spike of infections of the H1N1 Swine Flu—a mutation of a pork virus that jumped from pigs to humans—happened in the city of Mexico (103 dead already) and it is quickly spreading through the world now, thanks to airline connections.
Reading the map is very simple:
We are all going to dieThe pink markers are suspect, the purple markers are confirmed, and deaths don't have a black dot in the marker. The yellow markers are negative, but I don't see any.
Have fun watching. While you can (added another map, which is getting updated faster.)
Click to view
View 2009 H1N1 Flu Outbreak Map in a larger map
Click to view
View H1N1 Swine Flu in a larger map
Click to viewP.S. Stupid Apophis can't reach us in time! Hahahaha. Ha. But it looks like pigs are getting their revenge for all these centuries of crispy bacon and pork buns. [Google Maps]
Bonus post soundtrack:


text:
Thursday, August 27, 2009
Work in Progress and Jaffa Cakes
26 comments:
Oh delicious Rita! Gorgeous selection!ReplyDelete
those colors are perfecto!! Ilove the combinationReplyDelete
Can I come live in your stash? Fabulous.ReplyDelete
Wow beautiful colors! Reminds me of the 70's and the wallpaper on our kitchen:-)ReplyDelete
You must have a truly wonderful stash!
Rita, your stash must be a magical place indeed. i would like to come and gaze upon it's magnificence (whilst trying to stifle the urge to roll around in it, lest I look slightly nuts). *sigh*ReplyDelete
Inspired :-)ReplyDelete
But now I'm craving Jaffa cake biscuits and a packet of Jaffas to roll down the aisle at the cinema!
- AnonymousAugust 27, 2009 3:31 PM
I love Jaffa Cakes!ReplyDelete
What a great idea for a colour combination!
I miss Jaffa cakes! I'm so hesitant about orange in quilts, but calling it a Jaffa cake makes me reconsider, lol.ReplyDelete
Ooo! Squeeeeeee! Loving those colours. Thanks, purchased a lovely brown and cream fat quarter on the weekend NOW I know what towork towrads with it ;-)ReplyDelete
wow,amazing color combinations...ReplyDelete
Home Security Systems no CREDIT CHECK everyone is approved
Love the colours together! And now I want a Jaffa cake... You're making miss Australia!ReplyDelete
I have always loved the choc orange combo.ReplyDelete
jaffa cakes are a great inspiration! Do you not get them over in Aus? If not that is an absolute travesty and I think something that should be addressed in parliament!!!ReplyDelete
Oh I love those colors!!!ReplyDelete
The color combo on this one is terrific! Sure to be hit!ReplyDelete
you create the most adorable and lovely quilts...i can't wait to see this one finished...i just LOVE orange...and i'm sure as quick as you are at finishing projects (*i'm so jealous by the way*)...i won't have to wait long!!ReplyDelete
OH Jaffa Cakes!! I fell in love with them when I studied abroad over in London and Scotland a few years ago! I even brought a couple boxes home with me, because we don't have anything like them here in the States. But I did just find something like them at the grocery store this week. I'm hoping they are the same! Can't wait to see the finished product!ReplyDelete
what a sweet way to remember something that looks so tasty!!! i love the color plan...those always look great together, and you are a genius with quilts so there is no way this can go wrong.ReplyDelete
You know me, I love food inspiration!ReplyDelete
I've never had a jaffa but they sure look yummy. I can't wait to see your Jaffa quilt.ReplyDelete
Your stash rocks! I need to get out and do some shopping. I can't wait to see the quilt done!ReplyDelete
- AnonymousAugust 28, 2009 10:45 PM
Wow I can't wait to see this one!ReplyDelete
What a wonderful selection. I can't wait to see the finished project!ReplyDelete
Ms Robin Blake
i love the fabric selection you came up with and i look forward to seeing what you make!ReplyDelete
What an incredible stash you must have! Its going to be gorgeous!ReplyDelete
I'm so excited, I just found your blog for the first time! yay, I'm loving it. The men are watching the football and I'm snuggled up reading your blog - a great Friday night! Love your work ;)ReplyDelete
Thank you for stopping by and leaving a comment! I really appreciate it.
Comments are published after review.
Feel free to ask questions and I will answer either here or by email, as is appropriate.


text:
Aug 4, 2009
A visit with Susan @ A Southern Daydreamer will be time well spent. You can see all the different Outdoor Wednesday posts.
These photos were taken over the last 12 days up around our cabin in the Princeton area. Ignore the date on the camera as my BB guy has no idea how to change the date and it is his work camera.
These guys range in age from 13 to about 57 years old but they still have one thing in common. They love the outdoors. Our sons were not there but our friend was there with his young son and our other friend was there with his grown son.
They eat like kings (I taught him everything he knows about cooking) and they travel through the mountain sides on roads that trucks can't get through. And they have fun. Dirty, grimy fun.
Well that is all I can say because you couldn't pay me enough to go along on one of these rides.
15 comments:
Lucy, what fun you must have doing laundry caked with mud! *big smile* Gorgeous scenery, though...ReplyDelete
hugs, Ethel
OMG Boys and their Toys - don't blame you for not wanting to join in. My son used to take over the laundry room last year when he lived here after one of his bike weekends.ReplyDelete
Meeting for coffee is so civilized!! Mom reminded me to stop at Hopcott for fresh corn - hope they have some on Saturday.
- AnonymousAugust 5, 2009 at 4:35 AM
Uggh, the first thing I thought of when I saw these pictures was... clothes are going to a laundromat - there would be no way I'd let all that back in my home! Hose the boys off in the driveway! Give em a scrub brush & a beer & have at it!ReplyDelete
Ahhh...the testosterone. That looks like an adventure that would make my 16 year old dare devil son sooo very happy. Better not show him this post.ReplyDelete
Becky K.
Hospitality Lane
Only one of those mud puppies belongs to me. The rest will have to figure out their own laundry issues.ReplyDelete
The funny part is they were up there for several days. I don't want to know what kind of smell was coming off their clothes by last day.
see, now this is my perfect example of boys and their toys and it makes NOOOO sense to me :)ReplyDelete
TTFN~~Claudia ♥
Hahahaha... getting dirty! Man's favorite sport. (And I have no double meaning in there!)ReplyDelete
Great mud! Cass
I suspect they had a great time man camping. The pictures are a hoot. Good luck with the laundry.ReplyDelete
- AnonymousAugust 5, 2009 at 8:15 AM
It's a beautiful place! Why do men love to roar around in mud? It's some sort of primeval thing isn't it? I once had a pig that used to do the same thing sans motor and clothes.ReplyDelete
- AnonymousAugust 5, 2009 at 8:46 AM
Looks like they had a ball!!!!!ReplyDelete
Donna Marie
I hope to chat about your genealogy research one day! I managed to trace my family (paternal side) back to 1754. I plan to write a book one of these days on my family history!
A fun ride. Great post.ReplyDelete
What a fantastic place to ride quads - Yep even a girlie can aspire to get dirty occasionally (no I'm not being rude!)ReplyDelete
It's a shame the lovely scenery had to be spoiled by the noise of the machinery, but what fun!
Yes I am living in rose coloured glasses land - WHAT LAUNDRY?? Does it still have to be done if you chose not to notice it LOL
Men will be boys.ReplyDelete
- AnonymousAugust 6, 2009 at 8:15 AM
Very cool! I would absolutely LOVE this trip!ReplyDelete
You must have enjoyed that vacation. Seeing the pictures makes me want to go there. It's like anyone who wants adventure will have a blast on that place. It's a good thing that the boys love outdoors. They appreciate what nature has to offer.Thank you for sharing the photos. Really great.ReplyDelete
Thank you for taking the time to leave a comment. I appreciate every one of them and respond to all.


text:
SRD:Sutra of Tranquil Thought
From D&D Wiki
|This material is published under the OGL 1.0a.
Sutra of Tranquil Thought: This monastic tome describes ancient techniques of mental focus and is highly prized by psionic practitioners. If a psionic character who is not evil studies the work during one week of solitary contemplation, he gains 17 bonus power points and experience points sufficient to place him halfway into the next level of experience. Those who use their powers for evil are punished for their impertinence, losing 5d6 x 1,000 XP for defiling the book. In addition, an evil reader must make an immediate DC 15 Will save or become permanently confused as if affected by the insanity power. Only psychic chirurgery or similarly extreme measures can restore sanity.
The minds of nonpsionic beings are too clouded to benefit from the secrets of this book. To anyone without psionic aptitude, the book's pages appear to contain nothing but elaborate patterns and drawings of mysterious beings. Once it is read, the book vanishes into the Astral Plane to an unknown destination. Even if it is found again, the same character cannot benefit twice from perusing its contents.
Strong telepathy; ML 20th; Weight 3 lb.
Back to Main Page → 3.5e Open Game Content → System Reference Document → Psionic Items


text:
If you have a buy position, for example, on a company which announces a dividend, your account will be credited/debited prior to market open on the day the stock goes 'ex-dividend'. Here's a typical example:
Please note that the amount you are credited or debited will be subject to the relevant tax holding rates according to the region in which the share is listed.
When a stock goes ex-dividend, ignoring other market forces, the value of that stock effectively falls by the dividend amount. In most cases this will in turn cause the index value to drop since the value of the index is calculated from the value of the stocks within it. The amount that the index drops is dependent on the weighting of the stock within the index. If more than one constituent stock of an index goes ex-dividend on the same day, we will add the amount of points each stock will cause the index to drop by together to calculate the total dividend amount in relation to the relevant index CFD offered by us.
In the event that a listed issuer of a security (on which you hold an open CFD position with us) announces a share sub-division or share consolidation, or makes changes to its capital structure by way of rights issues, bonus issues or cash dividend payments, we will make an appropriate adjustment on the relevant listed share CFD on the ex-date or the corporate action effective day.
With a rights issue, a company will offer its shareholders a chance to buy newly issued shares, usually at a discounted price, before they are offered to the public.
Price adjustments may be applied to your account where you are holding positions on relevant CFD shares or cash indices.
How do company stock splits affect my account?
Stock splits are usually undertaken when the value of a company's stock is becoming too high. The company will essentially offer more stocks in the company but at a lower price. Here's a typical example:
As you would have benefitted from the artificial price movement at the time where in fact you shouldn't have, the equivalent amount is debited from your account in order to offset this. Overall, you do not lose or gain anything due to this price adjustment.
Learn more


text:
Tappan Zee Bridge at dusk.
Promenade on the Hudson River at dusk.
Tappan Zee Bridge at sunset.
Sailboat passing the Sleepy Hollow Lighthouse.
Sailboat on the Hudson River, with Rockland County in the background.
Tappan Zee Bridge with sailboats on the water.
Sunset on the Hudson River.
Sunset sail on the Hudson River.
Hudson RiverWalk at sunset.
Sailboats on the Hudson River, at sunset.
Sleepy Hollow Lighthouse
Sleepy Hollow Lighthouse on the Hudson River.
Tappan Zee Bridge, up close, at sunset.
Ripening apples in the Hudson Valley- a signal that muggy summer days will soon give way to crisp fall moments.
Pretty courtyard at the Boscobel House and Gardens in Garrison, NY.
Sometimes the best thing about a path is not knowing what's around the bend.
Tea for two... maybe two fairies. Something about this table and chairs is inviting and magical.
A misty view of the Hudson River view from Boscobel House in Garrison, NY.
A view of the Hudson River on a muggy, misty afternoon.
Fall colors over the water, Hudson Park.
Fall color grace a park path as autumn comes to New York.
Trees for a chorus line along the rocky shore.
Hilly, winding path through the fall leaves at Hudson Park, New Rochelle, NY.
I'd say this tree is 50% ready for Fall. The rest of her leaves will turn, soon, too.
A change of direction offers a change of perspective.
A path lays before you in the gathering dusk; which way will you roam?


text:
Canada Place is one of the most recognized spots in Vancouver and is located next to the new Convention Center which was completed in 2009 at a cost of CDN900,000,000 - twice the original projected cost.
The 10 'sails' on the roof, 5 on the East side and 5 on the West side, represent the 10 provinces of Canada.
The capital of Canada is Ottawa, in the province of Ontario. There are offically ten provinces and three territories in Canada, which is the second largest country in the world in terms of land area.While politically and legally an independant nation, the titular head of state for Canada is still Queen Elizabeth.On the east end of Canada, you have Montreal as the bastion of activity. Montreal is famous for two things, VICE magazine and the Montreal Jazz Festival. One is the bible of hipster life (disposable, of course) and the other is a world-famous event that draws more than two million people every summer. Quebec is a French speaking province that has almost seceded from Canada on several occasions, by the way..When you think of Canada, you think of . . . snow, right?But not on the West Coast. In Vancouver, it rains. And you'll find more of the population speaking Mandarin than French (but also Punjabi, Tagalog, Korean, Farsi, German, and much more).Like the other big cities in Canada, Vancouver is vividly multicultural and Vancouverites are very, very serious about their coffee.Your standard Vancouverite can be found attired head-to-toe in Lululemon gear, mainlining Cafe Artigiano Americanos (spot the irony for ten points).But here's a Vancouver secret only the coolest kids know: the best sandwiches in the city aren't found downtown. Actually, they're hidden in Edgemont Village at the foot of Grouse Mountain on the North Shore."It's actually worth coming to Canada for these sandwiches alone." -- Michelle Superle, VancouverText by Steve Smith.