Changes between Version 2 and Version 3 of S3/S3Profile

Timestamp:

05/12/14 11:50:10 (11 years ago)

Author:

Dominic König

Comment:

--

S3/S3Profile

@@ -24 +24 @@
 == Configuration ==
 The profile pages are configured by configuring a few profile_* variables and storing these against the tablename with the usual {{{s3db.configure(tablename, key=value)}}}, e.g.:
-{{{
+{{{#!python
 s3db.configure(tablename,
                profile_title = title,
@@ -48 +48 @@
 * {{{profile_widgets}}} are the Widgets (see below)
 * {{{profile_layers}}} are additional layers to display on the map, defined like:
-{{{
+{{{#!python
 layer = dict(name = record_name,
              id = "profile-header-%s-%s" % (tablename, record_id),
@@ -61 +61 @@
 === Widget configuration ===
 Here is an example configuration for a map widget:
-{{{
+{{{#!python
 map_widget = dict(label = "Map",
                   type = "map",
@@ -79 +79 @@
 
 Here is an example configuration for a datalist widget:
-{{{
+{{{#!python
 alerts_widget = dict(label = "Alerts",
                      label_create = "Create Alert",
@@ -99 +99 @@
 
 NB You should ensure that your create forms establish the context link automatically. This is usually done by checking for a context filter, and then setting table.field.default, e.g.:
-{{{
+{{{#!python
 incident_id = get_vars.get("~.(incident)", None)
 if incident_id:
@@ -108 +108 @@
 
 If the link is via a link table then you need to add the link onaccept, e.g.:
-{{{
+{{{#!python
 incident_id = r.get_vars.get("~.(incident)", None)
 if incident_id:
@@ -126 +126 @@
 
 The hook to link the 'profile' method to this class is in {{{s3_rest_controller()}}} in {{{models/00_utils.py}}}:
-{{{
+{{{#!python
 set_handler("profile", s3base.S3Profile)
 }}}
@@ -156 +156 @@
 * Allow component resources to be filtered
 * Comments widget
+* Use widget() function of target method handler instead of internal widgets
 
 == See Also ==