From dev-return-21950-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Tue Jan 03 02:08:09 2006 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 53678 invoked from network); 3 Jan 2006 02:08:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Jan 2006 02:08:08 -0000 Received: (qmail 64344 invoked by uid 500); 3 Jan 2006 02:08:07 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 64297 invoked by uid 500); 3 Jan 2006 02:08:07 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 64286 invoked by uid 99); 3 Jan 2006 02:08:07 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2006 18:08:07 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [65.77.211.84] (HELO www2.kc.aoindustries.com) (65.77.211.84) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2006 18:08:06 -0800 Received: from fo2.kc.aoindustries.com (www2.kc.aoindustries.com [65.77.211.84]) by www2.kc.aoindustries.com (8.13.1/8.13.1) with ESMTP id k0327juT008053 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 2 Jan 2006 20:07:45 -0600 Received: from localhost (localhost [[UNIX: localhost]]) by fo2.kc.aoindustries.com (8.13.1/8.13.1/Submit) id k0327iVp007949 for dev@forrest.apache.org; Mon, 2 Jan 2006 20:07:44 -0600 X-Authentication-Warning: fo2.kc.aoindustries.com: indexgeo set sender to crossley@apache.org using -f Date: Tue, 3 Jan 2006 13:07:34 +1100 From: David Crossley To: dev@forrest.apache.org Subject: Re: [RT] Writing generated page to disk in "forrest run" Message-ID: <20060103020734.GA13473@igg.indexgeo.com.au> References: <43B554D1.7050804@apache.org> <20060102034132.GB11592@igg.indexgeo.com.au> <43B8A985.5050205@apache.org> <20060102215951.GA12371@igg.indexgeo.com.au> <43B9ACD4.90207@apache.org> <20060103004000.GA13141@igg.indexgeo.com.au> <43B9CDA7.1060804@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43B9CDA7.1060804@apache.org> User-Agent: Mutt/1.4i X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Ross Gardler wrote: > David Crossley wrote: > >Ross Gardler wrote: > > ... > > >>>I am also wary about turning Forrest into a poor person's > >>>content management system by using htmlarea and such. > >> > >>I agree I think we should deprecate the htmlArea plugin (it probably > >>doesn't work anymore anyway). What other plugins are there that cause > >>concern about being a poor mans CMS? > > > >Well it is hard to know where the line is. > >Our mission statement is intentionally vague. > >http://forrest.apache.org/guidelines.html#mission > >The Introduction on the home page also avoids > >mention of it. Perhaps it would help to have an > >FAQ about the CMS aspect. > > > >Every day i intend to explore the new "NoteTaking" plugin. > >(Oh, something wrong with the online docs.) > >I suspect that that is a fine use. > > The note-taking plugin is quite different from CMS. It is simply a place > to jot notes about each page. No version control, no user management > etc. They are rendered separately from the core content. All notes are > stored in a single file, linked to the source files by URL. > > Editing is just a plain text form field - no wysiwyg or anything like that. > > I use it in a (protoype) educational product that allows text books to > be distrbited as Forrest content objects. > > I have no problem moving it over to Burrokeet if it blurs the boundaries > too much. Thinking about it it may be better to do that in order to keep > the distinction between publication and content editing. It would also > provide another off-site plugin which would be a good idea. Wait. I was trying to say that it is probably a good example of something that is within our scope. And probably nicely defines the limit. -David