Releases: GerHobbelt/qiqqa-open-source
v83.0.7656.6401 (**unpublished**)
This HotFix fixes Known Issue #292 for previous release https://github.com/GerHobbelt/qiqqa-open-source/releases/tag/v83.0.7655.37537.
Remainder of this info is taken from v83.0.7655.37537:
Test release targeting issues jimmejardine#290, jimmejardine#288, jimmejardine#286, jimmejardine#283, jimmejardine#281, jimmejardine#280, jimmejardine#264.
- The obnoxious 'Something has happened' dialogs popping up with the previous "unpublished" release should be gone now.
- A few bugs have been fixed, which hopefully reduce the amount of trouble for folks with larger libraries.
- Improved responsiveness at startup: the status bar now shows better where Qiqqa is at while loading large libraries, while you're waiting for the Windows hourglass to go away. 😉
Known Issues
- Regrettably I haven't been able yet to reduce the internal GC/Memory pressure by a significant factor, which is technology mumbo-jumbo for: users with (very) large libraries or library collections spanning more than about 20K to 50K documents will still suffer from Out Of Memory issues, i.e. Qiqqa crashes.
(That one is a tough nut to crack, given the current 32-bit constraints on Qiqqa 😢 -- work on that one continues...)
Features
(ahem) official support for the "developer overrides config file", documented at this link. This config file is normally absent, but when created (using a text editor), Qiqqa will pick up those configuration settings and disable chunks of its behaviour/feature set as described at the link. When you're done with it and want the standard behaviour back again, simply delete the config file -- or set all config items in there to true (the default for everything as described in the linked document.
83.0.7655.37537 (**unpublished**)
Test release targeting issues jimmejardine#290, jimmejardine#288, jimmejardine#286, jimmejardine#283, jimmejardine#281, jimmejardine#280, jimmejardine#264.
- The obnoxious 'Something has happened' dialogs popping up with the previous "unpublished" release should be gone now.
- A few bugs have been fixed, which hopefully reduce the amount of trouble for folks with larger libraries.
- Improved responsiveness at startup: the status bar now shows better where Qiqqa is at while loading large libraries, while you're waiting for the Windows hourglass to go away. 😉
Known Issues
-
Regrettably I haven't been able yet to reduce the internal GC/Memory pressure by a significant factor, which is technology mumbo-jumbo for: users with (very) large libraries or library collections spanning more than about 20K to 50K documents will still suffer from Out Of Memory issues, i.e. Qiqqa crashes.
(That one is a tough nut to crack, given the current 32-bit constraints on Qiqqa 😢 -- work on that one continues...) -
#292: menu's don't act smoothly; need to jiggle a bit sometimes before the 'focus' blue background shows up. 😭
Features
First release to (ahem) officially support the "developer overrides config file", documented at this link. This config file is normally absent, but when created (using a text editor), Qiqqa will pick up those configuration settings and disable chunks of its behaviour/feature set as described at the link. When you're done with it and want the standard behaviour back again, simply delete the config file -- or set all config items in there to true (the default for everything as described in the linked document.
v83.0.7649.30836 (**unpublished**)
Qiqqa release specifically targetting the issues jimmejardine#288 & jimmejardine#283 :
New
-
option to point Qiqqa at a different base directory (where all libraries are stored) in the startup dialog screen. This change will be persisted: when you quit Qiqqa and restart it later, it will have remembered the directory you pointed it at the last time around. (Technically: path is written to Windows registry)
-
extra logging to help diagnose some particular issues.
-
unrelated: work done the sync dialog: all libraries (except imported 'Qiqqa Bundles' -- which are zipped archives, really) are now fully syncable.
- new is the [browse] button for each library in the sync dialog, where you can pick a new directory (anywhere on any disk your machine can access; doesn't have to be a Google Drive or DropBox or other cloud storage directory, it can also be another local disk or USB bay) to sync to/from.
Known issues
- hand-editing the path is not working in UI; changing the sync path is only doable via the [browse] button next to it.
- while all libraries (including detected Qiqqa Cloud and other ex-v79 Commercial Qiqqa library types) are now re-dubbed "Intranet Libraries", the checkboxes 'autofill' for full and partial ssync are still a little crazy, flagging only very particular libraries instead of being sensible and only flagging the ones which HAVE a target directory.
- you CANNOT reset the sync directory to NOTHING ('(null)') yet. (Largely because hand-editing that path doesn't work in the UI)
Who may benefit from this test release too?
Anyone who wants their libraries to be syncable/sharable in the new 'open source' world of Qiqqa where the old commercial cloud access is not available any more. Note the Known Issues above: usability is not top notch, but at least you now have the chance to do this and use the sync facility, instead of having to wait until the UI has been cleaned up.
What if I don't like this release's behaviour?
Step 1
Please report an issue, be prepared to send me the zipped logfiles (so that I can have a look at what happened under the hood and get a hopefully better idea about what went wrong and thus help us all to get the software to behave properly. Often ZIPping the logfiles still produces a rather large ZIP file, which is too large for email. Please consider sending me a link to Google Drive or similar web storage where I can download your ZIP file when you've sent me a link to the one. Please DO mention Qiqqa and the issie number (plus issue titlee) in your email subject line so my gmail spam filters will consider your mail as probably okay and thus less risk of 'loss in transmission'.
Also be sure to write a comment in your github issue that you have sent me an email for the case where it does end up in the spambox: if I read you have seent me something, I can specifically search for it and dig through both spambox and busy email folders. Sometimes gmail drops qiqqa stuff in the oddest places, despite me filtering on qiqqa.... Weird but it happens. Thanks for your cooperation and I hope you will get a gradually improving experience with the application.
Step 2
Download the installer for another version of Qiqqa (at the time of writing the preferred one would be: https://github.com/GerHobbelt/qiqqa-open-source/releases/tag/v82.0.7568-29227 as also mentioned/explained here: jimmejardine#282
v82.0.7579.33985 (**unpublished**)
A quick preliminary installer produced, mainly for jimmejardine#257 and jimmejardine#264 while the Sync rework needs to be completed so users can finally change the Sync Point for any library.
The most important changes in this one are:
-
several additions towards recognizing and recovering botched/corrupted library databases, both local (
*.library) and at Sync Point (*.s3db) -
SQLite database errors are of critical importance to the functioning of Qiqqa: when an SQLite error occurs, a diagnostic report is appended in the log files. This info includes all available File System information and a quick analysis & test of the accessibility / readability of the DB file.
This should help us diagnose otherwise obscure problems like jimmejardine#257 and jimmejardine#264
-
wholesale refactor of some internals which should improve memory management and reduce bugs, at least in the long term. (commit jimmejardine@0d35bf6)
While a number of bugs have been thwarted this way, I still cannot guarantee that you won't see a few 'null reference' errors being reported with this version.
I haven't had time to kill them all, because removing those error reports also makes it much harder for me to diagnose WHY this erroneous result happens and what the underlying issue is, which SHOULD be fixed. In other words: silencing Qiqqa right now will severely reduce my chances to observe graver, underlying, errors and fix those, as those will become harder to spot and report.
-
various integrity checks have been added and any findings will be reported in the log files.
-
tested against a slew of v76-v79 commercial Qiqqa databases in various states of disrepair: this version will cope better with those than any previous Qiqqa release and 'recover' more data.
IMPORTANT NOTE on the 'recover' words above:
Qiqqa currently 'recovers' such databases in that it attempts to load them as best it can, repair the gaps if finds and has redundant data for, but the original database files ARE NOT rewritten, hence these errors will recur on every application start.
A future Qiqqa release will include an option to bulk-copy PDFs and metadata from such damaged libraries to a fresh one as a form of real recovery process. Ditto for metadata gathering for PDFs which have no metadata attached, but whose metadata MAY be found in a alternate library -- giving you the ability to recover from hard library failures from arbitrary backups.
Status: Unpublished?
- this is an unpublished release as the now visible links and popup menu items for library edit & delete are still non-functional.
- the second reason being that you will currently be informed of damaged libraries, but have not easy means to really recover. See the notes further above.
Qiqqa now knows only about three (or rather: two) types of libraries:
- regular libraries, including the default/guest library
- Intranet libraries -- which are the regular libraries that have a known Sync Point a.k.a. Share Target directory. This can be observed in the Sync Manager dialog.
- Bundle libraries -- which remain read-only as before.
See also the CHANGELOG (and the CHANGELOG_FULL for a complete report.
v82.0.7578.6369 (**unpublished**)
A quick preliminary installer produced, mainly for jimmejardine#257 and jimmejardine#264 while the Sync rework needs to be completed so users can finally change the Sync Point for any library.
The most important changes in this one are:
- finally got rid of the library notions of Commercial Qiqqa: now all libraries are treated equal re Synchronization.
- this is an unpublished release as AutoSync can pop up (harmless) error dialogs at times.
- various fixes for stability at startup
- includes code to report database corruption as it is discovered at startup - all previous versions would silently ignore the error and truncate the database. 😢
- this is an unpublished release as the now visible links and popup menu items for library edit & delete are still non-functional.
Qiqqa now knows only about three (or rather: two) types of libraries:
- regular libraries, including the default/guest library
- Intranet libraries -- which are the regular libraries that have a known Sync Point a.k.a. Share Target directory. This can be observed in the Sync Manager dialog.
- Bundle libraries -- which remain read-only as before.
See also the CHANGELOG (and the CHANGELOG_FULL for a complete report.
v82.0.7568-29227 (i.e. v82pre11)
Update for v82pre10.
- Fixes jimmejardine#253
See also the CHANGELOG (and the CHANGELOG_FULL for a complete report.
What has been fixed / done in Qiqqa already since v82pre10?
click to go to the filtered closed issues list
What has been fixed / done in Qiqqa since the last commercial release (v79)?
v82.0.7555-31312 (i.e. v82pre10)
Update for v82pre9.
Includes work done by @mahfiaz.
- Fixes jimmejardine#201
- Fixes jimmejardine#240
- added GoogleScholar_DoExtraBackgroundQueries configuration option (checkbox, OFF by default to keep the Scholar load to a minimum with regards to jimmejardine#225
- Fix a few crashes, e.g. jimmejardine#220 and jimmejardine#236
- This should fix obscure hangs of Qiqqa (without a window visible)
- Adding Ctrl+W keyboard shortcut in addition to Ctrl+F4, to close currently active tab.
- Crude patch to allow commandline parameter to change the Qiqqa "base directory": useful for independent library sets and testing rigs. Also a beginning for a 'portable / non-admin' Qiqqa install (jimmejardine#124)
See also the CHANGELOG (and the CHANGELOG_FULL for a complete report.
What has been fixed / done in Qiqqa already since v82pre8?
click to go to the filtered closed issues list
What has been fixed / done in Qiqqa since the last commercial release (v79)?
v82.0.7357.40407 (i.e. v82pre9)
Hotfix for v82pre8.
Fixes jimmejardine#180 : WatchFolder functionality not working.
What has been fixed / done in Qiqqa already since v82pre8?
click to go to the filtered closed issues list
What has been fixed / done in Qiqqa since the last commercial release (v79)?
click to go to the closed issues list
A closer look at the actual code changes & commits
When you want to inspect the absolute total and everything that's changed since, say, the previous release, including all commit messages with the option to drill-down to the code changes in the source code itself, then we've got GitHub Compare set up for you at this link.
And here's the GitHub Compare report for all changes since the very beginning.
― Do note that this last one currently overwhelms GitHub so you'll only see the most recent couple of hundred commits in the list there. ―
v82.0.7356.40890 (i.e. v82pre8)
Quick experimental release for testing latest behaviour and fixes.
What has been fixed / done in Qiqqa already since v82pre7?
click to go to the filtered closed issues list
What has been fixed / done in Qiqqa since the last commercial release (v79)?
click to go to the closed issues list
Open issues
click to go to the open issues list for the v82 final release
v82pre7
What's new vs. v82pre7?
- (functionality bug) should fix jimmejardine#142 (to be verified by OP)
- a few more tugs & tweaks.
All other info is as for the previous prerelease: v82pre6.
What has been fixed / done in Qiqqa already since v82pre6?
click to go to the filtered closed issues list
What has been fixed / done in Qiqqa since the last commercial release (v79)?
click to go to the closed issues list
Open issues
click to go to the open issues list for the v82 final release