A homebrewed program for viewing image archives (cbz, cbr,...)

[rkomar]

Oh wait. Looking more closely at the initial request, I see that it was for the cover to be shown when the device is sleeping. I don't think I can do that. My hack only causes the cover to be shown when the device is powered off, because that can be controlled via the System Settings. I don't see any setting for sleep image in my settings.

[trewelu]

Another feature request (it's complex and taking time, so no expectation here):
Is it possible to have thumbnail views (2x2, 3x3, or 4x4) to make browsing to/looking for specific scene/page easier.

Slightly unrelated:
I tried to rename an epub file to cbz and the library listing still doesn't use the cover image as thumbnail. So I guess there is no way of having library thumbnail using file named .cbz , even if the actual file is actually an epub.

[rkomar]

Originally Posted by trewelu

Another feature request (it's complex and taking time, so no expectation here):
Is it possible to have thumbnail views (2x2, 3x3, or 4x4) to make browsing to/looking for specific scene/page easier.

Slightly unrelated:
I tried to rename an epub file to cbz and the library listing still doesn't use the cover image as thumbnail. So I guess there is no way of having library thumbnail using file named .cbz , even if the actual file is actually an epub.

The thumbnail feature sounds like a lot of work, and it would probably be pretty slow on these devices. So, I doubt I would ever get around to coding it up. Have you tried using the Contents menu to choose pages? It shows the filenames and directory structure, and those are sometimes useful at least for selecting chapters.

I don't think the library software knows how to handle cbz/cbr files in terms of cover images. So, changing the file extension to cbz probably wouldn't make it more likely for a cover image to be generated. Does your epub have a cover defined in it? It should have worked if that was the case.

[trewelu]

Originally Posted by rkomar

I don't see how to control the light level from the API they provide, so I don't think it would be simple to do. I think you can control it via the status bar, which you can bring up in the program, so I think I'll leave it at that. I believe that either coolreader or koreader can control the light level, so I might look in there later for some clues, but I don't think it will be soon. No time.

I take a quicklook on the coolreader source and the pocketbook sdk source. Look like there is an api for that.

https://github.com/pocketbook-free/S...rontlightState

https://github.com/pocketbook-free/S...tate&type=Code

That's probably the best I can do to help.

PS: how to install the custom sdk you mentioned on your page? I would like to play around a bit if I have time. Though I'm not really good with C++

[brucelee]

If I remember correctly this works only for FW5

inkinternal.h (SDK_481)

PHP Code:

/*
* Returns frontlight state (0-100 - brightness, negative value if off)
* returns INT_MIN if can't read or not supported
*/
int GetFrontlightState(void);

/*
* Sets frontlight state (0-100 - brightness, negative value if off)
*/
void SetFrontlightState(int flstate);

/*
* Sets frontlight state (0-100 - brightness, negative value if off)
* temporary for use when about to keylock and this value should not be stored
*/
void SetFrontlightStateEx(int flstate, int temporary);

/*
* If supported open special application
*/
void OpenFrontLightConfig();

/*
On/off FrontLight
*/
void SwitchFrontlightState(); 


CR3 implementation

PHP Code:

virtual bool onClientTouch(lvPoint &pt, CRGUITouchEventType evType)
{
    // TOUCH DOWN
    if( evType == CRTOUCH_DOWN ) {
        finger1.start.x = pt.x;
        finger1.start.y = pt.y;

        touchPointing = 1;
    }

    // RELEASE / LONG TAP
    else if (CRTOUCH_UP == evType || CRTOUCH_DOWN_LONG == evType) {...}

    // MULTI
    #if defined(POCKETBOOK_PRO) && !defined(POCKETBOOK_PRO_PRO2)
    else if (CRTOUCH_MULTI_TOUCH == evType && touchPointing && max(pt.x,pt.y) > 2) {...}
    #endif

    // DRAG
    #ifdef POCKETBOOK_PRO_FW5
    else if( evType == CRTOUCH_MOVE && touchPointing == 1 ) {

        // VERTICAL
        if( abs(finger1.start.x-pt.x) < abs(finger1.start.y-pt.y) ) {
            int front_light_swipes_mode = CRPocketBookDocView::instance->getProps()->getIntDef(PROP_CTRL_FRONT_LIGHT_SWIPES, 2);

            if( front_light_swipes_mode == 1 ) {
                setFrontLightValue(
                    /* bottom to top */
                    100 -
                    /* value (%) */
                    (
                        100 *
                        (
                            /* touch point (PX) */
                            pt.y -
                            /* offset (PX) used to center the region */
                            ScreenHeight() * FRONTLIGHT_SWIPE_USABLE_SCREEN_HEIGHT / 2
                        )
                        /
                        /* usable screen (PX) */
                        ( ScreenHeight() * FRONTLIGHT_SWIPE_USABLE_SCREEN_HEIGHT )
                    )
                    );
                ignoreNextTouchRelease = true;
            }
            else if( front_light_swipes_mode == 2 ) {
                setFrontLightValue(
                    getFrontLightValue() -
                    /* value (%) */
                    (
                        100 *
                        (
                            /* step height (PX) */
                            pt.y - finger1.start.y
                        )
                        /
                        /* usable screen (PX) */
                        ( ScreenHeight() * FRONTLIGHT_SWIPE_USABLE_SCREEN_HEIGHT )
                    )
                    );
                finger1.start.y = pt.y;
                ignoreNextTouchRelease = true;
            }
            return true;
        }

        // HORIZONTALY
        else {

        }

    }
    #endif

    return false;
} 


[marian42]

Originally Posted by rkomar

Oh wait. Looking more closely at the initial request, I see that it was for the cover to be shown when the device is sleeping. I don't think I can do that. My hack only causes the cover to be shown when the device is powered off, because that can be controlled via the System Settings. I don't see any setting for sleep image in my settings.

Hi rkomar,

sorry for my misleading terminology. To be honest I was not sure how to describe what I wanted and I see that I did not use correct definition / terminology.

But generally I was talking about power-off image. So if the work-around for power-off image could be implemented without any big complications, it would be very nice feature.

[rkomar]

Originally Posted by marian42

Hi rkomar,

sorry for my misleading terminology. To be honest I was not sure how to describe what I wanted and I see that I did not use correct definition / terminology.

But generally I was talking about power-off image. So if the work-around for power-off image could be implemented without any big complications, it would be very nice feature.

In that case, you are in luck. The feature is already implemented, and will be part of the next release. I'm still adding the touch navigation lock. There were a couple of other features suggested recently that I was going to look at first, as well. After that, we'll need to wait for the volunteer translators to get their work done. So, it will probably be at least another week before the next release.

[rkomar]

Thanks for the info, @brucelee. Unfortunately, pbimageviewer covers many firmware versions, and including code for specific versions is a pain. Another problem is that every gesture I can easily code is already being used for something else in the program. I would need to think up another way of setting the light level that is still less work than pulling up the status bar and launching the light controller from there. Maybe I'll just try launching the light controller on tapping the top-middle zone. That way, I won't have to implement any controls for it myself, nor add any menu items that need to be translated.

[trewelu]

The one I read typically have 16-20 pages a chapter, and 9-11 chapter per volume. Assuming I use a volume zip with approximately 200 pages, will it cause any performance issue? How about per 10 books (2000 images a zip)?

[rkomar]

Originally Posted by trewelu

The one I read typically have 16-20 pages a chapter, and 9-11 chapter per volume. Assuming I use a volume zip with approximately 200 pages, will it cause any performance issue? How about per 10 books (2000 images a zip)?

200 pages is okay, but 2000 might be slow, depending on the type of archive. cbz/zip might still be fast enough because it is indexed, but cbr/rar will probably be somewhat slower. The fastest is cbt/tar (no compression) using the 7z.so library. Using zip or rar without compression would probably speed things up, as well. cb7/7zip would be dreadfully slow on big files.

Large numbers of images would make the Table of Contents very large, as well, and harder to navigate in.

The best advice is to just try it and see.

[rkomar]

Originally Posted by trewelu

PS: how to install the custom sdk you mentioned on your page? I would like to play around a bit if I have time. Though I'm not really good with C++

Now that I think about it, I don't think you can. The last time Sergey Vlasov released a version of his SDK was about four or five years ago. It was only capable of building for firmware version 4 and earlier. PocketBook has released an SDK for firmware version 5, but Sergey no longer does the conversion. Last time, I did it myself, but it was a lot of work, and it's too big for me to distribute from my ftp site. It would probably be best to create a cmake file for the project that would work with the latest SDK. However, I'm not comfortable with cmake even though I am with make.

If you're comfortable with cmake, perhaps you can create the files yourself. If so, I would be willing to include them with the source code, so that it would be easier for others to build it. I'm also willing to give you whatever help I can for that. PM me if you are interested.

[marian42]

Originally Posted by rkomar

In that case, you are in luck. The feature is already implemented, and will be part of the next release. I'm still adding the touch navigation lock. There were a couple of other features suggested recently that I was going to look at first, as well. After that, we'll need to wait for the volunteer translators to get their work done. So, it will probably be at least another week before the next release.

Unbelievable! Thank you very much for your work.

[brucelee]

Originally Posted by rkomar

If you're comfortable with cmake, perhaps you can create the files yourself. If so, I would be willing to include them with the source code, so that it would be easier for others to build it. I'm also willing to give you whatever help I can for that. PM me if you are interested.

If you're willing to wait until tomorrow I'll give you the source working with this SDK.

I've already built it for FW5 but I'll have to commit the SDK changes and make the build script work with all 4 build types just like CR3.

[rkomar]

Originally Posted by brucelee

If you're willing to wait until tomorrow I'll give you the source working with this SDK.

I've already built it for FW5 but I'll have to commit the SDK changes and make the build script work with all 4 build types just like CR3.

That sounds good. Keep in mind that you need some external libraries and header files, which I include here http://www3.telus.net/rkomar/pbimage...rebuilt.tar.gz.

[brucelee]

Originally Posted by rkomar

That sounds good. Keep in mind that you need some external libraries and header files, which I include here http://www3.telus.net/rkomar/pbimage...rebuilt.tar.gz.

That's why I have to commit the SDK changes. I've included them there. Unfortunately what I've done is in my work PC so I won't be able to do anything until tomorrow. (I mean I could but I'm too lazy to do the same thing again )