Uploaded image for project: 'ModeShape'
  1. ModeShape
  2. MODE-2093

Web explorer should provide modern view on content

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 4.0.0.Alpha4
    • 3.6.0.Final
    • Web Application
    • None

    Description

      At the moment web-explorer provides classic IDE -style view on the content. Would be better to provide more fresh 'page' view on the node without explicit tree view

      Attachments

        1. s1.png
          s1.png
          132 kB
        2. s1.png
          s1.png
          141 kB
        3. s2.png
          s2.png
          173 kB
        4. s2.png
          s2.png
          141 kB
        5. s3.png
          s3.png
          149 kB
        6. s3.png
          s3.png
          157 kB
        7. s4.png
          s4.png
          162 kB
        8. s6.png
          s6.png
          171 kB
        9. ss1.png
          ss1.png
          160 kB
        10. ss2.png
          ss2.png
          160 kB
        11. ss3.png
          ss3.png
          175 kB

        Issue Links

          blocks

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-2244 Backport new Repository Explorer web application

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. MODE-2236 Repository Explorer's "Node Types" button results in error (?) popup, but it works

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. MODE-2238 Repository Explorer's query results only show 1 line at a time

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-2233 Repository Explorer's administrative functions should be separated onto administrative page

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-2234 Repository Explorer's save button should be moved closer to where changes are actually made

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-2237 Repository Explorer's query page should default to "JCR-SQL2" query language

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-2230 Breadcrumb path in RepositoryExplorer needs to clearly show as separate links for each segment

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-2232 Repository Explorer links should be standard colors but should not be underlined

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-2231 Enable navigating in Repository Explorer to content of BINARY property

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODE-2235 Repository Explorer's administrative page should show metrics

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              oleg.kulikov Oleg Kulikov (Inactive)
              oleg.kulikov Oleg Kulikov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: