PUBLIC MARKS from pvergain with tag web

There is a Python version of CodeInvestigator to debug your Python scripts with. The user interface is through a web browser. For this you need: * Python. Version 2.5 and over. * A Firefox browser

Welcome to the lift Web Framework lift is yet another web development framework. lift runs inside a Java web container and uses the Scala programming language for coding. lift stresses security, developer productivity, ease of deployment, ease of maintainability, performance, and compatibility with existing systems. lift borrows from the best of existing frameworks including Seaside's highly granular sessions and security, Rails fast flash-to-bang, Django's "more than just CRUD is included", and Erlyweb's scalability for Comet-style applications. lift is built on Scala, a hybrid Functional and O-O language that compiles code down to the Java Virtual Machine. Scala code can call any Java code and make use of all Java classes. Java code can call some Scala code. lift applications are packaged as WAR files and can be deployed on any Servlet 2.4 engine (e.g., Tomcat 5.5.xx, Jetty 6.0, etc.)

Comet is a software concept that enables web servers to send data to the client program (normally a web browser) without having any need for the client to request it. It allows creation of event-driven web applications, enabling real-time interaction otherwise impossible in a browser.

OpenStreetMap is a free editable map of the whole world. It is made by people like you. OpenStreetMap allows you to view, edit and use geographical data in a collaborative way from anywhere on Earth.

The Planet I18n aggregates posts from various blogs that talk about Web internationalization (i18n). While it is hosted by the W3C Internationalization Activity, the content of the individual entries represent only the opinion of their respective authors and does not reflect the position of the Internationalization Activity.

What is Grok? Now even cavemen can use Zope3 Grok is a web application framework for Python developers. It is aimed at both beginners and very experienced web developers. Grok has an emphasis on agile development. Grok is easy and powerful. You will likely have heard about many different web frameworks for Python as well as other languages. Why should you consider Grok? * Grok offers a lot of building blocks for your web application. * Grok is informed by a lot of hard-earned wisdom. Grok accomplishes this by being based on Zope 3, an advanced object-oriented web framework. While Grok is based on Zope 3, and benefits a lot from it, you do not need to know Zope at all in order to get productive with Grok.

New Python-based database communication tool represents first open source component of Launchpad LONDON, July 9, 2007 – Canonical Ltd today announced the release of Storm, a generic open source object relational mapper (ORM) for Python. Storm is designed to support communication with multiple databases simultaneously. Canonical is best known for the popular Ubuntu operating system and Launchpad, a web-based collaboration platform for open source developers. "Storm is an ORM that simplifies the development of database-backed applications in Python, especially for projects that use very large databases or multiple databases with a seamless web front-end", said Gustavo Niemeyer, lead developer of Storm at Canonical. "Storm is particularly designed to feel very natural to Python programmers, and exposes multiple databases as /stores/ in a clean and easy to use fashion." The project has been in development for more than a year for use in Canonical projects such as Launchpad, and is now publicly available under the LGPL license. This will be the first complete Launchpad component to be released as open source software. "We're excited about using Storm for Launchpad, and that it is being released as open source. Storm's API is clear and well designed, making it a joy to work with, " said Steve Alexander, Launchpad Product Manager at Canonical. "The scalability advantages of Storm's architecture are important for us to ensure that Launchpad continues to perform well as the number of Launchpad users grows." Launchpad currently includes developers data for several thousand projects and is used by tens of thousands of developers, translators, and other free software contributors. The Storm project welcomes participation, and has a new website at http://storm.canonical.com. That site includes a tutorial, and links to allow developers to download, report bugs and join the mailing list.

The Django REST interface is a Summer of Code project that implements a general method offering a public and private API for existing Django models. New generic views will simplify data retrieval and modification via different web services in a resource-centric REST architecture, providing model data in formats such as XML, JSON and YAML with very little custom code. The REST interface consists of two major parts: 1. Easily configured Create/Read/Update/Delete (CRUD) method access patterns for models. 2. Resources that don't correspond 1:1 to models. More information: * Initial proposal * First mail to django-developers

I've just released templatemaker, which is something I've been hacking on and off (mostly off) the past couple of months. It's a Python library for extracting data from similarly formatted text strings. What the heck does that mean? Well, say you want to get the raw data from a bunch of Web pages that use the same template -- like restaurant reviews on Yelp.com, for instance. You can give templatemaker an arbitrary number of HTML files, and it will create the "template" that was used to create those files. ("Template," in this case, means a string with a number of "holes" in it, where the holes represent the parts of the page that change.) Once you've got the template, you can then give it any HTML file that uses that same template, and it will give you the raw data: "The value for hole 1 is 'July 6, 2007', the value for hole 2 is 'blue'," etc.

The Google Data APIs (Google data) provide a simple protocol for reading and writing data on the web. Each of the following Google services provides a Google data API: * Base * Blogger * Calendar * Picasa Web Albums * Spreadsheets * Google Apps Provisioning * Code Search * Notebook The Google data Python Client Library provides a library and source code that make it easy to access data through Google Data APIs. To browse the Google data Python client library source code, visit the Source tab. If you have a problem or want a new feature to be included in the Google data Python Client Library, please submit an issue. If you are interested in contributing to the library, please read the Contributor Guide and join the contributor group. - The Google data API Team

AroundWord is a free and open Blog Publishing System built upon the great web framework Pylons. Currently, AroundWord is in early planning and development. You are welcome to take participate in the development: Main Features * Multi-user * Atom/RSS feeds * Trackbacks * OpenID for users that want to comment (this would avoid to use anti-spam feauture) * Anti-spam * Plugin * Theme * Tags * Multi-blog ? (but with a different data base for each blog) * Plug-in system * Easy to install for end users (as easy as wordpress if possible) Development Currently, we are building the models. More details about development here (http://www.aroundword.org/wiki/AroundWordDevelopment) The AroundWord team is happy to take contributions, patches and bug-fixes. We use the following code conventions: * PEP 8 - Style Guide for Python Code * PEP 257 - Docstring Conventions The Mercurial repository can be accessed via: http://hg.aroundword.org/ AroundWord is a free and open Blog Publishing System built on Python using the most advanced technologies: * Framework: Tesla upon Pylons * Database Engine: SQLAlchemy + Elixir + SAContext * Templates: Mako * Widgets and Forms: ToscaWidgets + twForms + FormEncode * Authorization and Authentication: AuthKit * Internationalization (i18n) and Localization (L10n): Babel * JavaScript Library: jQuery * Site Search: Xapian

Welcome to the fourth installment of "Under The Grid", an irregular look at the mechanics underneath Second Life. This time we'll look at the basics of a bot. An automaton in avatar form. Building a bot is hard, right? The sole purview of C or C# programmers, you think? Not so. If you're familiar with python, and are willing to take some time to learn the structure of libsecondlife, you can put together simple task oriented bots fairly quickly. As with any programming task, the more complex the task the more research, writing and testing you will need to do. If you're going to start, start small. In many cases a simple task-oriented bot can automate an annoying task for you, while placing significantly lower demands on Second Life than logging in and doing it yourself. An important aspect of any Second Life automaton is to remember that Second Life is a shared space and set of resources and never to impose more load on the system than an ordinary avatar might. Less, if possible - and it is frequently possible.You'll need several things for this. You'll need to know your python. You'll need to download and build libsecondlife. You'll need ironpython. You'll need to know how to find necessary programming information on libsecondlife on your own. That said, if you can manage those things, read on. If not, you've got a bit more learning to do.

From these two SCDL documents, you can see that all the components are implemented in Python (as specified by the implementation.python elements) and the composite services are exposed using the REST binding. These choices are not mandated by the SCA runtime; any of the components could be implemented in any of the languages supported by the runtime, which currently includes C , Python, Ruby, and PHP for the Tuscany Native runtime. For instance, the sample includes a Ruby implementation of the POPChecker component that could be swapped in to replace the Python implementation. Equally, the choice of bindings used to expose a composite as a service can be easily changed, simply by altering the SCDL. For example, the Alerter Composite could also be exposed as a SOAP Web Service.

Ce tutorial traite de la procédure à suivre pour installer une solution LAMP (Linux, Apache, MySQL, Php/Perl/Python) sur un système (machine) disposant d'Ubuntu Dapper Drake (6.06 LTS) ou Edgy Eft (6.10) en mode graphique.

iBlocked est un proxy qui vous permet d'avoir accès aux sites interdits ou bloqués. Vous pourrez donc accéder à tous les sites que votre service informatique vous interdits.

voici des cours, tutoriaux, sous forme de vidéos et de documents qui vous permettent de vous mettre au dveloppement d'applications web avec Dotnet sans difficulté. Il existe des cours pour de nombreux niveaux. Il y a également des travaux pratiques permettant de s'entraîner

It seems likely that TurboGears and Pylons will merge. This looks like a good thing. ... It’s conceivable, it was definitely discussed a few times as well. It wouldn’t be so much a merger in any sense, as more of a coalescing of common parts. –Ben Bangert (On the Pylons mailing list) So, yes we did spend quite a bit of time talking about this at PyCon. And yes the word merger was used, but if you’re looking for some kind of big bang switchover, I think you’ll be disappointed. From my perspective, the philosophical approach behind all of our discussions has been “The more we can share parts the better.” But we all have taken it one step further — were we have different ideas about how things should be done, we need to weigh the relative merits of maintaining those differences against what those differences cost us. In particular I’m thinking about the cost in terms of mantaining: * separate libraries * separate documentation efforts * separate mailing lists * separate bug tracking systems * decreased visibility in the wider web marketplace * and ultimately separate user communities. .... Surprisingly enough, this is also something we have in common with the Zope guys, who have created a lot of great stuff that none of us got to use because it was too tightly integrated with the Zope core. They have been spinning out components pretty regularly for the last couple of years, and we want to work together with them more. Obviously, we won’t merge with Zope, but I hope that we can work with them in lots of interesting ways to move the state of Python web development forward. I for one would like to have access to their Transaction manager for multi-database transactions, and I worked a bit with Zope guys last week on integrating Tosca Widgets into their Forms system. What I want is for there to be diversity where there are real differences, and unity where those differences don’t matter. We don’t want to limit either framework, but we don’t want to have pointless duplication of effort either. .... Or, if we’re smart enough, creative enough, and and flexible enough, we may end up as one framework. To quote a line from Terminator 2 “The future is not yet set. The future is what we make it.“ ....

"A complex system that works is invariably found to have evolved from a simple system that worked." --John Gall, Systemantics To design a website you need to know about HTTP, XHTML, and URIs. To design a web application you need to know about HTTP, XHTML, and URIs. To design a web service you need to know about XML, SOAP, WSDL, UDDI, WS-Policy, WS-Security, WS-Eventing, WS-Reliability, WS-Coordination, WS-Transaction, WS-Notification, WS-BaseNotification, WS-Topics, WS-Transfer... What happened there? The web is the most successful distributed platform in the world, and it's simple enough for average humans to understand. How come adapting it for use by computer programs requires that smart people spend billions of dollars and devote years of their lives to coming up with all these new standards? And what happened to HTTP and URIs? The answer is that "Web Services" aren't the web. They're a heavyweight architecture for distributed object access, like COM and CORBA. This architecture is associated with the web, because HTTP is a trendy protocol, and flexible enough that you can implement almost anything on top of it. But it's not really of the web. The architecture of Big Web Services reinvents or ignores every feature that makes the web successful. This is the book that puts the "web" back into "web services". You can design a web service that uses HTTP, XHTML, and URIs. You just need to understand REST, the architectural principles that drive the web. RESTful Web Services gives you the tools you need to argue for sensible web services, and the strategies and code you need to create them. The book is manuscript complete at around 440 pages, and it'll be published by O'Reilly in May 2007. We think this can be the definitive work on the real-world use of REST.

Le pattern MVC: Comparaison ASP.Net et Monorail dans l’optique d’une utilisation Web Internet et Intranet

A practical comparison between Zope/Plone, Ruby on Rails, Turbogears, Django and J2EE.

Feedity (formerly FeedTier) is a web feeds generator for web pages without an existing syndication format like RSS or Atom. Feedity performs content analysis, picks-up the most prominent cluster of hyperlinks and automatically generates RSS web feeds from web pages without existing syndication. Feedity (beta) is an experimental service and free for personal use.

Vous cherchez à connaitre l'origine d'un mot, la biographie d'un grand homme , la bibliographie d'un grand auteur, la discographie d'un grand chanteur... Cochez "Encyclopédie" et vous allez parcourir de manière plus pertinente le contenu des plus grandes encyclopédies (version française) !

Flex is a way to develop Flash applications by programming. It includes a declarative XML language called MXML for laying out user interfaces, and a programming language called ActionScript, which is a superset of ECMAScript (that is, standardized JavaScript), with extra features like optional static type checking. ActionScript is a single language that works across all platforms, so you don’t have to worry about differences. Because it is based on ECMAScript, your JavaScript knowledge is not lost. All MXML components are actually written in ActionScript, which is what you use if you want to write your own components. Flex applications compile directly into SWFs (Flash binaries), which are then Just-In-Time (JIT) compiled by the Flash runtime, for extra speed.

Les blogs (cf. ce mot dans note lexique) sont des outils incontournables du Web 2.0. Ils sont, en quelque sorte, une amélioration de l’offre « Pages persos » des ancêtres tels que Multimania.fr et Respublica.fr. En effet, le système de création et de publication a été considérablement amélioré et il est désormais possible – pour le néophyte – de lancer un blog disposant d’une interface conviviale sans aucune connaissance en développement Web. Parmi les prestataires proposant gratuitement de créer un blog, nous pouvons mentionner Haut et Fort (http://www.hautetfort.com/), OverBlog (http://www.over-blog.com/) ou encore Blogger (http://www.blogger.com/) de Google. Outre ces services qui proposent d’héberger le blog sur leur plateforme (avec une adresse type comme "http://monjournal.hautetfort.com"), il est possible d’installer un logiciel de blog sur son propre serveur web pour disposer d’une plus grande autonomie ainsi que d’un nom de domaine propre. Le choix est là encore assez vaste : Dotclear (http://www.dotclear.net/), Worldpress (http://wordpress.org/) ou encore Drupal (http://www.drupal.org).

Le concept de Web2.0 s'est répandu comme une traînée de poudre, dans les milieux du Web tout d'abord, puis dans les médias grand public. Il semble ainsi que, près de 15 ans après la naissance du Web, les grands médias aient de nouveau de la matière à se mettre sous la dent à propos du phénomène Internet. Et comme d'habitude, avec un cortège d'approximations et de slogans plus ou moins marketing. Bref, le Web 2.0 est devenu une mode. Une raison de plus – a priori – pour Defidoc de ne pas en parler, tant il est vrai que notre ligne éditoriale est de s'élever au-dessus des modes et des phénomènes d'engouement superficiel. Nous avons tant vus de prétendues révolutions disparaître comme elles étaient venues, sans laisser de traces… Mais cette fois, en dépit de la mode, le phénomène Web 2.0 est vraiment sérieux, même s'il est difficile à cerner. Le concept lui-même a été lancé à l'anglo-saxonne, de manière très pragmatique, comme une nébuleuse indéfinissable, tout juste illustrée d'exemples "pour faire comprendre ce qu'on veut dire". On est loin de la conceptualisation à la française et l'esprit cartésien est toujours un rien dérouté par l'empirisme d'outre-Atlantique.