Re: Bibledit Lite (was: Re: [be] Packages (bibledit-web and build time mysql server checking))

[Teus Benschop]

Hi Dan,

I was glad to read about Bibledit-Lite. You are fixing bugs and making
that Bibledit-Lite reaches a larger audience. It is good to hear all
these things. Do the translators like using Bibledit-Lite in your
organisation? 

I am interested in the patch for config.xml.cpp, and any other patches
that fix corruptions or leaks. Good that you made it use less memory.
Thanks for offering the fix.

Quite a number of improvements you are planning. I am sure all of these
will result in a better bibledit-lite.exe.

The mystery you describe, about the screen jumping to the left,
Bibledit-Gtk had this same thing, but it no longer occurs now. Perhaps
the solution will apply to your situation as well. If I recall well,
there was something with the scrolledwindow in editor.cpp, its policy,
and how it interacts with the textview. I notice it now uses a viewport
as well in editor.cpp. I'd think that the problem lies somewhere there.

Teus


On Mon, 2011-03-21 at 21:35 -0400, Dan Dennison wrote:
> On Tue, Dec 28, 2010 at 5:36 PM, Jonathan Marsden
> <address@hidden> wrote:
>         I started on this today.  I soon encountered something I am
>         not sure how
>         to handle -- bibledit-web seems to expect a working and
>         configured mysql
>         server at *build* time.
> 
> I actually second this view. The buildbot at buildbot.biblesint.org
> used to work from Bibledit HEAD, but stopped working once a running
> mysqld was required at build time. We decided it would be easier to
> fork into Bibledit Lite than to try and track a bunch of changes for
> what is now server-code, when all we want is the GTK+ client.
> 
> That said, we do have Bibledit Lite for Windows downloadable at
> http://buildbot.biblesint.org. It's not quite where we want it,
> notably it still needs a better answer for USB repositories, but it's
> working a lot better than Bibledit for Windows ever has, and a number
> of heap corruptions and other more-Windows specific issues have been
> address. Bibledit Lite is a fork of Bibledit from just before the
> detached windows patch went in, so it has the old paned/tabbed UI.
> Bibledit Lite also uses Git instead of snapshots.
> 
> Teus, if you want to patch in my changes for config.xml.cpp feel free.
> There were several failure-to-xmlFree cases in there. I've noted these
> problems are still in 4.2. Once those were fixed, the code seemed to
> use a lot less RAM. We've seen running Bibledits under 25MB RAM.
> Bibledit on Windows used to use > 50MB RAM. We also fixed the keyterms
> import causes crash, which happened because the keytermsgui object
> wasn't initialized. There were a bunch of other crash fixes as well.
> 
> Our next area of code to fix is screen.cpp, to solve the random
> crashes that happen when the GTK+ text buffer changes while we're
> trying to scroll to a reference, as well as a few edge cases such as
> what happens when you scroll to verse 0 or chapter 0.
> 
> Looking ahead, we plan to kill the verse tracker in its polling form
> and move it to event-driven. This should reduce the background CPU
> usage of Bibledit to almost zero. Further out is checkpointing of Git
> state on every change to the queue, rather than at exit. This way a
> crash will not cause the pending Git tasks to be lost, rather to be
> pending it must write out gitjobs.xml.
> 
> The big mysteries we're trying to solve right now is the screen
> jumping to the left on restore/maximize, and various screen corruption
> bugs that happen when window elements go out of bounds.
> 
> dan :)