
Software Engineering
Histoire Bas Vode a developpé un petit test pour les équipes qu'il accompagnait chez Nokia, ce qui a donné le Nokia Test. En 2008, Jeff Sutherland l'a repris pour lui ajouter un système de score. Dans ses formations, il nomme ça le "Scrum But" test. C'est cette version que nous vous proposons de passer ici. Objectifs Nous avons implémenté ce test pour deux objectifs :
- Vous donner un indicateur pour savoir où vous en êtes dans votre mise en pratique
- Collecter des informations sur l'usage de scrum
Une fois que vous aurez obtenu votre résultat, vous pourrez nous le soumettre. Les seules informations conservées sont :
* les résultats du questionnaire question par question
* la langue dans laquel le test a été fait (anglais ou français pour l'instant)
* l'adresse IP. Nous conservons celle-ci pour détecter des réponses cherchant à fausser les résultats ainsi que faire des statistiques géographiques.
En aucun cas les informations collectées ne pourront être utilisées à des fins commerciales.
Alors, êtes vous Scrum ?
FluentDOM provides an easy to use fluent interface for DOMDocument.
The idea was born in a workshop of Tobias Schlitt, about the PHP XML extensions at the IPC Spring , in Berlin. He used this idea to show XPath samples in the session.
Many thanks to the jQuery , people for their work, who did an exceptional job describing their interfaces and providing examples. This saved us a lot of work.
We implemented most of the jQuery methods into FluentDOM, but here are differences. Most important: we use XPath for expressions, not CSS selectors. Since XPath is supported by the ext/xml extension, no extra parsing need to be done. This should be faster processing the selectors and btw it was easier for us to implement. And as a nice topping it supports namespaces, too.
I've been nominated again for the eZ Components Award. Thanks to eZ Systems for honour and to me employer YMC for the food! So this is a good occasion to assemble a list I've had in mind for a longer time. In a big project like eZ Components, which has been programmed by many contributors over a long time it is natural, that there are some better and some worse parts. So which components are the good, the bad and the ugly? Maybe this kind of overview could also be done by other users of other libraries too. Then we could assemble a big comparison table of framework or library components and one could pick the best parts of each. You'll notice that even if I consider myself a power user of eZ Components, I won't give a rating for every component, because there are still a few, I've not intensively used by now. So let's complete this table in a wiki somewhere together!
eZclipse is an Eclipse plug-in for supporting the CMS eZ Publish.
eZclipse offers the following features
* Syntax highlighting for INI and TPL files.
* Validation of TPL files.
* Var Browser for exploring the $node variable.
* Wizard for creating a new template file
* Wizard for creating a new configuration file
The project is actually hosted on SourceForge :
Punjab is a HTTP jabber client interface. It is a BOSH or XEP-0124 connection manager that allows persistent client connections to a XMPP server. Supporting XMPP over BOSH or XEP-0206
For more information you can also go to the BOSH Technology page : http://www.xmpp.org/tech/bosh.shtml
Strophe is a library for writing XMPP clients. It is implemented in both JavaScript and C for use in a wide variety of languages. The implementations are production ready, well documented, easy to use, and easy to extend.
Strophe provides the following features:
* XMPP compliant
* Browser and platform agnostic
* TLS support via SChannel, GNUTLS, or OpenSSL
* SASL authentication using ANONYMOUS, DIGEST-MD5, or PLAIN methods as well as legacy jabber authentication
* Customizable logging and memory management
Daisy is a content management system that offers rich out-of-the-box functionality combined with solid foundations for extensibility and integration. Daisy consists of two main components:
* a stand-alone repository server accessible through HTTP/XML (using the ReST style of WebServices) and/or a high-level (remote) Java API, and
* an extensive editing and publishing front-end web application running inside Apache Cocoon.
Due to its genericity and flexibility, Daisy can be used for many different purposes, but is ideally suited for information-rich, structured content and asset management applications. Even for advanced content management applications, Daisy can be used and configured without any Java-coding skills: Daisy offers a Javascript/Cocoon-based extension framework.
Daisy is licensed under the open source, business-friendly Apache License 2.0. Enjoy!
Jester is a JavaScript implementation of REST, with syntax modeled after ActiveResource. You can use it to write code to read, create, and update the data on your server.
* Great Syntax – If you’ve gotten used to dirt-easy syntax like ActiveRecord’s “User.find(1)” for getting records, you can look forward to the same simplicity in Jester. Wherever possible, Jester takes advantage of JavaScript’s flexibility to keep things simple.
* Associations – Jester supports and reflects your Rails associations, detecting them automatically if your server includes them in its output.
* Plays With Others – Jester supports “JSONP”, a format for JSON that allows your API to be shared with JavaScript remotely. Sites like Twitter that support this work perfectly with Twitter, with minimal configuration on your part.
* Dependencies – Prototype, a server that uses RESTful URL and format conventions as popularized by Rails and ActiveResource. In Rails, a controller whose routes are defined using “map.resources” will work with Jester with no extra configuration.