Este fué el resultado, Si tienen Ubiquity instalado, verán arriba una barra que les indica que existe un comando Ubiquity en esta página. Sólo hay que suscribirse y listo.

Como parte de las medidas de seguridad Ubiquity pone una pantalla de advertencia para asegurarse que uno sabe que está instalando y tenga oportunidad de revisar que no hay código malicioso en el comando. Se confirma y listo.

Para usarlo lanzan Ubiquity (con el comando que hayan configurado) y usen irpe lo que reemplzará la diercción seleccionada por una del tipo ir.

Now, this book has 444 pages compared to the 272 pages from Django book. There is much more to teach about jQuery than about the django template language .

The book has 11 chapters and 4 great appendixes. It starts off teaching you how to set up a page to use jQuery, teaches you selector magic and from then on the example scripts get more and more complicated as the chapters pass by.

Once you’ve read the first half of the book (Free sample chapter), you’re good to go. At this point you should know what is it that you can do with jQuery and start using it. But this is the moment where it just starts to get interesting.

Chapters, 7 on Table manipulation, 8 on Forms with function and chapter 9 about Shufflers and rotators show you how to do amazing stuff you (well, I) wouldn’t have thought of. This is the most important part of the book as it shows you how to put all the jQuery functionality together and teaches you several awesome tricks and techniques to make transparency gradients, lightboxes, scrollers, sort, tables, invoices and tons more.

What’s also great about the book is that it enforces graceful degradation and progressive enhancement through all the examples. So all your development is funcional even for people without Javascript. And he does that providing good arguments on why it is a good idea to keep it that way, since I know lots of people that are just not willing to care about people not using Javascript.

I was gladly surprised with Appendix on Closures, it has a good explanation of that concept that takes so long to grasp. the rest of the appendixes are great resource of information with reference to tools, plugins and related reading to increase your Javascript fu.

Overall

This is a great book, that could have easily be divided in two books, Basic jQuery and Mastering jQuery. Goes from the basic to some medium/advanced level. Every web developer (front end and backend) should read this in order to know how to provider great user experience :).

When developing Django Widgets that require Javascript interaction with the server (Ajax, XHR, etc… ), you want your widget seamlessly deployable and have it know where to find its information (the endpoint).

Elf’s solution is pretty interesting, as he runs the static fles through the Django Template renderer and stores the expanded versions for deployment. This is nice, but :

• You have to re-render all the files if you change the endpoint
• You have to re-render if you use the widget somewhere else (different proyect).
• It becomes difficult to have an URL with parameters like a model Id or any variable (since there’s no context).

What I do is add the URL to the Widget and set it as a document javascript variable, then use that variable on my .js

It goes something like this:

class MyWidget(forms.Widget):
  def __init__(self, endpoing, *args, **kwargs):
    self.endpoint = endpoint
    super(self, MyWidget).__init__(*args, **kwargs)

  def render(self):
    output = super(self, MyWidget).render()
    output =+ '<script>var WIDGET_ENDPOINT = "%s";</script%gt;' % self.endpoint

  class Media:
    js = ('my_widget.js',)

So you can just use django.core.urlresolvers.reverse to your endpoint when defining the widget .

On the template just render the field and add the {{form.media}} (at the bottom fo the document where scripts belong).

In your .js file:

$.getJSON(WIDGET_ENDPOINT, {}, function(resp) {
   $("#somenode").html(resp.results);
});

The downside is that you have to have that SCRIPT tag in the middle of your document, but really.. its only to ser a variable so it doesn’t hurt much.

This is similar to this solution on accessing MEDIA_URL in Javascript files.

Now, I’m a lazy and slow reader. But this book was quite an easy read. I liked how fast I went through the pages and how friendly the writer seemed .

This is a book focused on Django templates, not in Django itself, but through out the book it becomes obvious that you’ll always need to have basic knowledge on how views and urls work.

My first impression of the book was a bit of disappointment since it’s a Django 1.0 book, but there hasn’t really been any big changes in Django 1.1 that would affect the book. So the book is still valid .

Highlights

The chapters that I found most useful were “Chapter 5: Loading and inheriting Templates” (I would have liked someone telling me about inheriting best practices when I started), “Chapter 6: Serving Multiple Templates” (great use case of the mobile site ) and “Chapter 9:Customizing the Admin Look and Feel” (Found it easier to read than the actual Django documentation on the subject), I was pretty interested on chapter 11 about Internationalization, but it felt a tad too short.

Missing?

I don’t know if I missed this part when reading but I think it would have been good to address the fact that a template is a list of nodes and each of these nodes has to be rendered. It’s mentioned when teaching you how to create your own template tag, but I feel this could have been explained a little bit further to have knowledge on how the templating system works.

Here in Aureal we work with two Web designers, they don’t do any code. They just help us making the HTML look pretty and one of their biggest issues is with forms, we lazy coders like to print the default table format {{my_form}}. German and Justina always have a hard time figuring out what’s behind that form, what attribues are in it, why is it a table, hwo to change that and all that… I was expecting the book to have an extra chapter on that but I never found it .

Overall

The book is a great introduction to templates best practices and even after working heavily with Django you might learn a trick or two from it.

After installing the right WM, installing the right firefox extensions and settings the right font size. I added these lines to my userContent.css

body.gecko div#search, body.gecko a#logo-container { display: none !important;}
body.gecko div#main { margin-top: -30px !important;}

This hides Google reader’s search bar which I never use and gives me valuable extra room

Before

After

Great drawing used by the Nebula team at Nasa to show proudly that they use Django for their development.

The first thing I  hated was havign to make so many HTTP requests to fetch the provider icons, so now Open-selector makes use of CSS sprites to fetch all icons from a single sprite file.

The second feature was to have Open-selector remember your log in choice, so the next time you visit a site you don’t have to fill anything, just hit the button. This means single click log in.

They were actually pretty trivial to implement, so this new version is out

A pesar de todo esos argumentos el público que usa IE siempre tenía un contraargumento de comodidad, o de que no les importaba los tabs o webs mas bonitas por que simplemente funciona, viene instalado y no hay que hacer “esfuerzo” extra para obtenerlo.

Sin embargo hace poco me encontre hablando con mi papá y con otras personas y encontré un motivo que hizo que estas personas pongan cara de preocupación y entendimiento a por que Internet Explorer 6 es verdaderamente un cancer, no sólo para Internet sino para todos nosotros.

La forma de lograrlo es comentando sobre todo el avance tecnológico que está sucediendo en Internet y en las tecnologías de información (no me refiero al IT “corporate” sino a como nos comunicamos y como se transmite la información entre nosotros que por ahora es en gran parte por Internet). Les cuento como IE6 fué creado en el 2001 y ya estamos 2009, eso son 8 años de desarrollo en Internet que no puede ver la luz debido al público usando Internet Explorer 6, y eso todos pueden entender :).

A comparación de lo que suelo ver acá en Perú.

To install just set up an URL where should external links should be redirected to, this endpoint will keep track of the hit and redirect to the destination url

    urlpatterns += patterns(''
        url(r'^external/', include('external_links.urls')),
    )

Now you have two ways to use it, via the inline {% external %} template tag or the blog tag {% externalblock %}

The “external” tag translates a regular link into a redirected link, from <a href="{% external "http://example.com" %}">Other site</a> to <a href="/external/?link=http%3a%2f%2example.com">Other site</a>

The “externalblock” will do the same for a big block of text, it will perform the same transformation on all the anchor tags found inside, this is useful for blogposts, articles and such.