Hey everybody,
I've created two detailed tickets to deal with the sapphire/cms split:
http://open.silverstripe.org/ticket/6519The reason we're doing this now is to avoid breaking mergebacks from topic branches (which will become
more numerous as SS3 development progresses).
We're about halfway there already (thanks Paul Meyrick for helping out there), see topic branches on my git repo:
Highlights:
* Moved SiteTree, SiteConfig, ErrorPage ContentController, ModelAsController and related features to cms
* Moved translatable to own module
* Moved widgets subsystem into cms - they're (not very tightly) coupled to SiteTree, and typically used in a website context
* Replaced unnecessary test dependencies on SiteTree
* Some class_exists() hacks where functionality couldn't be moved easily
To check out sapphire without CMS, simply remove the CMS folder and Page.php from the sample silverstripe-installer project.
I've got the unit tests passing both with and without sapphire.
The second part (described in #6520) will move files the other way: from cms to sapphire.
Questions:
* What should the default (root) response look like in sapphire if we don't have a Page.php or a Page.ss/theme?
We could put in a specific template detailing how to add routes (I think Django does that), which would be targeted at developers.
* Do we encapsulate image selection/insertion/upload in HtmlEditorField to allow it in ModelAdmin/sapphire even when no AssetAdmin is available?
Given that AssetAdmin and image selection UIs in the new design drafts look very similiar, this will be a challenge.
* How about link insertion in HtmlEditorField without having SiteTree available? I don't see a good way to provide an out of the box experience here (other than inserting raw URLs)
* Any reason we can't make ReportAdmin a new module? Its rarely used as such (in contrast to the "side reports" which are baked into the CMS UI)