[
https://issues.apache.org/jira/browse/HTRACE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565766#comment-14565766
]
Colin Patrick McCabe commented on HTRACE-174:
---------------------------------------------
{{htrace-htraced/src/go/src/org/apache/htrace/common/rest.go}}: update comment
to reflect the fact that the server info URL is now {{/server/info}}, not
{{/serverInfo}}.
{{span.js}}: we need to do more validation of what the server sends. Fields
that are left out must default to 0 or the empty array (it is legal for span
JSON to leave out fields.) "begin" and "end" should be coerced to numbers.
serverInfo: this represents the serverInfo structure sent back from htraced.
span_id.js: functions for parsing and dealing with span ID.
about view: add this view and populate it from /server/info.
span query view / predicate view: do not hard-code a "description" field
(searching by description is actually something we're not very fast at right
now). Allow times and durations to be entered as text. Add validation for all
fields. Add more predicate types.
search (general): we need to be using the last span returned from the previous
query as our continuation token. This code adds that. Add a method of getting
debug information about a search by holding down control while pressing
"search." Prepare for the "more" button by making it possible to add new
results to the end of the resultSet without clearing what's already there.
search view: Get rid of the grid view since ultimately what we want is a canvas
view with some fancier stuff. I am working on a canvas view as described on
HTRACE-143 that will be similar to the swimlane view.
queryResults: this represents what the server sends back. It gets appended to
searchResults when the query completes successfully.
{{custom.css}}: add a custom CSS file which gives us a nice blue menu bar. We
can add more stuff here later.
libraries: always use the un-minimized form of all libraries. There is no
point to minimizing libraries at this stage... it just makes debugging harder.
If it becomes a performance issue we can change it later, but it seems unlikely
to ever be an issue in HTrace's target use-case. Avoid using Marionette since
we don't (yet?) need it. Best to keep things simple right now.
> Refactor GUI to fix pagination, form validation, about screen
> -------------------------------------------------------------
>
> Key: HTRACE-174
> URL: https://issues.apache.org/jira/browse/HTRACE-174
> Project: HTrace
> Issue Type: Bug
> Affects Versions: 3.1.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HTRACE-174.001.patch
>
>
> Refactor the GUI to fix pagination, form validation, and add an about screen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
