Comments on: pQuery - Messing with the DOM from PHP http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/ Mr Quinn, one word for your fans? "Ehm, astronaut." Wed, 07 Jan 2009 04:53:50 +0000 http://wordpress.org/?v=2.3.3 By: jjshell http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-2347 jjshell Sun, 04 Jan 2009 13:12:54 +0000 http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-2347 Hi, I am very interested in using pQuery. Under which license is it released? Do you plan to develop/maintain it in the future, or was it a small side-project? Regards, -jj. Hi,

I am very interested in using pQuery. Under which license is it released? Do you plan to develop/maintain it in the future, or was it a small side-project?

Regards,

-jj.

]]> By: Jim Spence http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-2328 Jim Spence Fri, 19 Dec 2008 04:10:34 +0000 http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-2328 <strong>Jim Spence...</strong> I am not sure that I can completely understand your comments. Would you be so kind as to expand on your reasoning a little more before I comment.... Jim Spence…

I am not sure that I can completely understand your comments. Would you be so kind as to expand on your reasoning a little more before I comment….

]]> By: Godar http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-640 Godar Fri, 03 Oct 2008 06:57:49 +0000 http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-640 We have put together a PHP DOM Template engine that seperates design from development and works well. It uses three new attributes which are removed at render time. We have tested is speed against a number of other PHP Template engines and while it is slightly slower than some of the pre-compiled template engines this one fairs well for a direct parsing renderer. The best thing is if you want to re-template a site and not redo the code it is all quite possible if you have the site planned out well. We have put together a PHP DOM Template engine that seperates design from development and works well. It uses three new attributes which are removed at render time.

We have tested is speed against a number of other PHP Template engines and while it is slightly slower than some of the pre-compiled template engines this one fairs well for a direct parsing renderer.

The best thing is if you want to re-template a site and not redo the code it is all quite possible if you have the site planned out well.

]]> By: Umkus http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-637 Umkus Sat, 27 Sep 2008 12:13:11 +0000 http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-637 Hey there! Nice implementation. As the matter of fact I was searching for those kinds of TE for my framework. But two things always tend to stop me: 1) DOM-manipulating is quite hungry for the resources 2) If you get some templates changed (in a web-designing studiowhere I work I get them alot!) you are forced to change your php-code as well. And that's really bad. Chears. Hey there! Nice implementation. As the matter of fact I was searching for those kinds of TE for my framework. But two things always tend to stop me:
1) DOM-manipulating is quite hungry for the resources
2) If you get some templates changed (in a web-designing studiowhere I work I get them alot!) you are forced to change your php-code as well. And that’s really bad.
Chears.

]]> By: Fredrik Holmström http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-635 Fredrik Holmström Fri, 26 Sep 2008 17:33:00 +0000 http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-635 Koen yes, as it is now the "abstraction" of using a php:id or py:id disconnects the all together so that you can change the html structure in any way you want aslong as you keep the php/py:id structure the same. The current implementation of option 1) is in python and im going to tidy it up and put a post up about it. Koen yes, as it is now the “abstraction” of using a php:id or py:id disconnects the all together so that you can change the html structure in any way you want aslong as you keep the php/py:id structure the same.

The current implementation of option 1) is in python and im going to tidy it up and put a post up about it.

]]> By: Koen http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-634 Koen Fri, 26 Sep 2008 17:28:42 +0000 http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-634 I think number 1) is good step in the direction I would favor. The question I still have at this point is this: suppose you iterate through a list using list items (ul, li). Would the designer (who is instructed about php:id) be able to change the <li php:id="posts"> into a similare div structure? I think number 1) is good step in the direction I would favor. The question I still have at this point is this: suppose you iterate through a list using list items (ul, li). Would the designer (who is instructed about php:id) be able to change the <li php:id=”posts”> into a similare div structure?

]]> By: Fredrik Holmström http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-633 Fredrik Holmström Fri, 26 Sep 2008 11:55:39 +0000 http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-633 @ All people that noted on the fact that it "moves html into php": Yes in this version you're right, I have two other prototypes at my harddrive (one written in python and one in php) that solves this issue in two different ways: 1) Adds a separate php:id or py:id that lets you access those elements from within python/php 2) Allows you to select elements based on css rules, such as: $s("#posts li").each(function($element, $i) { /* do something to each li here */ }); All in all I like 1) better since it disconnects the php/python from the css/html completely, sure you need to add php:id="title" for say the h2-tag on a post or something, but it also means you dont have to clutter your tags with dom-id's that are only used in php/python or unnecessary css-classes so you can disconnect the php/python from the html structure. @ All people that noted on the fact that it “moves html into php”: Yes in this version you’re right, I have two other prototypes at my harddrive (one written in python and one in php) that solves this issue in two different ways:

1) Adds a separate php:id or py:id that lets you access those elements from within python/php
2) Allows you to select elements based on css rules, such as: $s(”#posts li”).each(function($element, $i) { /* do something to each li here */ });

All in all I like 1) better since it disconnects the php/python from the css/html completely, sure you need to add php:id=”title” for say the h2-tag on a post or something, but it also means you dont have to clutter your tags with dom-id’s that are only used in php/python or unnecessary css-classes so you can disconnect the php/python from the html structure.

]]> By: SitePoint PHP Blog: DOM vs. Template : Dragonfly Networks http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-632 SitePoint PHP Blog: DOM vs. Template : Dragonfly Networks Fri, 26 Sep 2008 10:28:05 +0000 http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-632 [...] this new post to the SitePoint PHP Blog there’s a look at using a small templating engine recently released by Fredrik Holmstrom that takes a different tack on working with template files - [...] […] this new post to the SitePoint PHP Blog there’s a look at using a small templating engine recently released by Fredrik Holmstrom that takes a different tack on working with template files - […]

]]> By: Jaik http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-631 Jaik Fri, 26 Sep 2008 08:38:13 +0000 http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-631 I think Koen has hit the nail on the head here. In trying to remove PHP code from your HTML, you've gone too far the other way and started putting HTML into your PHP. If the template changes significantly in the future then you'll end up doing just as much work as you would if there was no templating system at all. The code looks quite elegantly done from the brief look I've just had and it's quite compact considering the functionality it seems to have, I just think it's missing the target somewhat in its current guise. I think Koen has hit the nail on the head here. In trying to remove PHP code from your HTML, you’ve gone too far the other way and started putting HTML into your PHP.

If the template changes significantly in the future then you’ll end up doing just as much work as you would if there was no templating system at all.

The code looks quite elegantly done from the brief look I’ve just had and it’s quite compact considering the functionality it seems to have, I just think it’s missing the target somewhat in its current guise.

]]> By: Koen http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-629 Koen Thu, 25 Sep 2008 18:38:41 +0000 http://loveandtheft.org/2008/09/17/pquery-messing-with-the-dom-from-php/#comment-629 There's indeed no PHP in the template, however there IS HTML in the PHP code. If the problem is with PHP in templates becoming unwieldly, this is the other way round: the reference to HTML elements will become unwieldly in the PHP code. What's more, if you look at the template (eg from a designer perspective) it's not at all clear anymore what you can change. Rule number one probably is to keep of the classes. But can you delete an element with a certain class? Will you know what you just have deleted that depended upon that class? There’s indeed no PHP in the template, however there IS HTML in the PHP code. If the problem is with PHP in templates becoming unwieldly, this is the other way round: the reference to HTML elements will become unwieldly in the PHP code.
What’s more, if you look at the template (eg from a designer perspective) it’s not at all clear anymore what you can change. Rule number one probably is to keep of the classes. But can you delete an element with a certain class? Will you know what you just have deleted that depended upon that class?

]]>