 |
From: Sam Minnée <s...@silverstripe.com>
Date: Tue, 1 Mar 2011 09:06:56 +1300
Local: Mon, Feb 28 2011 3:06 pm
Subject: Re: [silverstripe-dev] Re: Sapphire / CMS Split
Can we get some explanation of the kinds of projects that you would see yourself building that would make this split logical? I don't think a +1, -1 argument based on everyone's gut feel is the best way forward. For those of you arguing for a leaner core, what about the whole form system? It certainly defines a lot of UI, does that need a separate module too? I only ask this rhetorically, because to remove the form system would whittle Sapphire down to pointlessness. We're still want to have a system that is a good choice for application development. The really-lean framework - no forms, email handling, rest API, security, or UI - would be used only in exceptional cases; if you want that you can get sapphire/core Remember, people: this is a pragmatic and not an ideological debate. We need to be putting *use-cases* on the table! On 1/03/2011, at 6:19 AM, "Peter Bacon Darwin" <bacondar...@googlemail.com> wrote: > +1 to Uncle Cheese. Just provide the Security Admin in its own module then people can choose to use it in their Sapphire projects as needed.
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||