So I'm considering multiple roads ahead, and I have some difficulty deciding on which path to choose first.
I've been polishing and wrapping up the current state, and am on the verge to release just released a package on our. It doesn't have the velocity it deserves atm, 'cause I'm also moving into a new house, but please bear with me. However, it is in a state where I could accept the other pull request, if done with style. ;)
So here's the current plans, not necessarily in implementation order:
1. Add attributes for document-, media- and property type information as an alternative to the current BCL attributes and fields.
2. Create a supplemental (!) project / package with
* A new base page for MVC views replacing the dynamic CurrentDocument with a generated / code-first typed model
* A factory for the models (using some convention)
* A new "default" controller feeding the typed model to the view
*(I've got the above code, but it'll take some polish to make it a package)
* Different base classes to use for roots.
* one also implementing IPublishedContent
* one exposing it as a property "Content"
* Another or both the previous wrapping IPublishedContent in an adapter so it's easier to unit-test some of the tightly coupled extensions
3. Fluent configuration of the generator and parser
4. More documentation and a tutorial
5. Video walkthrough of usage
And that's it for now.
Suggestions / wishes / criticism?
Lars-Erik
↧