# condition è un qualche valore booleano
if str(condition) == "True":
    # fai qualcosa

Un pony è rimasto gravemente ferito è morto durante la scrittura del codice…

J’Attendrai – (French for “I Will Wait”) The original version was recorded by Rina Ketty in 1939, a French translation of the Italian song Tornerai (Italian for “You Will Return”) by Dino Olivieri,1933.

The QHCF recorded the song twice, the second one being filmed. It is the best film footage of Django performing according to djangopedia.

April/May 1938, Soundtrack – Paris – Stephane Grappelli (v), Django Reinhardt (g), Joseph Reinhardt, Pierre Ferret (g), Roger Grasset (b). – “Jazz Hot”(film)

Tears (Jean Reinhardt, Stephane Grapelli) – 21/4/37, Paris – QHCF – Stephane Grappelly (v), Django Reinhardt, Pierre Ferret, Marcel Bianchi (g), Louis Vola (b)

Conectemos nuestro pgadmin con postgresql localmente, hey hey en 4 paso:

Paso Uno

Así se ve pgadmin apenas lo instalemos, nos dirigimos donde se ecuentra como un símbolo de cable de plancha jajaja y damos clic , nos aparece una ventana de configuración:

Paso Dos

en la ventana anterior digitados los datos correspondiente a una conexión local como sigue acontinuación:

Paso Tres

le quitamos donde dice guardar el password !!! por proteccion de nuestros datos.

Paso Cuarto

Listo ya tenemos nuestras base de datos a la vista

En esta entrada tratare de tocar como activar el administrador de contenido de django, esto requiere activar la aplicación en el archivo de configuración del proyecto de django y crear la base de datos para esta. Después de seguir los pasos de entrando en onda con django y llevando un proyecto de django a  eclipse, vamos a activar la aplicacion de administrador de nuestro proyecto y a configurar algunas variables de nuestro proyecto pero sin antes mirar como instalar django.

Dentro de la estructura de archivos creados con el comando:

django-admin startproject proyecto

se editan los modulos, urls y settings, dentro de urls este modulo representa una tabla de contenido de todas la paginas que generamos con python:

http://midominio.com/blog/

en nuestro urla se declara que /blog/ representa una aplicación dentro de nuestro proyecto o puede ser una vista que muestre algo de información, por ahora activamos la función de administración :

en la linea 4 y 5 descomentamos y en la  linea 16 descomentamos la url para nuestro adminstrador. Listo ahora vamos a nuestro settings en donde configuramos algunas variables.

en la linea 7 de settings descomentamos y colocamos el administrador del proyecto o administradores, de la linea 12 a la 17 se habla del gestor de base de datos, que en esta oportunidad colocamos postgresql_psycopg2, luego el nombre de la base de datos que en mi ejemplo se llama blog, el usuario de la bd que es postgres, el password que en mi caso por prueba he colocado desarrollo, el host sera local es por eso que se coloca localhost y el puerto que es 5432 para postgresql.

En la linea 24 colocamos donde esta ubicada la aplicación que en nuestro caso es America/Bogota, en la linea 28 se coloca el idioma que es espaniol, es-CO, si se quiere ver mas opciones puedes seguir los enlaces que hay en la linea 20 que es la zona horaria y en la linea el unicode.

de la linea 74 a la 80 se habla de las aplicaciones que se crean para nuestro proyecto, si creamos una blog hay debe estar incluido, se dice instalado, bueno bueno instalamos es decir escribimos la aplicación de administrador al final de la lista, que en este caso es la linea 79.

Luego queda cuadrar la base de datos, nos dirigimos a nuestra terminal y entramos lo siguiente:

jonathanorlando@jonathanorlando-laptop:~/produccion$ sudo su
[sudo] password for jonathanorlando:
root@jonathanorlando-laptop:/home/jonathanorlando/produccion# nano /etc/postgresql/8.4/main/pg_hba.conf

en la lineas anteriores nos volvemos superusuario para administrar el sistema en este caso editar el archivo de postgresql.

al final del archivo encontramos para decirle a postgresql si debe pedir o no password, bueno en donde dice md5 le colocamos trust , menos en la ultima linea, guardamos el archivo con control + x, y reiniciamos postgresql con el comando:

root@jonathanorlando-laptop:/home/jonathanorlando/produccion# /etc/init.d/postgresql-8.4 restart

ahora en modo usuario normal le damos en terminal:

jonathanorlando@jonathanorlando-laptop:~/produccion$ psql -U postgres
psql (8.4.1)
Digite «help» para obtener ayuda.

postgres=#

en donde queda el #, escribimos

postgres=# ALTER USER postgres with password ‘nuevo’;

en donde nuevo es el nuevo passwdor del usuario postgres. luego de cambiar el password creamos una base de datos llamada blog de la siguiente manera:

postgres=# CREATE DATABASE blog;

si ya terminamos damos con el teclado control + d, para salir de psql y volvemos al archivo de configuración y cambiamos a como esta la imagen de arriba y reiniciamos a postgresql.

root@jonathanorlando-laptop:/home/jonathanorlando/produccion# /etc/init.d/postgresql-8.4 restart

ahora con el comando jonathanorlando@jonathanorlando-laptop:~/produccion$ psql -U postgres -W

podremos adminstrar postgresql en terminal, esta parte de postgresql la he tomado de url.

Bueno es hora de probar que funciona postgresql con django, entramos por terminal a donde se encuentra nuestro proyecto de django, estando hay le damos el comando siguiente para sincronizar nuestro proyecto con postgresql:

jonathanorlando@jonathanorlando-laptop:~/produccion/blog$ python manage.py syncdb
Creating table auth_permission
Creating table auth_group
Creating table auth_user
Creating table auth_message
Creating table django_content_type
Creating table django_session
Creating table django_site
Creating table django_admin_log

You just installed Django’s auth system, which means you don’t have any superusers defined.
Would you like to create one now? (yes/no): yes
Username (Leave blank to use ‘jonathanorlando’): admin
E-mail address: solosekenadase@gmail.com
Password:
Password (again):
Superuser created successfully.
Installing index for auth.Permission model
Installing index for auth.Message model
Installing index for admin.LogEntry model

listo las anteriores lineas deben aparecer la linea que aparece en rojo debes contestar que si para crear el usuario administrador, después de crear esto digitamos lo siguiente para correr la aplicación:

jonathanorlando@jonathanorlando-laptop:~/produccion/blog$ python manage.py runserver 8080
Validating models…
0 errors found

Django version 1.1.1, using settings ‘blog.settings’
Development server is running at http://127.0.0.1:8080/
Quit the server with CONTROL-C.

hay veces que cuando arrancamos la aplicacion nos dice el servidor de desarrollo de django que el puerto por defecto que es el 8000 se esta utilizando pues le pasamos el 8080 y tolis. Entramos a la url http://127.0.0.1:8080/ nos aparece lo siguiente:

nos marca un erro de url, en cual se muestra que hay disponible la url ^admin/ en la cual esta corriendo el administrador de nuestra aplicacion.

que bonita esta el login . Bueno entramos el usuario admin en mi caso y el password correspondiente, despues del login aparece lo siguiente:

esta herramienta es muy poderosa ya que podremos mesclar nuestras aplicaciones a esta herramienta con tan solo poco codigo, y lo mejor es que solo en python cool .

El proyecto django se propone crear una herramienta para elaborar aplicaciones web de una manera rapida codificando en python, esta herramienta se encuentra en nuestro repositorio de software dentro de Ubuntu. Procedo a instalar el software:

Entrar en nuestro gestor de paquetes synaptic y colocar en la búsqueda de paquetes django,  el paquete que nos interesa por ahora es python-django:

seleccionamos el paquete con doble clic, luego lo otro es el gestor de base de datos postgresql lo buscamos también en nuestro synaptic:

ahora necesitamos administrar a postgresql de modo gráfico, para esto utilizamos pgadmin:

en la imagen anterior se puede observar que tenemos en la parte superior pgadmin con la base de datos blog, y en la parte inferior de modo texto con psql que es la herramienta de adminstracion que viene con el paquete de postgresql, mostrando la misma base de datos. En la parte de la izquierda encontramos el paquete en nuestro gestor de paquetes synaptic.

Ahora queda el conector de base de datos para django, los conectores disponibles se muestran aqui:

en la linea 12 encontramos los conectores de las bases de datos que soporta django. El que utilizamos en esta oportunidad sera  python-psycopg2 que veremos en synaptic de la siguiente manera:

luego nos queda enviar a instalar los paquetes seleccionados. Ahora para saber si todo bien abrimos nuestra consola y escribimos lo siquiente :

Ahora estas listo para comenzar a tirar código.

I recently came across of need of models that are separated by discriminator. It means that I have one lookup table that is divided in parts by using one value in one column.

So my original model was like:

class LookupTable(models.Model):
    groupname = models.CharField(max_length=64)
    key = models.CharField(max_length=64)
    value = models.CharField(max_length=512)

I had dozens of models pointing to this single lookup table which started to be nightmare, specially with reverse relations. But I managed to figure one way out of this situation.

I used a piece of save code, custom manager and magical proxy functionality in Django and got quite neat approach. Not perfect but quite close.

So here is my magical GenericLookupManager

class GenericLookupManager(models.Manager):
    def get_query_set(self):
        qs = super(GenericLookupManager, self).get_query_set()
        try:
            return qs.filter(groupname=self.model.GROUPNAME)
        except (ValueError, AttributeError):
            return qs
        return None

Enhanced LookupTable model

class LookupTable(models.Model):
    groupname = models.CharField(max_length=64)
    key = models.CharField(max_length=64)
    value = models.CharField(max_length=512)

    objects = GenericLookupManager()

    def save(self, *args, **kwargs):
        try:
            self.groupname = self.GROUPNAME
        except (ValueError, AttributeError):
            pass # No GROUPNAME, pass

        super(LookupTable, self).save(*args, **kwargs)

And finally, how to use that model with proxying

class UserType(LookupTable):
    GROUPNAME = 'USER_TYPE'

    class Meta:
        proxy = True

Now you can use proxied model to save, load and query it. Overridden LookupTable manager and save takes care that groupname is always taken into account.

I haven’t spent this much time talking to journalism professors and students since I graduated from Texas Christian University (let’s just say some time ago).

I visited TCU last week to present seminars on the Complete Community Connection and journalism ethics in the digital age. And since I was sticking around for some memory-lane time, the curriculum committee at TCU’s Schieffer School of Journalism asked me to meet with them and tell them what I think journalism schools should be teaching about our swiftly changing field.

I shared my views with them and will share them with you here shortly. The TCU meetings continued a heavy fall schedule of consultations with journalism faculty and students on a variety of related topics:

• In late August, I was a panelist for the Accreditation Council on Education in Journalism and Mass Communication, sharing my views on how journalism schools should be teaching today and what sort of standards the council should require. Afterward, I shared some resources for journalism educators on this blog.
• In mid-September, I met with University of Missouri faculty to advise on plans for digital-only coverage of the Associated Press Managing Editors convention in St. Louis.
• Later in September, I presented an ethics seminar at the University of Kentucky. The visit included an informal discussion over pizza with students about what editors are seeking in interns and journalism graduates. I developed a post of career advice for journalism students and called their attention to an earlier post on the importance of your digital profile.
• The next week, I met with faculty advisers and editors of the Iowa State Daily, who came to Cedar Rapids to brainstorm issues such as digital coverage, C3 and organizational changes we’ve made at Gazette Communications.
• In November, I led another ethics seminar at the University of Nebraska-Lincoln and critiqued the senior portfolios of three UNL seniors (part of the UNL accreditation process, as well as providing advice to the seniors).
• Before visiting TCU, I returned to the University of Missouri for an American Society of News Editors/Reynolds Journalism Institute Ethics and Values Forum. Participants included journalism faculty from four other universities, in addition to Missouri. After dinner one night, we had an interesting discussion with several Missouri students, many of whom are already looking for jobs.
• I have had frequent discussions with David Perlmutter, new director of the School of Journalism and Mass Communication at the University of Iowa, including plans to team-teach a course with Jim Cremer on creating an iPhone application.

In various ways in formal events and private conversations, similar concerns about how to teach journalism today came up again and again. If I could summarize the concerns (admitting that I am drawing conclusions that weren’t always stated explicitly), I would say this: Lots of journalism educators worry how they can and should teach to prepare students for a world that has changed vastly since professors practiced and/or earned graduate degrees and is changing so swiftly that even if professors were current in all respects, their lessons may be outdated by the time their students graduate. While journalism school enrollment is stronger than the businesses that support journalism, educators are keenly aware that they need to update their curriculum and knowledge or they could face the same sort of crash that news media companies are experiencing.

My response focuses heavily on what journalism schools should be doing to address new needs and challenges. I have not looked at closely at what they should not be doing. But I would suggest that in the current environment, every requirement and every course needs to be re-examined and face demanding questions:

• Does the course need to be updated?
• Should the course be dropped?
• Should the course be taught less frequently?
• Should the course be combined with another?
• Should a required course become an elective?

Journalism schools also need to examine their tracks, sequences and structures. If your school offers a “print sequence,” you might as well call it an “outdated sequence.” While newspapers still command large audiences and generate large revenues, newspaper companies are diversifying and journalism schools need to be educating multi-platform journalists, not print journalists.

As I go through topics that journalism schools might not be covering adequately, I would argue that many of these issues don’t need to be addressed in a standalone class, required or elective. Rather, they should be integrated throughout the curriculum. For instance, if you offer an elective course in Twitter but don’t teach students in your basic reporting course how reporters should use Twitter, you aren’t teaching what you need to teach. I would advise requiring students in their first media writing course to spend at least a couple weeks taking their class notes in Twitter, so they get an early practical exposure and see it as a tool for journalism from the start. And each course should decide the appropriate way to use Twitter in that course.

In other cases, a required or elective course – or perhaps a course combining a few of these topics – might be exactly what a journalism curriculum needs. I will make specific recommendations about how digital skills should be infused throughout the curriculum and about specific courses a journalism school should consider. But as curriculum committees and J-school leaders consider these issues, they will need to consider other factors. As j-schools weigh such factors as course loads, total hours students can take and so on, I would usually err on the side of incorporating digital skills throughout the curriculum, rather than addressing them in specific courses.

These are the topics I think journalism schools need to address:

Social media. Journalism schools today need to educate students about how social media are changing professional media and society. Twitter is the social platform that needs the most attention right now, but professors need to stay abreast of how society and journalists are using social tools and update their courses appropriately. If Twitter goes the way of MySpace, you need to adjust swiftly to address the next hot social tool. Students are already active in using Facebook, so Facebook is less urgent. Professors also should consider how to use Facebook in courses, such as using a fan page for assignments and exchanges about a course. My primary recommendation here is that social media need to be incorporated throughout the curriculum: Twitter in media writing, reporting, ethics, specialized reporting courses, appropriate strategic communication courses, etc.; visual journalism courses should cover such social tools as YouTube, Flickr, Twitpic and Qik. Ethics courses certainly need to incorporate social media, including Facebook. I also would recommend an advanced course on social media strategy. This would focus on how media organizations need to use social tools to engage the community and serve business customers. This course also would cover potential uses of emerging social tools. This should be an advanced or graduate-level course, serving journalism and strategic communication sequences.

Interactive databases and computer-assisted reporting. I have been critical before of the use of the term computer-assisted reporting. You might as well refer to notebook-assisted reporting or telephone-assisted reporting. This is 2009 and computers have been an essential tool for reporters for a couple decades now. Journalism schools should take the lead in breaking down the data ghettos that have emerged in our profession. Basic reporting courses should cover use of basic spreadsheet, database and mapping programs. These are essential journalism tools and skills and their use should start in basic courses and be required throughout the curriculum. An advanced course should cover development of interactive databases using such tools as Caspio, Django and Ruby on Rails. Again, these skills are as valuable to strategic communication students as to journalism majors.

Programming. As I mentioned to the TCU curriculum committee, I encourage working with a computer science department to develop cross-disciplinary courses such as my iPhone app course at Iowa. I also encourage working with the computer science department to develop double-major or major-minor combos to help “hacker journalists” get the appropriate education in journalism and programming. (I’m delighted that two students in the iPhone class will be double majors in journalism and informatics.

Mobile journalism. Basic reporting courses should introduce students to the multitasking skills and demands of mobile journalism. The University of Missouri is requiring journalism students to buy iPhones. I don’t know how important it is to specify a brand (I do use an iPhone), but I think requiring students to use smart phones as journalism tools is an excellent idea. If I were teaching a reporting or multimedia course now, I would require that some specific assignments be carried out entirely with a mobile device. This would require writing on the phone, shooting still photos and video and providing geocoding metadata. An advanced course(s) could focus specifically on mobile journalism, such as developing mobile applications or a mobile-first strategy.

The business of journalism. Journalism students need a more thorough introduction to the business of journalism than I received as a student (almost none) or than students receive today. They need to learn about traditional business models for print and broadcast. They should understand the disruption that is causing the collapse of the business models. They should understand why and how some organizations are seeking to try paid-content digital models (and they should understand how paid content has been tried before and that it hasn’t worked). They should examine and understand efforts to develop new business models (such as my own Complete Community Connection model). They should learn about product development and entrepreneurial journalism. They should understand how the advertising model is collapsing on all platforms and study efforts to develop new revenue streams. Tim McGuire’s Business and Future of Journalism course at Arizona State University provides a good model. While some coverage of business models would be good in lower-level courses, an upper-level course is a good idea and I would encourage requiring it for all students or for some particular majors. The lack of business literacy is a huge problem among journalists and tunnel vision on business issues is a huge problem for people in advertising and executive offices.

Community engagement. Interaction is a significant part of the future of journalism, from crowdsourcing of stories (investigative, events, features, reviews) to engaging comments on blogs to aggregating the work of community bloggers and citizen journalists. This could certainly be a full course.

Digital content in specialized courses. A question raised in an email about TCU’s curriculum asked how much digital content should be integrated into advanced courses on journalism specialties, such as public affairs reporting and sports reporting. My answer is that the courses should have as much digital emphasis as the specialties have now, and that’s a lot. For instance, even TCU sportswriting legend Dan Jenkins, became a Twitter icon this year at age 79. Blogging, liveblogging and video are essential parts of sportswriting now, and the traditional game story is declining in importance to the point that sports writers are debating whether it’s dying. Any course on a specialty should reflect the current state and projected direction of that specialty.

Visual journalism. Photojournalism and graphic arts, as narrowly defined for much of my career, are outdated journalism specialties. While those skills remain important, visual journalists need to master (and be taught) a range of digital skills: video, audio, animation, multimedia graphics using programs such as Flash. And, of course, visual journalists need to learn ethical standards for using all these new tools and skills. Journalism students learning graphic arts should certainly learn how to make print graphics, but they also should learn to develop interactive multimedia, including simulations and games.

Live coverage. Increasingly, journalists need to provide live, unedited coverage of events. Whether in a reporting course, a visual journalism course, a live-coverage course or all three, students should learn how to liveblog, stream live video and aggregate real-time public content from social media.

Managing digital content. Digital journalism and strategic communication both will require a range of digital skills that are rapidly developing. The specific content of such a course and the balance of topics covered would change by semester, but someone should stay abreast of issues such as search-engine optimization, analytics, tagging, curation, aggregation, archiving, content-management systems and semantic technology. Some of these topics need to be introduced in lower-level courses, but they easily could be an upper-level course.

Design. Print design is fading in importance as newspapers cut newsholes and resources and require more regional design and use of templates. But web design and mobile design are areas of growing importance. Design courses should be adjusted accordingly.

Blogging. I don’t see a need for a course specifically in blogging (though I wouldn’t object either). Blogging should be part of nearly every writing course. In many courses, students should be required to keep a course blog. I evaluated portfolio blogs for seniors at the University of Nebraska, and I would encourage any journalism school to require students to maintain portfolio blogs.

Link journalism. Students need to learn how to use links, which are the footnotes of the digital world. This certainly should be part of reporting and editing courses.

Law and Ethics. As I address in my Upholding and Updating Ethical Standards seminars, ethics education needs to address a wide range of digital issues. Of course, digital journalism presents many legal issues as well. In fact, many (I suspect most) editors and journalism professors continue to follow outdated advice on court interpretations of Section 230 of the Communications Decency Act.

First Amendment. The American Press Institute, where I worked for three years, collaborates with the First Amendment Center and the Freedom Forum to take our seminars to programs on the First Amendment. These programs gave me both a deep appreciation of our First Amendment freedoms and a keen realization that professional journalists don’t know enough about the history and current status of the First Amendment and the freedoms it guarantees. A First Amendment course could be a cross-disciplinary course with credit in journalism, religion and political science. With TCU’s international communication major, this course should include units on restrictions on our key freedoms in other nations.

TCU’s curriculum committee asked me whether I thought professionals would be interested in a certificate program in digital journalism for professionals needing to update their skills. While ability to pay might be impaired by staff reductions and fears about job security, I think interest in such programs would be high. I encourage journalism schools to offer such programs in person and/or online, and to either develop financial aid support for such courses or to cut down the university overhead in determining tuition, since professionals would not draw as heavily as younger students on university resources. Such a certificate program should allow considerable flexibility for professionals to fill the gaps in their own skills.

Many journalism schools will be hard-pressed to update their curricula as I’ve described (though some certainly are already doing some of these things). They will need to hire more faculty with digital skills, use adjunct faculty with digital skills and require faculty to update their own skills and knowledge.

I’m glad journalism schools are considering these issues and I hope they move decisively and swiftly to update.

Sometimes I wonder if getting to do an Xmas album with a lot of schmaltz means you’ve made it in the record industry with the seemingly endless stream of releases. When there is finally something different from a group this reviewer immediately takes notice. Such is the case with the Cool Yule release.

Operating under the guiding principle of what would Django do with bumper stickers available (www.hcsf.com), The Hot Club of San Francisco have released a refreshing change in a Xmas album for 2009. Patterned after the music performed by Grappelli and Reinhardt with the Quintette du Hot Club de France in the 30’s which featured string instruments (no percussion) in a unique jazz style. Even if you like percussion as I do your ear will quickly adapt to the bass beat.

Starting off with “Cool Yule,” a somewhat obscure Steve Allen song, the group sets the tone for the CD. Featuring a cool vocal, guitar, and violin solos in a foot stomping style the table is set. The gypsy/latin arrangement of “Don Rodolfo” follows in an arrangement of Rudolph the likes of which I’m sure you’ve not heard before. “Sugar Rum Cherry,” from Tchaikovsky’s Nutcracker Suite and originally arranged and performed by Ellington is an example of what a jazz group can do with any melody. You can certainly hear the influence from Duke with the wa- wa trumpet. “I’ll Be Home For Christmas” is the only arrangement that schmaltz is the order of the day. “Baby It’s Cold Outside” is the other vocal number on the CD and it is a pleasant exchange between Isabelle Fontaine and Jeff Magidson.

If your looking for something unusual and out of the ordinary for some of your Xmas music for this year I think you’ll find this release to be an attractive offering. Recommended.

CD# is Azica AJD-72242

Produced by Alan Bise

Mixing and Mastering by Alan Bise

Track Listing:

1. Cool Yule (2:17)

2. Don Rodolfo (5:00)

3. Carol of the Bells (4:53)

4. I’ll Be Home for Christmas (3:00)

5. Baby It’s Cold Outside (4:23)

6. Djingle Bells (6:51)

7. Sugar Rum Cherry (3:35)

8. I Wonder As I Wonder (4:49)

9. March of the Toys (4:55)

10. The Christmas Song (4:52)

11. Santa Claus is Coming to Town (2:54)

12. Auld Lang Syne (7:40)

Total Track Time is 51:09

There is an interesting scenario regarding automation of routines related to model.
I want make my model in such a way that, everytime it is modified by some user, it should automatically set “modified by” field with current logged in user.
first step is to override “save” method in model, do update fields as you require and call super class save method.
but the question is, how model can access logged in user object, there is no request object wright?
there is a way with thread locals to deal with this kind of situation, click on following link
thread local and user objct in django models

Mi primer código en python, trata de plasmar de una manera facíl un bloque de código orientado a objetos. Dandome cuenta que lo aprendido en mis clase de java en mi carrera me ayudan a entender la programación y la lógica  que guarda las aplicaciones dentro, en esta ocación me pregunto como comenzar en python y de una manera que no sea traumática,  tome la situación de un registro de un estudiante, cosa que pasa a menudo, he realizado la herencia dicho estudiante con una clase persona, y mi registro de estudiantes será guardado en una estructura de datos llamada lista.

Luego de tener registrado a los estudiantes realizo la impresión de los datos de cada estudiante.

Estamos listos para ingresar en el fantabuloso mundo de python, entramo a eclipse y señalamos la casilla de un nuevo proyecto:

Nos aparece una ventana en la cual seleccionamos el tipo de proyecto que se desea comenzar, en este caso como usuamos el plugins de python para eclipse pydev, damos clic en pydev y buscamos pydev Project.

La siguiente ventana nos pedira el nombre del proyecto en mi caso lo he llamado clase.

Le damos finish y todo listo para entrar a digitar codigo. Veremos algo como esto:

Estamos parados dentro de nuestro proyecto clase, la carpeta src nos guarda todo el codigo fuente, tenemos la ruta del interprete de python dentro de nuestro sistema.  El paso siguiente es crear un paquete dentro de nuestro proyecto, le damos clic derecho en la parte azul de la imagen de arriba que es el nombre de nuestro proyecto, y tomamos la opción New, luego buscamos donde dice pytho packege.

Nos pedira el nombre del paquete, le he puesto general.

Lo que caracteriza a una carpeta dentro de un proyecto de python que sea un paquete es el archivo __init__.py. De nuevo le damos clic sobre el nombre del proyecto y seleccionamos New, buscamos la opción de new module, un modulo es un archivo .py, nos aparece una ventana en la cual nos pedira el nombre del modulo que en mi caso he colocado ejemplo, no es necesario colocar  .py.

Veremos algo como lo que sigue:

hey !!! hey !!!! ya estamos listo para crear nuetro proyecto. Dentro de nuestro modulo ejemplo escribiremos todo, el ambiente de trabajo que vamos a simular es un registro de algunos estudiantes, y practicamos herencia y  funciones. Listo muestro lo que es la clase Persona:

En la linea 1 se escribe la linea en la cual el modulo encuentra el interprete de python dentro del entorno de ejecución. De la linea de 3 a 6 es un comentario para la api del proyecto. De la 8 a la 28 se declara la clase Persona. De la 9 a 11 se declara el constructor de la clase en la cual se declara los atributos de la clase Persona en esta clase se ha declarado nombre y cedula. Explico lo que significa la linea 10 y 11 es en la cual se asigna los atributos que en este caso se encapsulan en modo private.

self.__nombre = nombre

self.__cedula = cedula

Cuando tienes una asignación de la siguiente manera self.__ ,  quiere decir que es una variable privada. Luego en la linea 14 declaramos los metodos get de la clase Persona, en este caso los get de nombre y cedula.  Los metodos get sirven para mostrar lo atributos privados de la clase. En la linea 21 declaramos los metodos set de la clase Persona estos metodos nos permite actualizar los atributos privados de la clase. Por ultimo declarmos un metodo toString que es una cosa que me quedo de java, pero si no lo quieres implementar no importa. Este metodo lo que hace es imprimir los atributos de una forma ordenada.

Luego coloco la clase Estudiante con herencia hacia Persona.

De esta clase solo se explica la linea 31 en la cual se declara la herencia dentro de los parentices, en python se puede hacer herencia multiple en la cual separas las clases con comas. Entonces dentro del constructor de Estudiante debo ejecutar el constructor de mi padre Persona que seria de la siguiente manera:

Persona.__init__(self, nombre, cedula)

le pasamos los datos al constructor padre. Y luego se asignan los nuevos atributos de Estudiante que efectivamente son privados. Al final de la clase declaro toString para mostrar los datos ordenados, como tengo herencia hacia Persona ejecutamos el toStrinf de Persona primero y luego los datos de Estudiante.

Ahora tengo una serie de metodos que manipulan ls clases.

Comienzo con un metodo imprimir en el cual le paso un lista y con un for recorro e imprimo todos los objetos que he guardado. Por cada elemento ejecuto el toString() de cada objeto Estudiante. Entonces el metodo main declaro la lista vacia para guardar los objetos Estudiantes, luego una variable llamada numeroEstudiantes en la cual por asuntos de prueba, solo coloco 2 iteraciones. Utilizo un while para recorrer las dos opciones, por cada iteración agrego con el metodo de la lista append cada Estudiante, con el metodo de captura de datos raw_input tomo los datos de cada Estudiante.  Por ultimo ejecuto el main con el truco:

if __name__ == “__main__”:

Ahora ejecutamos,

para probar el codigo nos dirigimos hacia el botón verde de play en la parte superior, luego buscas la opción python run !!! y tolis te aparece la consola, debajo en el cual puedes introduccir los datos.

Hey hey me dio mucho gusto escribie este post un saludo

Serwer kolos daje nam możliwość umieszczania swoich skryptów napisanych przy pomocy frameworka Django. By przenieść się w fazę “produkcyjną”, w katalogu /home/user/public_html wrzucamy plik .htaccess o następującej zawartości:

SetHandler mod_python
PythonPath "['/home/user/django_projects'] + sys.path"
PythonOption mod_python.importer.path "['/home/user/django_projects']+ sys.path"
PythonHandler django.core.handlers.modpython
PythonDebug On
SetEnv DJANGO_SETTINGS_MODULE nazwa.settings


Przy czym nasze projekty umieszczone są w katalogu /home/user/django_projects i nazwa, to nazwa projektu z tego katalogu. Linijka, gdzie się znajduje “PythonDebug On” powinna być odkomentowana tylko na czas sprawdzenia instalacji.

Hello world.

I’ve created this blog for myself mainly so I can collect and organize various info regarding developing web-apps with Django & Python.

But, nonetheless, if this blog will help somebody to solve an issue they have – that’d be great.

So, let’s go. Let’s see what I’ll be able to come up with.

Um dos maiores problemas da sociedade moderna é a dificuldade de locomoção diária, a maioria das pessoas passa horas em seus carros, ou em meios de transporte públicos para irem de lugar a outro. Há alguns anos atrás quando morava na zona norte de São Paulo e trabalha na zona sul, essa era minha realidade. Uma vez que naquela época passar por isso era inevitável procurei formas de fazer com esse tempo pudesse de alguma forma torna-se produtivo, foi então que comecei a ouvir à podcasts.

iPod FM radio remote por dan taylor

De acordo com a Wikipedia, Podcasting é uma forma de publicação de arquivos de mídia digital (áudio, vídeo, foto, etc.) pela Internet, através de um feed RSS, que permite aos utilizadores acompanhar a sua atualização. Assim, é possível o acompanhamento e/ou download automático do conteúdo de um podcast.

Neste post apresentarei os podcasts aos quais escuto e os episódios principais para que você ouça. Sugiro que você utilize o iTunes para inscrever-se nos podcasts e sincronizar com seu iPod.

Desenvolvimento Ágil

por pcalcado

Podcast da ImproveIt

por Vinícius Teles
http://improveit.com.br/podcast
Português

• Entrevista com Alisson Vale da Phidelis
• Entrevista com Alexandre Magno na Série Experiências Ágeis
• Entrevista com Carlos Barbieri sobre o MPS.BR
• Entrevista com a equipe da Ancar na Série Experiências Ágeis

AgilCast

Por AgilCoop
http://agilcoop.incubadora.fapesp.br/portal/agilcast
Português

• Uma Visão Geral Sobre Scrum
• Testes Automatizados
• Bancos de dados ágeis e refatoração de bancos de dados

Agile Toolkit Podcast
http://agiletoolkit.libsyn.com
Inglês

• Tom Goulet – Cucumber, Ruby and the transition to Generalizing Specialist (2009)
• Jim Miller – The Product Owner Role and Business Alignmnet
• Tips and Advice – Retrospectives

ThoughtWorks Podcast

http://www.thoughtworks.com/what-we-say/podcasts.html
Inglês

Open Source

FLOSS Weekly

por Leo Laport, Jono Bacon e Randal Schwartz
Inglês

• Entrevista com Kent Beck sobre Extreme Programming (XP)
• Entrevista com Linus Torvalds, o criador do Linux e do Git
• Entrevista com David Heinemeier Hansson criador do Ruby On Rails
• Entrevista com Tim O’Reilly, fundador e CEO da  O’Reilly Media
• Entrevista com John Resig criador e líder do Projeto jQuery
• Entrevista com Jan Lehnardt evangelista do projeto CouchDB
• Entrevista com  Jacob Kaplan-Moss criador do Django
• Entrevista com Bruno Souza sobre o OpenJDK
• Entrevista com Ward Cunningham inventor do Wiki e grande Personalidade da Comunidade Ágil
• Entrevista com  D. Richard Hipp criador do SQLite
• Entrevista com Nate Koechley sobre o Yahoo User Interface Library (YUI)
• Entrevista com Junio Hamano, Mantenedor do Git
• Entrevista com Rasmus Lerdorf, criador do PHP
• Entrevista com Guido van Rossum, Criador do Python
• Entrevista com o fundador da Wikipedia, Jimmy Wales

Java

HorecaExpo - Java por bramloquet

JavaPosse

Por Tor Norbye, Carl Quinn, Dick Wall e Joe Nuxoll
Inglês
http://www.javaposse.com

Java Technology Insider

Inglês
http://www.javaworld.com/podcasts/jtech

• Rod Johnson: SpringSource and the future of Spring (2008)

Grails Podcast

Por Glen Smith e Sven Haiges
http://grailspodcast.com

Ruby

Ruby on Rails por Andrew*

Rails Envy

Por Jason Seifer e Gregg Pollack
Inglês
http://railsenvy.com

Rails Podcast

por Geoffrey Grosenbach
Inglês
http://podcast.rubyonrails.com/

• Entrevista com David Heinemeier Hansson (2005)
• Entrevista com Dave Thomas (2005)
• Entrevista com Chad Fowler (2005)
• Entrevista com Obie Fernandez (2006)
• Entrevista com Dave Thomas e Mike Clark (2006)

Rubiverse Podcast

Por Mike Moore
Ingles
http://rubiverse.com

• Dave Hoover on Software Crafsmanship (2009)
• Obie Fernandez on the Rails Maturity Model (2009)
• Ola Bini on Polyglot Programming (2008)

JavaScript

jQuery Podcast

Português
http://blog.jquery.com/2009/11/13/announcing-the-official-jquery-podcast/

Gadgets

GeekBrief TV

por Cali Lewis
Inglês
http://www.geekbrief.tv

Software

Desk por Guillermo Esteves

Pragmatic Podcasts

por Pragmatic Bookshelf
Inglês
http://www.pragprog.com/podcasts

• Chad Fowler on the Passionate Programmer
• Fred Daoud on Stripes
• Chad Fowler Finding the Jagged Edges
• Andy Hunt on Pragmatic Wetware

Software Engineering Radio

por Software Engineering Radio
http://www.se-radio.net
Inglês

• Software Archaelogy with Dame Thomas
• Fearless Change with Linda Rising
• Learning as a Part of Development with Allan Kelly
• SQL with Jim Melton
• Continuous Integration with Chris Read
• Top 10 Architecture Mistakes with Eoin Woods
• Usability with Joachim Machate
• Introduction to AOP with Christa Schwanninger e Iris Groher
• Retrospectives with Linda Rising
• 10 years of Agile Experiences
• Joe Armstrong on Erlang
• Interview Dave Thomas
• Dick Gabriel on Lisp
• Jeff DeLuca on Feature Driven Development
• Interview Erich Gamma
• Gerard Meszaros on XUnit Test Patterns
• Static Code Analysis with Jonathan Aldrich
• Refactoring Pt. 1
• Refactoring Pt. 2
• eXtreme Programming Pt.1
• eXtreme Programming Pt.2
• Agile Documentation
• Interview Jutta Eckstein
• Interview Eric Evans
• Patterns

Elegant Code

por Elegant Code Community
http://elegantcode.com
Inglês

• Agile for Families
• Entrevista com Jim Wierich o Criador do Rake (Ruby)
• David Laribee on Lean / Kanban
• Uncle Bob Martin on Clean Code
• Alan Shalloway on Lean
• Entrevista com Jarod Ferguson
• Entrevista com Darrel Carver
• Entrevista com Scott Nichols
• Entrevista com Scott Schimanski

Google Developer Podcast

http://code.google.com/p/google-developer-podcast/downloads/list
Inglês

Hearding Code

http://herdingcode.com
Inglês

Tecnologia

IT Conversations

http://itc.conversationsnetwork.org
Inglês

net@Night

por Amber MacArthur e Leo Laport
http://www.twit.tv/natn

Twit – This Week in Tech

por  Leo Laporte, Jeff Jarvis, Baratunde Thurston, e John C. Dvorak
http://www.twit.tv/twit

MacBreak Weekly

por Leo Laporte, Don McAllister, Paul Kent, and Andy Ihnatko
http://www.twit.tv/mbw

This Week in Google

por Leo Laporte, Gina Trapani, Jeff Jarvis e Mary Hodder
http://www.twit.tv/twig

SitePoint Podcast

inglês
http://www.sitepoint.com/podcast

Empreendedorismo e Negócios

37 Signals Podcast

por 37 Signals
Inglês
http://37signals.com/podcast

Max Gehringer (CBN)

por Max Gehringer
Português
http://cbn.globoradio.globo.com/servicos/podcast/NOME.htm

Mundo Corporativo (CBN)

por Heródoto Barbeiro
Português em Áudio
http://cbn.globoradio.globo.com/servicos/podcast/NOME.htm

The Startup Success Podcast

http://startuppodcast.wordpress.com
Inglês

TED Talks

por TED Talks
Inglês
http://www.ted.com

Se você quiser incluir algum outro podcast nesta lista, deixe um comentário. Espero que seja Útil!

Jag målade in mig lite i ett hörn när jag började med den här serien med inlägg. Ingen dag har känts helt rätt för att skriva det sista inlägget – det i sin tur har hindrat mig från att släng in smånotiser i bloggen med. Trist.

Nu är det så dags att avsluta, storstilat avsluta till och med. Detta inlägg kommer att behandla och vara en historieskrivning för Blekinge studentkårs aktiva arbete med öppen källkod. Studentkåren har länge varit en förkämpe och stor nyttjare av öppen källkod men man har inte precist levt som man lär. Vi är väl inte hela vägen fram i något som andra kan ta del av men ambitionen finns där.

Vårterminen 2005 började jag engagera mig i studentkårens sektion för kårpuben i Ronneby. Som nyvald informationsansvarig blev jag involverad i driften av informationssystemet som en ensam stackare utvecklat för sektionens vinst. När jag var en del av driften av de fysiska maskinerna blev jag snart en del av utvecklingen av koden också. Det var inte precis något kontrollerat och snyggt uppstyrt bygge vi hade att göra med här. Men det funkade och folk var nöjda med hur det blev. Åren gick och när jag lämnat sektionen satt jag kvar med inloggningar och hjälpte till med lagningar. Efter mig på informationsposten hamnade Lars/Läffe/Laeffe – även han hängde kvar och i sin tur drog han in Jonas/DrLaban i det hela. Det var bara underhåll och i någon yttepytte mån kunde det hamna en ny funktion på sidan. Undantagsfall. Tills sommaren 2008.

I maj 2008 tog DrLaban initiativet till att vi skulle göra något mer med det som kallas “kårsajten“. Laga fel, lägga till funktioner och helt enkelt ta hand om den. Jag skulle börja min sista termin på BTH och hade inget särskilt för mig utöver studier. Det är dessutom roligare om man kan snacka med nån om det man gör än att bara sitta hemma och hitta på egna ideer och se om de funkar. Jag hoppade på tåget. Med följde dessutom både DrLaban och Laeffe. Snart hörde Emma/Soya och Thomas/Tomten av sig och även de hakade på. Tomten mer åt drift, säkerhet och kringsystem medan Soya grävde ner sig rejält i koden tillsammans med oss andra tre. Vi jobbade på bra, DrLaban och Laeffe drev på i utvecklingsmetodikspåret som de vana PT-studenter de är och en metod närliggande Scrum började nyttjas. Allt gick inte tokbra men det blev ganska snyggt. Vi strukturerade upp källkoden i ett kodförråd i Subversion, kopplade det till projektverktyget Trac och det skapades en massa dokumentation och ideer på nya funktioner och koncept föddes. Vi drog lite åt olika håll och vi gör väl det fortfarande men arbetet löper på så jädra snyggt månad efter månad. Det har nu gått ett och ett halvt år i arbetet med kårsajten, vi har numera börjat jobba med att ta in åsikter och ideer från kårhussektionerna som en naturlig del i processen. Ytterligare en källa till inspiration och irritation. Det ser ut att gå riktigt bra.

Men det är inte änden på historien, det är snarare historien i sin linda. För ungefär ett år sedan började kårstyrelsen intressera sig för vad vi sysslade med. Jag hade aviserat att jag skulle nog flytta från Blekinge halvsnart så det stöd jag var i att ta hand om mailsystem och annat behövde omvärderas.

För att vi fem skulle kunna utveckla kårsajten på ett bra sätt framöver och för att kunna skänka lite struktur för vem som äger vad och hur saker förhåller sig till studentpopulationen så diskuterade vi organisationsform. Att sträva efter att bli en del av studentkårens paraply var vi helt ense om från början. Hur det skulle genomföras var mer svårdefinierat. Vi skrev en Verksamhetsförordning (typ stadga) som reglerade hur arbetet sköttes och leddes och hur vårt förhållande till organisationen såg ut. Den antogs av Kårstyrelsen i december 2008. När vi väl hade blivit Sektionen för Internetbaserad Socialisering så hörde Kårstyrelsen av sig och undrade om vi inte kunde ha tid för övriga delar av verksamheten, typ 15-20 servrar och klientdatorer, skrivare, nätverk, kassaapparater och sånt. Det var inte riktigt vad vi planerat och kanske var det inte vad vi skulle gjort men glada och trevliga och vänliga som vi är så sa vi ja och bad att få återkomma med ett förslag på hur.

SIS skulle omformas men grundtanken och processerna skulle kvarstå. Hur i hela friden då? Vi lyckades skapa en organisation i studentkårens sektionsramverk med två nivåer. En visionär övergripande styrelse(Äldsterådet) och autonoma undergrupper (basgrupper). Basgrupperna sätter sina ramar själva om hur de jobbar med vilka verktyg och vilka som är en del av dem. De enda kraven i organisationen är att basgrupperna leds av någon i Äldsterådet, att allting ska göras så öppet det bara går för att leva med den öppna källkodens natur och att sektionen inte ska vara ekonomiskt beroende av någon.

Funkar det då? Det har snart gått ett halvår med den nya organisationen. På papperet fungerar det utmärkt. Fysiskt vet jag inte riktigt. Kårsajtsgruppen jobbar på som sagt. Driftgruppen som tar hand om fysiska maskiner och nätverk och sånt ser ut att funka men det är mycket personberoende och mycket adhoc snarare än strukturerat och tydligt. Väldokumenterat är det dock i driften. För övriga delar är arbetet inte särskilt tydligt eller ens särskilt påtagligt alls. En av grupperna är den jag själv leder, leder och leder förresten. Det har inte hänt så mycket men bot och bättring hoppas jag på =)

Jag tror att konceptet med SIS är bra. Grundstommen i hur gruppen funkar är jättebra. Vi har en del berg kvar att bestiga, ett av dem är att skaffa fler som kan hjälpa till. Vi har alldeles för lite resurser för den kostym vi tagit in i provrummet just nu. Därmed inte sagt att vi inte kan leverera för det kan vi, alla som är med sliter så sjukt hårt och är hjälpsamma och glada och trevliga. Det är nästa steg som saknas och det är ett jädra hästakliv att ta.

Låt oss titta lite mer på det här med tekniken i gruppen. Jag nämnde att kårsajten kör en utvecklingsmetod närliggaden Scrum. Processen för den finns ganska väl dokumenterat i wikin vi använder men i korta drag har vi anpassat saker för att fungera distribuerat på nätet och utan att alla involverade har projektet som huvudsyssla. Istället för dagliga möten har vi avstämningar tisdagar, torsdag och söndagar – kort och koncist för att fånga besvären i projektet. Dessutom håller alla till på Trac, IRC och mail så det går att få hjälp relativt omgående. Kårsajten är ett stort PHP-bygge med en MySQL-databas i botten och ett eget ramverk i PHP ovanpå en Debianmaskin som kör Apache.

Som konstrast till strukturerade Kårsajten så har vi då Diariet och 2.0/www, Diariet har haft möten och jag har en intention på hur jag vill jobba med uppdraget men det är inte mycket mer än så idag. Bland annat är det klart och färdigt att vi kommer att skriva den mesta koden i Python och nyttja Django som ramverk – nya impulser och nya intryck för SIS. 2.0/www styrs av Laeffe och ävan han är helt adhoc så vitt jag vet. Jag tror att det kommer en rejäl runda med grejjer inom de närmsta månaderna där – det uppdraget är dock mycket mer löst specat än mitt eget som faktiskt ska producera något färdigt till den siste juni 2010.

Blekinge studentkår är inte öppen källkod än men det finns stor potential i det vi bygger inom studentkåren vad gäller både källkod och kultur för att vi snart ska kunna flytta mer saker till öppenheten.

Läs även andra bloggares åsikter om öppen källkod, open source, php, python, apache, mysql, django, blekinge studentkår, bth, sis

I like to separate my applications from project code. So basically my project contains only bunch of settings files and bunch of modules. One day I felt that different setting.py files was too much. Most of my settings are static so I found out  local settings approach.

I have second configuration file, named local_settings.py to contain settings that are local for that particular instance. And that file is kept as small as possible just to make things easier. It’s imported quite end of settings.py to override any setting there.

This is nothing new actually. But then I felt that why I always need to play with PYTHONPATH settings and such? Why things just can’t work seamlessy. And while wondering that I added autofind features to make life easier.

First at all, I use convention /my-module/my_module. It’s just because I use Eclipse with PyDev and mercurial I wanted to keep all that non-app config and settings from polluting actual application code. My site is constructed like:

/my-site/my-app1/my_app1
/my-site/my-app2/my_app2
/my-site/my-proj/my_proj

Rationale behind this is just that root of application may contain some other data than just app itself, documentation, SQL scripts and so on.

We define four new configuration variables for this purposes:

• AUTOFIND_PATHS
  • Does settings.py try to find paths automatically or not.
• AUTOFIND_APP_URLS
  • Does urls.py try to construct toplevel urls automatically or not
• AUTOFIND_ROOT
  • Absolute path to toplevel dir where apps are.
• MYSITE_APPS
  • List of installed applications for this site (project).

Now, let’s create stripped down settings.py:

import os
import sys
DEBUG = bool(os.environ.get('MYSITE_DEBUG', False))
TEMPLATE_DEBUG = DEBUG

MYSITE_APPS = ()
AUTOFIND_PATHS = False

AUTOFIND_APP_URLS = True
# Default root absolute path to (../..)
AUTOFIND_ROOT = os.path.abspath(os.path.dirname(os.path.abspath(__file__))  + '/../../')

# Import local_settings always to override global settings
from local_settings import *

INSTALLED_APPS = INSTALLED_APPS + MYSITE_APPS

# Autofinder
if AUTOFIND_PATHS:
    _finder_root = AUTOFIND_ROOT

    # Automatically inject all listed apps to path using our convention:
    for app in MYSITE_APPS:
        try:
            sys.path.index(_finder_root + '/' + app.replace('_', '-'))
        except ValueError:
            sys.path.append(_finder_root + '/' + app.replace('_', '-'))

And then you need your local_settings.py which is file that is meant to be modified locally. Do not store it under version control.

local_settings.py:

DEBUG = True

# List your apps here
MYSITE_APPS = (
    # 'my_app',
)

AUTOFIND_PATHS = True
AUTOFIND_APP_URLS = True

To push automation even further it’s nice to get app urls automatically imported. So modify your toplevel urls.py to look something like:

# Autofind plugin URLs.
if settings.AUTOFIND_APP_URLS:
     for app in settings.MYSITE_APPS:
         try:
             m = getattr(__import__('%s.urls' % app), 'urls')
             p = getattr(m, 'urlpatterns')
             urlpatterns += patterns('', ('^%s/' % app, include(p)), )
         except (ImportError, AttributeError):
             pass # Pass silently import errors

Now you should be good to go. You can easily vary this according to your preferences and workstyles.

Nessa thread, podemos encontrar vídeo aulas sobre Django. Bom para quem está iniciando nesse poderoso framework, que é destaque na web 2.0.
Até a proxíma!

Back when I joined Flumotion, my team was given the choice between implementing a HTML/JavaScript or a Flex powered back office. Most developers I know would immediately turn down the later for a number of reasons:

• Platform portability, notably turning down mobile users.
• Flash plugin sometimes appears to only work properly on Windows machines, raising performance issues.
• Commitment to a proprietary technology.
• Smaller choice of developers and community resources.
• What is it with Adobe and their beloved RIA buzzword anyway? I don’t see anyone else using it!
• Obviously not as trendy as Ajax.

among others that spiced up the discussion.

But there were some particular reasons to strongly consider it in our specific case. For one, we would be working with media management, editing and playback of video, a technology closely tied with Flash at the moment, so it was really about going with Ajax with some Flex components or just Flex alone. Truth is I already had my share of pain working on projects with a heavy Ajax interface, from what our Product Manager expectations of the product, I could see those memories coming to light again. Furthermore, and more on a personal perspective, I felt tempted to give it a try and only afterward draw my conclusions. Based on that, I handed my vote out to Flex.

A few months later, I have a better shaped opinion, I had some nice surprises, as well as really disappointing ones!

I need to give credit to PyAMF for the achievement of making Python and Django integration the easiest possible. On very few occasions I had to step out of my backend bubble and worry about issues regarding frontend. The AMF protocol itself helped here, a little but nice example feature I recall is that datetimes are always passed in UTC, being the Flash plug-in responsible of handling the offset, based on the client timezone system setting. Not having to worry about details such as these was a joy and made the development process faster, allowing me to focus on backend performance. In the end I was developing a Python request handler, very far from your regular Django application, using little more than the ORM and URL handlers.

But there was a few downturns along the way. First, only the fact that code was compiled made me feel in a strange place a lot of times. Every small fix implies a full build and update on production code. I believe that hot fixing should be avoided at all cost, but it is still needed sometimes and this only made it harder, heavier and even more dangerous. Then of course there were the problems of the Flash plugin on Linux, it is really frustrating for a guy that stays 80% of his time on a console having to deal with Firefox taking away all system resources the minute you open something Flash making it virtually impossible to test without booting up a virtual machine. On AMF itself, I never quite understand for the data transferred to come “encrypted” in a weird format, it certainly didn’t made it feel safer or smaller. Also, the fact that each messaged carried a message ID and time, made it harder to smart cache responses. Although I came up with a interesting cache decorator for AMF requests that I will post in the future, I would have preferred to do it on a lower level so that I wouldn’t have to waste time decoding the AMF requests (yes, as fast as it is it’s always unneeded overhead).

But the one thing that really annoyed me was the cross domain sandbox issue. As the project architect, it was very frustrating being forced to spread several copies of a crossdomain.xml file that makes very little sense to me. To date, no one as yet succeeded in properly justifying it and proving me wrong, but I will get into this issue on a following post, don’t worry.

As a conclusion, in the context of this specific project, I believe we made the right choice. Still, I very much doubt that we will see Adobe’s “Rich Internet Applications” taking over Ajax anytime soon. The new media support on HTML5 is here to confirm that. Rare examples like Google Wave make me believe that given the right developers (I presume), it is possible to make very nice JavaScript powered applications.

That said, on a future decision, my vote would again depend on the project details and target audience, but in most cases I can think of at the moment I would have to go with Ajax.

If you have a similar experience with a different outcome, I would very much like to hear you!