All Buttons Pressed

SEEKING WORK - Remote Team of 3 developers with extensive experience in a wide range of technologies, like: * Python, Django (we've build Django-nonrel) * PostgreSQL, NoSQL, App Engine * Docker * iOS (Objective-C, Core Audio, Core Midi) * Android (Java) * Web apps (jQuery, JavaScript, pyjs) * Computer Vision, Machine Learning, Statistics * Bitcoin, Eloipool, Stratum We have a passion for creating great user experiences and high-quality code. You can find our portfolio here: http://www.allbuttonspressed.com We're based in Germany and have already worked for several startups in Germany and the USA. Contact: [email protected]

I use django-mediagenerator[1], I love it to bits. [1]: http://www.allbuttonspressed.com/projects/django-mediagenerator

Don't forget to use django-nonrel so that you can move apps b/w App Engine and any normal ISP supporting Django apps. You only need to change your database in settings.py! http://allbuttonspressed.com

I'm not sure I follow all the points you're making. But... 1.) I've created CSV import/export admin functions for models many times and I agree it's a minor customization. I'm not sure why changing templates is a no-go for this or anything else. 2.) To me it seems self-evident that the admin was designed to facilitate model-oriented CRUD operations. The fact that it's hard to integrate non-relational data stores like mongo have nothing to do with the admin, and everything to do with the fact that there is currently no agreed on way to plug NoSQL data stores into Django's ORM. Although this has been is a longstanding point of contention and there was a GSOC project that I think eventually became http://www.allbuttonspressed.com/projects/django-nonrel , my sense is that there just wasn't/isn't enough interest in making this a part of Django core. In other words, this goes well beyond what I would call "admin customization" and get's down to pretty basic questions about what sorts of persistent data stores should be supported by the ORM. 3.) Again, this seems to me to want to be able to stretch the admin beyond what it was designed for. To your point: "the first page must be a list of models regrouped by apps. This is in advanced apps [nonsense], most likely when you use a lot of reusable apps, where the code doesn't reflect the end-user experience, the admin will look ugly. But should the admin reflect or map somehow the end-user experience? It's a 'complex mapping'." I…

> And having used django user authentication, something similar would be really useful. How about exactly that on App Engine, rather than just something similar: https://www.allbuttonspressed.com/projects/djangoappengine

Regarding gzipping, you don't want your webserver doing this on the fly. At least in nginx, you can tell the webserver to load pre-gzipped files, I'm sure apache has something similar. Put this into nginx.conf: gzip_static on; Then run this command in /var/www to gzip your content: find . -name "*' + ext + '" -print | xargs -I filename echo "gzip -c filename > filename.gz" | sh This is a small win (reduced cpu/disk IO), but at two lines it's an even smaller cost. Also, if you use django mediagenerator, it will handle a lot of this stuff for you. http://www.allbuttonspressed.com/projects/django-mediagenerator

It seems to apply not only to django-nonrel, but also to their other (equally awesome) projects like django-mediagenerator, django-filetransfers and django-autoload. These guys contributed so much to the django ecosystem, it's very sad to see their projects getting abandoned. Edit - Full list of projects here: http://www.allbuttonspressed.com/projects Edit2 - Alt. discussion here: http://news.ycombinator.com/item?id=3274662

You might want to try django-mediagenerator for Pyjamas integration. We already have a pyjs filter. See [1] for an example of how to use pyjs with mediagenerator. You should be prepared for lots of subtle pyjs bugs, though. The translation isn't perfect. One problem is that the Pyjamas team is replicating GWT, so they only need a small subset of Python's features. They also don't use more advanced features for performance reasons. This means that many code paths are practically untested. [1] http://www.allbuttonspressed.com/blog/django/2010/11/Offline-HTML5-can…

Analogy fail. I believe the point is that you are severely limited in what you can do with Django on App Engine. It used to be that you could not use the ORM on BigTable, which prevented the use of the Admin. Not anymore. See: http://www.allbuttonspressed.com/projects/django-nonrel

Have you tried Django Appengine?[1] It works pretty well and supports most things in django (including the admin interface). [1] http://www.allbuttonspressed.com/projects/djangoappengine

Hey. That USED to be the case that app engine required substantial rework. However there are now no-sql libraries to make normal Django work. I also think there was a summer of code project that might add no-sql support to the django core eventually. You should search around stackoverflow.com or hit up the #django on freenode IRC. My advice is you need to look into how the django community is deploying to app engine more closely. edit: Dug through my bookmarks, this is what you need: http://www.allbuttonspressed.com/projects/djangoappengine If you still need assistance email me at dhllndr [at] gmail

How do they plan to compete against Google App Engine? http://www.allbuttonspressed.com/projects/djangoappengine

I thought this was going to be about Django-nonrel http://www.allbuttonspressed.com/projects/django-nonrel