In-line forms are forms that are rendered as one field. The data of the
inline form is also saved in the data for one field. Currently, the data is
rendered to JSON and stashed in the database.

The data in the field is also accessible via the variable replacement
system, so something line %{ticket.field.subfield} can be handled by the
inline form field.

Also fix syntax error preventing deletes and drop the [manage all phrases]
feature for now.

Link entry and form and entryAnswer and field. This will alleviate extra
queries which would otherwise be required.

Also, autodetect the endusers timezone using the jstimezonedetect Javascript
library.

This patch adds support for automatic date and time formatting based on a
selection of locale. The locale can default to the system or user specified
language+locale, or can be elected separately. For instance, English
speakers can pick between US, GB, and many other English speaking locales.

This also removes the need of the %timezone table and uses the timezonedb
built into PHP 5.3+. User's can now select from a much longer list of
database and no longer need to deal with the DST checkbox.

This allows for things like related COUNTs and such:

```php
ThreadEntry::objects()->annotate(
    'attachment_count'=>Aggregate::COUNT('attachments')
    )
    ->filter(array('attachments__type__contains'=>'image/'))
    ->filter(array('attachment_count__gt'=>0));
```
This would find all thread entries with at least one image attached.

Move the attachments to the sidebar, add the concept of language-specific
attachments. Add a sidebar to the front page. De-emphasize the "open new
ticket" button. Add a knowledge base search feature to front page and also
add the concept of "featured" articles and categories on the front page.

Ensure that for a model class name and primary key, there is only one object
floating around in PHP runtime. In doing so, ensure that models loaded from
the database are not duplicated in memory. Instead, check the cache when
creating objects to see if the object has already been loaded. If so, use
the loaded model rather than a new instance. This ensures that updates to a
model object are reflected consistently.

Also, short circuit lookups so that the cached version is retrieved without
consulting the database.

For instance
join table2 on (field = 'T' and table1.field_id = table2.id)

Implement select_related() for querysets. Now, related models are loaded
along with the requested models automatically.