public marks

PUBLIC MARKS from pvergain with tags web & frameworks

09 March 2007

Merging TurboGears and Pylons , Zope

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.“ ....

07 March 2007

Presentation MVC et Monorail v2

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

03 March 2007

Zope/Plone, Ruby on Rails, Turbogears, Django and J2EE.

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

25 January 2007

DjangoPoweredSites - Django Code - Trac

Django-powered sites ¶ This page lists sites on the public Web that are powered by Django. WorldOnline is the Web development shop that created Django and open-sourced it. Django was originally extracted from Ellington, a commercially-available content management system for newspapers developed by World Online.

16 January 2007

Votre blog sous Symfony, pas à pas

Le choix d'un framework pour ses développements Web est donc un choix tout à fait justifié. Il existe différents frameworks - Cake PHP, Code Igniter, Ruby on Rails, Django pour ne citer que les plus connus et dynamiques du monde Open-Source. Il s'agit, au final, d'une question de choix personnel, de préférences, et pour bien choisir il faut avoir utilisé et testé plusieurs frameworks. Considérez-donc que ce tutoriel vous permettra de vous faire une idée plus précise de ce que vous permet de faire Symfony, et comment vous pouvez y parvenir.

Le comparatif de Rails, Django et CakePHP

by 2 others
Choisir un framework peut être une tâche difficile ! Pour vous aider dans votre choix, nous avons effectué un benchmark fonctionnel couvrant : * Django * Ruby on Rails * CakePHP Vous pouvez le télécharger sur notre page “Extras”. Ce benchmark a été réalisé avec Le projet web. Nous remercions pour leur participation les communautés Ruby on Rails, Django et CakePHP, que nous avons consultées afin que le benchmark soit le plus objectif possible :

08 January 2007