[mapguide-commits] r7675 - in trunk/Tools/Maestro/UserDoc/source: . images
svn_mapguide at osgeo.org
svn_mapguide at osgeo.org
Tue Jul 9 05:32:26 PDT 2013
Author: jng
Date: 2013-07-09 05:32:25 -0700 (Tue, 09 Jul 2013)
New Revision: 7675
Added:
trunk/Tools/Maestro/UserDoc/source/images/edit_as_xml_button.PNG
trunk/Tools/Maestro/UserDoc/source/images/fl_widget_config_map.PNG
trunk/Tools/Maestro/UserDoc/source/images/fl_widget_info.PNG
trunk/Tools/Maestro/UserDoc/source/images/fs_gdal_composite.PNG
trunk/Tools/Maestro/UserDoc/source/images/fs_gdal_configuration_document_extents.PNG
trunk/Tools/Maestro/UserDoc/source/images/fs_generic_set_credentials.PNG
trunk/Tools/Maestro/UserDoc/source/images/fs_other_options.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_point_rule_pt2.PNG
trunk/Tools/Maestro/UserDoc/source/images/xml_editor.PNG
Modified:
trunk/Tools/Maestro/UserDoc/source/differences.rst
trunk/Tools/Maestro/UserDoc/source/edit_xml.rst
trunk/Tools/Maestro/UserDoc/source/images/connect_local.png
trunk/Tools/Maestro/UserDoc/source/images/fl_widget_config.PNG
trunk/Tools/Maestro/UserDoc/source/images/fs_generic.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_symbol_instances_dialog.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_area_rule.png
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_composite_rule.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_label.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_point_rule.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_scale_range.PNG
trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_theme_generator.PNG
trunk/Tools/Maestro/UserDoc/source/images/local_repository.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/validation_results.PNG
trunk/Tools/Maestro/UserDoc/source/local_connection_mode.rst
trunk/Tools/Maestro/UserDoc/source/localpreview.rst
trunk/Tools/Maestro/UserDoc/source/publish_workflow.rst
trunk/Tools/Maestro/UserDoc/source/resource_validation.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/understanding_symbol_definitions.rst
trunk/Tools/Maestro/UserDoc/source/user_interface.rst
Log:
User guide update for Maestro 5.0
Modified: trunk/Tools/Maestro/UserDoc/source/differences.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/differences.rst 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/differences.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -20,7 +20,7 @@
* MapGuide Studio supports loading of DWG files and raster images. Due to licensing and/or the need to be multi-platform, Maestro does not (and probably will never) support these features.
* MapGuide Studio supports creating and editing Symbol Libraries. Maestro cannot edit Symbol Libraries, however it has read support for these resources and Maestro supports symbol selection from Symbol Libraries.
* MapGuide Studio supports the "Convert to SDF" and generalization options of Load Procedures.
- * Autodesk Infrastructure Studio (2013 onwards) supports publishing DWG files directly with no conversion.
+ * Autodesk Infrastructure Studio (2013 onwards) supports publishing DWG files directly with no conversion and full visual fidelity.
* Autodesk Infrastructure Studio supports creating connections to Industry Model (Topobase) data sources.
Features unique to MapGuide Maestro
@@ -32,6 +32,7 @@
* Maestro has a small installation footprint compared to MapGuide Studio.
* Maestro allows you to edit any resource in its XML form. The XML editor is used as a fallback measure if Maestro encounters unsupported or unrecognised resources.
* Maestro supports all known resource versions. Maestro will *never* silently upgrade your resources to the latest version.
+ * Maestro's functionality can be extended by users, either through dedicated extension APIs or through the built-in IronPython scripting engine.
* Maestro supports custom resource templates
* Maestro supports the creation and loading of MapGuide Packages (MGP) without needing to use the Site Administrator web application.
* Maestro has a more active development cycle.
Modified: trunk/Tools/Maestro/UserDoc/source/edit_xml.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/edit_xml.rst 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/edit_xml.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -4,6 +4,10 @@
The XML Editor is the generic editor that can be used to edit the XML form of any resource in the MapGuide Server. If you are intimately familiar with the XML schema
of the resource in question, editing via the XML editor can often be much faster in terms of productivity than having to go through the specialized editor.
+.. figure:: images/xml_editor.png
+
+ *The Generic XML editor*
+
For resources that are not recognised by the current release of Maestro or a specialized editor does not exist, this editor will be used as a fallback. Otherwise, you can
choose to open any resource in the XML editor by right clicking the resource in the **Site Explorer** and choosing the **Open Resource with XML Editor** context menu item.
@@ -12,4 +16,10 @@
You cannot have an XML editor or specialized editor editing the same resource. Maestro will not let it happen.
If you are editing a resource via a specialized editor, you can instantly go to and edit the resource in its XML form via the XML editor with the **Edit as XML** toolbar
-command. Upon saving the XML content in this mode, the original specialized editor will be immediately refreshed with the latest resource settings.
\ No newline at end of file
+command.
+
+.. figure:: images/edit_as_xml_button.png
+
+ *The Edit as XML command*
+
+Upon saving the XML content in this mode, the original specialized editor will be immediately refreshed with the latest resource settings.
\ No newline at end of file
Modified: trunk/Tools/Maestro/UserDoc/source/images/connect_local.png
===================================================================
(Binary files differ)
Added: trunk/Tools/Maestro/UserDoc/source/images/edit_as_xml_button.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/edit_as_xml_button.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Modified: trunk/Tools/Maestro/UserDoc/source/images/fl_widget_config.PNG
===================================================================
(Binary files differ)
Added: trunk/Tools/Maestro/UserDoc/source/images/fl_widget_config_map.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/fl_widget_config_map.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/fl_widget_info.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/fl_widget_info.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/fs_gdal_composite.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/fs_gdal_composite.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/fs_gdal_configuration_document_extents.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/fs_gdal_configuration_document_extents.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Modified: trunk/Tools/Maestro/UserDoc/source/images/fs_generic.PNG
===================================================================
(Binary files differ)
Added: trunk/Tools/Maestro/UserDoc/source/images/fs_generic_set_credentials.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/fs_generic_set_credentials.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: trunk/Tools/Maestro/UserDoc/source/images/fs_other_options.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/fs_other_options.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Modified: trunk/Tools/Maestro/UserDoc/source/images/ldf_symbol_instances_dialog.PNG
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_area_rule.png
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_composite_rule.PNG
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_label.PNG
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_point_rule.PNG
===================================================================
(Binary files differ)
Added: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_point_rule_pt2.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_point_rule_pt2.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Modified: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_scale_range.PNG
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/ldf_vector_theme_generator.PNG
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/local_repository.png
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/maestro_ui.png
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_base.PNG
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_draworder.PNG
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/mdf_layers_grouping.PNG
===================================================================
(Binary files differ)
Modified: trunk/Tools/Maestro/UserDoc/source/images/validation_results.PNG
===================================================================
(Binary files differ)
Added: trunk/Tools/Maestro/UserDoc/source/images/xml_editor.PNG
===================================================================
(Binary files differ)
Property changes on: trunk/Tools/Maestro/UserDoc/source/images/xml_editor.PNG
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Modified: trunk/Tools/Maestro/UserDoc/source/local_connection_mode.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/local_connection_mode.rst 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/local_connection_mode.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -3,7 +3,7 @@
The Local Connection Mode
=========================
-The Local Connection Mode is a new feature of Maestro 4.0 that allows you to work with a resource repository that is local on your machine.
+The Local Connection Mode is a new feature of Maestro that allows you to work with a resource repository that is local on your machine.
The Local Connection Mode is designed for the following user scenarios:
Modified: trunk/Tools/Maestro/UserDoc/source/localpreview.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/localpreview.rst 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/localpreview.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -1,3 +1,5 @@
+.. _local-fs-preview:
+
Using Local Feature Source Preview
==================================
Modified: trunk/Tools/Maestro/UserDoc/source/publish_workflow.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/publish_workflow.rst 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/publish_workflow.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -48,7 +48,7 @@
----------
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
+order with rasters and polygon layers at the bottom, followed by line layers, 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
Modified: trunk/Tools/Maestro/UserDoc/source/resource_validation.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/resource_validation.rst 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/resource_validation.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -1,3 +1,5 @@
+.. _resource-validation:
+
Resource Validation
===================
Modified: trunk/Tools/Maestro/UserDoc/source/understanding_applications.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/understanding_applications.rst 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_applications.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -132,10 +132,21 @@
Widget Management
^^^^^^^^^^^^^^^^^
-The **Widget Management** dialog allows you to add and configure widgets in the widget set. Widgets in the widget set can then be referenced in the **Widgets** section of the editor.
+The **Widget Management** dialog allows you to configure the main map widget and to add/configure other widgets in the widget set.
+Widgets in the widget set can then be referenced in the **Widgets** section of the editor.
+
+.. figure:: images/fl_widget_config_map.png
+
+ *Widget Management Dialog (map widget)*
+
.. figure:: images/fl_widget_config.png
- *Widget Management Dialog*
+ *Widget Management Dialog (other widgets)*
-Most widgets have a specialized editor to configure widget parameters. For those that don't a generic XML editor is available as a fallback mechanism.
\ No newline at end of file
+All widgets are edited via XML. Widget behaviour is customised by editing the `<Extension>` element of the widget XML. If you are not sure what elements are allowed in the widget's extension
+element, you can click the **Widget Info** button, which will list all the available extension properties for this widget
+
+.. figure:: images/fl_widget_info.png
+
+ *Widget Info Dialog (for Redline widget)*
\ 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 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_feature_sources.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -49,6 +49,8 @@
If a connection property involves an embedded data file, upload the file first as a **Resource Data File** and you can reference it
by prefixing `%MG_DATA_FILE_PATH%` in front of the resource data file name.
+.. _coordsys-override:
+
Coordinate System Overrides
---------------------------
@@ -62,7 +64,7 @@
have real world geographical relevance. You can use this editor to replace this Arbitrary coordinate system with a different coordinate
system.
-This is important if you require MapGuide to transform data. The source and target coordinate systems need to be correct. This override
+This is important if you require MapGuide to transform data. The source and target coordinate systems need to be correct. This override
mechanism allows you to fix the source side of the transformation.
Joins and Extensions
@@ -91,4 +93,74 @@
.. 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
+ 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
+
+.. note::
+
+ For best Feature Join performance, both sides of the join should support sortable query results. Providers that support sortable query results include:
+
+ * SDF (single property only)
+ * SHP (single property only)
+ * Any of the RDBMS providers (ODBC, SQL Server, MySQL, PostgreSQL, Oracle)
+
+ Any join that involves any of the above providers on both sides **on a single property** should have generally decent performance. Still doing these joins at the datastore level is preferable
+
+Specifying Credentials
+----------------------
+
+Some Feature Source editors (generic or specialized) support entering user login credentials. The specialized editors will automatically substitute your entered credentails with the **%MG_USERNAME%** and
+**%MG_PASSWORD%** placeholder tokens, with the actual values encrypted and stored into the **MG_USER_CREDENTIALS** resource data item.
+
+For the Generic Editor, a `Set Credentials` link allows you to specify credentials in a secure manner.
+
+.. figure:: images/fs_generic_set_credentials.png
+
+ *Specifying Credentials in the Generic editor*
+
+.. note::
+
+ Versions of Maestro before 4.0 did not support these feature and credentials were stored plaintext in the Resource XML documents themselves. It is **strongly** advised to run a validation process (see :ref:`resource-validation`) on your
+ repository, which will pick up such resources (which will be flagged as warnings in the Validation Results dialog). You should re-open these resources in a newer version of Maestro and apply credentials in a secured manner.
+
+.. _fs-other-options:
+
+Other Feature Source Options
+----------------------------
+
+All Feature Source editors whether the generic one or a specialized one will provide extra options for you which will be enabled or disabled based on the underlying capabilities of the FDO provider.
+
+.. figure:: images/fs_other_options.png
+
+ *Additional Feature Source Options*
+
+**Local Preview** opens the Local Feature Source Preview on this Feature Source allowing you to view the strucutre of this Feature Source and be able to do basic data queries on the Feature Source. See :ref:`local-fs-preview` for more information.
+
+**Edit Configuration Document** opens the associated configuration XML document. Most specialized Feature Source editors that support configuration will build this document for you. This feature allows you to look at the document itself and if required, edit
+the contents by hand
+
+**Spatial Contexts** displays the spatial contexts of the Feature Source
+
+Raster Configuration
+--------------------
+
+When creating Raster Feature Sources (with the GDAL provider), it is generally advised to use the **Composite** mode and build a configuration document by adding in the individual raster images. Adding in each raster image will update the
+configuration document with the details from that raster image such as the bounds and the physical file path.
+
+.. figure:: images/fs_gdal_composite.png
+
+ *GDAL Feature Source editor in composite mode*
+
+The configuration document serves as a Raster Tile Index and is referred to by MapGuide when doing raster data queries when rendering maps. The raster queries will use the bounds information recorded in the configuration document to grab the
+closest matching raster images for resampling. This is a much faster way for MapGuide to access raster imagery.
+
+After you have built your raster configuration document, be sure to check the overall final extents by clicking **Edit Configuration Document** under **Other Options** (see :ref:`fs-other-options`) to see the configuration document XML
+
+.. figure:: images/fs_gdal_configuration_document_extents.png
+
+ *Overall extents in the configuration document*
+
+This is the value used for previewing any layers you build off of this Feature Source and incorrect extents can cause massive performance issues.
+
+.. note::
+
+ After you have built your raster configuration document, you should also apply :ref:`coordsys-override` to ensure MapGuide will be reading this data under the correct coordinate system
\ No newline at end of file
Modified: trunk/Tools/Maestro/UserDoc/source/understanding_layers.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/understanding_layers.rst 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_layers.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -108,6 +108,9 @@
Each generated rule wil use a color from a specified color ramp. The color ramp can be gradient-based or use
ColorBrewer thematics.
+An option is also available that allows you to use the first rule of your current style as the "prototype" from which your theme rules will be created
+from, avoiding the need to manually re-style each individual theme rule after generation.
+
Once you have specified the theme settings and clicked **OK**, the matching rules will be generated and will replace
or be appended to your existing set of style rules for this scale range.
@@ -120,6 +123,10 @@
*The Point Style dialog*
+.. figure:: images/ldf_vector_point_rule_pt2.png
+
+ *The Point Style dialog (fill/border settings)*
+
There are many options here, but this guide will only cover the main ones.
Point features can be drawn as symbols or as text labels. The **Display Points** checkbox governs this behavior. Ticking it will
@@ -129,8 +136,10 @@
For point symbology, you can choose a pre-defined list of symbols under the **Symbol** dropdown. The very last option
in that dropdown (`Symbol`) allows you to pick a custom symbol from an existing **Symbol Library** resource.
-Note that the generated preview at the bottom of the dialog is not perfect and does not exactly reflect the style settings
-you have defined. Use the **Preview** command in the main toolbar to view this Layer in your system default web browser. Here
+Note that the generated preview at the bottom of the dialog is an approximation and does not exactly reflect the style settings you have defined. This preview would
+be the same image if you were to look at this layer's icon in the AJAX or Fusion viewer legend.
+
+If you want an exact representation, use the **Preview** command in the main toolbar to view this Layer in your system default web browser. Here
you can better verify your point style settings are correct.
Line Style Rules
@@ -197,8 +206,9 @@
.. note::
- Unlike Point/Line/Area styles, the preview is blank because rendering composite symbolization preview is not currently supported. The only
- means of previewing your composite symbolization settings is trial and error with the current edited layer defintion.
+ Unlike Point/Line/Area styles, the top-level preview is blank because rendering composite symbolization preview is not currently supported. However
+ the **Symbol Instances Dialog** does offer basic previewing support. What you see in the symbol preview is simply an enlarged version of the icon that
+ you would see for this layer if it was displayed in the AJAX or Fusion viewer legend.
Label Settings
^^^^^^^^^^^^^^
Modified: trunk/Tools/Maestro/UserDoc/source/understanding_symbol_definitions.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/understanding_symbol_definitions.rst 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/understanding_symbol_definitions.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -89,4 +89,11 @@
* A reference to an existing Simple Symbol Definition
* An inline Simple Symbol Definition
-Inline Simple Symbol Definitions use the same Simple Symbol Definition editor, embedded within the existing Compound Symbol Definition Editor.
\ No newline at end of file
+Inline Simple Symbol Definitions use the same Simple Symbol Definition editor, embedded within the existing Compound Symbol Definition Editor.
+
+Previewing
+----------
+
+Both Simple and Compound Symbol Definition editors support previewing, by clicking the **Preview** button in the main toolbar while the editor is the active tab.
+
+This generates an enlarged version of the icon that you would normally see for this layer if it was displayed in the AJAX or Fusion viewer legend.
\ No newline at end of file
Modified: trunk/Tools/Maestro/UserDoc/source/user_interface.rst
===================================================================
--- trunk/Tools/Maestro/UserDoc/source/user_interface.rst 2013-07-08 14:48:36 UTC (rev 7674)
+++ trunk/Tools/Maestro/UserDoc/source/user_interface.rst 2013-07-09 12:32:25 UTC (rev 7675)
@@ -1,10 +1,17 @@
The Maestro User Interface
==========================
-The main Maestro application window is composed of the following components:
+The main Maestro application window is composed of the following main components:
.. image:: images/maestro_ui.png
+Legend
+
+ 1. The Site Explorer
+ 2. Open Resource Editors
+ 3. Messages, Outbound Requests and IronPython Console
+ 4. Resource ID bar
+
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
@@ -15,5 +22,10 @@
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.
+The **IronPython Console** provides the user with an interactive REPL console, by which the user can run and evaluate snippets of IronPython code. The full Maestro API is
+exposed to the console, allowing the user to script and automate the application through IronPython code. IronPython is a dialect of Python geared towards integration with
+the .net Framework. For more information about IronPython, see `IronPython.net <http://ironpython.net/>`_
-
+The **Resource ID bar** functions like an address bar in a web browser. Entering a Resource ID in the **Resource ID bar** and clicking `Go` will allow you to directly open
+the specified resource for editing. Similarly, selecting an open editor tab will show you the Resource ID of the resource being edited. This is a feature that power users
+will appreciate, as it allows for quick resource access without the need to navigate the repository in the **Site Explorer** to find it.
\ No newline at end of file
More information about the mapguide-commits
mailing list