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

Added additional header info printing #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

KOLANICH
Copy link

@KOLANICH KOLANICH commented Nov 9, 2021

No description provided.

@Juul
Copy link
Member

Juul commented Nov 10, 2021

Hi. Apologies for not responding to your earlier pull requests. I am on vacation at the moment. I'll do my best to remember to look through all of your contributions when I get home. I am curious if you are working on some specific project where you need some features that don't exist yet or why you need rust and python versions?

@KOLANICH
Copy link
Author

I am curious if you are working on some specific project where you need some features that don't exist yet or why you need rust and python versions?

I just learn currently. My reading needs currently are satisfied my AMOLED screens pretty well (I got my e-ink based reader broken in 2013 when I have slipped on ice and then decided that the next my reader would be 1. shock-proof 2. colorful (both properties were advertised as advantages of Plastic Logic screens, but I don't see any readers based on the technologies developed by them, probably the tech is not as good as it was advertised) 3. won't be a reader at all, but a dumb device with a low power wireless interface and a eink display, which would just talk to a smartphone and render the "picture" (of course in a vector format, likely some binary encoding of postscript subset) generated by it). Python version was needed in as a proxy for creating a KS spec to allow me easier refactoring and adding features (I guess I gonna add exporting into CBOR somewhen) and now lives https://github.com/KOLANICH-tools/inkwave.py (I would rewrite #7, there is a lot of garbage there, I forgot that I have already sent that branch as a PR). Writing a KS spec is my way of learning (and reverse engineering) formats. Rust has stronger security guarantees and built-in integer overflow protection (I have encountered one and fixed it in #10 ), and in fact it was just automatically translated from python with some minor fixes.

It would be nice to know what the "waveforms" are, what each header field means, what is the offset of VCOM field in the header, and how to compute actual waveforms (as one can imagine to see them on an oscilloscope, if one managed to attach probes to a single pixel) from the data parsed from the file.

Also it'd be nice to know if there are any publicly available programs generating these waveform files and how they do that (I guess they are based on some model of a pixel tied to some measurable parameters).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants