I'm ending up adding a new option to set/calibrate the swiping.
I'm still trying to decide which solution:

- mouse-style: choose the amount of time and space to detect a swipe gesture (in a prompt), then try it on a popup box. Komic will let you know if you just clicked or swiped. You can then save the setting or edit it again (try&error method)

-calibration-style: click 3(?) times on a popup box. Komic will calculate the average time and space and then apply a tolerance (the user can set it in percentage). This setting is used to detect a click; above those amounts, you're swiping.

Anyway, I want to rework the control in the readingJS.js to:
- use a single if to detect swipe/click: the if will be placed in the trackMouse(). In the mUp() I will check a boolean flag. I.E: if the first control starts a swipe action, then in the mUp I will refresh the page; on the contrary, I will trigger the singleclick
- use settings provided by the option and stored in the localstorage

Just some dinner thoughts...
I **could**:
- pack all the option in only one localStorage entry
- pack all the bookmarks for one comic in a more decent way inside the localStorage and provide a way to bind a description to a bookmark (when saving a bookmark, if the user provide a description, this could be displayed when jumping to)
- add some comic-dependent options

The last thing is, probably, the most interesting. It means the user can set some options and Komic will always use those option when opening the same comic.
Those options could be:
- orientation
- brightness and contrast
- refreshrate
- scroll amount (if in orientation = landscape)
- background color
- imageration ON or OFF

As I just started working, I'm the last in the organization chart...so no holiday for me!
But, as I'm a bit lazy, I could use the "Developer's Summer Holiday from Kindle Hacking" excuse anyhow!!
So, I'm on a "half" developer's summer holiday!

As I just started working, I'm the last in the organization chart...so no holiday for me!
But, as I'm a bit lazy, I could use the "Developer's Summer Holiday from Kindle Hacking" excuse anyhow!!
So, I'm on a "half" developer's summer holiday!

Congratulations on the job.

Yeah, bottom of the org chart - you end up wading through all the things that nobody else was interested in doing.
The only good thought: It (being at the bottom) will not be forever.

@NiLuJe: I added it to Komic but I didn't test it yet. If they improved the speed, this is going to be a huge plus!!!
Thanks a lot for your build and for sharing with me!

Calibration option is working and seems to be pretty solid.
I decided to make the user touch 3 times a popup box following some instructions.
Every touch stores the delay in time and space between mousedown & mouseup then Komic calculates the average.
The swipe gesture is then activated ONLY if the user is moving his finger on the screen for more than the time/space stored before (plus a 10% tolerance). Otherwise, the gesture is interpreted as a touch.
I tried it last evening and it seems to work fine.
Moreover, the user can re-calibrate the gesture detection engine to suit its needings.

I just need to play around with CSS (I hate it!) to make it nicer.

NEXT: JSON for bookmarks and options (to be honest, I wanted to move options in a separate db but I always get a security error: it seems I can't create db on client-side)
NEXT: jqgrid for bookmarks and deletions pages

V2.3 will be release in the near (hope so) future and, ATM, users will have to readd manually bookmarks and options as the JSON-thing is going to be a huge change.

PaperWhite support will still be last in my list as I can't really assure you anything about the compatibility.

@silver18: Well, there were some upstream changes (you might want to check if some options changed behavior), sure, but mostly I just configured the build differently, it's now a bit less versatile, but much more Kindle friendly . [Switched from quantum-depth 16 to 8, which means we lose precision if we ever have to process 16bit-depth PNG files, but that's not a common sight, at least for what we're doing, and used the iPhone codepath for the dithering algorithm. Long story short, for the rescale+dither workflow, I went from 167MB of total allocs w/ a peak at 64MB to 30MB of total allocs w/ a peak at 4MB, and it's probably around 10-20% faster.]

Here are two screenshots.
The first one shows the calibration option (last one).
The last one shows the calibration box at the end of the process.
In the upper part is says "Calibration done!" while the last row shows average values.

As I'm trying to make Komic faster and lighter, could you please answer this superfast poll?
Those are the features I don't use so often (read never), so they could be expendables...
I just would like to know what do you think!
Thanks!

As I'm trying to make Komic faster and lighter, could you please answer this superfast poll?
Those are the features I don't use so often (read never), so they could be expendables...
I just would like to know what do you think!
Thanks!

Thanks for your votes!

Ok, so automatic page turner is on its way to the bin!
It's a shame that zoom buttons & scroll arrows are being used by someone...
I'll try to provide the pinch-to-zoom to replace them (this means using a single landing page + content window).

And now, for something completely different (), I'm going to refactoring all the code to help the garbage collection...

Some news....
I completely revisited bookmarks and options.
Thanks to JSON, now options uses only one entry in localStorage.

1) You can enter a bookmark description (if you want) when saving one.
If you save a bookmark using autosave or quick save, then it skips this step adding a default description ("Autosave" or "Quick save").

2) Bookmark menu is dynamic:

- Add bookmark is grayed out if the page already has a bookmark
- Jump to bookmark is grayed out if the comic doesn't have any bookmark
- Remove bookmark is grayed out if the page isn't bookmarked

All the code has been reworked to improve the performance.
Everything will be minified in the release (src will be non-minified!)

Next: rework the deletions, add pinch-to-zoom, revisit shell scripts.

In the meanwhile: does anybody know a JSON parser to be used in shell scripting?
Thanks!!