Thanks all, at least I didn't overlook something obvious. I'm not surprised
that
someone's thought of this kind of thing, and, under any circumstances there
*has* to be a more elegant way than the hack I used <G>....

I'm always reluctant to raise a JIRA on a project before I know I haven't
overlooked
something.. and in this case there already is one....

I'll keep an eye on 742. If I get really crazy I might even see if I can
make a patch.
In which case I'll no doubt bother folks on the dev list to get more
guidance.

Thanks again
Erick

On Thu, Jun 18, 2009 at 5:59 PM, Thiago H. de Paula Figueiredo <
[email protected]> wrote:

> Em Thu, 18 Jun 2009 13:29:29 -0300, Erick Erickson <
> [email protected]> escreveu:
>
>  An utter Tapestry newbie here, although I was at some recent training
>> Howard gave.
>>
>
> Welcome to the Tapestry mailing list and community!
>
>  My question is, "Given a page composed of components, is there an easy,
>> visual way to analyze the structure in terms of custom components *from
>> the browser *?".
>> The problem I'm trying to address is the most efficient way to bring
>> someone new (me, in this case <G>) up to speed on a project.
>>
>
> Howard thought of something like that, but in the form of comments, but
> hasn't implemented it yet: https://issues.apache.org/jira/browse/TAP5-742.
> Your proposition can also be a debugging tool. :) By the way, Tapestry's
> JIRA is the place to post bugs and requests for enhancements.
>
> Tapestry is veeeeery configurable, so I guess it is possible to do
> something like that with a ComponentClassTransformWorker or decorating some
> Tapestry service I don't have the time to find out which one now.
>
>  Now, when I'm viewing prior art I can hover over the icons I've inserted
>> and
>>
>
> This mention to prior art reminded me of software patent discussions in
> Slashdot . . . hehehe
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java consultant, developer, and instructor
> http://www.arsmachina.com.br/thiago
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to