The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
I just saw the presentation of Mr. Eric Florenzano at Pycon 2010, and he talks about a side project he did on facebook using django.
ReplyDeleteFrom PYCON 2010:
If you've been using Django for any
amount of time, you've probably
learned some pretty standard practices
on how to use it. This talk aims to
shatter those conceptions and teach
you alternative ways that you could
use Django.
These alternate ways
come broadly in two varieties: Using
parts of Django outside of it, and
choosing alternatives to what Django
offers. If you haven't done either of
these things before, it may seem
tricky or difficult. In fact, it may
not be.
This talk will walk you
through the process and talk about
what to expect if your project just
doesn't seem to "fit the mold".
I recommend you check out his blog and the presentation.
Blog: http://www.eflorenzano.com/
Presentation: http://blip.tv/file/3261337
More Resources:
How to build a Facebook app in Django
Example Facebook application in Django
Two-Faced Django Part 1: Building a
project that exists simultaniously
on Facebook and the web
Two-Faced Django Part 2: Models and Django Testing
Two-Faced Django Part 3: Newforms
Two-Faced Django Part 4: The Webapp
Python Sdk is rather badly maintained.
ReplyDeleteThink you best option is Django Facebook:
https://github.com/tschellenbach/Django-facebook
Basic tutorial
http://www.mellowmorning.com/2011/06/23/django-facebook-2-0-integrating-facebook/
Info:
ReplyDeletehere, here and here + pyFacebook.
If you just want to get started, check out Fandjango on github. Its a simple middleware layer that adds a facebook_user attribute to the request object when the user is logged in, and sets it to None when they are not logged in. It also has an easy way to call the Graph API with the users' credentials.
ReplyDeleteNote: It only works on Facebook Apps. Websites using facebook connect use a slightly different protocol.
Also note: Any library that references 'pyfacebook' is using the old FB API and you should avoid that. The new one that uses the Graph API is python-sdk. You shouldn't use python-sdk either since its deprecated - thanks @pydanny. I haven't researched it, but facebook-sdk looks actively maintained.
This tutorial teaches you to create a simple django based application on facebook. It also includes references to more resources.
ReplyDelete