[Hawkular-dev] [GSoC] Hawkular Android Client: Weekly Report
Thomas Heute
theute at redhat.com
Mon Jun 1 04:39:13 EDT 2015
Great to see progress !
One thing that I haven't seen which can have a direct impact, is to
display the push messages:
http://www.hawkular.org/blog/2015/04/09/alert-notifiers-for-mobile-devices.html
Displaying the notification and opening a screen with detail of an alert
would be good.
Looking at:
https://cloud.githubusercontent.com/assets/200401/7881453/bc1d1866-060b-11e5-81bc-b6662d344952.png
I have few comments:
- I am not sure about the authentication flow, user should first
authenticate and then somewhere in the interface he should be able to
switch tenant (*if* he has several). I guess a good place would be the
top entry of the side menu.
- Environment can be ignored for now, it won't be in the admin console
for a while. In the end, I think you could end up with a single screen,
with server Host+Port, login name and Password.
- I don't think we need the metric table, graph are way more useful.
- Resources at the moment are URLs or Servers. You would need to list
them.
Thanks again !
Thomas
On 06/01/2015 07:39 AM, Artur Dryomov wrote:
> Hi everyone,
>
> This year I am working on the Hawkular Android application as part of
> the Google Summer of Code 2015 program.
>
> The last week I spent of familiarization with the project and its key
> terms. With the help of public Hawkular servers, the Docker image and
> snapshots I looked at the API and experimented a bit to understand how
> things actually work. As a result I’ve created a wiki page [1] with the
> brief overview of key Hawkular terms. In the process I’ve opened a very
> first Hawkular issue regarding Docker image [2]. As a result of better
> understanding what is what I’ve created a very rough mockup of the UI
> [3] which I’ve also sent to the design team. Hopefully after a review of
> functions and design I can proceed with the development itself. There is
> some source code already [4] but mostly it is just a basic project
> structure, it is almost useless to the end user at this point.
>
> I would like to start the development process this week. Of course it
> will require a better understanding of what actually should be done —
> I’ve tried to clarify this with creating the mockup. I think a basic
> authentication plus resources fetching is a good bet to work on even
> without clear requirements, so it can be started right away. Probably I
> should prepare a script to fill a Hawkular instance with some sample
> information — in Python or just plain cURL. If anyone has something like
> that — that will be a great help. I was advised to look at the test
> scenario [5] as a departure point but maybe someone of you have a
> similar thing locally.
>
> Regards,
> Artur.
>
> [1]: https://github.com/hawkular/android-client/wiki/Overview
> [2]: https://issues.jboss.org/browse/HAWKULAR-268
> [3]: https://github.com/hawkular/android-client/wiki/Design
> [4]: https://github.com/hawkular/android-client
> [5]:
> https://github.com/hawkular/hawkular/blob/65f2573987890b1ffd4460e3449fb02b348816ea/modules/end-to-end-test/src/test/groovy/org/hawkular/integration/test/Scenario1ITest.groovy
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
More information about the hawkular-dev
mailing list