Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:5927
Return-Path: <john@coggeshall.org>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 33809 invoked by uid 1010); 1 Dec 2003 18:33:27 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 33775 invoked from network); 1 Dec 2003 18:33:26 -0000
Received: from unknown (HELO coogle.localdomain) (68.62.49.66)
  by pb1.pair.com with SMTP; 1 Dec 2003 18:33:26 -0000
Received: from coogle.localdomain (coogle.localdomain [127.0.0.1])
	by coogle.localdomain (8.12.8/8.12.8) with ESMTP id hB1IZ4O1031759;
	Mon, 1 Dec 2003 13:35:04 -0500
Received: (from john@localhost)
	by coogle.localdomain (8.12.8/8.12.8/Submit) id hB1IZ4mt031757;
	Mon, 1 Dec 2003 13:35:04 -0500
X-Authentication-Warning: coogle.localdomain: john set sender to john@coggeshall.org using -f
To: "Thies C.Arntzen" <thies@thiesos.org>
Cc: Georg Richter <georg@php.net>, PHP Internals <internals@lists.php.net>
In-Reply-To: <55C160D0-2426-11D8-B273-000393C4A12A@thiesos.org>
References: <200312010845.23909.ilia@prohost.org>
	 <200312011839.57724.georg@php.net>
	 <55C160D0-2426-11D8-B273-000393C4A12A@thiesos.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-ID: <1070303704.31739.42.camel@coogle.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Mon, 01 Dec 2003 13:35:04 -0500
Subject: Re: [PHP-DEV] Tidy & PHP5
From: john@coggeshall.org (John Coggeshall)

In the primary use of tidy (which is to validate HTML), there is very
little need for a returned resource other than to clutter the namespace.
Unlike most extensions, where it would be useful imo the resource is
unnecessary. Since we can reuse the container for the tidy
documentation, it's much faster to just perform serial operations for
the general case then it is to reallocate a brand new container every
time for no reason. 

As far as the API itself goes for the OO side of things, I think the API
that is exposed is just fine. Just as is the case with any
screen-scraping tool, the problem is not in the tool but in the document
you are scraping (trying to find that table you want buried in the
document). 

John

On Mon, 2003-12-01 at 12:46, Thies C.Arntzen wrote:
> before bundling i'd like to see the api refined...
> 
> right now it's not possible to work with more than one html-doc at a 
> time. (tidy_parse_file() does not return a resource to the internal 
> tidy doc, so you can only have one doc at a time)
> 
> also we should ask ourself if (i haven't used tidy so i might be wrong) 
> we want tidy to expose a similar API as SimpleXML does (which we all 
> seem to like - be it too magic or not)
> 
> re,
> tc
> 
> 
> Am 01.12.2003 um 18:39 schrieb Georg Richter:
> 
> >
> >> I would like to propose that tidy extension be bundled with PHP 5.
> >
> > +1
> >
> > Georg
> >
> > -- 
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >