From glongman@intelligentworks.com Sun Jun 1 00:44:08 2003 Return-Path: Mailing-List: contact tapestry-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tapestry-dev@jakarta.apache.org Received: (qmail 45167 invoked from network); 1 Jun 2003 00:44:08 -0000 Received: from dci.doncaster.on.ca (HELO smtp.istop.com) (66.11.168.194) by daedalus.apache.org with SMTP; 1 Jun 2003 00:44:08 -0000 Received: from turbonium (labserver.intelligentworks.com [66.11.174.240]) by smtp.istop.com (Postfix) with SMTP id 9DDF236948 for ; Sat, 31 May 2003 20:44:16 -0400 (EDT) Message-ID: <037a01c327d6$e40abf20$2400a8c0@turbonium> From: "Geoff Longman" To: Subject: Need an observation about the TemplateParser Date: Sat, 31 May 2003 20:43:59 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Howard, I'm about to start looking at the TemplateParser with the intent of adapting it for use with Spindle. I will not be suggesting any changes as I was thinking of copying the source and customizing to my needs. Was wondering if I could get some insight from you on the following... 1. How hard do you think it would be to add some kind of callback mechanism to report stuff like:? startTagStart(line, column) startTagEnd(line, column) AttributeStart(line, column) AttributeEnd(line, column) closeTag (I need no info really about the close tag, I just need to know which start tag has been closed.) 2. The parser stops when the first problem is encountered. Do you believe that a version that reports the error, but continues would still work, or would the parser go insane? Of course I'm hoping for positve responses to the above, but negative would be ok too as I wouldn't waste time learnig the parser code in detail. Geoff Geoffrey Longman Intelligent Works Inc.