Bug 1035949 - RFE: Conditional View for XML
Summary: RFE: Conditional View for XML
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.4
Assignee: Matthew Casperson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-29 01:28 UTC by Misha H. Ali
Modified: 2014-08-04 22:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-23 23:43:48 UTC


Attachments (Terms of Use)
conditional elements in XML editor (11.27 KB, image/png)
2014-01-12 21:22 UTC, Matthew Casperson
no flags Details

Description Misha H. Ali 2013-11-29 01:28:34 UTC
Description of problem:

The conditional rendered in the CCMS UI works great but it is hard to locate the correct XML bit in densely conditioned topics.

If there is a way to show only the condition agnostic + specific condition XML, it would be very useful.

Comment 1 Matthew Casperson 2014-01-12 21:22:04 UTC
We could "black out" elements that don't match the selected condition. See the attached screenshot for an example of what this might look like.

Keep in mind that any visual clue to elements that don't match the current condition needs to work across multiple themes.

Comment 2 Matthew Casperson 2014-01-12 21:22:39 UTC
Created attachment 849008 [details]
conditional elements in XML editor

Comment 4 Matthew Casperson 2014-01-17 20:36:17 UTC
I fixed a few bugs with the calculation of the character range of elements that whose condition excludes them, and also made changes to the selected spec cause the highlighting to change.

Comment 5 Lee Newson 2014-01-28 00:23:25 UTC
Verified that content that will be removed during conditional processing is blacked out.

Tested with:
- Global Conditions
- Container Conditions
- Topic Conditions
- Various different XML elements


Note You need to log in before you can comment on or make changes to this bug.