maemo.org - Talk - New FBReader build in Extras-Devel

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - New FBReader build in Extras-Devel (https://talk.maemo.org/showthread.php?t=36857)

Re: New FBReader build in Extras-Devel

Thanks fms, properly updated now, with Maemo tab and nice new icon. Tapscrolling works, but only with fingernail. Don't know if it's just me, but it feels more responsive than the last build. Ticking Scroll on Finger Tap Only still disables all tapscrolling.

Re: New FBReader build in Extras-Devel

Still new on this.

Does not work with me.
These are the steps to uninstall fbreader but mine does not work yet
1. install rootsh
2. go to terminal
3. sudo gainroot
4. dpkg --purge fbreader
5. dpkg --purge libzlibrary
6. reinstall fbreader (found the latest version .7)
7. when opening the fbreader after that
my last book is automaically open (the config file definitely is still there).

finger tap not working.

Question:
How can I remove the config file ?

is there any steps that I missed ?

Re: New FBReader build in Extras-Devel

In xterm: rm -rf /home/user/.FBReader

Re: New FBReader build in Extras-Devel

For those who have problems:

1. install rootsh
2. go to terminal
3. sudo gainroot
4. dpkg --purge fbreader
5. dpkg --purge libzlibrary
6. rm -r ~/.FBReader
7. reinstall fbreader (found the latest version .7)

Finger tap should works. (It works better with stylus).

You need to press it "HARD" and hold it for 1 second at the bottom right. (for a test).

And you will see the tap now works.

After that, you can play around and see how "hard" you need to press the screen to make it works :).

great application, Look forward for a new update :).

Re: New FBReader build in Extras-Devel

Looks like I will have to put zlibrary into user/libs again. This mess cannot be allowed to continue.

Re: New FBReader build in Extras-Devel

Quote:

Originally Posted by fms (Post 431492)

I had to disable qwerty's fix to the overlay widget, as there are issues with it.

This appears to be a problem [the solution] on Maemo 5. (It has been discussed on -developers twice.)

Conny and I decided to workaround it by disabling/enabling the widget depending on if the HildonWindow (or any widget derived from it, like HildonStackableWindow) is on the screen.

I don't have the time now to do a diff, but the following in he-fullscreen-button.c should do it:

Code:

static void

fullscreen_button_on_is_topmost_changed (GObject *object G_GNUC_UNUSED,

                                                 GParamSpec *property G_GNUC_UNUSED,

                                                 gpointer data)

{

        HeFullscreenButton *self = HE_FULLSCREEN_BUTTON (data);



        if (hildon_window_get_is_topmost (HILDON_WINDOW(self->parent_window))) {

                if (gdk_window_get_state (GTK_WIDGET (self->parent_window)->window) & GDK_WINDOW_STATE_FULLSCREEN) {

                        fullscreen_button_enable (self);

                }

        }

        else {

                fullscreen_button_disable (self);

        }

}



[Before return self in he_fullscreen_button_new()]

    if (HILDON_IS_WINDOW(parent_window)) {

        g_signal_connect (parent_window, "notify::is-topmost",

            G_CALLBACK(fullscreen_button_on_is_topmost_changed), self);

    }



[After g_signal_handlers_disconnect_by_func (self->parent_window, fullscreen_button_destroy, self);]

g_signal_handlers_disconnect_by_func (self->parent_window, fullscreen_button_on_is_topmost_changed, self);

Oh, fullscreen_button_disable/fullscreen_button_enable are not called fullscreen_button_disable/fullscreen_button_enable in the castrated he-fullscreen-button.c for FBReader...

If you need to see the full code, check out the hildon-extras SVN project; I just committed rev. 13.

Re: New FBReader build in Extras-Devel

Quote:

Originally Posted by fms (Post 432265)

Looks like I will have to put zlibrary into user/libs again. This mess cannot be allowed to continue.

Which is exactly why you shouldn't but it back in user/*. :)

It's like a virus, currently some users are infected but that number is relatively small. It needs to be stopped now before users beyond Extras-devel get exposed.

Besides, it can't go into Extras with a lib in user/*.

Re: New FBReader build in Extras-Devel

Quote:

Originally Posted by GeneralAntilles (Post 432296)

Which is exactly why you shouldn't but it back in user/*. It's like a virus, currently some users are infected but that number is relatively small. It needs to be stopped now before users beyond Extras-devel get exposed. Besides, it can't go into Extras with a lib in user/*.

Ok, here is what we have determined so far:

1. It cannot go to user/libs because it is "like a virus".
2. It cannot go into libs because then the users cannot update the master package properly.
3. Fixing #1 requires some community gatekeepers to stop considering it a virus, which is not going to happen because it is "like a virus".
4. Fixing #2 requires changes to HAM, which are not going to happen because Nokia controls HAM distribution (even although its source may be open).

So, based on the stuff above, what is the solution for promoting library dependencies into Extras and making them upgrade through HAM?

Re: New FBReader build in Extras-Devel

Quote:

Originally Posted by qwerty12 (Post 432284)

This appears to be a problem [the solution] on Maemo 5. (It has been discussed on -developers twice.) Conny and I decided to workaround it by disabling/enabling the widget depending on if the HildonWindow (or any widget derived from it, like HildonStackableWindow) is on the screen. I don't have the time now to do a diff, but the following in he-fullscreen-button.c should do it:

Thanks, this should be enough for me. Integrating.

Re: New FBReader build in Extras-Devel

My understanding is that the only people affected by #2 are those who currently have it installed in user/libs.