Changes between Version 47 and Version 48 of IIRS/DevelopmentPlan

Timestamp:

11/13/13 13:11:49 (3 years ago)

Author:

jim

Comment:

--

IIRS/DevelopmentPlan

@@ -23 +23 @@
   1. (2) Map view -- views based again, using Leaflet or Leaflet Map Box plus [https://drupal.org/project/ip_geoloc IP Geolocation Views and Maps]...
   1. (2) About page/pane - to decide if this is a [https://drupal.org/project/fieldable_panels_panes fieldable panel pane], a node or some included text in module. Ed asked...
-1. UNDERWAY (5) Get workflow to working state, test
-1. UNDERWAY (3) Create wireframe panes to test workflow progression though pages.
-1. UNDERWAY (3) Create widget panel from panes and instances created so far. Add placeholder strings and deliver to Ed to get sign off and translated into Portuguese.
-1. UNDERWAY (4) Build stub Widget Instance entity and part of related UI for viewing/managing them. -- https://api.drupal.org/api/examples/entity_example!entity_example.module/7 and http://www.trellon.com/content/blog/creating-own-entities-entity-api
-1. (1) Expose Widget Instance entity to Panels/CTools as a context.
+1. UNDERWAY (5) Get workflow to working state, test -- now need to integrate entry form then am done.
+1. UNDERWAY (2) Create new CTools content type that wraps the Workflow already built.
+1. UNDERWAY (2) Make settings form for Workflow plugin, make part of Workflow container settings.
+1. UNDERWAY (8) Build pages for entry/view and get workflow connected via 
 1. (1) Convert and update Drupal Features and modules.
 1. (2) Set up test site on Jim's server -- allows us to set up Hybrid Auth social media login
 1. (3) Create very simple Bootstrap-based theme (little/no customisations)
-1. (2) Enable Portuguese language, import language files.
+1. (2) ~~Enable Portuguese & Frensh languages~~, import language files.
 1. (4) Convert key entry pages from PSE to Panes/CTools Content Types, extending stubs built
 1. (4) Update all views, panes, features to handle language context.
@@ -162 +161 @@
     * Thank you message - A WYSIWYG field that is the thankyou message. Ideally needs to be translatable in the UI.
   3. Will create an entry panels page with URL ''[language]/tn-widgets/view/country/[country-code]'', meaning the ''[country-code]'' will be used to do the filtering. Language is separate from country (though connected in real life) and present by the ''[language]'' argument.
+  4. The widget container/framework/layout that puts these above two pages into other web pages will remain a CTools plugin, but will need its own UI for getting the widget. I'm looking at modules to do this for me, otherwise I'll re-use the PSE code as much as possible.
 
-==== 12 November -- 1h (15.5 total) ====
+==== 12 November -- 1h (16.5 total) ====
 * Quickly converted the PSE to D7 to aid in grabbing/reusing code -- especially around the 'Get Widget' page.
+* Reviewed many modules and CTools best practice..
 
-==== 13 November -- 1h (15.5 total) ====
-* Identified the [https://drupal.org/project/mlpanels Multilingual Panels module] that allows settings for panes to be translated from within Panels. This solves a big issue!
+==== 13 November -- 1.5..h (+16.5 total) ====
+* Identified the [https://drupal.org/project/mlpanels Multilingual Panels module] which solves a big issue... Allows settings for panes (e.g. thank you text) to be translated from within Panels.
+* Refactored code to match the above plan.
+* Updated plan and log.