into view_new.py
* Added error indication of the top of the page, in case there are any
errors further down.
* Set more fields to required, matching the old perl code
* Various other tweaks.
- Legacy-Id: 140
callback to provide a RegexpField class.
* Added checkbox for submitter contact information being the same as
IETF contact information; with javascript support and validation
support.
* Cleaned out the old split_form() and mk_formatting_form() functions from
ietf.utils.
- Legacy-Id: 138
* Add 'area' to class ResolveAcronym
* MeetingTime.session returns WgMeetingSession objects, BUT STILL NEED TO FIGURE OUT WHICH sched_room_id[1|2|3] TO USE
- Legacy-Id: 137
to Django, work around this in our code. Sort the session list with Python
code, rather than doing it as part of the query. Since the session list is
very short, there is no problem with memory consumption in doing it this way.
- Legacy-Id: 136
Note: SVN reference [133] has been migrated to Git commit 587d2baafe
* add a method, acronym_name to ResolveAcronym
* Sunday sessions displaying is done
* Need to figure out how to increment date by one day in a template
- Legacy-Id: 135
utilities into separate files.
* Added a log() function in ietf/utils. It uses syslog, but adds some
information about where it was called from.
- Legacy-Id: 130
Add Positions, IESGComment, IESGDiscuss tables. (These are
database tables 'ballots', 'ballots_comment' and ballots_discuss'
but I decided to name the classes differently.)
- Legacy-Id: 126
The nonwg_lists/submit wizard is nearly done; it needs templates
and to figure out why submit from step 2 goes back to step 1 instead
of calling done.
The req_list wizard is just started. It needs to get the incoming
value of domain_name as an alternat version of dname, and be able to
get dname from GET args to handle the javascript redirect. It also
needs all the workflow ("I'm allowed to create this list",
who-is-approver, etc.) and additional forms.
- Legacy-Id: 122
Using some more logic in views.py, less in the templated.
* Some tweaks in FormattingForm rendering.
* Selection of which sections to show is now table driven in views.py
* Some minor refactoring and cleanup in views.py
* Some more form subclassing in ipr/views.py in order to support form
validation.
* Removed style information from ipr/details.html template, and added
ipr/style.html
* Cleanup of details.html
* Fixed ipr/formfield.html to display error messages, and with the right
class.
- Legacy-Id: 105
using pretty much the same template as for a non-form view.
This solution is less hackish than the previous one which
used the form.as_table() rendering of a form, and then split
the resulting html in chunks.
Instead, '''all''' the html has been moved out to a formfield
template, and a custom form class is generated which will render
the form elements using an indicated template.
* Add form factory in utils.py (an old version which still has
html in the code is there for history, but will be removed
* Changes in ipr/views.py:new(), now subclassing one form with
some class members being other form instances, matching the
members used for the show() view
* A fix in ipr/models, making an email field use models.EmailField
* Reverting a number of changes in ipr/details.html which aren't
needed any more, as well as in ipr/new.html; and adding
ipr/formfield.html
- Legacy-Id: 104
* Moved RFCs model into idtracker
* Switched idtracker querys to use idinternal
* Created idinternal.document which returns either an InternetDraft or
an Rfc depending on the value of rfc_flag
* Create compatability methods in InternetDraft and Rfc models
to be able to use certain attributes in the template without
worring about where they come from.
Ticket #59 has a list of remaining bits.
- Legacy-Id: 98
* Re-wrote the IPR declaration form using form.to_table()
and the split_form() function in order to get sub-blocks
of the form which could easily be used with the existing
IPR detail display templates.
How to merge forms from multiple models took some thinking;
since the forms have a common ancestor, multiple inheritance
doesn't preserve the form data. In the end the merging
didn't turn out too horrible. See ipr.views.new().
* Changed the IprDetail model; first to specify editable=False
for all fieleds which shouldn't be shown in the form, but
this has the drawback of also removing them from the admin
page form. Simply bagging them in an un-used sub block with
split_form() works fine.
* Changed the URLs for IPR by-date some again
* Updated the ipr/new* templates to use the form sub-blocks
- Legacy-Id: 97
