| Age | Commit message (Collapse) | Author |
|---|
|
Also added the Leader page to the normal Chapter list.
|
|
* Fixing thread ordering.
* Adding a limit of 5 threads per topic.
* Changing frontend /account references to UserRecord.
|
|
* Adding an Author indicator on the feed.
* Adding showfeed cookie to enable/disable feed demo.
* Hiding the feed on the introduction chapter.
* Adding whitespace compression to all pages.
|
|
Changed MessageThread so that a thread always contains one original
message.
Added support in JsonEncodedProvider for JavaTypes in addition to
classes.
Updated communityfeed.ftl to actually display questions and answers.
|
|
|
|
After refactoring users were required to watch all videos regardless of
their assessment score.
Also enabling strict video ordering and adding the option magicskip to
watch out of order.
|
|
Video numbers may now be decimals (i.e. 5.1, 5.2). If the number is 0 it
is not displayed on the website.
Updating the videos-from-csv.py script to distinguish between user
facing video numbers and video ids.
Also updating urls for many videos.
|
|
|
|
|
|
Also made the Outline links more noticeable.
|
|
Playlists are now generated from a default playlist and regularly
merged with the default playlist to get updates.
Also adding the Question tests that got left out of a previous commit.
|
|
Introduction chapter is always required and thus after the assessment
the user is taken directly to the introduction. After the introduction
training continues with whichever section the user assessed in to.
|
|
|
|
The TrainingRecordResource now builds a playlist of videos for each
user. The playlist is a map of video id to meta-data (completion date,
completed, required). Some videos are required, others are not.
TrainingPageResource now redirects to the earliest uncompleted chapter,
based on information in the playlist.
SurveyResultsResource now caches computed scores.
|
|
|
|
This change introduced the f1oauth and jesterpm oauth packages for
interacting with Fellowship One's developer API. I have also reworked
the login authentication to verify credentials through F1 and added
session management to track logged in users.
The Authenticator chain works as follows: on every page load we check
for a session cookie, if the cookie exists, the Request is marked as
authenticated and the OAuthUser object is restored in ClientInfo. If
this request is going to an account page, we require authentication. The
LoginFormAuthenticator checks if the user is already authenticated (via
cookie) and if not redirects the user to the login page. When the login
form is submitted, LoginFormAuthenticator catches the POST request and
authenticates the user through F1.
I'm also adding a new account page, but it is currently a work in
progress.
This commit also adds Allen's content to the site.
|
|
|
|
|
