[
https://issues.apache.org/jira/browse/BROOKLYN-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393594#comment-16393594
]
Geoff Macartney commented on BROOKLYN-575:
------------------------------------------
Something to think about for this proposal - we should avoid thinking that the
idea is to reproduce the current interface using more modern technologies. This
is an opportunity to rethink the structure of the user interface, irrespective
of the technology. The current interface presents a fairly data-structure
oriented view of applications, drilling down through nested entity structures
and presenting tables of properties and action records. This might be an
opportunity to introduce a new structure using modern ideas of UI design,
thinking about how to highlight what's important to users and present that in a
human-oriented way. For example when there are errors in activities it should
not require a long series of clicks to navigate to them, rather the errors
should be visible without any clicks or with just one. Sensors are probably the
most important aspects of entities so good presentation of sensors is
important. I'm no sort of UI expert but perhaps there are some out there who
could help design the new UI.
> GSOC: New Brooklyn UI
> ---------------------
>
> Key: BROOKLYN-575
> URL: https://issues.apache.org/jira/browse/BROOKLYN-575
> Project: Brooklyn
> Issue Type: Improvement
> Affects Versions: 1.0.0
> Reporter: Thomas Bouron
> Priority: Major
> Labels: cloud, gsoc2018, javascript, rest, ui
>
> This is an idea for [Google Summer of
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> h1. Background
> Apache Brooklyn is a tool for running stuff in "the cloud", such as Amazon
> EC2. In more detail, it's a tool for describing applications and their
> components, deploying these applications to the cloud, and managing the
> ongoing health and responsiveness. Brooklyn does this using blueprints -
> human readable documents which describe in detail an application component,
> or a whole application. Blueprints are stored in a catalog, essentially a
> built-in database of components and applications. An application blueprint
> can call on component blueprints from the catalog, therefore allowing complex
> applications to be built from simple pieces.
> h1. Issue
> The currently Brooklyn UI is getting old and lagging behind the newest
> changes made into the REST API. It would need an overhaul to refresh it and
> more importantly, use the newest technologies out there in terms of front-end
> dev.
> h1. Proposal
> Rewrite the Brooklyn UI and take advantage of the novelties introduced
> recently on the REST API. The goal is to improve the overall user experience,
> especially when:
> # deploying an application
> # viewing and managing deployed applications
> # viewing and managing the catalog
> At least, feature parity with the current UI should be achieved. The only
> requirement is to use the Brooklyn colour palette.
> This project for green-field development of a new web based UI will involve:
> * selecting a modern Javascript web and CSS framework
> * working with REST APIs
> * a nice UI/UX
> * writing unit tests
> _Note: The server side API is written in Java but an understanding of Java
> *is NOT required*._
> Prospective GSOC mentor: [email protected]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
