Page 1 of 1 (9 items)

This post has
8
Replies |
0
Followers

The current 3 level options are a definite improvement. However, "Minimal" isn't nearly minimal enough. Please provide either a "Bare Bones" or "No Resources" install (or both). My preference would be to have a "No Resources" install specifically for those who plan to scan resources or know exactly what they need/want (this option shouldn't include anything in the resources folder).

A "Bare Bones" install would be an alternative and could perhaps have 1 Bible and 1 Commentary (e.g. ESV, BKC).

From the "minimal" install option I waited a LONG time for the app to even open (due to excruciatingly slow internet). Once it opened I quickly opened the library and started scrolling through and canceling downloads (4.3 GBs were downloading which will take a few days!). Here is the list of downloads that I canceled from the "minimal" install (I left a few and I'm sure I missed some):

Rose Then and Now Bible Map Atlas with Biblical Background and Culture

The Treasury of Scripture Knowledge

Edit: I happened to notice that the Help File was not being downloaded with the minimal install which surprised me in light of the list above. I think it probably should be the first resource included...

One of the primary reasons why the Minimal download is so large is that we always download all datasets. This is because there isn't currently a mechanism to give the user control over hiding and downloading dataset resources. Implementing this is unfortunately beyond the scope of the current work, but is something we want to implement in the future.

Thanks for pointing out the missing help file. We've got a case now to make sure that gets added.

One of the primary reasons why the Minimal download is so large is that we always download all datasets.

That's a problem.

After repeatedly purchasing more data, and restarting the download I've finally finished with the "minimal" download. The 6.39 GB of disk space used by the 154 datasets alone is cause enough for concern, but the download experience is horrendous in most places that Bible translators are working. Selective Download has the greatest potential benefit (IMO) in the translation community, but disk space is only ~30% of the issue. Data usage is a bigger concern and the needed workarounds currently make installing Logos a distasteful process and negatively affects the impression of the software.

Please provide an install option that is intended to be used with a scan command (perhaps with an optional link to download any 'mandatory' resources to a user's downloads folder for further distribution).

Please provide an install option that is intended to be used with a scan command (perhaps with an optional link to download any 'mandatory' resources to a user's downloads folder for further distribution).

Reuben, we'll consider this in a future version. As Andrew said, there currently isn't any UI to choose which datasets you want, which makes them all "required," in a sense. We have some mock-ups of what dataset control could look like, but it's not part of the current project.

As Andrew said, there currently isn't any UI to choose which datasets you want, which makes them all "required," in a sense.

That wasn't part of, nor necessary to the request, so the install option could download all datasets (Datasets only), and the user could then select their library resources or use the Scan command. The main idea is to have an alternative to the Recommended or Minimal options which is truly minimal, and avoids indexing a set of library resources that may well be far from optimal (in number as well as pre-selection). The Scan command would come into its own during a re-install, when the user has made all their selections and backed up the Resources folder.

The main idea is to have an alternative to the Recommended or Minimal options which is truly minimal

We've heard your and Reuben's repeated requests for this feature. We completely understand it. We discussed it internally long before we started implementation of Cloud Resources and decided that we were willing to ship without it. It is not, and will not be, part of the first released version of Cloud Resources.

We are considering implementing a more "minimal" bundle in a future version of Logos. When we implement it, it will be announced in the Beta 1 release notes.

We've heard your and Reuben's repeated requests for this feature. We completely understand it. We discussed it internally long before we started implementation of Cloud Resources and decided that we were willing to ship without it.