Thanks! I had it earlier like that (no parameter to c'tor), also on
Windows. But at least on Windows it did not seem to work.
I'll play with it once more tomorrow.
One more question: How are Linux frontends typically installing modules
in /usr/share/sword? Doesn't that require root permissions? Unless the
directory is set to 777 or something similar.
If you want to reset the Ezra Project database, you should delete the
file ~/.config/ezra-project/ezra.sqlite and also the Settings file
(remembers the last opened translations) ~/.config/ezra-project/Settings.
Best regards,
Tobias
Am 22/06/2019 um 22:50 schrieb Troy A. Griffitts:
Yeah, so, if you don't pass a path to the SWMgr c-tor, it will do
everything automatically. Since you passed a path, it assumes you know
what you want and doesn't do discovery of paths. Try an empty c-tor.
Enjoy Belgium!
Troy
On June 22, 2019 1:45:09 PM MST, Tobias Klein <[email protected]>
wrote:
Hi Troy,
Thanks for trying the new version! :)
That previously installed modules are still available is actually
not a bug. I'm importing the module texts into the sqlite database
of Ezra Project. I know that this may not be necessary and I could
read text directly from the modules during runtime (like any other
Sword frontend). But it's based on how I designed Ezra Project
initially before I integrated it with Sword. Initially I was
working off of a database without Sword. Last year I ported that
software (it was web-based before) into an Electron desktop
application. I kept the database interface and integrated Sword in
a way where I import the text into the database when installing
any module. When removing a module via Ezra, the module is also
removed from the database again. Currently I'm still relying on
the database concept also due to how verses are linked with tags.
So the other thing you observed is that modules installed to
/usr/share/sword are not appearing in the frontend, huh?
Looks like I should have tested that a bit more. On Windows I did
and there it works.
Let me ask you a question about SWMgr here. Is it supposed to
automatically augment the "global module path" to the standard
user module path?
On WIndows I could only make SWMgr aware of both the user path and
the global path by explicitly calling SWMgr::augmentModules().
It looks like this at the moment:
this->_mgr = new
SWMgr(this->_fileSystemHelper.getUserSwordDir().c_str());
#ifdef _WIN32
this->_mgr->augmentModules(this->_fileSystemHelper.getSystemSwordDir().c_str());
#endif
For some reason I thought that on Linux the module path is
extended automatically. Could you shed some light on that? Thanks!
Greetings from Antwerp, Belgium! Earlier my wife and I walked by a
restaurant called "Troy" and I was remembering you.
Best regards,
Tobias
Am 22/06/2019 um 21:57 schrieb Troy A. Griffitts:
Hi Tobias,
So, I've had a chance to try 0.8.1. I hope this feedback is useful:
Wanting to test the SWORD configuration improvements in the new
build, I removed my ~/.sword folder. I have 5 or so modules
installed machine-wide under /usr/share/sword so I was hoping
those would be seen. Just to be sure SWORD is configured
correctly on my box, in my source folder I go down into the
examples at: ~/src/sword/examples/cmdline and run ./lookup yoyo yoyo
[scribe@localhost cmdline]$ ./lookup yoyo yoyo
Could not find module [yoyo]. Available modules:
[ESV2011] - English Standard Version with Strongs numbers.
[KJV] - King James Version (1769) with Strongs Numbers and
Morphology
[SahidicBible] - Sahidic Bible - Askeland / Schulz
[StrongsGreek] - Strong's Greek Bible Dictionary
[WHNU] - Westcott and Hort with NA27/UBS4 variants
On my previous test, using 0.8.0, I installed KJVA and WLC which
went into ~/.sword/ which is fine but wanting to test more
cleanly, I removed the ~/.sword folder completely.
OK, installed latest ezra package for F29 x86_64.
It created ~/.sword and an empty mods.d and installMgr folder
underneath. All fine. No sword.conf. Good.
Launched ezra-project.
To my surprise, I see my two previous modules available in the
dropdown AND the KJVA is showing data!
So, I could image a bug if you maybe cached available modules
someplace and didn't re-read SWMgr between app restarts to see
what modules were available, but I can't imagine how you can
still lookup data for both of my previously installed modules
since I have removed ~/.sword/ where they were installed and
these modules are not available in my system-wide
/usr/share/sword library.
:)
Hope this initial feedback is a little useful,
Troy
On 6/21/19 1:06 AM, Tobias Klein wrote:
Hi all,
Ezra Project 0.8.1 has been released. This is a bugfix release.
Ezra Project is a topical bible study tool.
https://github.com/tobias-klein/ezra-project/releases/tag/0.8.1
Noteworthy improvements are:
* Support for all languages of ISO-639-1/2/3. This enables the
usage of all the available Sword modules.
* Added sync functionality for Sword modules that have been
installed by other programs. Those modules are now also
available in Ezra Project and synced on start-up.
* Do not use custom sword.conf anymore.
* Static Sword library now included. This means that Ezra
Project will run on more systems, because there is no
specific dependency on Sword packages anymore.
Downloads are available for:
* Ubuntu 18.04 + 19.04
* CentOS 7
* Fedora 29
* Windows (tested on Windows 10)
Feedback is appreciated!
Best regards,
Tobias
_______________________________________________
sword-devel mailing list:[email protected]
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list:[email protected]
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
sword-devel mailing list: [email protected]
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
