Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a menu with basic options & settings #102

Closed
jgaehring opened this issue Oct 9, 2018 · 6 comments
Closed

Provide a menu with basic options & settings #102

jgaehring opened this issue Oct 9, 2018 · 6 comments

Comments

@jgaehring
Copy link
Member

This would be very minimal for right now, primarily a way for the user to see the full extent of navigation options available to them, and to be able to log out. Being able to switch host/user profiles would be a nice addition as well, if multiple profiles could be saved, but that's probably a feature for further down the road.

I'm imagining this right now as a drawer/sidebar that expands from the left, but we could use a different approach or a combination of approaches. iOS apps definitely favor more use of "bars" for this kind of UI, but I think a nice compromise between web/native, iOS/Android would be ideal. Material Design can be overused, but it does provide a nice precedent for this kind of cross-platform design.

Eventually this could also encompass more robust settings and controls, as the app gains more features and navigation options. For right now, this would just be a place to distinguish the view layer portion of the app shell.

@jgaehring
Copy link
Member Author

Some progress:

image

The menu items and heading are all hard-coded for right now.

@mstenta @alexadamsmith , what do we want to do with this? As shown here, I'm toying with the idea of including links to the EditLog form with the type autopopulated and certain fields added/removed depending on the type (per some discussion Alex & I had re: the input form we're doing for Knuth Farm). Do we like the idea of including the user's name, farm name and url in the header? Is it worth doing a query after login to get that info? I'm scratching my head where to go next here... 🤔

@mstenta
Copy link
Member

mstenta commented Jan 29, 2019

Oh dang! That's nice!

As shown here, I'm toying with the idea of including links to the EditLog form with the type autopopulated and certain fields added/removed depending on the type

I love it!

I wonder if it would be possible to put them under a sub-menu "Add log"? Which you can expand/collapse? Not sure if that's easy or not.

Do we like the idea of including the user's name, farm name and url in the header?

Yes absolutely! This is great.

Is it worth doing a query after login to get that info?

Yea!

Question is... is there a way to get that info via the API?

You can get the username by querying /user.json?mail=[email address] - this will give you information about the user with that email address.

The site name isn't available over API, I don't think. In the future, it would be good to have some kind of generic API endpoint to get info about a farm, including its name. But in the meantime you could just pull it from the <title> tag of the homepage, perhaps?

Have to give thought to when that info gets updated internally, though. It is possible for someone to change their username and email address. And potentially the site name (although less likely).

@jgaehring
Copy link
Member Author

I wonder if it would be possible to put them under a sub-menu "Add log"? Which you can expand/collapse?

Yea, I was thinking that too. Not too hard, although I'd probably put it lower on my priorities (the actual links themselves might take some doing). For now, I also want something to fill up all that space! Then maybe once we have other forms as a part of the app, we could have a "Logs" or "Add Logs" category which expands/collapses.

The site name isn't available over API, I don't think. In the future, it would be good to have some kind of generic API endpoint to get info about a farm, including its name.

Darn. Yea that would be really nice.

But in the meantime you could just pull it from the <title> tag of the homepage, perhaps?

That sounds workable... tricky, but workable.

@mstenta
Copy link
Member

mstenta commented Jan 30, 2019

Agree on all.

@jgaehring
Copy link
Member Author

Closing this, since most of the functionality is complete and the last thing to work on now is #21 and some bug fixes.

@mstenta mstenta transferred this issue from farmOS-legacy/farmOS-client Feb 19, 2019
@mstenta
Copy link
Member

mstenta commented Feb 19, 2019

(Transferring all issues from old repository. See #92)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants