7 Oct
2013
7 Oct
'13
11:30 a.m.
On Mon, Oct 7, 2013 at 10:15 AM, Diego Lont <diego.lont(a)delware.nl> wrote:
If you take the configuration of Pier3 and load it
by:
ConfigurationOfPier3 project stable load: 'Pier-Model'
it loads Pier-Model, Pier-Pharo-Model and Magritte Core. This means there is no Seaside
loaded then. So I think you do not need a separate configuration and / or project.
I understand (and understood) what you are both saying: technically, I
don't need a separate project. That's for sure. But technically, Pier,
Magritte and Seaside don't have to be separate projects as well,
right?
I think it would make sense to separate the wiki (that can be used in
many projects) from the CMS. Not because there is a technical problem
having both in the same place. But because developing, testing, and
depending on the wiki will be simplified. If you think about
communication, a concurrent to Markdown cannot be "Pier", because Pier
is much larger. However, "Pillar" is a concurrent of Markdown.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill