Step by Step instructions for kindle development environment

[nasser]

Originally Posted by encol

... or maybe encol

Wow!;Great!!
Thanks a lot, encol!
Will try it out.

[nasser]

Working OK on PW1, KT3! Will try later on PW3.

I tried running it in two ways: through SSH from PC and directly through kterm.
There were some differences in the memory usage. When starting, Popeye declares the amount of memory it is using and this figure obviously varies with the actual memory available.
PW1: through SSH - 128 MB used, through kterm - 64 MB used
KT3: through both SSH and kterm - 256 MB used

Not clear why the difference exists for PW1.

[knc1]

Originally Posted by nasser

Working OK on PW1, KT3! Will try later on PW3.

I tried running it in two ways: through SSH from PC and directly through kterm.
There were some differences in the memory usage. When starting, Popeye declares the amount of memory it is using and this figure obviously varies with the actual memory available.
PW1: through SSH - 128 MB used, through kterm - 64 MB used
KT3: through both SSH and kterm - 256 MB used

Not clear why the difference exists for PW1.

PW-1 is running firmware 5.6.1.1 or earlier and has 1/2 the ram.
(for both reasons, memory management is different)

[nasser]

knc1, encol:
I will make a post on this forum(http://matplus.net/start.php?px=1483...t=forum&fid=it) informing the availability of a Kindle port of Popeye.
I would like to post a link to the executable in encol's post.

Is that OK? Are there any mobileread related formalities I should observe?

[nasser]

Works OK on PW3 too!
In PW1, the memory used seems to vary between 64MB and 128MB. Cache/Buffers/Garbage collection/memory leak?

[encol]

Originally Posted by nasser

knc1, encol:
I will make a post on this forum(http://matplus.net/start.php?px=1483...t=forum&fid=it) informing the availability of a Kindle port of Popeye.
I would like to post a link to the executable in encol's post.

Is that OK? Are there any mobileread related formalities I should observe?

I have no problem. I don't know about such mobileread formalities

[knc1]

Originally Posted by encol

I have no problem. I don't know about such mobileread formalities

Not specifically a site policy, but ....
Right now, Popeye is buried in a thread of another matter.

It is our forum practice to have a 'Release Thread' - titled appropriately (maybe: Popeye??).
Post the release as an attachment to the first post -
Have any limitations, installation, usage, nice-to-know things in that first (and sometimes second) post -
Make any off-site links to the thread, not the attachment.

Why:
1) Potential users do not have to search the thread to find the current release -
2) Attachment URLs change when you change the attachment, which means linking directly to an attachment here breaks.

The site software is old here and does not allow co-owners of a thread or post -
So flip a coin over who's name gets to start the thread.

Keep in mind that only the owner or a moderator can change an attachment.
And we don't have a moderator in this forum, the ones listed are either dead, dyeing, or gone.

[nasser]

Got it, knc1! Thank you for your guidelines.

Will prepare a nice preamble first and make a separate release thread, with references to the posts here, and the release as an attachment.

[knc1]

Originally Posted by nasser

Got it, knc1! Thank you for your guidelines.

Will prepare a nice preamble first and make a separate release thread, with references to the posts here, and the release as an attachment.

Ah,
"py" is a frequently used nickname for: Python
you might want to change its name.

[nasser]

Originally Posted by knc1

Ah,
"py" is a frequently used nickname for: Python
you might want to change its name.

Will think of a suitable alternative!

And a KUAL button too may be handy. Will add that too.

[knc1]

Originally Posted by nasser

Will think of a suitable alternative!

And a KUAL button too may be handy. Will add that too.

That: "Will solve a chess problem in a text file ...." feature -

Only KUAL does not accept user input fields ....
Two choices that I can think of :
Have a button that uses a fixed filename in visible USB storage (seen as /mnt/us from KUAL scripts); or
Use our 'extended' search bar command - that can take arguments.

or single purpose the
;log runme
;log custom
extensions of the search bar.

See a copy of the extension script in:
*/mkk/dispatch.sh

Hmm...
dispatch.sh does not, currently, pass arguments or handle anything other than the fixed filename 'RUNME.sh' but those things could be fixed.
(Its distribution home is part of the 'hotfix' package, and it was done in a hurry, late at night, so it is about as simple as a dispatcher can get).

But the only part of it in public use is the:
;log mrpi
so as long as that continues to work as the current users expect, that dispatcher is open to change.
Note: the copy */mkk/dispatch.sh is just that, a backup copy, not the one actually executed, that one is installed by the 'hotfix' bridge code into /var/local (or somewhere, I would have to read the hotfix install script).

Edit:
Hmm...
The searchbar extension is only for touch screen devices....
All touch screen devices have Lua and the Lua-Json library pre-installed....
It would not be too much trouble to make that dispatcher read a directory of extensions, similar to how KUAL reads */extensions/name/menu.json files.

That way we would not have to re-build the 'hotfix' package everytime someone wanted to extend the ;log command. The
;log mrpi
command extension could remain hardcoded in the new dispatcher so we do not have an unexpected behavior change.

Note: The extension of the ;log search bar command is one of those things that are bridged across Amazon updates.

[nasser]

Originally Posted by coplate

Starting with this image twobob linked:
https://www.mobileread.com/forums/sh...46&postcount=6

That image by twobob is no longer accessible. Dropbox recently changed their method for sharing files. Instead of a public folder, you now have to specify a shared file.

Maybe somebody who has this image can upload it again someplace and post a link here.

[encol]

Just follow method #1, you will create your own image

[coplate]

Hi @nasser, and everyone!

I updated post #4 to remove the twobob image instructions, and put in a whole new set of instructions.

These are based on the instructions inside the 5.8.1 PW3 source code downloaded from amazon.
You might look over it.

[nasser]

Thanks, Coplate!
There are several 5.8.1 sources on the Amazon page.
I assume this is the one you're referring to?
Kindle_src_5.8.1_2974910023.tar.gz (Kindle Paperwhite 7th Generation)