Sheill
David D. Sheill, White Lake, MI US
Patent application number | Description | Published |
---|---|---|
20100283301 | RECLINER MECHANISM - A vehicle seat is movable between a first position to a second position and includes a seat back, seat cushion for coupling to a track adjuster for use in a vehicle. The vehicle seat includes a recliner mechanism coupled to the seat back and the seat cushion. The vehicle seat further includes a stow mechanism coupled to the recliner mechanism and an easy entry mechanism coupled to the recliner mechanism and stow mechanism, wherein, when the stow mechanism is actuated, the easy entry mechanism is not actuated and when the easy entry mechanism is actuated, the stow mechanism is not actuated. | 11-11-2010 |
Pete Sheill, Mercer Island, WA US
Patent application number | Description | Published |
---|---|---|
20080222598 | Using a system of annotations to generate views and adapters - Various technologies and techniques are disclosed for using annotations in contracts to generate views and adapters. A framework is provided that supports annotations that can be used in a contract to allow a user to express how one or more members of the contract should be represented in at least one view, and to express how to adapt the members in at least one adapter. Annotations can also be used to indicate which of the components should be programmatically generated. The contract is accessed and at least a portion of the at least one view and the at least one adapter are generated based on the annotations and other information contained in the contract. For example, source code can programmatically be generated for a host side view, an add-in side view, a host side adapter, and an add-in side adapter using the various contract details and the annotations. | 09-11-2008 |
Peter H. Sheill, Mercer Island, WA US
Patent application number | Description | Published |
---|---|---|
20090006629 | Instantiating a communication pipeline between software - An embodiment not only instantiates a pipeline that allows communication between first and second executable nodes regardless of whether the nodes have compatible or incompatible interface views, but also structures the pipeline based on the relationship between the interface views so, for example, the pipeline does not consume unnecessary overhead or introduce unnecessary data-transfer delay. For example, an embodiment compares a first interface view of a first executable node to a second interface view of a second executable node. A first communication pipeline having a first structure is instantiated between the first and second nodes if the first view has a first pre-established relationship to the second view, and a second communication pipeline having a second structure is instantiated between the first and second nodes if the first view has a second pre-established relationship to the second view. | 01-01-2009 |