Hello,
Is there a way to switch between the Verbum and Logos interface if you own both products?
Thanks!
If Logos you can type set verbum to yes to switch to the Verbum interface. Some Verbum features require a restart after you have done this.
Is there a way to switch between the Verbum and Logos interface if you own both products? If Logos you can type set verbum to yes to switch to the Verbum interface. Some Verbum features require a restart after you have done this.
And to switch from verbum to Logos interface type in the command box set verbum to no
That was so easy. Thank you both for your help!
For the present this works but in the future, we are told that there will be features built into Verbum that you will need the Verbum App to have all the features.
-Dan
Hello, Is there a way to switch between the Verbum and Logos interface if you own both products? Thanks!
I hate typing, so I just set it as a link in my tool bar. [:D]
For the present this works but in the future, we are told that there will be features built into Verbum that you will need the Verbum App to have all the features. -Dan
Has Logos stated why we will need two libraries? Two programs is fine but two 14 Gig data pools is a bit much!
[So they do not want Verbum to use a data tree with the words Logos4. OK So just change that to Logos and put both libraries in the same bucket]
BTW this doesn't work on the Verbum App, which is in Verbum mode only..
For the present this works but in the future, we are told that there will be features built into Verbum that you will need the Verbum App to have all the features. -Dan Has Logos stated why we will need two libraries? Two programs is fine but two 14 Gig data pools is a bit much! [So they do not want Verbum to use a data tree with the words Logos4. OK So just change that to Logos and put both libraries in the same bucket]
I was able to avoid downloading things again by forcing the newly downloading verbum APP to quit and then deleting the
Initial start up took awhile (15-20 minutes minutes) but saved me a long download time.
Unwise to copy files into resource folder, better to use scan command for resource copying and subsequent indexing.
Wiki has => http://wiki.logos.com/Quick_Installation_onto_Multiple_Macs#Copy_Logos_Resources_to_Mac_OS_X
Keep Smiling [:)]
Initial start up took awhile (15-20 minutes minutes) but saved me a long download time. Unwise to copy files into resource folder, better to use scan command for resource copying and subsequent indexing. Wiki has => http://wiki.logos.com/Quick_Installation_onto_Multiple_Macs#Copy_Logos_Resources_to_Mac_OS_X Keep Smiling
Keep Smiling
In a perfect world that should work fine... but my experience was Verbum starting up with no way to stop the vital download, also that way would end up with resources in both the Logos and the verbum folders.. I had only 17 gb free and one can't put 20+ GB of material into 17GB of space, my SSD is not the Tardis
I had only 17 gb free and one can't put 20+ GB of material into 17GB of space, my SSD is not the Tardis
My backup drive (using OSX "Time Machine") IS named the TARDIS... complete with a TARDIS icon. [:)]
... but my experience was Verbum starting up with no way to stop the vital download
Personally used an offline scan variation to avoid 32 GB download while duplicating Logos library for Verbum use. Fortunately had adequate free SSD space for two complete 5.2 SR3 installations.
Technical challenge for sharing resource files is updating indexes in all Logos and Verbum installations when a resource file is added or updated.
Use at own risk possibility: one installation could be set to automatically download updates while second one has automatically download updates set to no, but has use internet set to yes. When resource(s) are ready to add to first installation; use second installation to scan Resource Manager Downloaded folder to copy resource files into shared Resource folder. After second installation completes indexing, then quit first installation so that indexer can move resource files from Resource Manager Downloaded into shared Resource folder then update indexes. Use at own risk possiblity
Keep Smiling [:D]
Use at own risk possibility:
It is quite risky.
When resource(s) are ready to add to first installation; use second installation to scan Resource Manager Downloaded folder to copy resource files into shared Resource folder.
How do you set up the shared resource folder?
one installation could be set to automatically download updates while second one has automatically download updates set to no, but has use internet set to yes. When resource(s) are ready to add to first installation; use second installation to scan Resource Manager Downloaded folder to copy resource files into shared Resource folder. After second installation completes indexing, then quit first installation so that indexer can move resource files from Resource Manager Downloaded into shared Resource folder then update indexes. Use at own risk possiblity
Using a shared resource folder strikes me as being a really bad idea. I'm sure one or both of the Logos installations will end up getting confused, or worse.
It is possible for two installations to share the entire Documents/Data folders by creating symbolic links, but this will require you to keep both installations running at exactly the same version, but it's still too risky to be worthwhile. And we don't even know whether Verbum/Logos will always be on the same version at the same time.
When resource(s) are ready to add to first installation; use second installation to scan Resource Manager Downloaded folder to copy resource files into shared Resource folder. How do you set up the shared resource folder?
Shared resource folder needs to appear as the Resource Manager Resources folder to each application (perhaps use a junction or symbolic link).
Sharing a resource folder assumes all file content is identical for all applications. If one file has different content for differernt applications, then sharing is problematic. Comparing resource file integrity sums provided reason to post => Logos and Verbum 5.2 SR3 Resource File Differences ?
Found vast majority of files in Logos 5 and Verbum 5.2 SR3 Resource folders have identical content (~32 GB of files are duplicates).
Copying resource files directly to Resources folder bypasses Indexer Discovery so resource(s) do not appear in Library and are not indexed. If forget to use scan command in secondary installation when resource files are in primary installation Downloaded folder, then secondary resource discovery and indexing is an issue.
If sharing resources folder, would avoid inclusion of resources folder in scan path since copying the same file to the same location may have corruption potential (reading and writing the same file using different paths). Seem to remember Logos advice to avoid scan of Resource Manager Resources folder.
A risk when using scan in secondary installation to copy resource file(s) from primary Downloaded folder into shared Resources folder is file being used in an installation so would be prudent to use close all command in all installations before using scan command in secondary installation. A risk for primary installation is indexer file movement from Downloaded folder to Resources folder when the same file already exists in the shared Resources folder.
If entire Documents/Data folders are shared, then opening both applications at the same time is an invitation for disaster.
