You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2008/05/02 20:48:55 UTC

[jira] Updated: (SLING-398) [Patch] Separate bundle details page in sling web console

     [ https://issues.apache.org/jira/browse/SLING-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Klimetschek updated SLING-398:
----------------------------------------

    Attachment: bundle-details-html-page.patch

And yet another patch update that fixes a problem with broken layout on long headlines (ie. long symbolic bundle names) on the detail page

> [Patch] Separate bundle details page in sling web console
> ---------------------------------------------------------
>
>                 Key: SLING-398
>                 URL: https://issues.apache.org/jira/browse/SLING-398
>             Project: Sling
>          Issue Type: New Feature
>          Components: Console
>            Reporter: Alexander Klimetschek
>         Attachments: bundle-details-html-page.patch, bundle-details-html-page.patch, bundle-details-html-page.patch
>
>
> This patch adds a separate HTML page showing bundle details to the Sling web console. It displays the same details as those displayed by the ajax-based "popup".
> Use case: I found myself configuring a bundle with Export-Package etc. and continuously installing it to Sling to see if all package dependencies could be resolved. It is quite tedious to reload the bundle list page, scroll down to the bundle in question and click on the link to get the ajax-based details popup. A simpler (and more restful) way is to have a separate URL and HTML page for a single bundle's details.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.