[
https://issues.apache.org/jira/browse/HTRACE-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262406#comment-14262406
]
Abraham Elmahrek commented on HTRACE-29:
----------------------------------------
Following up on [~cmccabe]'s thoughts specifically for the front end only.
For the first version of the UI, let's focus on the following use cases:
# Search within a time frame
# Search by description
# Search by duration
# See a detailed break down of the span
This means 2 different pages:
# Search/filter spans (start/end time, duration, and description)
# Span details page
Front-end libraries:
# JQuery - MIT licensed (https://jquery.org/license/)
# Backbone - MIT licensed
(https://github.com/jashkenas/backbone/blob/master/LICENSE)
# Underscore - MIT licensed (http://underscorejs.org/docs/underscore.html)
# Bootstrap - MIT licensed
(http://getbootstrap.com/getting-started/#license-faqs)
We can add libraries if needed (e.g. D3 for graphs in the future).
Let's do this iteratively:
# Skeleton - Basics for each page - basic structural layout only
# Functionality - Add functionality that seems useful for the the use cases
above
# Style - Make the UI actually nice to look at - Widgets, CSS, etc.
The skeleton is the most important part to separate out. Style and
functionality can be done in parallel to some degree.
Also, it's my understanding that the front end will be purely static with AJAX
calls to the web server.
[~cmccabe] does this strategy sound good for the front end? Also, is there any
more detail to add to V1?
> add javascript web UI for htraced
> ---------------------------------
>
> Key: HTRACE-29
> URL: https://issues.apache.org/jira/browse/HTRACE-29
> Project: HTrace
> Issue Type: Improvement
> Reporter: Colin Patrick McCabe
> Assignee: Abraham Elmahrek
>
> We should add a javascript web UI for htraced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
