jbox
I wrote about handling this in Python: http://www.mobify.com/blog/http-requests-are-hard/
Could you aggregate the messages and post an update when the entire task is complete?
Seeing the commits come seems to be a good progress indicator.
If you are "watching" a repo, you get an notification for every comment, not every commit.
You could also just create the PR with a link to the job on ShrinkRay and have the progress updates there...
I gave it a shot on one of our private repos this morning and it did what it said on the box.
In the process it also generated ~150 comments on the repo.
For folks watching the repo, this is a fair amount of email.
Is there anyway to aggregate the comments? Perhaps into the Pull Request description?
This rule is also good to keep in mind when choosing a domain for non-production environments!
Zepto Closest Implementation: https://github.com/madrobby/zepto/blob/master/src/zepto.js#L...
JQ.Mobi: https://github.com/appMobi/jQ.Mobi/blob/master/jq.mobi.js#L3...
Zepto End Implementation: https://github.com/madrobby/zepto/blob/master/src/zepto.js#L...
JQ.Mobi: https://github.com/appMobi/jQ.Mobi/blob/master/jq.mobi.js#L4...
That said, it's all open source and there are only so many ways to write these functions succinctly.
Director of Engineering
Mobify is a growing, profitable, bootstrapped startup. Our goal is to build a web where every website delivers and amazing experience on every device. We serve millions of pageviews for companies like Starbucks, Threadless and Conde Nast using a combination of client/server side JavaScript.
We're looking for an experienced technical manager with a history of delivering successful web products.
We have a glee club, yoga classes and an awesome team.
I particularly like the idea of TemplateResponse - the earliest implementation I saw was in simonw's:
https://github.com/simonw/django-openid/blob/master/django_o...
This approach makes template rendering much more flexible!
For example, it would be easy to swap out a template for a mobile one ... or to A/B test a template. Or choose the content type of the output (HTML, JSON etc.)
We're building great mobile experiences using HTML5.
Looking for smart people with a background in web development.
We're based out of downtown Vancouver - right by the water, mountains and nightlight. Weekly yoga classes, flexible schedules and all the latest gadgets :)
Mail me a john at mobify dot me.
Mobify is a mobile web company. We're changing the way people surf the mobile web. We work with traditional publishers like Wired and SPIN Magazine as well as top websites like BoingBoing and Smashing Magazine.
We're looking for more devs to help us take our client side interactions to the next level. If it's your dream to optimize the performance of top mobile websites drop us a line!
john at mobify dot me.
This app solves the problem by allowing users to log in using their email address.
It's not a bug that it doesn't deal with account creation - it's outside the scope of the app.
That said, it is fairly trivial to create a registration form that enforces the constraints you mentioned.
You'll need to setup a listener on your server to process the request and save the contents to file.
Ultimately, your success will depend on one thing - you. Build your business for profitably and don't count on money until it's safely cleared in your account.
“For most web sites, the possible performance gains from optimizing CSS selectors will be small, and are not worth the costs. ”
http://www.stevesouders.com/blog/2009/03/10/performance-impa...
Having worked on mobile web applications that serve a wide range of devices, I can honestly say that this is not the case.
I would challange ppk to cite examples of this behaviour.
A few months ago I was looking for a Django forum. Of the existing solutions, I liked Snapboard best for it's clean code, relative simplicity and test coverage. In the end I used it but rewrote a substantial part. This code is available on GitHub: http://github.com/johnboxall/snapboard/tree/dev/snapboard/
It's currently used to host the Mobify forums: http://community.mobify.me/
Django Pattern: get_allowed_or_404
http://www.3oh2.com/2009/12/23/django-pattern-get_allowed_or_404/
In Django, a common view pattern is to protect access to a resource by user ownership. This article discusses how to allow staff to access any resource while still restricting regular user access.
http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.js
Be patient and focus on understanding one part that your are familiar with - perhaps handling AJAX requests.
For example airG (http://corp.airg.com/) has deployed white label social networks on most North American carriers. They don't come up for "white label mobile social network" :)
What's the point of having a status page it's only up as long as your service? We shouldn't have to hunt around a Google Group for information about what's going on.
Couldn't you use a creation counter in a metaclasses and assign order to the attributes as they are added? (like Django's forms use to keep track of field order)
If all that importing is really necessary then you might want to check out Django's new preferred import method, importlib, it might clean that up a bit: http://code.djangoproject.com/ticket/8193
And here in the J/S - lots of evals - is that really necessary?: http://code.google.com/p/dajaxproject/source/browse/trunk/da...
Best slides from the bunch IMHO:
James Tauber's Django Patterns - an in depth overview of common patterns found throughout a Django Project:
http://eldarion.com/talks/2009/05/eurodjangocon_djangopatter...
Alex Gaynor's Form's presentation included many interesting ideas including a few 'ohhhh' moments using some functional hotness to get things done fast:
http://www.slideshare.net/kingkilr/forms-getting-your-moneys...
Paul Smith's talk on the EveryBlock stack dives into map tile generation and rendering using Django.
http://www.slideshare.net/pauladamsmith/the-web-map-stack-on...
Simon Willison's talk was excellent though you might not get as much out of the slides. Turtles all the way down!
I think class implementations of Directories & Files would probably go a long way to helping cut down cruft in the view code:
http://code.google.com/p/django-filebrowser/source/browse/tr...