Hi Sbastien
Yes, sure. I think it would be cool to have a PhpXpath based
on PHP 5 features. Would call it version V5 and would of
course be a sibling that only runs on PHP V5.
FYI:
Dan Allen had a similar idea in the PHP4 days using the DOM
extension and realized it as a sibling project under PEAR.
See: http://pear.php.net/package/XML_XPath
I'm not a fan of PEAR (yet). I don't like the idea of a lib that
tries to 'update' a language (PEAR is based on PHP4 and has
it's own Destructors, Constructors, Exception Handling - a
concept you MUST use to be PEAR compatible)
Ive added you as developer on sourceforge but with no
rights to update the CVS (for the moment). If you can
confirm me that you can handle sourcforge-CVS Ill grant you
the rights and give you a CVS branch where you can start.
Regards
Sam
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've look at "Dan Allen" source ! It's not very flexible !
I would like to implement Xpath 2.0 so your classes are better.
Well ! For start I need to understand well your classes.
The standard php5 xpath object is DomXpath !
We must extends XpathV5 from it !
I want to maximize use of the standard Xpath support !
If it's an Xpath2.0's expression we switch to the new support !
I believe that is necessary to delete export (asXML, as
HTML,...), dom internal (of course), and redone and error and
debug support con PHP5 exceptions. I think an Xpath class
just do Xpath query !
Tell me if you are ok. And give informations about project
name code, version, etc ...
Best regards !
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Having a look at PHP's DOM functions and XPath ability (I
havent followed the progress for some time) I see it has
grown quite a bit since we wrote phpxpath!
Most of the code we wrote can be dumped and be replaced
by the fancy PHP-DOM lib.
I would keep the export, it so often used and you'll need it
for debugging anyway.
My tip is to try to keep the interface (if possible) because
your then able to use our test bench
(see http://www.carrubbers.org/scripts/php/xpath/testBench/valid
ationTests/)
Would give you a feeling on how fast an stable it is :-)
Im ok with the rest.
I would call the project PhpXpath V5 and stress out that its
only for PHP5 and supporting Xpath 2.0
Dont have that much time to support you, but easiest would
be, that you start and contact me when its in beta stage.
Have fun!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Having never seen any of your code before, I am nervous
about giving you checkin access to the main branch of
Php.XPath. Could you possibly send us your code via email
for us to review, and if it meets the required quality
standards then we'll feel happier about giving you checkin
permissions?
Also are there any unit tests or documentation that will
require update as a result of your changes?
I looked for documentation on XPath 2.0 at w3c and couldn't
find any :o(
Nigel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=308859
Hi Sbastien
Yes, sure. I think it would be cool to have a PhpXpath based
on PHP 5 features. Would call it version V5 and would of
course be a sibling that only runs on PHP V5.
FYI:
Dan Allen had a similar idea in the PHP4 days using the DOM
extension and realized it as a sibling project under PEAR.
See: http://pear.php.net/package/XML_XPath
I'm not a fan of PEAR (yet). I don't like the idea of a lib that
tries to 'update' a language (PEAR is based on PHP4 and has
it's own Destructors, Constructors, Exception Handling - a
concept you MUST use to be PEAR compatible)
Ive added you as developer on sourceforge but with no
rights to update the CVS (for the moment). If you can
confirm me that you can handle sourcforge-CVS Ill grant you
the rights and give you a CVS branch where you can start.
Regards
Sam
Logged In: YES
user_id=1084173
Hi
I've look at "Dan Allen" source ! It's not very flexible !
I would like to implement Xpath 2.0 so your classes are better.
Well ! For start I need to understand well your classes.
The standard php5 xpath object is DomXpath !
We must extends XpathV5 from it !
I want to maximize use of the standard Xpath support !
If it's an Xpath2.0's expression we switch to the new support !
I believe that is necessary to delete export (asXML, as
HTML,...), dom internal (of course), and redone and error and
debug support con PHP5 exceptions. I think an Xpath class
just do Xpath query !
Tell me if you are ok. And give informations about project
name code, version, etc ...
Best regards !
Logged In: YES
user_id=308859
Having a look at PHP's DOM functions and XPath ability (I
havent followed the progress for some time) I see it has
grown quite a bit since we wrote phpxpath!
Most of the code we wrote can be dumped and be replaced
by the fancy PHP-DOM lib.
I would keep the export, it so often used and you'll need it
for debugging anyway.
My tip is to try to keep the interface (if possible) because
your then able to use our test bench
(see
http://www.carrubbers.org/scripts/php/xpath/testBench/valid
ationTests/)
Would give you a feeling on how fast an stable it is :-)
Im ok with the rest.
I would call the project PhpXpath V5 and stress out that its
only for PHP5 and supporting Xpath 2.0
Dont have that much time to support you, but easiest would
be, that you start and contact me when its in beta stage.
Have fun!
Logged In: YES
user_id=1084173
Hi
I redone the export system to use it with dom
Ant put new code in a class.
Maybe the interface will be little bit different due to PHP 5
specific features.
See you soon !
Logged In: YES
user_id=1084173
Hi,
PhpXpath V5 beta will ready around the next week.
This version will not support yet Xpath 2.0 features.
It will support PHP5 dom with exceptions, debug class, and
few exports method.
Moreover it will possible to choice between the internal XPath
parser or XPath PHP5 native parser based on libxml.
For simple Xpath 1.0 expressions we will use native parser and
the pure php parser for Xpath 2.0 expressions.
Please give an CVS account.
I would like to propose this package on Pear too since it will
ready.
Could you remind me how can I use CVS on a specific branch.
There is a long time that I haven't used CVS.
See you soon
Bye.
See you soon
Bye.
Logged In: YES
user_id=270120
Hi Sbastien,
Having never seen any of your code before, I am nervous
about giving you checkin access to the main branch of
Php.XPath. Could you possibly send us your code via email
for us to review, and if it meets the required quality
standards then we'll feel happier about giving you checkin
permissions?
Also are there any unit tests or documentation that will
require update as a result of your changes?
I looked for documentation on XPath 2.0 at w3c and couldn't
find any :o(
Nigel