[mapguide-users] Maestro 3.0 test build #2

[Jason Birch]

Wow.

I'm totally blown away by the speed that you're iterating features.  Either
you're not sleeping, or your heavy re-factor of Maestro is really paying
off.  Or maybe both :)

I'm really looking forward to testing the inter-server migration features;
hope I can do this tonight.  This will really help with my current process
(dump both sites to MGP, extract, check for differences with Beyond Compare,
migrate smaller packages or XML copy/paste of the differing areas).

Do the migration tools check the site version to make sure that the
resources being migrated are compatible with the other server? Hopefully the
person doing the migration would know what's going on, but... :)

My pipe dream would be a tool for opening two sites side-by-side and
visually seeing the differences somehow.  Beyond Compare has an awesome UI
for this on the filesystem level where the differences are colour coded and
you can filter to only see differences, etc.

Jason

On 26 October 2010 05:07, Jackie Ng wrote:

>
> Hi All,
>
> I've put up the 2nd test build of Maestro 3.0 for download. This is the
> first Maestro 3.0 test build that should work on Mono.
>
>
> http://download.osgeo.org/mapguide/maestro/MapGuide%20Maestro%203.0.0.5334%20Test2.zip
>
> Once again, I'll preface all of this with your standard warning:
>
> HERE BE DRAGONS! THIS BUILD SHOULD NOT BE CONSIDERED PRODUCTION-QUALITY AND
> SHOULD ONLY BE USED FOR TESTING PURPOSES AND FEEDBACK. DO NOT USE THIS ON
> PRODUCTION MAPGUIDE SERVERS!
>
> With that out of the way and your knowledge/acceptance of the above fact
> when testing this build, here's the changes from Test Build #1:
>
> The missing stuff:
>
>   - Migrated MgCooker.exe
>   - Migrated Official MapGuide API support. However this is disabled by
> default as it requires additional setup. ConnectionProviders.xml and
> Maestro.exe.config are documented to detail how to get Maestro working with
> official MapGuide API dlls.
>   - Migrated Server Status Monitoring window (under Tools menu)
>
> The fixes and tweaks:
>
>   - Modify the resource picker to support beginning from a specific folder
> (as per Jason's suggestion). When creating a new resource via right click,
> the folder you right-clicked is the initial starting point for the save
> dialog when you save for the first time.
>   - New Resource Dialog fixes and UX enhancements (as per Jason's
> suggestion)
>   - Prevent dangling editors as a result of closing the connection or
> deleting the edited resource.
>   - Drag/Drop support for the Resource Data UI (and any UI component that
> uses this control)
>   - Only prompt for restart when changing option values that actually
> require a restart
>   - New validation rules for DWF-based Layers
>   - Mono fixes
>     - Fix XML deserialization problems in Mono
>     - Fix double height UI elements in Mono
>
> The awesome sauce:
>
>   - Inter-server Migration tools (based on ideas suggested by Jason in trac
> ticket 1112)
>     - Move/Copy resources to a folder on another server with option to
> overwrite existing resources.
>     - Copy selected resource (and its dependencies) to the same path on
> another server. You have a choice of which dependent resources to copy and
> whether to overwrite existing resources.
>
>
> Note that Maestro 3.0 is still lacking some features from 2.x as they are
> still in the process of being ported over:
>
>  - Custom user resource templates
>  - Runtime Map API
>  - Raster layer editor
>  - Package editor
>  - Fusion editor
>  - Specialized feature source editors for other providers
>  - Possibly others
>
> Once again, general notes when testing this build:
>
>  - Found a bug? Ask yourself: Did this bug exist in Maestro 2.x, and hence
> is a known problem?
>  - Similarly, that Maestro 2.x issue you filed in Trac some time ago: Has
> it
> been fixed or successfully worked around with this build?
>  - So generally speaking, it really helps to have an existing installation
> of Maestro 2.x on hand (current release being 2.1.4) as a baseline
> comparison to whether something has been fixed or broken.
>  - Filed an issue under the previous test build? Did this test build fix
> this issue for you?
>  - All existing Maestro tickets will be re-targeted to the maestro-3.0
> milestone
>  - Something breaks when running in Mono? It helps to specify the expected
> behaviour when running in Windows. Screenshots help as well. Also indicate
> the version of Mono
>
> - Jackie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20101026/69c36840/attachment.html