Received: by 10.142.76.3 with SMTP id y3mr789082wfa.54.1298874304195;
        Sun, 27 Feb 2011 22:25:04 -0800 (PST)
X-BeenThere: silverstripe-dev@googlegroups.com
Received: by 10.143.178.9 with SMTP id f9ls3294901wfp.0.p; Sun, 27 Feb 2011
 22:25:02 -0800 (PST)
Received: by 10.142.241.17 with SMTP id o17mr781485wfh.41.1298874302503;
        Sun, 27 Feb 2011 22:25:02 -0800 (PST)
Received: by 10.142.241.17 with SMTP id o17mr781484wfh.41.1298874302479;
        Sun, 27 Feb 2011 22:25:02 -0800 (PST)
Return-Path: <s...@silverstripe.com>
Received: from mail-px0-f175.google.com (mail-px0-f175.google.com [209.85.212.175])
        by gmr-mx.google.com with ESMTPS id k41si3405086wfa.7.2011.02.27.22.25.01
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 27 Feb 2011 22:25:01 -0800 (PST)
Received-SPF: pass (google.com: domain of s...@silverstripe.com designates 209.85.212.175 as permitted sender) client-ip=209.85.212.175;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of s...@silverstripe.com designates 209.85.212.175 as permitted sender) smtp.mail=...@silverstripe.com
Received: by pxi17 with SMTP id 17so552058pxi.6
        for <silverstripe-dev@googlegroups.com>; Sun, 27 Feb 2011 22:25:01 -0800 (PST)
Received: by 10.142.144.4 with SMTP id r4mr4038768wfd.76.1298874301698;
        Sun, 27 Feb 2011 22:25:01 -0800 (PST)
Return-Path: <s...@silverstripe.com>
Received: from sminnee.silverstripe.com (router.silverstripe.com [202.160.48.160])
        by mx.google.com with ESMTPS id z1sm5508564wfd.21.2011.02.27.22.24.59
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 27 Feb 2011 22:25:00 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: [silverstripe-dev] Re: Sapphire / CMS Split
From: =?iso-8859-1?Q?Sam_Minn=E9e?= <s...@silverstripe.com>
In-Reply-To: <AANLkTikO+gLAzrEHvzz9WeYJAxpPSH9r97QvdH=s+5kJ@mail.gmail.com>
Date: Mon, 28 Feb 2011 19:24:56 +1300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4588D921-115D-47E7-A9FF-798907AE4...@silverstripe.com>
References: <2B5A2EA5-3DFD-421B-9916-E89BC2C98...@silverstripe.com> <f6da9e7d-eb9d-4740-8ef4-6dbc975ee...@u24g2000prn.googlegroups.com> <7789B680-6E88-4E9B-8385-B69107B51...@gmail.com> <FE40A47F-B13A-49E9-ADD8-EEA6FB040...@silverstripe.com> <A74E2B50-B922-434D-8CE3-748AE4568...@gmail.com> <AANLkTikO+gLAzrEHvzz9WeYJAxpPSH9r97QvdH=s+...@mail.gmail.com>
To: silverstripe-dev@googlegroups.com
X-Mailer: Apple Mail (2.1082)

I'm a little hesitant to fracture the codebase any further than breaking =
things into sapphire and cms at this stage, because

 - the module manager is still a theoretical entity and I don't want to =
rely on it just yet
 - i don't want to create another git repo; we already have too many!

However, I am thinking that it would be worth structuring our files such =
that the content of sapphire/core could be used as this stripped down =
framework, and potentially we have some kind of build process to create =
a Sapphire Core package from it.

On 28/02/2011, at 6:12 PM, Marcus Nyeholt wrote:

> The purist in me says to separate the LeftAndMain and especially the =
SecurityAdmin stuff outside of Sapphire - the UI should just be a way of =
doing things that you can do in the underlying APIs of sapphire anyway. =
You should be able to specify the same permission sets via code as you =
can via the UI (well, you'd hope that the UI just interfaces to the same =
code APIs).=20
>=20
> The realist in me says that it's probably rare for someone to develop =
a Sapphire application and not want these parts as Sam has mentioned, =
and would rather make life easier for these 90%.
>=20
> Cheers,
>=20
> Marcus