Hmm, the GSOC Application of Simpletest didnt make it through

But the PHP Project ofiicially supports the PHPUnit as part of its application.

I dio not like the way how php mixes its related open source projects.
Why do people who already have all support, written books, have spoken on all important conferences mixup things here? Is there any need for?

I dont think so: In the end it is bad for the whole php community and from my point of view a kind of a political move.

The PHP-test Information Minister Says: There is only one unittesting framework supporting testing in PHP:



Anyway, my will to participate on the php-test-sessions get lesser and lesser every day.

http://fosterburgess.com/kimsal/?

and

http://paul-m-jones.com/?p=273

Started beating and ranting around on smarty. Since my comment on one of the blogs was deleted. I will rant here.

1. The discussion is really biased towards the non smarty opinion. I can only repeat myself stating that the php-jetset has decided another BAAAD thing to point out and spread FUD. They are just bringing arguments that everybody with a pee warm piece of brain just knows the pros and cons about.

2. More important smarty is well documented and a kind of standard, see the list of applications using smarty as templating. Its just a good product in terms of documentation and examples. Is that the same for the other templating languages that are present out there ? I don't remember seeing any other templating toolkit with that numerous examples.

3. If you dont like it, dont think you have the top-notch-opinion-overall.

I am very sorry to be this harsh, but the actual discussion lacks very basic things:
respect for the work on smarty, repect for the people putting effort in it, respect for a kind of standard.

Eclox is a simple doxygen frontend plug-in for eclipse. It aims to provide a slim and sleek integration of the code documentation process into eclipse.

from http://home.gna.org/eclox/

yehaaa ;)

LOL .. again ... now it parses deep array structures, but does not enter the content into a CDATA Area ... So far a & seems to be a impossible char forteh rest Server ..
it isnt for the JSON Server so i patched the thing a little bit ;) I guess the guys at Zend are a bit of brain only workers ..... could be that i missed reading some tutorial or so .. but works anyway.

Changed: U   library/Zend/Rest/Server.php
A   ws/json_server.php
Diff: Modified: library/Zend/Rest/Server.php ===================================================================
--- library/Zend/Rest/Server.php    2007-03-12 12:06:30 UTC (rev 107)
+++ library/Zend/Rest/Server.php    2007-03-12 13:41:19 UTC (rev 108)
@@ -304,12 +304,13 @@
             }
 
             if (is_array($value) || is_object($value)) {
-                $element = $dom->createElement($key);
+                $element = $dom->createElement($key);
                 $this->_structValue($value, $dom, $element);
             } else {
-                $element = $dom->createElement($key, $value);
+                $element = $dom->createElement($key);
+                $data = $dom->createCDATASection($value);
+                $element->appendChild($data);
             }
-               
             $parent->appendChild($element);
         }
     }

silly, but the zend rest server does not serialize nested arrays ... so i came up with a little fix (for the .7.0 incubator):

--- library/Zend/Rest/Server.php 2007-03-07 11:18:03 UTC (rev 39)
+++ library/Zend/Rest/Server.php 2007-03-07 12:23:40 UTC (rev 40)
@@ -199,7 +199,7 @@
}

$method = $function->getName();
-
+
if ($class) {
$xml = "<$class generator='zend' version='1.0'>";
$xml .= "<$method>";
@@ -222,7 +222,15 @@
if (ctype_digit((string) $key)) {
$key = 'key_' . $key;
}
- $xml .= "<$key>$value</$key>";
+ if (is_array($value))
+ {
+ $xml .= "<$key>" . $this->_to_xml($value). "</$key>";
+ }
+ else
+ {
+ $xml .= "<$key>$value</$key>";
+ }
+
}

if (!$has_status) {
@@ -236,6 +244,21 @@
return $xml;
}

+
+ function _to_xml($data)
+ {
+ $xml = '';
+ foreach ($data as $key => $value) {
+ if (is_array($value))
+ {
+ $xml .= _to_xml($value);
+ continue;
+ }
+ $xml .= '<' . $key . '>' . $value . '</' . $key . '>';
+ }
+ return $xml;
+ }
+
/**
* Handle a single value
*

I have a new job and now I am working at   chip.de  where I am responsible for the development of a subproject for the website.
We are a team of 5 developers and have a backoffice/sales team that outnumbers us by the factor 2. So far so good. From the technical point of view it's a interesting thing here:

• the it website with the most pi's in germany
  
• a large webfarm where our application runs in
  
• a IT department that is 50% of teh company ;)
  
• a lot of php coding people

One of my first jobs is a prototype project that should help us deciding how and if we should develop a special sub site for the whole company. So far, this time it is up to me to decide the toolbox we are using. So far, there is a lot to choose, its a high load website application that must be able to deliver a lot of pi's a day.

• PHP5
  
• Mysql 4.x with PDO
• Smarty: because were already using it
• Zend Framework, because i do not like having glued together components like PEAR
  
• Simpletest, because i still likeit more than PHP-Unit (All Objects were doing for our selfes need to be unit-tested)
  
• Moo.fx (Javascritp Framework) for Ajax/Client Interactivity

Since it will be a effort to establish PHP5, UnitTesting, modern AJAX Principles, its surely interesting for all the readers  of that blog. Illkeep you people Updated.

SCHWING .........

With a little help from e-voc i made the json serializer work.
No well go soon to be async and the all will be much better.

Besides i started work hard on the integration of jsobjects. I guess ill have to rewrite some of the code to make it work w.o. evil eval.
The grid example is still simple, dropping notices etc .. but the api is growing. I dont have this much time, bus as ill make pnAjax a important component on the pncommerce project, reusing the grid and the tree for basic gui layout, it will get a lot of commits anyway.

The big Ajax discussion has come in place to postnuke. Again it looks like writing down things, instead of write code in the first blink of an idea is considered to be a bad thing there. Markwest requested a unified ajax Project for the postnukeworld, but i guess that will not take place .. why ?

The Approaches are too different

Chestnuts Ajax example is
- not using serialization
- relies on handcoded servers
- has no framework components
- has no event model catching errors from the serverside

Frank Schummertz pnForum Stuff:
- is using AHAH data (returning HTML instead of XML or serialized data
- relies on handcoded servers
- has no framework components
- has no event model catching errors from the serverside

pnAjax
- uses json data serialization
- has a tested gui kit / framework
- relies on no handcoded server to use ajax funcs on the client
- has a event model catching errors from the serverside

Anyway, i am really opposing doing 3 times the same work, but as i see from the mailing list postings, there is a request for a lot of functionality that is already in pnAJax. So i guess it was worth the time to sit down and thing of a framework that can totally integrate with postnuke instead of building stuff on top, that might be sexy, but is ugly code.

You migth call me a thread , but if there is no movement twoards a performant approach for the data stuff and nothing more that, hey, integrate scriptacolous into postnuke, Ill not be the one to jump in and make the lead on such a project .. ill guess it takes a year to explain to others what they need to develop .... pnAjax is rather complex on the code side of the project development ... but easy to use for the final developer, implementing his own apps with just a buch of loc.