-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Better UI for ZIM content: minimal first step #65
Conversation
Yes about testing it with kiwix-JS, already done by myself of course, plus it is the same base as freecodecamp which was tested AFAIK, but anyway, I will send a file for test once this is ready to be merged Open questions:
|
There should be flags for it as for the rest. You need to identify the underlying tool that emits the issue though
Are there regressions? If no, it should be merged to main IMO |
I found them indeed ...
There are limitations as mentioned in the first comment, which could be considered like a regression. Somehow my question could be rephrased:
I would answer yes to both points, but need your PoV as well. |
I see no reason to.
Kolibri channel is mostly files. Those are the content. I think placing them in |
If it's ready you can push it now. Haven't started.
kind of the same question. Please (and that should be standard for UI revamp liek this) share one screenshot so that @kelson42 can weight in. I don't understand what ”topics are not searchable anymore” mean exactly. The missing breadcrumbs would be terrible with the former UI but maybe that's OK with the new one… |
This is the layout which has been used for freecodecamp (but maybe this is a bad decision). |
And I find it much easier to understand as a dev, that we have a |
I just fixed the eslint issue + renamed |
That's exactly why I was surprised to see it here. |
As long as it's thought about and not just a copy of a fringe scraper I'm OK with it. |
Sure |
I'd be happy to test a ZIM. I need to test in two modes: ServiceWorker local in a Chromium extension, where inline JS is blocked (and eval, and all eval-like expressions), and ServiceWorker remote, which is the more permissive mode based on (essentially) the remote, offline-first PWA stored at https://browser-extension.kiwix.org. Freecodecamp works only in the remote mode, because it relies on evaluating strings of JS. Since this is essential to how it works, this is fine. For Kolibri, I imagine it will be expected to work in the former (local-only) mode? |
I forgot about the Freecodecamp usage of eval and its impact on local mode. I expect Kolibri to work in both modes, and especially in the former (local-only) mode. |
I've just uploaded test ZIMs to dev library (please forgive the filename, I suspect they are not 100% compatible with our naming convention).
|
Thanks! I've just tested the "small test" version in Chromium browser extension. The Kolibri UI all seems to work fine. I could access the menus for all resources I tested in the ServiceWorker local mode. (Also tested in PWA mode, of course, no issues). However, some of the resources contained in the ZIM have eval and inline JS that is blocked in ServiceWorker local mode -- e.g. PheT and the Quizzes, but which works fine in the PWA mode. I realize Kolibri is a container format, and you don't control what is put in the container. As an aside, I'm not sure we can win the battle against inline JS and eval given that ZIM archives are increasingly becoming containers for content from a very wide range of web resources over which we don't have full control. But thanks for making the UI conformant! 👍 |
Thank you for the test! |
As discussed Friday, the search for a topic must be fixed and this cannot be merged to |
Fix #53
Fix #31
Changes:
scraper
subfolderzimui
subfolder ; it is rendered with Vite to produce a static websitepydantic
slugify
lib_1
,_2
, ... suffix/
/thumbnails
/topics
/static
(some content is still placed at the root to not break some stuff which was found hard to fix for now, will be tackled in specific issues for each content type)is_front
property has been adjusted when adding the item to the ZIM--zimui-dist
to specify the folder where zimui has been built (by Vite)Known side effects to be discussed: