tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-864) ComponentResources should expose an API that describes sub-components & formal/informal parameters (to be used as a diagnostic tool)
Date Mon, 12 Jan 2015 08:10:44 GMT

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

Jochen Kemnade closed TAP5-864.
-------------------------------
    Resolution: Invalid

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4
preview release), feel free to provide the necessary information and reopen.

> ComponentResources should expose an API that describes sub-components & formal/informal
parameters (to be used as a diagnostic tool)
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-864
>                 URL: https://issues.apache.org/jira/browse/TAP5-864
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> T3 had the inspector ... and I've built on-offs in T4 that identifies the # of components
on a page.  A ComponentStats interface could identify the immediate components (by id), the
type (and count) of each components directly within a component, as well as a roll up. This
would make it possible (given a UI) to drill-down and see which pages and which components
contribute to the Uber-component anti-pattern.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message