Issue 15 basic app browsing

[andrew-c-tran]

The Problem/Issue/Bug:

a number of app browse screens (card layout) were redesigned in collaboration with @rickmanelius .

How this PR Solves The Problem:

layout was changed, relevant actions moved to dropdown, and clickable links created as per wireframe in #15

Manual Testing Instructions:

run make test to build the application and run the tests

Related Issue Link(s):

#15

[rfay]

• I took this for a little spin, but didn't completely understand the point. I don't mind the new UI, but none of the features actually work do they? If this is intended to be just a visual change and not to be functional at all, please be more explicit about that in the PR. AFAICT none of the items in the dropdown do anything?
• There is no hover on the dropdown items- users will expect that.
• What does "browse" mean? I think that will have to be renamed.
• What would "edit" mean?

[andrew-c-tran]

Pull updated to remove non-functional items from dropdown. default color hover added to menu (to be color matched to ddev scheme upon completion of style guide). loading spinner to be addressed in style guide update.

[andrew-c-tran]

Rebased to include changes, tests pass, need another look at this to pull in

[rfay]

This doesn't work for me at all with ddev v0.10.0. Blank white screen, no sites shown even through 3 are running. Please, please add support for telling when something is going wrong. IMO that should be the first priority for ddev.

[andrew-c-tran]

The issue was corrected and I concur, error handling is long overdue at this point. Will shift gears after this PR and focus on #42

[rfay]

I guess I'm ok with this. It works now. Please always build and test your work when submitting a PR, or mark it as WIP.

I don't understand why every command in ddev-shell.js is not using js output at this point? Haven't we already stumbled on this twice or three times? Would it be appropriate to make that change here?

Is it ok that "Browse Local files" doesn't work?

[andrew-c-tran]

at this point everything is over to json. The reason this happened here is that this was a long running PR and it exposed a weakness in our automated testing.

When the PR was opened, the tests all passed. When the describe PR was merged in, we shifted to using all json output from the CLI and that merge was rebased into this PR, and the tests again passed. The view layer, however, was not expecting the change of the json format to include httpurl and httpsurl and failed out. This is something that our integration tests that actually confirm the contract between CLI and what the app is expecting is still valid that we discussed would handle, and I think i'll tackle said tests that exercise the CLI right after the error handling story that's in flight now.