Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE]: Move OWL import execution to a separate thread #204

Open
mnamici opened this issue Jun 15, 2022 · 0 comments
Open

[FEATURE]: Move OWL import execution to a separate thread #204

mnamici opened this issue Jun 15, 2022 · 0 comments
Labels
enhancement New feature or request owl-import

Comments

@mnamici
Copy link
Collaborator

mnamici commented Jun 15, 2022

Description

In the ontology importer, move the bulk of the work to a separate thread, so that we can monitor and control it's execution.

Motivation

Currently the import happens entirely on the main thread, and there are a lot of places where the importer has to yield to let events be handled to avoid making the application unresponsive. It would be better to move the importer into a separate threads, so that the execution can happen asynchronously and can be monitored and controlled (e.g. cancelled).

Example Use Cases

Imagine trying to import a large ontology, there is currently no way to cancel the import process, and in some places it could still make the application unresponsive to user inputs between calls to processEvents().

@mnamici mnamici added the enhancement New feature or request label Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request owl-import
Projects
None yet
Development

No branches or pull requests

2 participants