Re: [PROPOSAL] PHP Component Model

Still not conviced on the need for the actual classes.. - the methods/etc. appear to be Interfaces, or very small components of classes. - in the IDE model you describe, this is usually better performed by class templates, rather than interfaces (which are a very messy overhead in a scripted language....)

* Generate an XML representation of a PHP Component. Dont get in to it this way.. - I've been researching it quite a bit for my component designer... - Think more like:

Data Tree: - standard save/load format = serialize.. = optional format save/load = wddx (probably with indentation) = prefered save/view format = print_r(). = totally optioanl read/write format = xml_serializer../unserializer.. (last option...!!) dont try and write a parser/writer for xml - it will be increadibly slow loading up. It's also a waste of work as there are already a number of ways of doing it that are far more efficent..

* Generate a PHP source skeleton from an XML representation of a

     PHP Component.

Thats templates :)...

* Serialize a PHP Component's customization into an XML

     representation.

* Unserialize a PHP Component's customization from the above

     mentioned XML representation.

I've been attemping this with Gtk_AppBuilder. - http://devel.akbkhome.com/screenshots/Gtk_AppBuilder_2.jpg which uses PHP_Parser as a base.. - I'm kind of working on a Front(existing code)=>Back logic(theoritical representation), rather than a Back=>Front process... One of the early keys has been storing the PHP_Parser results in a project file.. Regards Alan

Greetings, Sebastian