StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15514944
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-20T03:50:17.120
FavoriteCount
0
LastActivityDate
2013-03-20T04:14:30.933
LastEditDate
2013-03-20T04:14:30.933
LastEditorUserId
70465
OwnerUserId
70465
ParentId
15489915
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I've written something similar which I put as a public closure in a category I then mixin to services: <pre><code>// TimingCategory.groovy /** * Provides common AOP timing functionality to Services which mixin this category. */ class TimingCategory { static Closure timer = { String label = "The call", Closure closure -> Long start = System.currentTimeMillis() def result = closure.call() Long end = System.currentTimeMillis() Long duration = end - start log.warn "${label} took ${duration} ms" return result } } </code></pre> In other classes, you just reference the <code>timer</code> closure as such: <pre><code>@Mixin(TimingCategory) public class WhateverService { public String doSomeWork() { timer "Doing a lot of work", { 1000.times { doSomething() } someMethodWithAStringReturnValue() } } } </code></pre> That will give you log output of "WARN: Doing a lot of work took nn ms" and return the value of the inner closure as the return value of the <code>doSomeWork</code> method. For your taglib instance, just wrap the <code>out << ...</code> in the <pre><code>timer "Writing an emoticon", { // your code } </code></pre> code. If you don't care about passing through the internal return value, you could instead return the duration as the result of the closure invocation. Update: I might have misread -- you're asking how to wrap the taglib execution without modifying the taglib code at all? What about creating a custom taglib which accepts the body and passes it to the other taglibs for execution? I haven't tried this, but something like: <pre><code>class TimedTagLib { static namespace = "timer" def timedTag = { attrs, body -> timer "Executing the timed tag", { out << body() } } } </code></pre> And invoking it like <pre><code><timer:timedTag><g:emoticon whatever="something">Text</g:emoticon></timer:timedTag> </code></pre> Update 2: Ok, so I tried it. Works fine. My final code (I added a second timer closure which returns the duration): <pre><code>// TimedTagLib.groovy @Mixin(TimingCategory) class TimedTagLib { static namespace = "timer" def timedTag = { attrs, body -> def duration = returnTimer "Printing the timed tag", { out << body() } out << "Took ${duration} ms to print" } } </code></pre> And the view: <pre><code>// someView.gsp <timer:timedTag> <g:formatLocalDate date="${LocalDate.now()}" /> </timer:timedTag> </code></pre> The resulting HTML is: <pre><code>03/19/2013 Took 6 ms to print </code></pre> And it also wrote to the log. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAspect(-like) function for closures
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAndy
UserOwnerUserId
1. USAndy
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.