Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-2628 [Tooling] Eclipse plugins/features for Sling-based development
  3. SLING-2634

[Tooling] Slingclipse should expose the operations it performs and their results

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • Sling Eclipse IDE 1.0.0
    • IDE
    • None

    Description

      I think that it's important for the user to know what Slingclipse is doing, especially since it uses some heuristics to detect Sling-based projects.

      My first thoughts would be:

      • from a UI point of view start with something simple like a text-only console . The subclipse console is a good starting point, we can simply log things like

      ADD $SLING_URL $PROJECT/$RESOURCE 200 OK
      REMOVE $SLING_URL $PROJECT/$RESOURCE 500 Internal Server Error

      • from an implementation point of view we could use something like a command pattern ( SaveResource command, DeleteResourceCommand ) . This would have the benefit of allowing this logging easily + encapsulating the operations for batching, handling of offline operations, redo etc.

      Thoughts? I'm willing to look into this, at least for a first iteration.

      Attachments

        1. SLING-2634-1.diff
          33 kB
          rmuntean
        2. SLING-2634-2.diff
          4 kB
          rmuntean
        3. SLING-2634-proof-of-design.diff
          16 kB
          rmuntean

        Activity

          People

            asanso Antonio Sanso
            rombert Robert Munteanu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: