Changes between Version 2 and Version 3 of Maestro3UI
- Timestamp:
- 07/07/10 06:54:34 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Maestro3UI
v2 v3 3 3 In one word: everything. 4 4 5 The UI architecture of Maestro 3.0 is intended to mirror that of [http://fdotoolbox.googlecode.com ]. Flexible and extensible.5 The UI architecture of Maestro 3.0 is intended to mirror that of [http://fdotoolbox.googlecode.com FDO Toolbox]. Flexible and extensible. 6 6 7 7 == Foundations == … … 38 38 == Versioning == 39 39 40 Unlike MapGuide Studio, Maestro 3.0 will not silently upgrade resources when saving. Like previous versions, Maestro 3.0 will edit the resource in its current version. Unlike previous versions of Maestro however, Maestro 3.0 will attempt to support every known version of a given resource. Though this sounds like a lot of work, the reality is only 2types of resources have various versions:40 Unlike MapGuide Studio, Maestro 3.0 will not silently upgrade resources when saving. Like previous versions, Maestro 3.0 will edit the resource in its current version. Unlike previous versions of Maestro however, Maestro 3.0 will attempt to support every known version of a given resource. Though this sounds like a lot of work, the reality is that only the following types of resources have various versions: 41 41 42 42 * Layer Definitions 43 43 * Load Procedure 44 * Symbol Definitions 45 * Web Layouts 44 46 45 47 And each new version incrementally builds on previous versions. The editor UIs as a result can follow the same pattern.