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

Implemented about section of help page #91

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Kunal-8789
Copy link
Contributor

Hi @razzeee
I have implemented About section of Help Page. Please Review.

Chorus 2 Elm Chorus
About Screenshot 2022-05-06 023425 Screenshot 2022-05-06 023509

I couldn't find a way to implement the strips in the Status report section. I tried making them code blocks but it wasn't looking quite right.


Status Report
---------
**Chorus Version** 19.x-2.4.8
Copy link
Member

@razzeee razzeee May 6, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All these shouldn't be hardcoded. Some are from chorus, some need to be fetched from kodi. Have a look at the original implementation as that should fetch these values too

Copy link
Contributor Author

@Kunal-8789 Kunal-8789 May 16, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @razzeee, I apologize for the delay in response. I was having my rigorous end-semester evaluations and therefore I was busy preparing for the same.
I found chorus version data was fetched from addon.xml but I didn't find any updated or good XML file decoder, so I converted the XML file to JSON and then fetched the data. I am facing 2 issues:-

  1. Http.get wants url. So I am pushing the file on a local server using the json-server package and then giving the absolute url in Http.get. I am trying to find a way to use the relative path in Http.get for which I have asked in Elm-Slack.
  2. I was not able to track down from where they are fetching KODI Version data in chorus2. If you could direct me toward the file or server.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can't convert the addon.xml, kodi needs it. having to maintain a second json would be fine, but inconvenient, so best would probably be a build step. at that point, you could also just build a small elm file with only the (version) constants, that should allow to sidestep the fetch problem.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @razzeee, Pls review the implementation.

@Kunal-8789 Kunal-8789 force-pushed the implementing_about_section_help_page branch from 5a459df to 824ffc4 Compare May 18, 2022 16:33

[Click here for more information]: https://github.com/xbmc/chorus2/blob/master/src/lang/en/license.md
[along with this program]: https://github.com/xbmc/chorus2/blob/master/LICENSE
[developers]: http://localhost:1234/help/developers
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't have links to localhost, they would need to be relative. So something like /help/developers would need to work here


kodiVersion : String
kodiVersion =
"19.3"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We would need to feed this automatically somehow

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

Successfully merging this pull request may close these issues.

3 participants