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

Wishlist for version 2.7 #541

Closed
mossroy opened this issue Jul 21, 2019 · 7 comments
Closed

Wishlist for version 2.7 #541

mossroy opened this issue Jul 21, 2019 · 7 comments
Labels
Milestone

Comments

@mossroy
Copy link
Contributor

mossroy commented Jul 21, 2019

This is to discuss what we would like (and could) do for next version.

Here is my wishlist :

  • @Jaifroid , if you're still interested in doing it, it would be great to improve the UI. By backporting some of the work you did for kiwix-js-windows, and other UI improvements we started to discuss. Even if we are no UI/UX specialists, I believe that our UI is simple enough to fit into already-existing best-practices that we might follow
  • We really need to go forward with libzim/kiwix-lib + emscripten. @kelson42 : we need some help on that. In particular on Javascript calls to wasm version of libzim/kiwix-lib only work the first time #509 (I gave all the steps to reproduce : if something is missing, please tell me)
  • Ideally, I would put on hold the performance optimizations (cache etc) until we see how it behaves with emscripten. It should hopefully be much faster, and the libzim already includes some memory cache
@mossroy mossroy added this to the v2.7 milestone Jul 21, 2019
@Jaifroid
Copy link
Member

@Jaifroid , if you're still interested in doing it, it would be great to improve the UI. By backporting some of the work you did for kiwix-js-windows, and other UI improvements we started to discuss. Even if we are no UI/UX specialists, I believe that our UI is simple enough to fit into already-existing best-practices that we might follow

Yes, I'm doing this in stages in #523, starting with #526 / #527. I think #527 is ready for review (I've just rebased it). Once we have Bootstrap 4 in place on our existing design, I can implement a test version of elements of the Kiwix JS Windows interface.

@kelson42
Copy link
Collaborator

I went through the older tickets and a few ones are of interested IMO:

@Popolechien
Copy link
Member

I think a simple UI first step would be to get rid of most of the text on the landing page (or move it to a help subpage), leaving only a single big "open file" like there is on macOS (+also "Access library" pointing to download.kiwix.org/zim would not hurt).
I'll have a look into #523 if I can.

@kelson42
Copy link
Collaborator

kelson42 commented Sep 3, 2019

Should we keep that ticket open?

@Popolechien
Copy link
Member

Sure why not.

@kelson42
Copy link
Collaborator

kelson42 commented Oct 4, 2019

Because this ticket seems useless to me. It should be decided what comes in the milestone and then closed.

@Jaifroid
Copy link
Member

Jaifroid commented Oct 4, 2019

We did actually merge a performance optimization over the summer, which was to add native Service Worker caching, as that was sorely missing and holding up development of the more modern Service Worker code. That is done.

What is an immediate priority is for me to work on UI, as we've agreed I should port the toolbars used in Kiwix JS Windows (approximately, there will be differences due to the different feature set) to Kiwix JS. This is going to take a bit of time because we are both extremely busy at the moment with RL (Real Life)... But I think we clearly know what we need to do, and unless anyone else thinks other issues should be opened as a result of this Wishlist, it can be closed.

@mossroy mossroy closed this as completed Oct 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants