New extension underway
| From: | Darren | Date: | Tue, 04 Nov 2008 06:15:40 +0000 |
| Subject: | New extension underway | ||
| Groups: | php.pecl.dev | ||
| Request: | Send a blank email to pecl-dev+get-5847@lists.php.net to get a copy of this message | ||
Hi all,
I'm a Senior Software Engineer who works with PHP and Extensions a lot.
I recently decided to develop a series of PHP5 Classes in an extension.
This started out as research for an idea I want to implement at the
office - sort of "cutting my teeth" on writing PHP classes in C. But,
once I got started and built up some steam, I decided what I'm writing
might be very useful to others. I have looked around on PEAR and PECL,
and I did find one similar package on the PEAR site. I believe my
approach is a little better founded though, and of course - my classes
are in an extension, which gives obvious performance gains over scripted
classes.
So, the idea is an XHTML DOM hierarchy. I'm developing classes that
represent XHTML elements, while drawing heavily on the DOM methods used
in JavaScript. I want to be able to declare a document object, set
properties and attributes on it, and build content into it. (And at this
point, I actually _can_.) I want to be able to manipulate the nodes in
my hierarchy in very much the same way one handles elements in
JavaScript applying the DOM standards. When I'm scripting in PHP, I like
to focus on what the script is doing, not whether I remembered to close
that tag or spelled some attribute correctly. I found the HTML_Page2
PEAR package to be similar, but all attributes appeared to be set via
named functions instead of property sets (more stuff to remember). The
API also looked incomplete to me, failing to represent most of the HTML
tags.
I intend to complete and run this extension on my web server. I am very
happy to open-source it and share with the world, and I would like to
see it published on PECL. Heck, it would be really great if it became a
standard extension, but let's not get ahead of ourselves. Presently, I
call the project XDOM (or XDom), because it's a hell of a lot easier to
say than "Extensible Hyper-Text Markup Language Document Object Model
Class Library". Does my project generally merit inclusion, and does the
name garner approval?
I look forward to hearing replies/thoughts on this, as well as joining
PECL, contributing, and interacting with other extension developers. I
hope I have some good things to share, and I'm sure I stand to learn a
lot from the community.
Sincerely,
Darren Hill (dchill42)