Roadmap about diohub HOT 51 CLOSED

Issue template for Issues and Feature Request.

from diohub.

#56 Some files don't have Syntax Highlighting

from diohub.

#56 Some files don't have Syntax Highlighting

I think instead of making this into the roadmap I'll open a different issue later on/have a section in the repo wiki to keep track of the supported/upcoming languages

from diohub.

from diohub.

Issue template for Issues and Feature Request.

In addition to multiple accounts, supporting accounts from different git providers such as gitlab, gitea, gogs would be really cool. The app is much nicer to use than the others that I have used with gitea, and it would be nice to have one application to do it all.

Can be hard to implement since all git providers have different APIs and some git providers doesn't have API at all i guess…

Yep, plus they likely send data in different formats so it'll be a lot of work as that means models that are not designed to a specific API and having to fill data in them manually for every type of Git provider.

We can use modular approach for every git provider though apple doesn't like that. Also, OP will need to create another repo for that(since doing it here is messy)

from diohub.

still busy irl?

Not as much anymore, restarted work on the project again, finally😅

also minor suggestion make repo clickable ob home

What do you mean? They're clickable already, aren't they? You're referring to the cards in the feed right?🤔

i am talking about this

from diohub.

Can you elaborate on 4 though?

#93 like u upload a screenshot somewhere in files & when u open commits allow to view those pics as well

from diohub.

oh and 1 more fix please

arrange folders first then single files

from diohub.

one more suggestion:
when viewing commits of a branch by default show commit title and an arrow if user wants to he can view whole thing.

Y this is needed:
in cases of weblate translation there is a whole page of description like signed by bla bla etc which looks weird. Here is the ss

maybe hide coauthor or something like this & if click on arrow it shows?

from diohub.

hey!
thanks for this nice client!
I have a two minor suggestions:

• ability to scroll down in comment list on the issue
• hook up android 12+ monet theming support

from diohub.

Suggestion: sorting the files in the "Code tab of a repo the same way the official github website does. I.e. directories at the top and loose files below. Instead of sorting them all as one group, sort them as files and directories separately

from diohub.

What happened with this project?

I’m still chipping away in #99 and #121

All the upcoming changes that are either done or almost done are mentioned in the changelog in the branch getting merged.

Honestly I’m getting close to a new release but haven’t had time to get the last few portions done currently.

from diohub.

#42

from diohub.

#42

Added to the roadmap, thanks!

from diohub.

Github Action to automate the release of the apks.

I could help with this one. Can you give me how does this become an APK?

from diohub.

Yes, I do plan on setting it up, but it's a bit cumbersome because of the way I'll have to set up the keystore to sign the APKs as I cannot add that directly to the repository (very sensitive info).

Do you have anything specific in mind?

from diohub.

I think you can create a branch(that's separate) that only you and the bot can access (or you can pass parameters(like an env file) that's stored separately). Or a private repo.

from diohub.

Protected branches just prevent collaborators from pushing to them, they're still visible.

I'll look into potential ways to set it up after my exams are over. Thank you for looking into it!

from diohub.

In addition to multiple accounts, supporting accounts from different git providers such as gitlab, gitea, gogs would be really cool. The app is much nicer to use than the others that I have used with gitea, and it would be nice to have one application to do it all.

from diohub.

In addition to multiple accounts, supporting accounts from different git providers such as gitlab, gitea, gogs would be really cool. The app is much nicer to use than the others that I have used with gitea, and it would be nice to have one application to do it all.

Can be hard to implement since all git providers have different APIs and some git providers doesn't have API at all i guess…

from diohub.

Material UI v3

from diohub.

Issue template for Issues and Feature Request.

In addition to multiple accounts, supporting accounts from different git providers such as gitlab, gitea, gogs would be really cool. The app is much nicer to use than the others that I have used with gitea, and it would be nice to have one application to do it all.

Can be hard to implement since all git providers have different APIs and some git providers doesn't have API at all i guess…

Yep, plus they likely send data in different formats so it'll be a lot of work as that means models that are not designed to a specific API and having to fill data in them manually for every type of Git provider.

from diohub.

Material UI v3

Should be straightforward to implement because of the way the app handles color schemes due to the dynamic color palettes already.

I'll do this theme changes when I add the light theme as well. I'll add it to the roadmap, thanks.

from diohub.

Will be added the ability to go to the sub module repository?

from diohub.

Will be added the ability to go to the sub module repository?

Yes, can you open a new issue for it?

from diohub.

Yes, I do plan on setting it up, but it's a bit cumbersome because of the way I'll have to set up the keystore to sign the APKs as I cannot add that directly to the repository (very sensitive info).

Do you have anything specific in mind?

Cant you use the build in secrets function ? Or do you have to use keyfiles?

If you have to use them as file, maybe store them encrypted publicly and put the pasword to decrypt them in a GitHub secret

https://docs.github.com/en/actions/security-guides/encrypted-secrets

from diohub.

If you have to use them as file, maybe store them encrypted publicly and put the pasword to decrypt them in a GitHub secret.

That's the approach I'm thinking of currently. I'll set it up when the next update is about to be done.

from diohub.

Yes, I do plan on setting it up, but it's a bit cumbersome because of the way I'll have to set up the keystore to sign the APKs as I cannot add that directly to the repository (very sensitive info).

Do you have anything specific in mind?

Just seen this gist

Hope this helps.

from diohub.

In app Project Boards(the one in beta)
GitHub actions setup
Built-in editor (with buffer)

from diohub.

Can be hard to implement since all git providers have different APIs and some git providers doesn't have API at all i guess…

Yep, plus they likely send data in different formats so it'll be a lot of work as that means models that are not designed to a specific API and having to fill data in them manually for every type of Git provider.

We can use modular approach for every git provider though apple doesn't like that. Also, OP will need to create another repo for that(since doing it here is messy)

Yeah, plus there are a lot of features for GitHub itself in the backlog on the roadmap (ie project boards) alongwith an App Store (currently working on the iOS build) and FDroid release, so I'm not sure if and when I could get around to something like this which likely needs to be a separate project based on this one. But hey, never say never!

from diohub.

In app Project Boards(the one in beta)

GitHub actions setup

Built-in editor (with buffer)

Thank you. I also need to work on the wiki you suggested, I should get around to it before the next release.

from diohub.

When adding strikethrough in roadmap to know which features already got implemented & which left for next release

from diohub.

When adding strikethrough in roadmap to know which features already got implemented & which left for next release

I need to rearrange it first, some stuff got shifted down, some got shifted up in the last few months. Will get around to it when I get some free time.

from diohub.

When adding strikethrough in roadmap to know which features already got implemented & which left for next release

I need to rearrange it first, some stuff got shifted down, some got shifted up in the last few months. Will get around to it when I get some free time.

still busy irl?

from diohub.

still busy irl?

Not as much anymore, restarted work on the project again, finally😅

from diohub.

still busy irl?

Not as much anymore, restarted work on the project again, finally😅

yayyyyy

btw instead of releasing app with many new features why not release one with completed features & fixes

from diohub.

still busy irl?

Not as much anymore, restarted work on the project again, finally😅

also minor suggestion make repo clickable ob home

from diohub.

yayyyyy

btw instead of releasing app with many new features why not release one with completed features & fixes

That's the plan from here on out. I made started work on too much features together so I need to finish them up first, but after that it should be small updates in shorter intervals.

from diohub.

still busy irl?

Not as much anymore, restarted work on the project again, finally😅

also minor suggestion make repo clickable ob home

What do you mean? They're clickable already, aren't they? You're referring to the cards in the feed right?🤔

from diohub.

yayyyyy

btw instead of releasing app with many new features why not release one with completed features & fixes

That's the plan from here on out. I made started work on too much features together so I need to finish them up first, but after that it should be small updates in shorter intervals.

that was y i am asking release one with bugfixes & dynamic tabs after finishing touches

from diohub.

still busy irl?

Not as much anymore, restarted work on the project again, finally😅

also minor suggestion make repo clickable ob home

What do you mean? They're clickable already, aren't they? You're referring to the cards in the feed right?🤔

btw currently u r working on what?

can you proritize these

anchor links views
release sections
edit comments
view pics
comments on single commits
multi account

from diohub.

btw currently u r working on what?

can you proritize these

anchor links views
release sections
edit comments
view pics
comments on single commits
multi account

1 is done, 3 is ongoing, and I plan to work on 2 next (although probably in the next release to not delay the current one further)

Other than those, working on a redesign to issues, pulls and repos screen.

Can you elaborate on 4 though?

As for 5 and 6, they're a bit complicated, so they would take a while.

from diohub.

Can you elaborate on 4 though?

#93 like u upload a screenshot somewhere in files & when u open commits allow to view those pics as well

Since this will look bad on some point, I suggest making it a gallery that can be enlarged when clicked.

from diohub.

Since this will look bad on some point, I suggest making it a gallery that can be enlarged when clicked.

pics shouldbe be hidden by default only viewable when u open that specific file in comits section or changed files list

from diohub.

Also there's this weird line every 3 notifications that looks quite strange

from diohub.

Also there's this weird line every 3 notifications that looks quite strange

That might be notifications for commit comments. The app hadn't implemented the navigation logic for them yet hence they skip them causing the dividers around it to merge. Hopefully should be implemented soon, it's a bit hard to figure out the possible payloads for it as the GitHub API docs are limited with the info they give.

from diohub.

*

from diohub.

What happened with this project?

from diohub.

What happened with this project?

I’m still chipping away in #99 and #121

All the upcoming changes that are either done or almost done are mentioned in the changelog in the branch getting merged.

Honestly I’m getting close to a new release but haven’t had time to get the last few portions done currently.

Oh awesome, I just looked at the commit history of the default branch, and thought it was dead.

from diohub.

#71

from diohub.

Considering this roadmap is WIDLY outdated, and hard to keep up to date, I'll add an updated roadmap here later: https://github.com/NamanShergill/diohub/blob/development/roadmap.md

Dev release for the next update is out: https://github.com/NamanShergill/diohub/releases/tag/v1.dev

from diohub.