8 Oct
2013
8 Oct
'13
3:29 p.m.
On Oct 7, 2013, at 11:30 AM, Damien Cassou wrote:
On Mon, Oct 7, 2013 at 10:15 AM, Diego Lont
<diego.lont(a)delware.nl> wrote:
Damien,
I do not understand your mail.
Pier-Model depends on Magritte Core. And Pier-Seaisde depends on Magritte Seaside. And
other display-layers then Pier-Seaside are possible as well and when they are stable
enough we should add them to Pier, and not the other way around. At least, that is what I
think. But I have the feeling this is not about the display of Pier, since you name
Markdown.
But maybe you want to isolate the part that Pier uses to parse its CMS? Currently
Pier-Model has a PRDocument parser integrated into Pier-Model-Document itself. It might
make sense to extra this part, so you can exchange this for Markdown and also the other
way around.
Cheers,
Diego
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
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki