| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This reporter updates two pairs of user-defined fields on an Individual
Profile. The first pair are pulldown & date fields used to track the
assessment results. The second pair are updated after each chapter is
completed.
|
|
|
|
|
|
|
|
|
|
Using the new ProgressReporter interface in AssessmentResultsPage and
ChapterCompletePage.
|
|
A ProgressReporter will be used to record progress in the ChMS. The F1
version in complete, but needs to be plugged into AssessmentResultPage
and ChapterCompletePage.
|
|
Beginning with this change all of the Church Management System
integration logic is moving into implementations of the new
IntegrationDriver interface. The desired IntegrationDriver can be
selected by setting the integrationDriver config to the appropriate
class name.
This commit is only moving login support. Progress reporting will move
in a later commit.
|
|
|
|
Previously scores aligned on the answer values: 0 (seeker), 2, 3, and 4
(teacher).
Now scores align halfway between: 0 (seeker), 1.5, 2.5, 3.5 (teacher)
|
|
|
|
|
|
|
|
|
|
|
|
Also added scan and scanf (filtered) options to DbTool.
|
|
|
|
Adding a new interface, F1API for F1 APIs which require a valid access
token. This is now used by AssessmentResultsPage to assign an attribute
each time someone completes the assessment.
Also adding an AttributeTool to list all attributes and assign
attributes to users.
|
|
F1Access will provide a collection of F1 API methods, rather than
placing all of those methods in F1User as I was originally planning.
|
|
Parts of addAttribute have been implemented in F1User, but I may move it
out into a general F1 API class.
|
|
The query param 'next' allows you specify which chapter to goto next.
This is being added to allow proofing specific chapter complete messages
even if all of the chapters have been completed.
|
|
Also added the Leader page to the normal Chapter list.
|
|
|
|
|
|
Also moved the Playlist related tests to their own class.
|
|
|
|
|
|
|
|
|
|
serverprod starts the frontend locally but points it to the prod
dynamodb.
The import tool loads data into dynamodb. Each record has a hash key and
one or more attribute/value pairs. Records are separated by an empty
line. The first line of the record is the hash key. Each subsequent line
is an attribute key, followed by a space, followed by the value.
|
|
|
|
|
|
AccountRedirectResource was expecting the user to have a UserRecord, but
new users did not have one. This caused JsonRequestProvider to throw an
IOException and AccountRedirectResource to return 500.
JsonRequestProvider now throws a NotFoundException on 404 and
AccountRedirectResource properly handles it.
|
|
While trying to fix this issue, I also moved FMFacade into this package
and fixed a couple bugs that snuck into the last commit.
|
|
* 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.
|
|
Other Changes:
* JsonEncodedProvider no longer implements Provider.
* Only the first answer is shown. Others slide down.
* Switch going deeper and the feed.
|
|
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.
|
|
|
|
Previously sliders were scored as a value between 1 and 4 based on the
percentage across the screen that the slider was slid. This required you
to slide fully to the right to get a 4.
Now the slider is divided into n sections, where n is the number of answers
on the slider. With 4 answers the score will be exactly 1, 2, 3, or 4.
With more answers you may get a decimals, but the last section of the
slider will always result in a 4.
|
|
|
|
|
|
|
|
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.
|
|
|
