Customization » History » Version 3
Phil Hodgson, 04/05/2014 03:10 PM
1 | 1 | Phil Hodgson | h1. Customization |
---|---|---|---|
2 | |||
3 | h2. Overriding Default Views, Partials, Templates, etc. |
||
4 | |||
5 | 2 | Phil Hodgson | It is possible to override any Rails view in the application by mimicking the directory structure in @app/views@ but under another folder @site_specific/app/views@. For example, to use your own version of @_dashboard.html.erb@ in @app/views/pages@ you would put it in @site_specific/app/views/pages@. |
6 | |||
7 | You can override the @#{Rails.root}/site_specific@ folder itself with the environment variable TAPESTRY_OVERRIDE_PATH, so that the folder can be left entirely outside of the Tapestry code base. |
||
8 | |||
9 | It is important to understand that including this folder, any subfolders, and all files is _optional_. If you do not wish to override a particular view, leave it out of the override folder. |
||
10 | 3 | Phil Hodgson | |
11 | h3. Caveat |
||
12 | |||
13 | _This statement to be followed up after more investigation._ |
||
14 | |||
15 | It is my impression that when using multiple paths that the technique of using @explicitly_unloadable_constants@ for having files reload without restarting the server will not work properly. This could mean that while developing these site-specific files that the server has to be restarted after each change. |
||
16 | |||
17 | h3. Overriding @lib@ Files |
||
18 | |||
19 | The same logic works for files in the override path under the @lib@ subfolder, i.e. either @#{Rails.root}/site_specific/lib@ or @#{ENV['TAPESTRY_OVERRIDE_PATH']}/lib@. |
||
20 | |||
21 | h2. Adding Custom Questions to the "Participation Consent" Form |
||
22 | |||
23 | Currently this text and form are found in @views/participation_consents/show.html.erb@. This currently saves the user's responses in the InformedConsentResponse model. There is in this model a field called "other_answers" that is a serialized Hash where any number of "dynamically defined" answers can be saved with keys of your choosing. To accomplish this you have to add form inputs that end up with a @name@ attribute that looks like (e.g. to record "age"): @other_answers[age]@ and it will be recorded in the "other_answers" Hash in the model under the :age key. |
||
24 | |||
25 | There is a view helper for creating radio boxes for the participation concept form using this "other_answers" field. Example: |
||
26 | |||
27 | <pre> |
||
28 | <div class="consent-form-question"> |
||
29 | <p> |
||
30 | Would you judge yourself to be sane? |
||
31 | <%= radio_answers( 'sanity', [['0', 'No'], |
||
32 | ['1', 'Sometimes'], |
||
33 | ['2', 'Yes']] ) %> |
||
34 | </p> |
||
35 | </div> |
||
36 | </pre> |
||
37 | |||
38 | |||
39 | h3. Adding Custom Validation of Your Custom Question |
||
40 | |||
41 | This is done by overriding a site specific validations file in the @lib@ override folder, in the @lib/site_specific/validations.rb@ module. By adding a method called @informed_consent_response_validations@ (after the name of the model relevant to the Participation Consent form) to the copy of this module you've placed in the @lib/site_specific@ _override_ folder, you can check @other_answers@ and add errors in the standard ActiveRecord way. For example: |
||
42 | |||
43 | <pre> |
||
44 | def informed_consent_response_validations |
||
45 | if self.other_answers[:sanity] == '2' |
||
46 | errors.add( :other_answers, :sanity_not_permitted) |
||
47 | end |
||
48 | end |
||
49 | </pre> |
||
50 | |||
51 | The message should be placed in your locale file under: |
||
52 | |||
53 | <pre> |
||
54 | en: |
||
55 | activerecord: |
||
56 | errors: |
||
57 | models: |
||
58 | informed_consent_response: |
||
59 | attributes: |
||
60 | other_answers: |
||
61 | sanity_not_permitted: 'You are not permitted to be sane.' |
||
62 | </pre> |