Return-Path: Delivered-To: apmail-lenya-dev-archive@www.apache.org Received: (qmail 44797 invoked from network); 3 Jul 2009 14:30:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Jul 2009 14:30:29 -0000 Received: (qmail 52175 invoked by uid 500); 3 Jul 2009 14:30:39 -0000 Delivered-To: apmail-lenya-dev-archive@lenya.apache.org Received: (qmail 52112 invoked by uid 500); 3 Jul 2009 14:30:39 -0000 Mailing-List: contact dev-help@lenya.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lenya.apache.org Delivered-To: mailing list dev@lenya.apache.org Received: (qmail 52104 invoked by uid 99); 3 Jul 2009 14:30:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jul 2009 14:30:39 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gccld-lenya-dev@m.gmane.org designates 80.91.229.2 as permitted sender) Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jul 2009 14:30:29 +0000 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1MMjm6-0000O1-KB for dev@lenya.apache.org; Fri, 03 Jul 2009 14:30:02 +0000 Received: from cust.static.84-253-63-109.cybernet.ch ([84.253.63.109]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Jul 2009 14:30:02 +0000 Received: from andreas by cust.static.84-253-63-109.cybernet.ch with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Jul 2009 14:30:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: dev@lenya.apache.org From: Andreas Hartmann Subject: Re: Blog Module Date: Fri, 03 Jul 2009 16:27:41 +0200 Lines: 73 Message-ID: References: <4A48A37E.2040703@propco.co.uk> <4A48EB4A.40609@propco.co.uk> <4A4DE330.1070400@propco.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: cust.static.84-253-63-109.cybernet.ch User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) In-Reply-To: Sender: news X-Virus-Checked: Checked by ClamAV on apache.org Andreas Hartmann schrieb: > Hi Vik, > > Vik Tara schrieb: >> Have spent a bit more time looking at roller - it's very good!! >> >> In my view a lenya integration would have to accommodate: > > [�] > >> 3. Styling >> >> Roller uses it's own theme/template mechanism - so we would need to >> think of how the module could create a template based on the users lenya >> styling. > > � or we just pull the RSS/Atom and feed it into a pipeline. The pipeline > + XSLT would be reusable for other feeds. > > > BTW, would it make sense to allow "mounting" a module at a particular > URL? E.g. > > /mypub/authoring/blog/** -> /modules/roller/{1} > > Of course that can be done in the publication sitemap, but maybe we can > provide a more generic mechanism? > > > In this context: How do we tell the roller module which Roller > application it shall access? Maybe we could use some kind of generic > "module configuration document" which is used to mount a module at a > particular URL: I guess this wasn't entirely clear: The "module configuation document" would be a document in the Lenya content repository. It could be edited using the source editor, Firedocs etc. -- Andreas > > /mypub/authoring/blog.xml > > > > > > > > In the easiest case, this could generate an Include statement: > > > > To support multiple-page apps, we could maybe generate Include > statements for "virtual" child documents (which don't exist in the site > structure), using the same params as the module base document: > > > > > Just some random thoughts � > > -- Andreas > > -- Andreas Hartmann, CTO BeCompany GmbH http://www.becompany.ch Tel.: +41 (0) 43 818 57 01 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org For additional commands, e-mail: dev-help@lenya.apache.org