[UI Improvements] collect ideas from the gitnex community #319

Closed
opened 2020-06-04 02:02:03 +00:00 by 6543 · 13 comments
Member

as title - each comment an idear

Once the idea is confirmed, new issue will be created and task should be updated to done here with link to issue.

  • Add FAB button for add comment on issue #336
  • Add RTE to issue desc etc
  • New screen for fav repos after implementation of db
as title - each comment an idear Once the idea is confirmed, new issue will be created and task should be updated to done here with link to issue. - [x] Add FAB button for add comment on issue #336 - [ ] Add RTE to issue desc etc - [ ] New screen for fav repos after implementation of db
6543 added the
💭 Brainstorming
label 2020-06-04 02:02:03 +00:00
Member

Add option in settings to add repositories of "Organisations" to "My repositories"

Add option in settings to add repositories of "Organisations" to "My repositories"
Member

Specify what you're about to search in the search bar as hint (e.g. 'Search repositories', 'Search issues', etc.).

Specify what you're about to search in the search bar as hint (e.g. 'Search repositories', 'Search issues', etc.).
Member

Built-in text editor.

Built-in text editor.
Member

Making issue tagslabels a little bit smaller and proportional.

Making issue ~~tags~~labels a little bit smaller and proportional.
Owner

Floating Action Button (with create-icon) rather than “Add comment” in menu.

Nice idea, you can send a PR. Check how it is done(it's diff than default FAB) in repos etc.

Add option in settings to add repositories of “Organisations” to “My repositories”

Starred repos works that way I guess?
My repositories are termed as repositories under your namespace. We can introduce something like Favourates for app only. But I am afraid it will create alot of confusions for users. My repos, starred repos, favourates.

Specify what you’re about to search in the search bar as hint (e.g. ‘Search repositories’, ‘Search issues’, etc.).

This is changed in commits PR(if I am not mistaken). It's generic search icon now. Every screen has its own search filter, so adding extra text is redunt to me.

Built-in text editor.

To edit/add new items something like Rich text editor?

Making issue tags a little bit smaller and proportional.

By tags you mean labels, which you already send a PR.

Thanks for the valuable inputs. I appreciate it.

> Floating Action Button (with create-icon) rather than “Add comment” in menu. Nice idea, you can send a PR. Check how it is done(it's diff than default FAB) in repos etc. > Add option in settings to add repositories of “Organisations” to “My repositories” Starred repos works that way I guess? My repositories are termed as repositories under your namespace. We can introduce something like `Favourates` for app only. But I am afraid it will create alot of confusions for users. My repos, starred repos, favourates. > Specify what you’re about to search in the search bar as hint (e.g. ‘Search repositories’, ‘Search issues’, etc.). This is changed in commits PR(if I am not mistaken). It's generic search icon now. Every screen has its own search filter, so adding extra text is redunt to me. > Built-in text editor. To edit/add new items something like Rich text editor? > Making issue tags a little bit smaller and proportional. By tags you mean labels, which you already send a PR. Thanks for the valuable inputs. I appreciate it.
Member

Nice idea, you can send a PR. Check how it is done(it’s diff than default FAB) in repos etc.

I will have a look into that, but as before, i can't promise anything.

This is changed in commits PR(if I am not mistaken). It’s generic search icon now. Every screen has its own search filter, so adding extra text is redunt to me.

I found it very confusing to search using the search bar, because it does not clearly state (as a hint, placeholder) what you're about to search. It just says "Search...". I think it would be more clear to use "Search pull requests..." on the pull request screen and so on ("Search open issues...", "Search milestones...").

To edit/add new items something like Rich text editor?

Exactly.

Starred repos works that way I guess? [...]

Imagine you have more than multiple repos in one oranization. It would be a hassle to add each repo one by one to "starred repositories".

> Nice idea, you can send a PR. Check how it is done(it’s diff than default FAB) in repos etc. I will have a look into that, but as before, i can't promise anything. > This is changed in commits PR(if I am not mistaken). It’s generic search icon now. Every screen has its own search filter, so adding extra text is redunt to me. I found it very confusing to search using the search bar, because it does not clearly state (as a hint, placeholder) what you're about to search. It just says "Search...". I think it would be more clear to use "Search pull requests..." on the pull request screen and so on ("Search open issues...", "Search milestones..."). > To edit/add new items something like Rich text editor? Exactly. > Starred repos works that way I guess? [...] Imagine you have more than multiple repos in one oranization. It would be a hassle to add each repo one by one to "starred repositories".
Owner

I will have a look into that, but as before, i can’t promise anything.

No rush

Imagine you have more than multiple repos in one oranization. It would be a hassle to add each repo one by one to “starred repositories”.

This could be discussed more once local db implemented. Because this is going to be app only feature. Also need a better name for this.

I will add the valid points to the main post for future implementation.

> I will have a look into that, but as before, i can’t promise anything. No rush > Imagine you have more than multiple repos in one oranization. It would be a hassle to add each repo one by one to “starred repositories”. This could be discussed more once local db implemented. Because this is going to be app only feature. Also need a better name for this. I will add the valid points to the main post for future implementation.
Member

Add link to commits on master branch to the first page "Details" of any repo.

Add link to commits on master branch to the first page "Details" of any repo.
Member

Display number of commits (master) on "Default"-page but also on each branch under "Branches"

Display number of commits (master) on "Default"-page but also on each branch under "Branches"
Member

Add "commits since this release".

Add "commits since this release".
Author
Member

Created By: @meena

I'd also like to see a switch for different Branches in the files Browser — and whereever else that applies.

There's currently no way to read code anywhere other than the main branch.

Created By: @meena I'd also like to see a switch for different Branches in the files Browser — and whereever else that applies. There's currently no way to read code anywhere other than the main branch.

it should be easier to visually distinguish issues from PRs (even without #332)

it should be easier to visually distinguish issues from PRs (even without #332)

Title: Render READMEs while browsing files

Idea: When browsing files, if a file named README.md is present at any level of a repo, render the markdown of the readme below the files.

Today, Gitnex renders only the top level README, in the Overview section. Browsing files section, we are two taps away from the most human readable version of the the readme (tap to open file, tap to render as markdown).

See Github on web. Having a readme at each level makes repositories more navigable, especially if complicated, contain many components that deserve a README.

Title: Render READMEs while browsing files Idea: When browsing files, if a file named `README.md` is present at any level of a repo, render the markdown of the readme below the files. Today, Gitnex renders only the top level README, in the Overview section. Browsing files section, we are two taps away from the most human readable version of the the readme (tap to open file, tap to render as markdown). See Github on web. Having a readme at each level makes repositories more navigable, especially if complicated, contain many components that deserve a README.
Sign in to join this conversation.
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitnex/GitNex#319
No description provided.