Changing component layering to allow more efficient dependencies
Marking several interfaces and services obsolete to produce warnings
Changing ITheme to FeatureDescriptor as a first step
--HG--
branch : perf
extra : rebase_source : 905b69eb1cc6ed05750908e41a2d0846dde22001
For convenience, so widgets can be moved to disabled rather than deleted
--HG--
branch : dev
extra : rebase_source : 36d5a75b58182c593ec690a015d77296c7ca02c0
Components that control using() scope for work context will also indicate transaction cancelled when an exception passes out of that scope
See http://orchard.codeplex.com/workitem/16604
--HG--
branch : dev
extra : rebase_source : 2d53cdbea1e9dd7ceb022f781621b01bb1f95a87
If lambda takes an argument, it is dynamic, and is an uninitialized shape of the named type
ShapeHelper and IShapeHelperFactory are obsolete - IShapeFactory itself is now dynamic
--HG--
branch : dev
Enabled Module and Theme Placement.info files are parsed, and influence the location of certain shapes
This only applies to part or field shapes that are added by returning ContentShape(...) from a display/editor driver
--HG--
branch : composition
extra : transplant_source : %CF%B0%17%E1%18%C1%06o%B2%91a%23%A1%3D%872%BE%F8%01%F3
ContentShapeResult.Apply calls through the context.FindPlacement to acquire placement location
DefaultContentDisplay component wires the FindPlacement onto the ShapeDescriptor.Placement
ShapeDescriptor.Placement func contains the chained per-theme rule stack for part shape placement
Next up - simple Placement.txt parser to convert rules into Placement chain
--HG--
branch : composition
Built-in zones need to be created with names
Binding and shape dictionary is now compare-ordinal-case-insensive
ZoneName is quirky - because it is an actual property some of the inline assignment mechanisms don't work as expected.
Main content area is salmon
--HG--
branch : dev
Shape specific events can be hooked with ShapeDescriptor Displaying and Displayed delegate arrays
Events for every shape can be hooked with IShapeDisplayEvents Displaying and Displayed methods
--HG--
branch : dev
ShapeMetadata.Alternates may be accumulated at any time after the shape is created
Most recently added alternate has highest priority
Alternates may target longer shape variations by appending something context specific to the base name
The alternate may match a shape binding name that is part of a different descriptor
--HG--
branch : dev
extra : rebase_source : 864892c019dbf2a7bd1c33c71bb01be3068b5081
IShapeProvider interface was not needed.
[ShapeAttribute] on methods is used instead.
--HG--
branch : dev
extra : rebase_source : 7d06d714281c48bed13a774303623ab9e1c5225b
The only thing it contained was done in a way that is very out of date
No reason to port it - would be cleaner and easier to create new sandbox module if needed
--HG--
branch : dev
Adding a back-reference from ShapeBinding to ShapeDescriptor
Changing HomePage display type to default ("_HomePage" will be indicated in a different way)
Moving IShapeFactoryEvents into its own file
--HG--
branch : theming
ShapeType and BindingName are treated as two strings
Shorter string broken at first delimiter is used as registered ShapeType name
All alterations of the same ShapeType are accumulated into the same ShapeDescriptor
--HG--
branch : theming
The same descriptor has all variants registered in the bindings collection
The descriptor is registered in the table under each of those names
--HG--
branch : theming
Removing unused IShapeTableFactory
ShapeTableBuilder has default Feature - components describing shapes from their own module do not need to pass feature in
Fixing some tests
IShapeDescriptorBindingStrategy becomes IShapeTableProvider
--HG--
branch : theming
ITagBuilderFactory returns a TagBuilder populated html related things taken from the shape
Updated zone/menu/menuitem shapes to use that service
Menu and menu item removed from TheAdmin to allow core\shapes rendering to show through
--HG--
branch : theming
Need to enumerate display types
Adds a diagnostic <div> to devtools that wraps everything being rendered with it's shape name and location
--HG--
branch : theming
Adding the ability to bind a method with a TextWriter Output parameter
Bringing over work from UnorderedList
Parameter bound with GetMember instead of array access to be compatible with base class properties
--HG--
branch : theming
A few details of Layout/Document/Zone shapes are described
Three utility shapes are provided as [Shape] methods
An IOrchardViewPage interface is introduced to ensure all base view classes have the same minimum number of methods and properties available
--HG--
branch : theming
Continued work towards making zone classes obsolete
Shape table construction per theme
Adding display helper to webforms view classes
--HG--
branch : theming
Louis DeJardin