- Switch from dataTable (returns a jquery object) to
DataTable (returns a DataTables API object)
- Update versions of libraries
Doesn't quite work, needs the full version of jquery rather than the
slim version.
- The schedule grid page is ridculously database-query heavy and hence
terribly lacking in perfmantitude.
- Caching can help with this, but the caching implemention at present
is not user-aware. If one user looks at the page, they'll get a
"YOU" in all the places they're chair and something else everywhere
else - and then everyone will see that for the next 600 seconds,
then YOU will become someone else
- to avoid this, remove the request.user-specific bit of the template
In the narrow view, lots of details that aren't in the normal view
appear to compensate for not having clear row/column headers any more.
However, all the detail can look very same-same; this tweak makes rooms and end times more distinct.
Session chair info is made always italic, and a label is added to make
it clear that this person is not the speaker.
* Adds session_detail page
* Adds session chairing information to the schedule grid
* Adds session_list.html
* Nicer volunteer text
Conflicts:
pinaxcon/templates/symposion/schedule/_grid.html
Conflict and migration performed by Sachi King <nakato@nakato.io>
Emoji changed, lca2017_tags to lca2018_tags, remove needless dependency
on django-user-account, use request instead like the remainder of the
calls n the template do anyways.
Remove blocktrans from a number of texts as they break {{ templating }}
and we don't translate anyways.
Modified-by: Sachi King <nakato@nakato.io>
- there's no btn-default, switch that to btn-primary
- consistently use info for standby, primary for undecided, success
for accept and warn for rejected
I've looked through the database and I can't find any accepted
proposals that actually contain anything to linkify - but I've had
several requests from people that I think are reasonable, things like
being able to link to their project (we ask them to provide a project
url but we don't use that link)
This seems like a reasonably fast way to let those people add a
link. We still have to manually accept changes to their proposal so we
have a chance to look at the content of the url if we want.
The urlize filter adds rel=nofollow to the link automatically.
Old code was initialising the dataTable twice - once in the parent
block and once in the child. This doesn't actually work and just
caused errors.
Switch to only initializing it once. Unfortunately this creates
copy-pasta :(
* Audience is visible on review details, but not the list. Perhaps
useful for cases where reviwer wishes to only review for a
particular audience. This change adds audience to the list view.
* Format is not visible anywhere. This changes adds it to list and
detail views for the reviewers.
This change also adds some buttons to control visibility of the new
columns.
* The base model requires a value here
* But we aren't using one; so there's none on the form
* This change supplies a custom enumeration that's specific for this
particular model, which has one value, which is a default value,
which simply says that the field is N/A
* This does mean that when viewing or reviewing the proposal one sees
the Target Audience field, but it will say N/A.
* Testing has shown that this does not affect the other types which
descend from the base Proposal class; they still use the default
enumeration.
I think this removes most references to "hobart", "pycon", and "2017"
There are still some references to some images that we don't have a
replacement for.
Flagging this as a review table means we get sorting, pagination, and
search. Much awesome, esp when we want to do this like "show me all
the ones that haven't been notified yet"
