[mapguide-commits] r5810 - in trunk/Tools/Maestro/UserDoc/source: .
images
svn_mapguide at osgeo.org
svn_mapguide at osgeo.org
Tue May 17 11:48:03 EDT 2011
Author: jng
Date: 2011-05-17 08:48:03 -0700 (Tue, 17 May 2011)
New Revision: 5810
Added:
trunk/Tools/Maestro/UserDoc/source/images/
trunk/Tools/Maestro/UserDoc/source/images/fs_cs_overrides.PNG
trunk/Tools/Maestro/UserDoc/source/images/fs_extensions.PNG
trunk/Tools/Maestro/UserDoc/source/images/fs_generic.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_area_rule.png
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_line_rule.png
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_line_rule_composite.png
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_point_rule.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_property_mappings.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_scale_range.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_settings.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_theme_generator.PNG
trunk/Tools/Maestro/UserDoc/source/images/maestro_publish_workflow.PNG
trunk/Tools/Maestro/UserDoc/source/images/maestro_ui.png
trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_base.PNG
trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_draworder.PNG
trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_grouping.PNG
trunk/Tools/Maestro/UserDoc/source/images/mdf_settings.PNG
trunk/Tools/Maestro/UserDoc/source/publish_workflow.rst
trunk/Tools/Maestro/UserDoc/source/understanding_drawing_sources.rst
trunk/Tools/Maestro/UserDoc/source/understanding_load_procedures.rst
trunk/Tools/Maestro/UserDoc/source/understanding_maps.rst
trunk/Tools/Maestro/UserDoc/source/understanding_print_layouts.rst
Modified:
trunk/Tools/Maestro/UserDoc/source/index.rst
trunk/Tools/Maestro/UserDoc/source/installation.rst
trunk/Tools/Maestro/UserDoc/source/mapguide_terminology.rst
trunk/Tools/Maestro/UserDoc/source/understanding_applications.rst
trunk/Tools/Maestro/UserDoc/source/understanding_feature_sources.rst
trunk/Tools/Maestro/UserDoc/source/understanding_layers.rst
trunk/Tools/Maestro/UserDoc/source/user_interface.rst
Log:
#1677: More content and screenshots for the Maestro User Guide
Added: trunk/Tools/Maestro/UserDoc/source/images/fs_cs_overrides.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/fs_cs_overrides.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/fs_extensions.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/fs_extensions.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/fs_generic.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/fs_generic.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_area_rule.png
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_area_rule.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_line_rule.png
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_line_rule.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_line_rule_composite.png
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_line_rule_composite.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_point_rule.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_point_rule.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_property_mappings.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_property_mappings.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_scale_range.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_scale_range.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_settings.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_settings.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_theme_generator.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_theme_generator.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/maestro_publish_workflow.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/maestro_publish_workflow.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/maestro_ui.png
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/maestro_ui.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_base.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_base.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_draworder.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_draworder.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_grouping.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_grouping.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/mdf_settings.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/mdf_settings.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Modified: trunk/Tools/Maestro/UserDoc/source/index.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/index.rst 2011-05-17 07:59:19 UTC (rev 5809)
+++ trunk/Tools/Maestro/UserDoc/source/index.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -9,7 +9,7 @@
Contents:
.. toctree::
- :maxdepth: 2
+ :maxdepth: 3
introduction
installation
@@ -17,10 +17,15 @@
differences
user_interface
+ publish_workflow
+ understanding_load_procedures
understanding_feature_sources
+ understanding_drawing_sources
understanding_layers
+ understanding_maps
understanding_applications
+ understanding_print_layouts
edit_xml
resource_validation
Modified: trunk/Tools/Maestro/UserDoc/source/installation.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/installation.rst 2011-05-17 07:59:19 UTC (rev 5809)
+++ trunk/Tools/Maestro/UserDoc/source/installation.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -1,8 +1,44 @@
Installing MapGuide Maestro
===========================
+MapGuide Maestro is available in two forms:
+
+ * A windows executable installer
+ * A zip file
+
Installing on Windows
---------------------
+You can choose either the installer or zip file
+
+.. note::
+
+ MapGuide Maestro requires .net Framework 2.0 or higher installed. For Windows Vista or newer versions of Windows, this is already installed.
+
Installing on Linux/Mac OSX
----------------------------
\ No newline at end of file
+---------------------------
+
+Before you run MapGuide Maestro, you need to install the Mono framework. Mono is available for download at `http://www.mono-project.com <http://www.mono-project.com>`_
+
+The installation is simply unzipping the file::
+
+ unzip "MapGuideMaestro-3.0.0-Release.zip"
+
+Then run the application::
+
+ cd Maestro
+ mono Maestro.exe
+
+.. note::
+
+ For distributions like Ubuntu, the Mono package is split into several components. You need to ensure that the winforms component is installed. The following command installs it for Ubuntu::
+
+ sudo apt-get install mono-runtime libmono-winforms2.0-cil
+
+ For other distros, please consult your system documentation.
+
+.. note::
+
+ **Please note that Mono support for WinForms is not 100% stable.** Even though WinForms is feature complete, some features do not work flawlessly. This means that there are occasional drawing problems. Flipping a tab page back and forth usually solves the problem. Some buttons are missing, because Mono renders them outside the visible area. There are also some issues with certain icons.
+ For best results, use the most current release of Mono (currently 2.10.2) where possible. The minimum usable release is Mono 2.0 (this was the release where WinForms was 100% API complete)
+
Modified: trunk/Tools/Maestro/UserDoc/source/mapguide_terminology.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/mapguide_terminology.rst 2011-05-17 07:59:19 UTC (rev 5809)
+++ trunk/Tools/Maestro/UserDoc/source/mapguide_terminology.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -1,14 +1,11 @@
-Understanding MapGuide Terminology
-==================================
+Understanding MapGuide Resources
+================================
.. todo::
Currently copy/paste of existing wiki content
Before you can start using MapGuide Maestro, you must understand how MapGuide divides the different parts that make up a map. To understand the MapGuide Maestro interface, you must also have a knowledgde of the names used in MapGuide.
-Types of Resources
-------------------
-
.. todo::
Detail the features offered with each schema revision. Most of this already is covered in resource-readme.txt in the Maestro source code.
@@ -50,6 +47,8 @@
Layer Definitions describe how data from a Feature Source is to be styled. (see below: Displaying Data)
+Layer Definitions are can be shared among different maps.
+
Map Definitions
^^^^^^^^^^^^^^^
@@ -120,6 +119,8 @@
Describes a collection of DWF-based symbols that can be used for point styles in a Layer Definitions
+There is no specialized editor support for Symbol Libraries. Opening Symbol Libraries will default to the generic XML editor.
+
Symbol Definitions
^^^^^^^^^^^^^^^^^^
@@ -132,6 +133,8 @@
Describes a cartographic symbol, which has lots of display and customisation parameters. Used by Layer Definitions.
+There is no specialized editor support for Symbol Definitions. Opening Symbol Definitions will default to the generic XML editor.
+
Watermark Definitions
^^^^^^^^^^^^^^^^^^^^^
@@ -143,53 +146,4 @@
Describes a watermark that is rendered as part of the map when viewing it. Used by Map Definitions.
-Spatial Data and Regular Data
------------------------------
-
-Data can come from a number of sources, such as a spread sheet or a database. Some data is spatially enabled, and this means that it has one or more columns of data that describes a geometric entry. Such data is usually called vector data. In spatially enabled data, the non-spatial data is usually called "attributes".
-
-Some data has an X and Y column (or LAT/LON), and is thus not spatially enabled. MapGuide can treat such data as if it was spatially enabled though.
-
-Another type of data is raster data, which is typically some form of aerial foto.
-
-MapGuide uses FDO to connect to data, and calls each connection a "FeatureSource", regardless of what type of data it points to.
-
-A "FeatureSource" does not have any information about how it looks, it's just lines, polygons and points.
-
-Displaying Data
----------------
-
-In MapGuide a "LayerDefinition" is used to describe how to represent a layer visually. This distinction between data and representation, means that you can define your "FeatureSource" once, and display it in red, green and blue.
-
-In a "LayerDefinition" you define how the layer should look in different "ScaleRanges". A "ScaleRange" is defined by two numbers, and while the map is displayed at a given scale, MapGuide will show it as the first matching "ScaleRange". If you define a "ScaleRange" 0 - 1000 and one 1001 - 2000, you can display the data differently depending on how close the user is viewing the map.
-
-For each "ScaleRange" you can define a number of rules. This can be used to visually show difference in the non-spatial values, eg. land value, or a broken pipe, etc. The default rule in MapGuide is a blank rule, which will match all data.
-
-If you use rules to display eg. land values with a gradient color, ranging from low land value to high land value, it is called "Theming".
-
-An object in the map can also have a "Label", which is displayed on top of the item. This can be used to display road names.
-
-You can also set a "Tooltip" on an object, which will be displayed when the cursor hovers over the object.
-
-Finally you can set a "Link" on an object, which will open when the user double clicks on the feature (CTRL+click in some places).
-
-Combining Data
---------------
-
-Once you have set up the visual apperance of your layers, you can combine them together in a map. In the map, the layers have a "Drawing Order", which is used to order how the layers are drawn. If you have a county and a subway layer, you might not be able to see the subways if they are below the large county layer. Usually polygons are at the bottom, then lines, then points, and finally labels on top.
-
-In MapGuide, such a collection of layers is called a "MapDefinition". In a "MapDefinition", you can also group layers, so the users can easily toggle the visibilty of a number of layers with a single click.
-
-In a "MapDefinition" you can also define what layers should be visible in the legend, and what names should be displayed in the legend.
-
-Presenting Data to the user
----------------------------
-
-Now that you have a "MapDefinition", you can set up a frame the user can view the data in. This frame defines what tools the user has (Zoom tool, select tool, measure tool, etc.), as well as what items are visible (legend, overview map, etc.).
-
-There are currently two types of frames you can use, one called "WebLayout" and one called "Fusion Application". Autodesk has named the "Fusion Application" "Flexible Layout", so you may see that term as well.
-
-MapGuide Packages
------------------
-
-When you have put a lot of effort into setting up a map, you can take a backup of the entire setup. Such a backup is known as a "Package". A "Package" is a compressed file with the extension ".mgp". You can create, edit and restore such packages using either MapGuide Maestro, or the MapGuide Site Administrator.
\ No newline at end of file
+There is no specialized editor support for Watermark Definitions. Opening Watermark Definitions will default to the generic XML editor.
\ No newline at end of file
Added: trunk/Tools/Maestro/UserDoc/source/publish_workflow.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/publish_workflow.rst (rev 0)
+++ trunk/Tools/Maestro/UserDoc/source/publish_workflow.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -0,0 +1,72 @@
+The Maestro Publishing Workflow
+===============================
+
+The basic workflow for creating maps and publishing them in Maestro is shown below
+
+.. image:: images/maestro_publish_workflow.png
+
+The first step is to connect to a MapGuide Server. Maestro will always prompt for a login when starting up.
+
+Find Data
+---------
+
+For this step, you have 2 choices.
+
+ 1. **Create a Load Procedure**. A **Load Procedure** specifies a set of source files to load from. When the **Load Procedure** is executed, the following occurs:
+
+ * A **Feature Source** is created for each source file
+ * A default **Layer Definition** is created for each created Feature Source
+
+ **Load Procedures** will always load the source files into the MapGuide Server as embedded resource data of the Feature Source. If you want to maintain
+ a connection to externally stored files, then you will have to create these **Feature Sources** manually. This approach is a quick way to load data into MapGuide.
+ **Load Procedures** can be saved and executed at a later point in time to refresh this data.
+
+ 2. **Create Feature Sources**. For data sources like relational databases or web services, you do not have the **Load Procedure** option available. So therefore
+ you have to create these **Feature Sources** manually. If you want to connect to externally stored or aliased data files, you have to use this approach.
+
+Build Layers
+------------
+
+For this step, create **Layer Definitions** that point to a **Feature Source**. **Layer Definitions** give defines style and presentation rules for data coming from a
+**Feature Sources**. You can do things like:
+
+ * Theme data by attributes
+ * Style line thickness by attributes (or a computed expression based on attributes)
+ * Size point features by attributes (or a computed expression based on attributes)
+ * Use attributes (or a computed expression based on attributes) for feature labels
+ * Filter data by an attribute filter
+
+**Layer Definitions** also contains settings for viewer interactions.
+
+ * You can specify a tooltip that is shown when you put a mouse over a feature from this layer. This can be an attribute or a computed expression based on attributes
+ * You can specify a url that is launched when the user selects a feature from this layer. This can be an attribute or a computed expression based on attributes.
+
+If you created and executed a **Load Procedure**, then these **Layer Definitions** have been created for you. However these are created with default settings
+(monochromatic styles with basic symbology). So you will have to open and edit these resources to suit your needs.
+
+Make a Map
+----------
+
+For this step, create a **Map Definition** and bring in the **Layer Definitions** you have created. Organise these layers into groups (optional) and sort them by drawing
+order with rasters and polygon layers at the bottom, followed by line layerse, then followed by point layers. You don't need to specifically follow this draw order, but
+it's a generally useful rule to follow.
+
+For layers that change very rarely, you can set them as tiled layers. Tiled layers are rendered once as tiles and stored into a Tile Cache. Subsequent requests for the
+same view will request the cached tiles. This is a useful way to improve map performance.
+
+.. note::
+
+ If you edit and save a map with tiled layers, the existing Tile Cache is deleted, as the generated tiles most likely no longer apply to the new map. Maestro will
+ warn you about such situations.
+
+Make the map available
+----------------------
+
+For this step. You can create either a **Web Layout** or a **Application Definition** which describe the viewer interface which to view and interact with the map.
+
+A **Web Layout** describes the user interface and functionality for the basic AJAX viewer. The AJAX viewer provies basic functionality for map viewing and interaction.
+
+A **Flexible Layout** describes the user interface and functionality for the Fusion viewer. The Fusion viewer has greater flexibility in terms of looks and functionality.
+
+Once you saved either resource, a preview URL will be visible in the respective editor. This URL allows your users to view the specific map using the specified
+viewer application.
\ No newline at end of file
Modified: trunk/Tools/Maestro/UserDoc/source/understanding_applications.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/understanding_applications.rst 2011-05-17 07:59:19 UTC (rev 5809)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_applications.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -4,5 +4,29 @@
Web Layouts
-----------
+Web Layout Settings
+^^^^^^^^^^^^^^^^^^^
+
+Menu and Toolbar Command Layout
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Command Set Configuration
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Importing/Exporting Commands
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
Application Definitions
------------------------
\ No newline at end of file
+-----------------------
+
+Template Selection
+^^^^^^^^^^^^^^^^^^
+
+Map Configuration
+^^^^^^^^^^^^^^^^^
+
+Widget and Container Layout
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Widget Management
+^^^^^^^^^^^^^^^^^
\ No newline at end of file
Added: trunk/Tools/Maestro/UserDoc/source/understanding_drawing_sources.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/understanding_drawing_sources.rst (rev 0)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_drawing_sources.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -0,0 +1,2 @@
+Understanding Drawing Sources
+=============================
\ No newline at end of file
Modified: trunk/Tools/Maestro/UserDoc/source/understanding_feature_sources.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/understanding_feature_sources.rst 2011-05-17 07:59:19 UTC (rev 5809)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_feature_sources.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -1,17 +1,63 @@
Understanding Feature Sources
=============================
+As already covered, **Feature Sources** describe a FDO connection to a particular spatial or non-spatial data store. FDO technology provides a generic,
+command-based interface to a number of back-end data source technologies for storing, retrieving, updating, and analyzing GIS (Geographic Information System) data.
+
+Support for various data sources exists in the form of FDO providers.
+
File-based Data
---------------
+Spatial data exists in many different forms and data formats. MapGuide supports various file-based data sources out of the box:
+
+ * SDF using the SDF FDO provider
+ * SHP using the SHP FDO provider
+ * SQLite using the SQLite FDO provider (for MapGuide Open Source 2.2 or newer)
+ * MS Access Databases and Excel Spreadsheets using the ODBC provider.
+ * Various other file formats using the OGR FDO provider.
+
+Support for other file formats exist via third party FDO providers.
+
Relational Data
---------------
+MapGuide also supports various relational data sources
+
+ * SQL Server
+ * MySQL
+ * Oracle
+ * PostgreSQL (for MapGuide Open Source 2.2 or newer)
+
+Support for other relational databases exist via third party FDO providers.
+
Raster Data
-----------
+MapGuide also supports raster data sources via the GDAL FDO provider.
+
The Generic Editor
------------------
-Provider-specific notes
------------------------
\ No newline at end of file
+Maestro provides a specialized feature source editor for the most frequently used FDO providers. For third party or other unrecognised FDO providers, a generic editor is
+available to configure the connection parameters to your particular data store.
+
+.. image:: images/fs_generic.png
+
+Coordinate System Overrides
+---------------------------
+
+TODO
+
+.. image:: images/fs_cs_overrides.png
+
+Joins and Extensions
+--------------------
+
+TODO
+
+.. image:: images/fs_extensions.png
+
+.. note::
+
+ Feature Join performance is generally bad, especially when the join is performed across Feature Classes from different Feature Sources for different FDO providers. Consider doing joins at the database level, outside of MapGuide
\ No newline at end of file
Modified: trunk/Tools/Maestro/UserDoc/source/understanding_layers.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/understanding_layers.rst 2011-05-17 07:59:19 UTC (rev 5809)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_layers.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -1,14 +1,94 @@
Understanding Layers
====================
+There are 3 types of Layer Definitions:
+
+ * Vector Layer Definitions
+ * Drawing Layer Definitions
+ * Grid (Raster) Layer Definitions
+
+Vector Layer Definitions describe style and presentation settings for vector data coming from a Feature Source
+
+Drawing Layer Definitions describe presentation settings for data coming from a Drawing Source
+
+Raster Layer Definitions describe style and presentation settings for raster data coming from a Feature Source
+
+Vector Layer Settings
+---------------------
+
Basic Layer Properties
+^^^^^^^^^^^^^^^^^^^^^^
+
+TODO
+
+.. image:: images/ldf_vector_settings.png
+
+TODO
+
+Layer Property Mappings
+^^^^^^^^^^^^^^^^^^^^^^^
+
+TODO
+
+.. image:: images/ldf_vector_property_mappings.png
+
+TODO
+
+Layer Scale Ranges
+^^^^^^^^^^^^^^^^^^
+
+TODO
+
+.. image:: images/ldf_vector_scale_range.png
+
+TODO
+
+Theming Layers
+^^^^^^^^^^^^^^
+
+TODO
+
+.. image:: images/ldf_vector_theme_generator.png
+
+TODO
+
+Point Style Rules
+^^^^^^^^^^^^^^^^^
+
+TODO
+
+.. image:: images/ldf_vector_point_rule.png
+
+TODO
+
+Line Style Rules
+^^^^^^^^^^^^^^^^
+
+TODO
+
+.. image:: images/ldf_vector_line_rule.png
+
+TODO
+
+.. image:: images/ldf_vector_line_rule_composite.png
+
+TODO
+
+Area Style Rules
+^^^^^^^^^^^^^^^^
+
+TODO
+
+.. image:: images/ldf_vector_area_rule.png
+
+TODO
+
+Drawing Layer Settings
----------------------
-Advanced Layer Properties
--------------------------
+TODO
-Styling Layers
---------------
+Raster Layer Settings
+---------------------
-Theming Layers
---------------
\ No newline at end of file
+TODO
\ No newline at end of file
Added: trunk/Tools/Maestro/UserDoc/source/understanding_load_procedures.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/understanding_load_procedures.rst (rev 0)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_load_procedures.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -0,0 +1,8 @@
+Understanding Load Procedures
+=============================
+
+Source Files
+------------
+
+Transformation Settings
+-----------------------
\ No newline at end of file
Added: trunk/Tools/Maestro/UserDoc/source/understanding_maps.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/understanding_maps.rst (rev 0)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_maps.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -0,0 +1,25 @@
+Understanding Map Definitions
+=============================
+
+Map Settings
+------------
+
+.. image:: images/mdf_settings.png
+
+Layer Configuration
+-------------------
+
+Layers by Group
+^^^^^^^^^^^^^^^
+
+.. image:: images/mdf_layers_grouping.png
+
+Layers by Drawing Order
+^^^^^^^^^^^^^^^^^^^^^^^
+
+.. image:: images/mdf_layers_draworder.png
+
+Base Layer Groups
+^^^^^^^^^^^^^^^^^
+
+.. image:: images/mdf_layers_base.png
\ No newline at end of file
Added: trunk/Tools/Maestro/UserDoc/source/understanding_print_layouts.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/understanding_print_layouts.rst (rev 0)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_print_layouts.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -0,0 +1,2 @@
+Understanding Print Layouts
+===========================
\ No newline at end of file
Modified: trunk/Tools/Maestro/UserDoc/source/user_interface.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/user_interface.rst 2011-05-17 07:59:19 UTC (rev 5809)
+++ trunk/Tools/Maestro/UserDoc/source/user_interface.rst 2011-05-17 15:48:03 UTC (rev 5810)
@@ -1,2 +1,19 @@
The Maestro User Interface
-==========================
\ No newline at end of file
+==========================
+
+The main Maestro application window is composed of the following components:
+
+.. image:: images/maestro_ui.png
+
+The **Site Explorer** presents the visual view of your MapGuide Server **Site Repository**, showing all the folders and resources stored within.
+When you double click a resource in the Site Explorer, it will open the matching editor for that particular resource. If the resource is not known to Maestro or the
+version of the resource is not known to Maestro the XML Editor will be shown instead loaded with the XML content of the selected resource. When you right click a
+resource in the Site Explorer a whole assortment of options on the context menu is available for that selected resource.
+
+All **Open Resources** will be shown in the main area of the Maestro application window.
+
+Maestro is designed to be as transparent as possible to the user, as such it logs a lot of messages useful for diagnostic purposes. Maestro also logs most communication
+that it makes to the MapGuide Server. You can see these logged messages and requests in the **Messages and Outbound Requests** tabs.
+
+
+
More information about the mapguide-commits
mailing list