Changes between Version 11 and Version 12 of IIRS/SolutionDesign

Timestamp:

08/25/13 16:56:22 (3 years ago)

Author:

jim

Comment:

--

IIRS/SolutionDesign

@@ -41 +41 @@
 
 ==== Widget modules ====
-1. '''Transition Initiatives Widget''' - D7 - a module providing the widget (converted from the [https://wiki.transitionnetwork.org/Sharing_Engine D6 PSE project]).
 1. '''Widget Core''' --- a ''module'' that holds all the shared variables, admin, functions, permissions and other logic that will drive all widgets and facilitate the rest of the components.
 1. '''Widget Builder''' -- this is the UI ''module'' that will allow a user (with permission) to chose the type of widget, Context (see below) Purpose and style of a Widget and build an instance. The module will take these options and create a 'Widget Recipe' (see Components, below) before generating the themed, styled ''Widget Chrome'' (below) for a user to paste into their website.
+1. '''Widget Plugins: Initiatives''' - D7 - a module providing the widget plugins and logic for adding the Initiatives (converted from the [https://wiki.transitionnetwork.org/Sharing_Engine D6 PSE project]).
 
 ==== Widget components ====
@@ -72 +72 @@
 
 ==== Widget Plugins needed ====
-Leveraging CTools, the following plugins are needed for the IIRS:
+Leveraging CTools, the following plugins are needed for the IIRS... Note that the code for most of these plugins is already written in Drupal 6. What is required is to convert to a standardised component/plugin architecture:
 * Style plugins:
   * Types: "Full page", "Sidebar", "Button only" = Chrome styles we currently have.
@@ -93 +93 @@
 * Pin down relationships between views (both Drupal Views and View per MVC), Displays, Workflows and Services. It's ''almost'' clear but until development is started and the abilities of CTools are known, this is not easy to fully document at this stage.
 * Work out how the 'Target' plugins will provide access to nodes, and what if anything they do to displays and services... Ideally they should extend such displays and make available certain fields that are important (e.g. location for initiatives/projects/events, date for events, type for resources etc).
+* NOTE It's likely that Purpose, Workflows and Targets either overlap, need combining or need an intermediary object. Again this will be pinned down as work begins on these parts.