emsearcy

About

Username
emsearcy
Joined
Visits
0
Last Active
Roles
Member

Comments

  • Oops, that's what happens when I don't preview first: that was supposed to say emsearcy (at) osuosl (dot) org. -Eric
  • That's odd, the same .olp file should work from multiple places ... the only other `external' requirement outside the database file are additional background images; if you move over just the .olp file you can have references to images that don't ex…
  • If it doesn't make it out in time, here's a solution for tomorrow (or today, depending on your timezone). Put almost-blank lines that only have a space character in them ( ' ' ). Because it isn't strictly a newline, it will keep these blank lines …
  • The command-line tool is sqlite (sqlite.exe on Windows). I wasn't meaning to make a reference to Linux, you can use the command line tool from the Windows command prompt too. You can download sqlite.exe for win32 from the SQLite download page, und…
  • Hi gruntus- Yes, this is a known problem. I'd watch that post for feedback on the problem. -- Eric Searcy OSU Open Source Lab
  • The database is sqlite, a database optimized for single-file DBs (sqlite.org). Are you familiar with databases? (queries, inserts, etc?) There are several available management interfaces for sqlite, though I stick to the command-line one myself, s…
  • How do you suppose would be a good way to allow users to configure this easily? For instance, a site-wide "max. font size" setting in points, or per-slide font settings? My personal request here would be that the text still auto-enlarges…
  • mamin- To answer your last question, the database importer is only set up up to import an OpenLP 0.99x database (the .olp binary database itself--it does not handle text dumps). Creating a general purpose import utility that could handle .csv as w…
  • Nancy, et al: The above issue with the splash screen appearing to hang is not caused by a bug in the ImporterApp, but I believe rather a problem in OpenLP. See splash screen slow-down. -Eric
  • Looking into it. I'll try to keep discussion on the ImporterApp in the bug reports thread.
  • Not sure if everyone saw this, but there is now an Importer App availiable for converting pre-beta2 files to the new format, as well as merging databases together. Get it at the SF project downloads page, under `tools'. http://sourceforge.net/proj…
  • Just for the record for this thread, beta1 used the same DB schema as .994, and is not compatible with >=beta2. Please use the Importer tool, linked to on the downloads page.
  • Nancy, et al: The above issue (the ImporterApp issue, not the .994 song loss issue) is not caused by a bug in the ImporterApp, but I believe rather a problem in OpenLP. See http://www.openlp.org/en/?q=node/62 -Eric
  • Looking into it. The converter was originally tested on both my church's .994 database and on the stock .994 database, but as I haven't had the opportunity to test it against many more database, bugs may exist.
  • If you want an *open* standard format, I would suggest OSIS [1]. That way we could link in to Crosswire's large module database of public-domain (and many-lingual!) bibles [2]. After all, this is an open-source project, and it's great to bring foc…