PUBLIC MARKS from kasi77 with tag code

Facebook still uses PHP, but it has built a compiler for it so it can be turned into native code on its web servers, thus boosting performance.

La nouvelle version de Java 7 est en cours de préparation. Malgré le retard et les incertitudes sur le contenu, nous considérons que Java 7 constitue une opportunité intéressante pour le langage. Après un premier article consacré aux nouvelles librairies proposées pour Java 7, ce second article introductif vous propose de découvrir les nouvelles fonctionnalités du langage et de la JVM. Là encore, en cas de doute sur le contenu de la version finale, nous préciserons les réserves concernant une librairie ou une syntaxe en indiquant si l'exemple de code proposé compilait avec la version de prévisualisation 1.7.0-ea-b37.

Donner pour mieux recevoir ? Facebook vient d'annoncer la mise à disposition d'une partie du code de son moteur interne Scribe sous licence open source. Désormais hébergé sur SourceForge, le projet est donc accessible à tous, à commencer par les concurrents du réseau social qui monte, qui pourront donc étudier la façon dont Facebook administre, au niveau des serveurs, les faramineuses quantités de données générées par ses cent millions d'utilisateurs.

A semi-automated, largely passive web application security audit tool, optimized for an accurate and sensitive detection, and automatic annotation, of potential problems and security-relevant design patterns based on the observation of existing, user-initiated traffic in complex web 2.0 environments.

Since we launched spreadsheet forms in January, one of the top user questions has been "How can I embed my form into a website or blog?" Last night, we added this option. You'll see this new feature during form creation, when you're prompted to invite people to fill out your form. Just skip the invitation step and look for "Embed" in the upper right-hand corner of the page. Paste the code provided into your blog or website.

My initial experiences with unit testing and PHP were with PHPUnit. While it's a great tool and I have to give kudos to Sebastian for contributing so much to its development, I've come to appreciate the simplicity of PHPT tests. Recently, I wrote some for a project and realized that I wasn't aware of how to generate code coverage reports. Many thanks to the very helpful patrons in the #pear channel on EFNet for helping me to get this working.

What is Conflict? Conflict notifies a software developer of potential conflicts between his/her work and that of other developers, before the commit. Conflict is an open source project composed of two parts: Conflict clients and a Conflict server. A Conflict client is a transparent process running on the workstation of each developer. It stays in the background, reporting local file system changes to the Conflict server. When the Conflict server detects a conflict between two or more developers, each developer is notified. The Conflict project improves feedback and communication while encouraging developers to check in code frequently.

Here's a helper that allow to generate cross apps urls in symfony 1.0

Login form in Symfony 1.1, with the new form system Symfony 1.1 comes with a complete new form system. It works completely according to the MVC draft: * Model: the validation * View: the form self through widgets * Controller: the form class that the model and view parts manages and uses Make sure you have a running Symfony 1.1 based project and application and modules. In this example I build the form inside the myModule module and myLogin action. My form makes use of i18n, which is in my case autoloaded in settings.yml. This tutorial uses Symfony 1.1 beta4 and RC1.

Among the remarks have about symfony 1.1, the most recurring one is the shift of philosophy between the 1.0 and 1.1 syntax. If symfony 1.0 syntax was made to write code fast, I believe it is not the case anymore with symfony 1.1, which is designed primarily for extensibility. The result is that a symfony 1.1 application looks a lot more like a Java program. I tend to agree that Object-Orientation is a good thing because it forces you to organize your code in a modular way. But when object-orientation makes you need to keep a symfony book aside at all times and multiply the number of LOC by two, I think it's a dead end.

# The only development solution for drag-and-drop visual design for PHP # Build data-driven Web applications with broad database connectivity # Create AJAX-enabled Web 2.0 pages and sites # Everything you need in a PHP development environment including a powerful code editor, debugger, profiler, database tools and much more # Use the VCL for PHP component library with more than 70 visual components to speed development and extend it with your own components # New version! See what's new in Delphi for PHP 2.0

Parfois, on a besoin d'inclure une vidéo QuickTime (.MOV) dans une page XHTML

High Performance Web Sites: The Importance of Front-End Performance In 2004, I started the Exceptional Performance group at Yahoo!. We're a small team chartered to measure and improve the performance of Yahoo!'s products. Having worked as a back-end engineer most of my career, I approached this as I would a code optimization project - I profiled web performance to identify where there was the greatest opportunity for improvement. Since our goal is to improve the end-user experience, I measured response times in a browser over various bandwidth speeds. What I saw is illustrated in the following chart showing HTTP traffic for http://www.yahoo.com.

While still messing around with the PHP_CodeSniffer Pear package, I took a somehow jealous 1000 feet look at some prominent code inspection tools of the Java community: PMD and Checkstyle. Browsing their available rule sets/checks I soon recognized that guaranteeing the coding standard adherence is just a partial aspect of these tools. The following post will focus on one of these additional aspects, which is finding problems related to the code size of the inspected code artifacts, by showing how to port two selected rules to sniffs for utilization with the PHP_CodeSniffer tool. These ported sniffs can be used to automatically spot obvious code smells in the code base and to signal the need to apply the appropriate and odour reducing activity known as refactoring. Further more a complete set of code size sniffs, going beyond the trageted realm of the sniffs to come, could be used to speed up the feedback loop and to reduce the effort for manual code reviews.

Depuis jeudi, Google Code héberge le projet OpenSocial, un ensemble d'API qui vont permettre le développement de programmes communs pour un certain nombre de sites de réseaux sociaux (voir liste en référence). Avant jeudi, tout programmeur souhaitant développer une application pour réseaux sociaux devait apprendre l'API, la syntaxe et parfois même un nouveau langage de chacun des réseaux (quand ceux-ci proposaient une API accessible de l'extérieur !). Maintenant, OpenSocial permet d'accéder aux fonctions de base, au plus petit commun dénominateur entre tous les réseaux sociaux participant.

PhpSecInfo provides an equivalent to the phpinfo() function that reports security information about the PHP environment, and offers suggestions for improvement. It is not a replacement for secure development techniques, and does not do any kind of code or app auditing, but can be a useful tool in a multilayered security approach.

PHP code snippets and articles, all user-contributed, tagged and searchable

This page contains the 252 allowed entities in HTML 4 and XHTML 1.0, as outlined in section 24 of the official HTML 4 specifications, published by the W3C