| | 1 | Tracking of things that need to be done to get Fusion integrated into MGOS |
| | 2 | |
| | 3 | 1. RFCs |
| | 4 | |
| | 5 | We probably need to create the following RFCs: |
| | 6 | |
| | 7 | 1.1 Modify MapAgent to provide a FORMAT option that can be either XML or JSON for some or all operations |
| | 8 | |
| | 9 | 1.2 Add Fusion to MapGuide |
| | 10 | |
| | 11 | 1.3 Modify WebStudio Jx version to be in sync with Fusion |
| | 12 | |
| | 13 | 2. Tasks |
| | 14 | |
| | 15 | 2.1 Templates |
| | 16 | |
| | 17 | - create an authentication example |
| | 18 | - create js for default index.html that parses the applicationdefinition from the query string (and user/password/session) |
| | 19 | - design and create templates |
| | 20 | |
| | 21 | 2.2 web tier changes: |
| | 22 | |
| | 23 | - json output from the map agent |
| | 24 | |
| | 25 | 2.3 add ApplicationDefinition resource type and schema |
| | 26 | |
| | 27 | - fix terminology (Command -> Widget) |
| | 28 | - create reference XML document |
| | 29 | - define XML structure for describing widgets |
| | 30 | - create XML snippet (XAML-like) for each widget |
| | 31 | - create schema |
| | 32 | |
| | 33 | 2.4 Fusion related stuff |
| | 34 | |
| | 35 | - create missing widgets |
| | 36 | - rename some widgets |
| | 37 | - verify behaviour of all components |
| | 38 | - create Fusion Application Developer Guide, Command Reference, Jx documentation |
| | 39 | - localisation |
| | 40 | - locale/en/constants.js |
| | 41 | - contains constants (units of measure) and error/warning messages |
| | 42 | |
| | 43 | 2.5 build process: |
| | 44 | |
| | 45 | - install fusion |
| | 46 | - install templates |
| | 47 | - figure out how to compress fusion as part of the build process and lint it |
| | 48 | - figure out how to load ext/ widgets when the rest is compressed |
