Pythoneer

I love it when technologies evolve that fast, as the browsers in general currently do, it’s just awesome! After just having read about SquirrelFish Extreme and some comparison to the other engines, I am getting really excited about the future and the sure future for us at uxebu where we are working with all the browser technologies and we are glad to be in a field that close to the bleeding edge tech.
It’s not only that the JavaScript engines are competing (and JSON becomes native in IE8 and in Firefox). Also the development tools are coming strong, especially the article about the debugging capabilities of IE8 and the installation of IE8 in my virtual machine, to use the dev tools, really make the future of web development look awesome! The extra efforts that Firebug gains lately are another evidence for the awareness of just about everybody in this sector. Douglas Crockford’s excitment about an Opera option for delayed script execution points to another important topic on that front. Also the merging of WebForms into the HTML5 spec is really a milestone. This will really push the open web (podcast), wow …

(Just an article fill of links, but it is so exciting I have to tell people!)

Before django 1.0 I don’t remember that there was a way to customize how the admin renders the User overview. Fortunately 1.0 does allow it.
It took me a bit to figure out. After searching the web and the django docs I didn’t find it right away, so I tried the normal fallback: auto-completion (WingIDE does that really good).
Normally if you just define your own UserAdmin class in admin.py, like this:

class UserAdmin(admin.ModelAdmin):
    list_display = ('username', 'email', 'first_name', 'last_name', 'date_joined', 'last_login')
    search_fields = ['username', 'email']
admin.site.register(User, UserAdmin)

You get the following error when starting up the server:

django.contrib.admin.sites.AlreadyRegistered:
    The model User is already registered

Well, as I said, the auto-completion just made me come across it pretty quickly, and it is so logical. Simply unregister the admin class for User before redefining it :-).

class UserAdmin(admin.ModelAdmin):
    list_display = ('username', 'email', 'first_name', 'last_name', 'date_joined', 'last_login')
    search_fields = ['username', 'email']
admin.site.unregister(User)
admin.site.register(User, UserAdmin)

Done. Cool, ha?
Congrats to all the people behind Django 1.0, good stuff!

I mean he is one of the leading geeks, the inventor of Seaside, Avi Bryant I expect him to be forward thinking, his idea for FTPlets proves it ones more. I especially like this idea of using FTP for “doing things”, especially given the justification for it:

The idea isn’t to get Squeak to serve out the filesystem, but to have a way to use the FTP protocol as an interface to any data you want, in the same way that dynamic web servers let you use HTTP for applications far beyond serving static HTML files.

Well, it’s true we are actually using HTTP far beyond static file serving. So why not push the limits of FTP too?

Btw listen to the podcast with Avi Bryant, it makes you want to get your hands on seaside. Although it’s almost a year ago I listened to it, I didn’t get to it yet :-(.

Update: LOL, I just saw that this post is from 2005. It’s easy to impress me :-). But still a provoking idea. Let’s see what exists …