Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 25733 invoked from network); 4 Jan 2006 09:57:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Jan 2006 09:57:19 -0000 Received: (qmail 27333 invoked by uid 500); 4 Jan 2006 09:57:17 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 27081 invoked by uid 500); 4 Jan 2006 09:57:13 -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 26847 invoked by uid 99); 4 Jan 2006 09:57:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2006 01:57:10 -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 [81.169.145.166] (HELO natnoddy.rzone.de) (81.169.145.166) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2006 01:57:08 -0800 Received: from [172.26.0.5] (242.Red-213-97-135.staticIP.rima-tde.net [213.97.135.242]) (authenticated bits=0) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id k049usQ1002064 for ; Wed, 4 Jan 2006 10:56:55 +0100 (MET) Subject: Re: Saving pages from forrest run From: Thorsten Scherler To: dev@forrest.apache.org In-Reply-To: <43BB2B21.9030407@apache.org> References: <43BB2B21.9030407@apache.org> Content-Type: text/plain; charset=utf-8 Date: Wed, 04 Jan 2006 10:56:53 +0100 Message-Id: <1136368613.9319.11.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N El mié, 04-01-2006 a las 01:55 +0000, Ross Gardler escribió: > OK, so there are concerns about doing this, but I think all the concerns > can be addressed, and besides *I* want an easier way of publishing a > spelling correction in a single page of a 500 page site (for example). > > So, I've done it. Well, OK to be fair I've done a really rough stab at it. > > I did it in XSP first, but hated it. Way too much mixing of content with > logic (never touched XSP before). Given the amount of logic we will need > in order to create the necessary "idiot checks" and "user warnings" we > have discussed, I decided it would be better to go for an action. > > I've left some of the XSP stuff in there because I reckon we will use > that to do the really simple stuff like do a site build and deploy. But > we'll see about that some other time. > > There's no cool GUI for creating the relevant URLs just yet, I have > locally extended the forrestbar but don't want to commit it because it > is only useful if you are using the devTools plugin and I don't want to > clutter it. If people want it I can attach a patch to an issue. > > Enjoy a faster workflow: > > - Edit > - preview > - save > - commit > > But be careful with it, there are currently no checks for things like > changed navigation files. > Very, nice I have not look at it yet, but I think we should not use XSP at all but jx. XSP is evil and should not be used for *new* stuff. ;-) Everything else after a review. ;-) salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)