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
- Includes changing display-related implementations (drivers & views) to work with shapes
- Editor implementations still on the old template model
- Orchard.Blogs is currently using a different display type instead of specifying alterations (for Blog and BlogPost)
--HG--
branch : dev
- content title added to the item shape (@Model.Title)
- some rough content item shape structure - needs real body zones and footer (need header @ footer markup at least as zone wrappers in a way so if there is nothing in the zone the tags aren't rendered)
- page title usage back in the picture though (impl.) not really touched
- contents and routable display type actions all falling back to the core shaped "Display" view
--HG--
branch : theming
Many modules are disabled by default to keep them out of the way for now. Run through the setup and hit ~/Contents/Item/Display/3 to get the homepage page
--HG--
branch : dev
extra : transplant_source : %8EH%F5%06%12%1D%3D%FC%7Bl%D6p%CF%DB%DAp%BF%1C%DB%A5
Verify consistent use of descriptor and blueprint
Update namespaces, but not folder paths, of same
Add small ISignal component for explicit app-triggered cache expiration tokens
--HG--
branch : dev
Contents/Item/Display/{Id} to show published
Contents/Item/Preview/{Id} to show latest (draft or published)
Contents/Item/Preview/{Id}?Version= to particular numbered version
{*Path} in Routable/ItemController.Display to show published where {Path}=RoutableRecord.Path
--HG--
branch : dev
