atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Bergenholtz (JIRA)" <>
Subject [jira] [Commented] (ATLAS-582) Move Atlas UI to use backboneJS
Date Wed, 06 Apr 2016 18:18:25 GMT


Erik Bergenholtz commented on ATLAS-582:

Patch Comments:

* When clicking on a Type, the default query should be a DSL query and not a full text query
* When clicking on a Type, the search field is populated with a preceding space, same when
clicking on a Tag (you can see this in the query string of the request as well). The preceding
space should be removed.
* The icon in front of the Types is the same as a Tag and should be differentiated to avoid
confusion. Can you come up with an appropriate/generic icon for Type?
* The results table appears to be variable width up to a point, but when the search results
are wide, the table does not re-size beyond a certain point regardless of the width of the
browser window (
* I see in the JS Console that I get quite a few exceptions and 404s. These should be reviewed.
* The detail page (for any type such as LoadProcess, DB, Column etc.) all have a Schema Tab.
I don't think this makes sense since there is no schema for these types. Schema only applied
to Table & View AFAIK. I think that these the types that do not have a schema should be
using a generic type page that does not include a schema.
* The lineage graph is not centered (
- is it possible to center on the page?
** Since the behavior of the graph has changed, is it possible to provide a hint (via hover
over) that left click will expand/contract the graph and that double clicking will follow
the link (this is not necessary for this patch however)

> Move Atlas UI to use backboneJS
> -------------------------------
>                 Key: ATLAS-582
>                 URL:
>             Project: Atlas
>          Issue Type: Improvement
>    Affects Versions: 0.7-incubating
>            Reporter: Erik Bergenholtz
>            Assignee: Keval Bhatt
>             Fix For: 0.7-incubating
>         Attachments: ATLAS-582.5.patch, ATLAS-582.6.patch, ATLAS-582.patch
> Desire is to move Atlas UI implementation to backboneJS for greater flexibility in the
implementation of the UI. Specifically, backbone provides a simple way to represent models
and collections as UI components. All components are also "skinnable" with CSS, and will render
consistently across browsers.

This message was sent by Atlassian JIRA

View raw message