Great App. Thanks. It would be nice to choose the wiki e.g. .de. com. .es. .. and as well to choose from different photos in case there are multiple in the page. Thanks and Greetings

https://github.com/babydots/babybook/commit/a1580206ad38c25db2bd06d4bc2fc3673218e5e8 selfbuilt

FATAL EXCEPTION: main
Process: com.serwylo.babybook, PID: 32702
io.ktor.network.sockets.ConnectTimeoutException: Connect timeout has expired [url=https://upload.wikimedia.org/wikipedia/commons/xxxx/xxxx/xxxxx.jpg, connect_timeout=unknown ms]
	at io.ktor.client.features.HttpTimeoutKt.ConnectTimeoutException(HttpTimeout.kt:183)
	at io.ktor.client.features.HttpTimeoutKt.ConnectTimeoutException$default(HttpTimeout.kt:180)
	at io.ktor.client.engine.cio.Endpoint.getTimeoutException(Endpoint.kt:240)
	at io.ktor.client.engine.cio.Endpoint.connect(Endpoint.kt:232)
	at io.ktor.client.engine.cio.Endpoint.access$connect(Endpoint.kt:28)
	at io.ktor.client.engine.cio.Endpoint$connect$1.invokeSuspend(Unknown Source:15)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33)
	at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)

Hi,

This small PR adds a button to get your app on F-Droid. You can later add a button for Google Play the same way : [<img src="https://play.google.com/intl/en_us/badges/images/generic/en-play-badge.png" alt="Get it on Google Play" height="80">]()

Configurable via the settings menu.

Also added paper background image for when images are loading or when there is not enough books/pages to fill the screen.

If I'm creating a book about the solar system, I'll probably start by Adding "Mercury", and then "Venus". After adding these two, there should be some links between these pages which indicate that there are other related pages ("Earth", "Mars", etc). We should investigate whether it is practical to offer suggestions to users, so that after typing "Mercury" and "Venus", they are then shown a list of suggested pages that includes other plannets.

It should then also work for vegetables, mammals, insects, animals, cities, countries, plants, etc, etc, etc.

My first thought is this could be done viacategory overlap. Here is an example using the solar system book:

• User adds Mercury, which is in categories:
  • Solar System
  • Mercury (planet)
  • Planets of the Solar System
  • Terrestrial planets
  • Astronomical objects known since antiquity
• Don't try to offer any suggestions yet, because the user could be going in any direction.
• User adds Venus, which is in categories:
  • Solar System
  • Venus
  • Astronomical objects known since antiquity
  • Planets of the Solar System
  • Terrestrial planets

Based on this, we could do the following:

• Count how many times each category is used by your books pages:
  • (2) Solar System
  • (2) Planets of the Solar System
  • (2) Terrestrial planets
  • (2) Astronomical objects known since antiquity
• (1) Mercury (planet)
• (1) Venus
• Offer recommendations from one or more of the categories at the top of the list.
• Perhaps go one level deeper - finding which pages within those top four categories are listed, and seeing how many times they appear in each page. For example, Astronomical objects known since antiquity includes the Large Magellanic Cloud, but that is not going to be present in any of the other categories, so it should never be offered. However, "Jupiter" is going to be in all of the top four matching categories.
• These same heuristics could also be used to eliminate that category completely.

There are many good tools for image processing, to produce cartoon style graphics from a source image (e.g. https://towardsdatascience.com/using-opencv-to-catoonize-an-image-1211473941b6). By doing so, we not only have the option of making our books adopt unique styles (e.g. hand drawn, colourful, etc), but also unify the style of all images. Right now images are all from different authors, cameras, styles and the resulting books can reflect this randomness.

Images currently download from Wikimedia Commons as a 1024px wide version. This was to ensure that the initial books provided with the app did not add too much to the filesize of the app itself.

However, for custom books, we want people to have the best experience possible, and so they should be able to get access to higher quality images. This should not make the editing process any slower though, so we should initially just download a low res thumbnail while first adding the page, and then in the background we should fetch a higher quality version of the image to save to disk.

Right now, this app is hard coded to English and so can't be added to https://hosted.weblate.org/ or other such services for community translation contributions.

Now that the UI is settling down, all strings should be externalised into strings.xml so that translations can be contributed by the community.

All generated books need to include attribution for text.

Simple Wikipedia pages all include this text in the footer of each page:

Text is available under the Creative Commons Attribution/Share-Alike License and the GFDL; additional terms may apply. See Terms of Use for details.

Images all come from Wikimedia Commons, and each is licensed individually. However most are CC BY-SA 3.0. I believe the metadata can be obtained via an API.

All attribution should:

• Recorded in the corresponding WikiImage database table (for images)
• Recorded in the corresponding WikiPage database table (for text)
• Shown in the generated PDF (perhaps in a final page which summarises all attribution for the entire book).
• Added as a menu item when viewing the book.