[
https://issues.apache.org/jira/browse/HTRACE-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261390#comment-14261390
]
Colin Patrick McCabe commented on HTRACE-28:
--------------------------------------------
So, it *does* need to be in a source directory... that way the string will get
included into the binary.
It doesn't need to be in org.apache.htrace.resource, but that seemed like the
logical place to put it.
I guess we could have a second source directory where generated sources go. Go
does allow you to have more source directories by adding them to GOPATH. That
might be a little nicer. That would mean that I would need to generate
catalog.go as well, though, which is slightly annoying. I guess let's do this
in a follow-on, if it seems like a good idea later...
So, the rationale for creating a single file out of each resource is that it
would minimize recompilation when only one javascript to HTML file had changed.
bq. The index.html will be in the binary too?
Right. We can revisit this later, of course. But I think a lot of people will
appreciate not needing to have a big install directory with HTMLs.
bq. Those are fat tabs in your go code. That convention? Looks 'strange' after
our hadoop escapades.
Yeah, it is a little different, but standard for go. I'm using "go format"...
described here: http://blog.golang.org/go-fmt-your-code
That way the formatting is automatic.
bq. What are dfiles and sfiles (src and dst?)
Right.
> htraced: add web UI directory
> -----------------------------
>
> Key: HTRACE-28
> URL: https://issues.apache.org/jira/browse/HTRACE-28
> Project: HTrace
> Issue Type: Improvement
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HTRACE-28.001.patch
>
>
> Add the web UI directory for htraced. Bundle the index.html file and any
> other files in that directory into the htraced daemon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
