Skip to content

Questions and comments about switching to open source Qiqqa, for different users #284

@dvbphd

Description

@dvbphd

After some efforts to switch from v79s to v82 of Qiqqa, I found some issues and stumbled across questions that may arise for new users and others. Some of these surely reveal my lack of understanding; some may call for documentation or programming changes. New users (starting with open source Qiqqa) will have different questions than older users transitioning from the commercial version -- as far as I can see, the Qiqqa manual doesn't address these users' different needs.

How do new users create libraries with a new copy of open source Qiqqa? As far as I can see (please correct me if this is wrong), we must create libraries at qiqqa.com, rather than locally within the desktop program, if we want more than the guest library. How can older users show open source Qiqqa where to find local copies of their (older commercial) libraries on the harddisk? And how can we avoid the lack of write privilages to our libraries (that I see in questions in Qiqqa community chat)?

When I installed v82 on a new laptop, it could not access my account at qiqqa.com (which still appears to be online). I've kept v79s on my older laptop (where existing libraries are), but haven't upgraded it to open source because I'm not clear how to turn my existing libraries into local (intranet) ones, and I'm afraid of losing them. Help on this issue will be most appreciated.

I did export my main library to dropbox, which eventually finished after seeming to choke on some files; I assume that worked since now dropbox says its not syncing anymore and wants more money for storage.

Apologies for my confusion, and hoping these questions and your answers may help other (new and old) users as well.

Metadata

Metadata

Assignees

No one assigned

    Labels

    📖documentationImprovements or additions to documentation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions