View Single Post
Old 08-03-2019, 04:22 PM   #11
Mavireck
Connoisseur
Mavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a TexanMavireck might easily be mistaken for a Texan
 
Posts: 63
Karma: 18290
Join Date: Jul 2016
Location: France
Device: Kobo H2O (broken), Kobo H2O Edition 2 v1 (stolen), Kobo Clara 2E
Quote:
Originally Posted by Lucas Malor View Post
Well, you don't need to cross-compile. You can simply create and use an ARM VM. I think the result it's also more reliable.

The problem of forks is the maintenance. What if the original maintainer continues to add features or bug fixing? You'll report all the changes every time in Py? And what if you abandon the project?
Well the problem of maintenance is a good point, although to be honest the code is simple enough for everyone to understand it and fix it. The script which sets up the input is only about 200 lines long...

Quote:
It's not as easy when using fbink, as it needs a cross-compiler for cgo to work. But, personally, I do think using go is easier than setting up python, unless you are using Windows (cross-compiling to Linux is a huge pain).
I am using Windows and that definitely makes the testing process very easy : one file to drag and drop through FTP, and 2 commands via ssh to start the scrit.
It would have required much more work to code in GO I guess.


Perhaps has my first post been too ambitious: at first, it is only about me publishing a WolframAlpha app for Kobo. I just added that I ported a few scripts to Python if anyone wanted to use them, without any guarantee.
I definitely think the main problem when starting to code on the Kobo is the lack of help and documentation.
I have no experience in writing such a code. I have learnt Python at my engineering classes to solve math problems mostly. I do not have a good Linux background, and I keep terrible memories of the time I tried to compile things in a console.
Therefore, the FBInk librairy was to me a dream coming true : an easy way to print things on a screen in a language I know. Then, it still lacked an easy way to deal with the touch input. I saw sherman's script in Go, ported it in Python so that I could use it easily.

Now, honestly, I find it very easy to build a Python app for Kobo : use the power of KFmon to start it, FBInk to print on the screen, and if you need touch, use my script.
The same could be done in Go, through sherman's work. I just don't know Go and don't want to learn it yet.

If you don't think posting this app here is of any use, tell an admin and delete it I am fine with it ! I only wanted to share the product of a few hours of work...

Last edited by Mavireck; 08-03-2019 at 04:25 PM.
Mavireck is offline   Reply With Quote