[
https://issues.apache.org/jira/browse/SLING-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484860#comment-13484860
]
Robert Munteanu commented on SLING-2634:
----------------------------------------
In reply to comment #1:
> [~rmuntean] I am not sure I really caught your subclipse example.
There's a screenshot of the SVN console view at
http://fossies.org/unix/privat/subclipse-1.6.18.tar.gz:a/subclipse-1.6.18/org.tigris.subversion.subclipse.doc/html/reference/svn-console.html
. It logs all operations and their results.
>
> For the Command pattern idea it was actually my first implementation but it
> did
> not really combined well with the declarative services (or at least my command
> pattern implementation :))
Right, I need to see how/if this would work ...
Anyway, if you have other ideas on how to show the operations which we perform
to the user I'm open to them. I simply want to know what slingclipse does
without using a http proxy :-)
> [Tooling] Slingclipse should expose the operations it performs and their
> results
> --------------------------------------------------------------------------------
>
> Key: SLING-2634
> URL: https://issues.apache.org/jira/browse/SLING-2634
> Project: Sling
> Issue Type: Sub-task
> Components: Extensions
> Reporter: Robert Munteanu
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
