Емил Иванов wrote, On 15/12/06 7.00 a:
Hmm, maybe you didn't understand me or you are right :). What I's
suggesting is that there be only ONE class with all the functionality,
aimed at simplicity. Currently when using the DOM I need to write a
lot of code and use a lot of classes. Also I don't think that this
should be a wrapper to any class. It should be just it. Written from
scratch with the ability for parsing and manipulating. ONE easy to use
class - that is my idea.
If this is just one class, encapsulating all of XML, how would you
handle functionality and features that are specific to certain
components of XML?
Where are you pulling DTD and XSD support from?
Also, what's wrong with using multiple classes to manipulate XML?
Although I have some issues with the PHP DOM classes, they seem well
designed to represent XML in an OO fashion.
Developing one super-class seems like a step backwards.
What's your rationale for developing this from scratch?
-Phil
