Opened 14 years ago

Closed 14 years ago

#1661 closed enhancement (fixed)

Maestro 3 - Find/Replace

Reported by: crispinatime Owned by:
Priority: medium Milestone: Maestro-3.0
Component: General Version:
Severity: major Keywords:
Cc: External ID:

Description

In Maestro 2.1 there was a folder-level right-click option to invoke a find/replace menu on the XML for all items in that folder.

This was designed to facilitate easier schema changes when migrating.

For example, having an Oracle or ArcSDE schema on a development environment and packaging up for deployment, typically the schema name is different, though classes are the same. Because the schema name is embedded in the .LayerDefinition (ArcSDE and KingOra both have the schema as part of the layers <FeatureName>) the find/replace provided a capability to update reliably and quickly.

Change History (6)

comment:1 by jng, 14 years ago

Resolution: fixed
Status: newclosed

Fixed in r5695. Note that because we currently cannot dynamically add custom context menu items, the command will prompt for the find/replace tokens.

I'll leave this for you to close if there are no further issues.

comment:2 by crispinatime, 14 years ago

Thanks - I can live with doing a multi-select rather than a folder-level find/replace.

Is the intent to auto-save the resource after the find-replace? Works for me but possibly inconsistent with other Maestro behaviour.

Comment: Win7 style it is difficult to see which tab is current as the 'highlight' style is not very distinguished from other tabs

comment:3 by jng, 14 years ago

The r5695 submission does auto-save after find replace. Did the 2.x impl just opened the resource in the XML editor and *then* do the find/replace, allowing you to review the XML content before saving? If this is the case, I can modify this behaviour in 3.0 to match.

Also nice find on the tab highlighting. When you've been working on the app for so long, some simple things just aren't readily apparent to you. A fix has been made with r5697

comment:4 by crispinatime, 14 years ago

Previous behaviour was (just checked) to open all the selected items in XML mode. If a replacement was made then the tree icon obviously highlights red (or as per new options) and the tab status has the edit "*"

This allowed you to see what was red and what was green and forces a manual save before the resource is committed. I think that is safer/better.

comment:5 by jng, 14 years ago

Resolution: fixed
Status: closedreopened

comment:6 by jng, 14 years ago

Resolution: fixed
Status: reopenedclosed

Fixed in r5698

Note: See TracTickets for help on using tickets.